Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

VMware Behaviour: Deleting Snapshots Before Cloning When a Drive is Detached

Updated: 19 Feb 2008 | 2 comments
SK's picture
0 0 Votes
Login to vote

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:

  1. A VM runs two disks (C: and D: partition on different hard disks)
  2. Snapshot function is active and a snapshot was created.
  3. The machine is shutdown and the second hard disk is detached (but not deleted).
  4. The snapshot is removed (for example due to the need to clone the box but only with C: enabled)
  5. 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!

Comments

riva11's picture
19
Feb
2008
1 Vote +1
Login to vote

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

riva11's picture
23
Mar
2009
1 Vote +1
Login to vote

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.