Snapshots best practices

Snapshots are not backups. As the snapshot file is only a change log of the original virtual disk, do not rely upon it as a direct backup process. The virtual machine is running on the most current snapshot, not the original vmdk disk files.
• Snapshots are not complete copies of the original vmdk disk files. The change log in the snapshot file combines with the original disk files to make up the current state of the virtual machine. If the base disks are deleted, the snapshot files are useless.

• Snapshot files can grow to the same size as the original base disk file, which is why the provisioned storage size of a virtual machine increases by an amount equal to the original size of the virtual machine multiplied by the number of snapshots on the virtual machine.

• The maximum supported amount in a chain is 32. However, VMware recommends that you use only 2-3 snapshots in a chain.

• Use no single snapshot for more than 24-72 hours:
1. This prevents snapshots from growing so large as to cause issues when deleting/committing them to the original virtual machine disks. Take the snapshot, make the changes to the virtual machine, and delete/commit the snapshot as soon as you have verified the proper working state of the virtual machine.
2. Be especially diligent with snapshot use on high-transaction virtual machines such as email and database servers. These snapshots can very quickly grow in size, filling datastore space. Commit snapshots on these virtual machines as soon as you can.

• If using a third party product that takes advantage of snapshots (such as virtual machine backup software), regularly monitor systems configured for backups to ensure that no snapshots remain active for extensive periods of time.- Snapshots should only be present for the duration of the backup process.- Snapshots taken by third party software (called via API) may not show up in the vCenter Snapshot Manager.

• An excessive number of snapshots in a chain or snapshots large in size may cause decreased virtual machine and host performance.

• Configure automated vCenter Server alarms to trigger when a virtual machine is running from snapshots.

• Confirm that there are no snapshots present before a Storage vMotion. If snapshots are present, delete them prior to the Storage vMotion. For more information.

• Confirm that there are no snapshots present before increasing the size of any Virtual Machine virtual disk or virtual RDM. If snapshots are present, delete them prior to increasing the size of the disk/s. Increasing the size of a disk with snapshots present can lead to corruption of the snapshots and potential data loss