Snapshot Best practices for vCenter Server Virtual Machines

Products

• VMware vCenter Server

Issue/Introduction

• This article provides snapshot best practices for vCenter Server Virtual Machines to avoid any replication or other issues while reverting to snapshots (in case of any failure).

Environment

VMware vCenter Server 8.X

Vmware vCenter Server 7.X

Resolution

1. Do not take snapshot of the vCenter VMs if it’s part of vCenter HA (VCHA) configuration
   
   VCHA configuration should be destroyed, then re-deployed after fixes are done.
   
   
2. Check whether the vCenter is Standalone or in Replication mode.
   
   Run below command from the VCSA appliance to get the info:
   
   

   # /usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartnerstatus -h localhost -u administrator

3. If the vCenter(s) are in Enhanced Linked Mode (ELM) mode, follow below steps to take proper snapshots 

   Connect to the ESXi host via the host UI using a web browser where the vCenter VM is running.
   Shutdown vCenter VMs
   Take snapshot
   Repeat Steps 1-3 for remaining vCenters in ELM environment.
   Power On each vCenter VM once you confirmed that offline snapshots have been performed

   Note: It is mandatory to follow the above steps while taking snapshots for vCenter's in ELM. And it also important to revert to snapshots on all vCenter's in ELM, when we fall in a situation to revert the snapshots. Reverting snapshot only on one vCenter in ELM can disrupt the vmdird (VMware Directory Service) state because ELM relies on synchronized replication of the vmdir database across all vCenter Servers in the same Single Sign-On. (SSO) domain.

   For more details, refer to article VMware vCenter in Enhanced Linked Mode pre-changes snapshot (online or offline) best practice

4. If this is a Standalone vCenter snapshots can be taken online

Additional Information

• Read more at Overview of virtual machine snapshots in vSphere