WilliamLam.com

Google Chat space notification for failed vCenter Server Appliance (VCSA) backups using VEBA

by // Leave a Comment

It is always good idea to verify that your vCenter Server Appliance (VCSA) backups are occurring and if there are any failures, you are notified about them immediately!

As alluded to at the end of that blog post, you can easily build event-driven automation using the popular VMware Event Broker Appliance (VEBA) solution, triggering notifications based on several types of VCSA backup events:

  • com.vmware.applmgmt.backup.job.failed.event
  • com.vmware.applmgmt.backup.job.finished.event
  • com.vmware.applmgmt.backup.job.start.event

I recently built a PowerShell function that would send a notification to a Google Chat space by enabling their incoming webhook integration as you can seen from the screenshot below:


While the message customization is not as extensive as using Slack (e.g. supporting advanced layouts and emoji), it does get the job done and you will know immediately when a backup has failed or when it has started or has completed.

Note: For existing VEBA users (pre-v0.8 release), the function.yaml needs to be updated to trigger off of the subject keyword rather than the type, which is due to replacing the event router with Tanzu Sources for vSphere. You also need to ensure the prefix of "com.vmware.vsphere" is removed along with trailing "v0" as this is the next syntax for vCenter Events once VEBA v0.8 is released.

spec:
  broker: default
  filter:
    attributes:
      subject: com.vmware.applmgmt.backup.job.failed.event

Quick Tip - Verifying vCenter Server Appliance (VCSA) Backup Status

by // 13 Comments

I recently found out that my vCenter Server Appliance (VCSA) scheduled backups had been failing for some time but I was not aware. While there is a default vCenter Server alarm for failed VCSA backups, however it is only visible when you have selected the vCenter Server inventory object in left hand navigation, which is not a typical item that I select as shown in the screenshot below.


Furthermore, I was actually logged into the VCSA's VMware Appliance Management Interface (VAMI) not too long ago while updating to a newer patch release and I had checked to see if backups were successful, which I thought they were when looking at the "Status" column.


It was not until I took a closer look, did I realize that the schedule backup activity log is ordered from oldest to newest, meaning what I saw was a backup that has happend a long time ago and not necessary the latest backup attempt. I found this to be a really strange UX since as you would need to page to very end to check whether the latest backups were succssful or not.

Note: I have already filed an internal bug to ask for the VCSA schedule backup activity to be ordered from newest to oldest, so users can quickly see if the latest backups are successful or not.

[Read more...]

How to deploy the vCenter Server Appliance (VCSA) 8.0 to VMware Fusion or Workstation?

by // 55 Comments

VMware Fusion and Workstation continues to be another popular way for customers to run a VMware Homelab while leveraging a users existing desktop. In the early days of vSphere 6.5, the method to deploy the vCenter Server Appliance (VCSA) to Fusion/Workstation was less than ideal with a lot of manual steps. In 2017, the Fusion/Workstation team introduced native OVF support and that made deploying the VCSA much simpler, especially with the VCSA two stage installer.

Even though this is not an officially supported method from VMware for deploying the VCSA, the process has not changed for the last several releases and it just works which was great for our users. With vSphere 8, it looks like there has been a change to the VCSA installer that causes a failure during the Stage 2 configuration.


I was made aware of this issue from a colleague who was looking to setup a vSphere 8 environment using VMware Workstation.

Taking a look at the log file, he noticed the error was regarding the upgrade.import.directory OVF property not being set, which seems to be causing the issue.

# cat /var/log/firstboot/vlcm_firstboot.py_9117_stderr.log
Traceback (most recent call last):
  File "/usr/lib/vmware-vlcm/firstboot/vlcm_firstboot.py", line 167, in <module>
    main()
  File "/usr/lib/vmware-vlcm/firstboot/vlcm_firstboot.py", line 129, in main
    fb = VlcmFirstboot(VLCM_COMP, VLCM_SOLUSERNAME)
  File "/usr/lib/vmware-vlcm/firstboot/vlcm_firstboot.py", line 50, in __init__
    os.path.join(get_install_parameter('upgrade.import.directory'), "vlcm")
  File "/usr/lib/vmware/site-packages/cis/tools.py", line 88, in get_install_parameter
    raise InstallParameterException('Install-parameter %s not set' % param)
cis.exceptions.InstallParameterException: {
    "detail": [
        {
            "id": "install.ciscommon.internal.error",
            "translatable": "Encountered an internal error.\n\n%(0)s",
            "args": [
                "Install-parameter upgrade.import.directory not set"
            ],
            "localized": "Encountered an internal error.\n\nInstall-parameter upgrade.import.directory not set"
        }
    ],
    "componentKey": null,
    "problemId": null,
    "resolution": {
        "id": "install.default.failure.resolution",
        "translatable": "This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.",
        "localized": "This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request."
    }
}

Using one of my previous blog post for guidance, he discovered a quick workaround to the problem by simply ensuring this variable is configured with a default value. After running into the problem myself and verifying the solution, I figure this might be useful for anyone looking to run vSphere 8 using VMware Fusion or Workstation, so here are the instructions to work around this issue.

Disclaimer: This is not officially supported by VMware, use at your own risk
[Read more...]