Snapshots are for test, not for real

So here’s one best practice that I for sure follow… I ignore the ability to do snapshots in anything other than my Test HyperV.  On my real production, snapshots are to be ignored.

Primarily in my mind for the fact that making a snapshot of a DC isn’t wise as it could lead to tombstone issues where if you roll back you could be going back in your AD history unknowingly, and then secondly …now granted by TestHyperV is an overgrown Frys desktop, but it nails that servers performance when it snaps an image.

So just plan on having a normal backup for your HyperV child and not taking snapshots.

2 Thoughts on “Snapshots are for test, not for real

  1. Sepp on May 21, 2012 at 6:34 am said:

    Have a try with Altaro Hyper-V Backup, its free for 2 clients and works extremely well on Hyper-V (core only)… I have been using it for some time and the assistance from the company is excellent ( even for the free version, which I am using).

    Have fun


  2. I agree w/Sepp – Altaro is a great product with excellent support. I, too, am using the free version.

    I do though use the Hyper-V snapshots – but in specific circumstances. On my production vms (neither are DCs or database servers), I run a snapshot before updates or any major changes, do the updates/change and all the testing and then if all is well, delete the previous snapshot, keeping only the latest snapshot per vm. As updates/changes take place during off hours, performance isn’t an issue. This has saved me in a couple instances. Given the info in the linked article, I will take a second look at keeping even that latest snapshot.

Post Navigation