vCenter Server Appliance VAMI – Stuck on Getting Started After Upgrade

You can use the VMware Consolidated Backup. If you are using ESXI you have to install a VM as VCB Proxy first to run the commands. If youre running an ESX host you can run the commands from its shell.

1. get the moref id from the vm which should be backuped: vcbVmName -h $HOST -u $USER -p $PW -s name:$VM

2. create a snapshot vcbSnapshot -h $HOST -u $USER -p $PW -c moref:$NR

3. create a backup of the vdisks vcbExport -M 1 -s /vmfs/volumes/..../disk.vmdk -d /backupdir/disk.vmdk

4. get the SSID of the snapshot and remove the snap SSID=vcbSnapshot -h $HOST -u $USER -p $PW -f moref:$NR Snapshot | grep "SsId" | cut -d: -f2 | tail -n 1

vcbSnapshot -h $HOST -u $USER -p $PW -d moref:$NR ssid:$SSID

Please pay attention this are just code snippets of a backup script which we use. Please edit the commands before using them.

The other vm files (vmx, vmxf...) arent backuped with this solution. If you want to save them you just have to copy them.

This works for our different remote offices where a single Vmware ESX Standard Host is running.

The answer in this case, both unfortunately and fortunately, appeared to be simple.

The error seems to be related to the fact that the VM was still powered on.

After powering off the VM, the fault tolerance option was able to be put in place.

In this case, VMWare appears to generate an error message that isn't very helpful.