Link to home
Create AccountLog in
Avatar of networkn
networkn

asked on

Collapse VM Server 2.02 Snapshots

We run VMWARE Server 2.02 on Windows 2008 and I am wanting to expand one of the disks, but when I run the command line it says I need to collapse the snapsots. I can find a place to remove them, but not collapse them. Where and how specifically can I collapse the snapshots please?
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
or if you want to preserve them for Backups, if you've been using them for that purpose.

I would recommend and use VMware Convertor to migrate and create a new virtual machine with the newly sized disk with the data and without the snapshots.
Avatar of networkn
networkn

ASKER

Err what? I thought that when you made a snapshot, all new data was wirtten to the snapshot, meaning that if you remove it you will lose all data contained in the snapshots?
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
So deleting the snapshot actually merges it with the base vdmk? I need to be 100% sure that I don't lose any data here.

I'll install converter.
How bigs is the delta vmdk file, and how long have you been running snapshots?
1 x 3gb snapshot file. Original vdmk is 15gb. 4 weeks
Okay, that's quite small.

VMware Converter is the safest option, but you shouldn't run on snapshots in production, because they grow out of control, people forget about disk space, and then the machine fails and will not turn on because the datastore, disk space has been used up, and you need free space to merge the snapshot. So be warned.

Most common question on EE, is I've got a Snaphot, and .......
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
"hanccocka" is accurate - this is one of the most common EE posts. A couple things to keep in mind regarding snaps -> they are not a backup solution at all; that being said, try not to keep them longer than a day...2 at most. They were designed to protect you when updating VMs (patches, app updates, etc.).

Regards,
~coolsport00
http://kb.vmware.com/kb/1015180

Is it ok that it refers to esx?
Yes...the functionality of what a snapshot is (and does) is the same across all VMware platforms. But, specifically for Server you can reference the User's Guide:
http://www.vmware.com/pdf/vmserver2.pdf, beginning on pg. 195

~coolsport00
I used Vmware converter to convert it to a bigger hard disk which merged the content. Seems to have worked. I just want to confirm before I close this, that DELETING snapshots in Server 2.0 100% collapses the snapshot back into the main vdmk? No loss of data? What happens if you have 3 snapshots and you delete the middle one? Does it delete the third one and data written to it is lost?
Yes...it *COMMITS* the data to the parent disk. Please read the KB given. It explains your questions in more detail. Snaps are in a chain, when a snap's data is 'committed', it's done so to its parent disk, which may not be the source/orig virtual disk if there are more than 1 snapshots. If you delete a middle of 3 snaps, you could lose your VM as a whole, or more than likely just the 3rd and middle snap data. I honestly don't know why VMware has the ability to have "tree'd" snaps. It causes more confusion and potential for corruption than benefit. But, they give users flexibility for their product, I guess.

Regards,
~coolsport00