YannSceti
Contributor
Contributor

Correct use of snapshots

Hi

I would like to have comments about the correct way to use snapshots.

Currently I have one ESXi 3.5 server with 4 VMs.

I use snapshots as follow :

- I always have 1 snapshot taken for each VM

- I regularly (before the size of the snapshot gets too big) delete the snapshot and right after take a new snapshot for each of the VM

- I will soon be able to take a backup of my VMs but I am not doing it now

I recently started to monitor the size of my VMs and they become several GB in only few days.

I am wondering if always having a snapshot on each VM is efficient.

I am starting to think that maybe snapshot should be taken only just before we make a big change on the server (software install or whatever) to be able to go back to the state we had before the operation in case it goes wrong, then delete the snapshot after we could confirm the operation went well, but shouldn't exist permanently.

Your comments are welcome! Thanks!

Yann

Reply
0 Kudos
NuggetGTR
VMware Employee
VMware Employee

Snapshots are not a backup solution, should only be used as a temp roll back when applying new patches, have it running for a day no issued then delete the snapshot. But a backup should still be made before any changes on the server, snapshot is justs a quick roll back if needed.

No this is not very efficient

You should look at a proper backup solution with VCB or other backup solutions

________________________________________ Blog: http://virtualiseme.net.au VCDX #201 Author of Mastering vRealize Operations Manager
AndreTheGiant
Immortal
Immortal

VMware snapshots are not optimized for performance and can slow down your VM disk access.

So use them only when you really need and remove as soon is possible.

For backup use backup solution.

For versioning, consider other products, like Lab Manager or similar.

Storage snapshots instead are usually optimized for performance, in this case you can use them also as a "recovery point" for a last good state.

But they works on the entire datastore and (to be consident) they require some kind of intergration with ESX/ESXi or vCenter.

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
AntonVZhbankov
Immortal
Immortal

Snapshots are NOT backup solution in any case. If you use snapshots as backup replacement then

1) you're wasting expensive storage space

2) you have lower reliability

3) you generate high disk load when commit snapshots

What is correct use of snasphots:

1) you have to install some patch on your VM

2) take snapshot

3) install patch

4) monitor system behavior in case of patch have broken something for some time

5) commit snapshot if everything is ok, or revert to snapshot if something bad happened.


---

MCSA, MCTS, VCP, VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda

View solution in original post

Reply
0 Kudos
YannSceti
Contributor
Contributor

Thank you all for your advices.

Yann

Reply
0 Kudos