VMware Behaviour: Deleting Snapshots Before Cloning When a Drive is Detached
Updated: 19 Feb 2008 | 2 comments
Just a quick heads up that might keep you from diving into the shallow end of the pool.
One of my customers that are running Notification Server on ESX, ran into this scenario recently:
- A VM runs two disks (C: and D: partition on different hard disks)
- Snapshot function is active and a snapshot was created.
- The machine is shutdown and the second hard disk is detached (but not deleted).
- The snapshot is removed (for example due to the need to clone the box but only with C: enabled)
- The second hard disk is reattached again and the box booted.
The result will be that drive C: stays in the current state but the content of the second hard disk (in this case D:) is reverted back to the state when the snapshot was taken!
blog entry Filed Under:
The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog.
Comments
Interesting information to
Interesting information to know in case of a similar extreme scenario (but Gremlins in the night sometimes working on that.... ).
Thanks for your heads up.
Paolo
This info is valid also in
This info is valid also in case of Vmware update ( ie. 3.01 -> 3.5 ).
Better remove the snapshot but please note that depending when this snapshot was created, could be take more time to remove it.
Would you like to reply?
Login or Register to post your comment.