Best practices for using snapshots in vsphere environment

From Notes_Wiki
Revision as of 15:06, 8 July 2018 by Saurabh (talk | contribs) (Created page with "<yambe:breadcrumb>VMWare_vSphere_or_ESXi|VMWare vSphere or ESXi</yambe:breadcrumb> =Best practices for using snapshots in vsphere environment= Snapshots are good way of creat...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

<yambe:breadcrumb>VMWare_vSphere_or_ESXi|VMWare vSphere or ESXi</yambe:breadcrumb>

Best practices for using snapshots in vsphere environment

Snapshots are good way of creating a quick recovery point in case the changes to be performed in immediate future cause VM to crash. However, there are best practices for using snapshots such as:

  • We should not use snapshots as backups. There should be separate backup mechanism for backup.
  • We should not use more than 2 or 3 snapshots in a chain.
  • It is not ideal to keep snapshot for more than 2-3 days. As soon as activity is over and VM is stable, snapshots should be deleted
  • If snapshots are used for backup process, then after backup is complete the snapshot should be deleted
  • We should delete snapshots before increasing VM disk space by increasing size of virtual RDM.

Refer: