Best way to backup vCenter, image backup or VAMI

[MeenaJ]

I know that when you are in a Linked Mode configuration, that image backup is not very useful and VAMI is the only way even though that can have issues. 

We have some new standalone vCenter v7 and v8 and we are considering only using daily VAMI backups for those. To not do image backups with Commvault anymore. 

Just wondering if this is a good idea. Thank you.

[Kinnison]

Hi,

It will be right or wrong, but with my "standalone" vCenter object I use both methods even if, under normal conditions, with a different time frame (via VAMI daily, via IMAGE weekly). Then beyond that, I keep separate copy of information related to "vDS" and "Native Key Provider" objects configuration (I don't use other features).

Others probably use a different approach that is better suited to their particular needs.

Regards,
Ferdinando

[virtualinca]

I am using scripted backup.

[GeoPerkins]

We use Commvault. Setup subclient on the vCenter client configured for the built-in quiesced snapshot backup of the VCSA. Runs late at night, never had any issues. Tested restore worked just fine. Why are you moving away from a Commvault setup? 

 

P.S. MeenaJ, I know you said you have a standalone vCenter, but for anyone else who has enhanced linked mode, VAMI and 3rd party tools all fail to deal with the complexities of in-flight ELM replication and if you restore one vCenter, the other ELM vCenter(s) replication will be broken. Only fix is to contact VMware support to run some scripts in internal VMware support (non-public) KBs to fix the replication DB.  I have asked VMware for a feature enhancement (really, this should have been included back in vCenter 6.0 VAMI when ELM was introduced) to allow backup and restore of ELM. You could ping VMware also and get some momentum on this. Backup limitations when using ELM: https://kb.vmware.com/s/article/85662?lang=en_us

[MeenaJ]

We are actually in an ELM configuration now and are rebuilding as standalone. The potential issues with ELM we just are not comfortable with. 

We were thinking of not using Commvault anymore, because in vSphere 8 it does not even mention image backups, only VAMI. In vSphere 7 it mentions image and VAMI, so I took that as image backups are not supported in vSphere 8 anymore?

Also does change block tracking in anyway interfere with the vCenter appliance?

[GeoPerkins]

We only are using vSphere 7. So no help here, sorry. Maybe open a support case if a VMware expert does not reply.

[Kinnison]

Hi,

Actually in the documentation there is still reference to image based backup, you can read it here:
https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-vcenter-installation/GUID-1C73996F-8312-4BBD-A16C-B2C8FC3C0D31.html

If you have found something else written elsewhere, it would be useful to know.

Regards,
Ferdinando

[wenoi6]

VAMI (vCenter Server Appliance Management Interface) backup is a convenient and reliable option for backing up a standalone vCenter Server Appliance (VCSA). The VAMI backup creates a complete backup of the VCSA's configuration, including its network settings, database, and vCenter Server settings. This backup can be used to restore the VCSA to its previous state in the event of a disaster or failure.

On the other hand, an image backup is a low-level backup that creates a copy of the entire virtual machine and its associated files, including the VCSA's operating system, applications, and data. This type of backup is useful for disaster recovery and can be used to restore the entire virtual machine to a previous state. However, image backups can be time-consuming and resource-intensive, and may not be necessary if you already have a VAMI backup in place.