Comments on: Manual commit snapshots delta file to vmdk flat file http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/ Tue, 07 Feb 2012 16:53:13 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: craig http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/comment-page-1/#comment-7246 craig Mon, 19 Dec 2011 13:56:28 +0000 http://malaysiavm.com/blog/?p=942#comment-7246 to access back the existing flat vmdk, you need to rebuild the chain of the .vmdk configuration file. Please refer to my pose with external URL link, which explain in details how to rebuild the chain. Once you rebuild it, you should able to access or commit the snapshot. to access back the existing flat vmdk, you need to rebuild the chain of the .vmdk configuration file. Please refer to my pose with external URL link, which explain in details how to rebuild the chain. Once you rebuild it, you should able to access or commit the snapshot.

]]> By: wenk http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/comment-page-1/#comment-7234 wenk Sat, 17 Dec 2011 17:03:36 +0000 http://malaysiavm.com/blog/?p=942#comment-7234 Thank for your answer, one more things, what about the flat vmdk was modified before i merge the delta files?? Can i still merge the delta to modified Flat files?? It is happen becoz the backup of the original was damage, and we have no chance to merge at first, but we already run the vm with only the flat vmdk, and that vmdk already access/modified by user...Could we still merge the lost data on delta file to the Flat?? It will disaster if we cannot get the data back Thanks for your great help Thank for your answer, one more things, what about the flat vmdk was modified before i merge the delta files?? Can i still merge the delta to modified Flat files?? It is happen becoz the backup of the original was damage, and we have no chance to merge at first, but we already run the vm with only the flat vmdk, and that vmdk already access/modified by user…Could we still merge the lost data on delta file to the Flat??

It will disaster if we cannot get the data back

Thanks for your great help

]]> By: craig http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/comment-page-1/#comment-7227 craig Fri, 16 Dec 2011 15:14:01 +0000 http://malaysiavm.com/blog/?p=942#comment-7227 You can check in CLI how many delta file created in the datastore, that will tell you how many snapshot you had created earlier. In the scenario you mentioned, you can try to create a new snapshot and delete all snapshot after that. It should able to commit all existing snapshot. If failed, you will need to go through the method that I mentioned here to perform a manual commit on broken chain snapshot for VM level. You can check in CLI how many delta file created in the datastore, that will tell you how many snapshot you had created earlier. In the scenario you mentioned, you can try to create a new snapshot and delete all snapshot after that. It should able to commit all existing snapshot. If failed, you will need to go through the method that I mentioned here to perform a manual commit on broken chain snapshot for VM level.

]]> By: wenk http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/comment-page-1/#comment-7213 wenk Thu, 15 Dec 2011 07:57:09 +0000 http://malaysiavm.com/blog/?p=942#comment-7213 Dear mr Craig, What about if i forgot how many snapshots file that i have done, and i just want to commit only the lates snapshots (ignoring all the snapshot before - i have 2 disk attach as c & d, so i must have 2 file delta and vmdk at least). Can i just re-create 1 snapshots, and then change the original delta that will be commited with the latest snapshot, and run delete all snapshot...and will it be succeed to commit to the flat vmdk?? thanks a lot for your help Dear mr Craig,

What about if i forgot how many snapshots file that i have done, and i just want to commit only the lates snapshots (ignoring all the snapshot before – i have 2 disk attach as c & d, so i must have 2 file delta and vmdk at least).
Can i just re-create 1 snapshots, and then change the original delta that will be commited with the latest snapshot, and run delete all snapshot…and will it be succeed to commit to the flat vmdk??

thanks a lot for your help

]]> By: craig http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/comment-page-1/#comment-7001 craig Sun, 13 Nov 2011 15:17:51 +0000 http://malaysiavm.com/blog/?p=942#comment-7001 The concept is the same, you need to rebuild the chain follow the description in the post. .vmdk is the config file that point to the contain data flat file. Easiest way is full clone to new machine. The concept is the same, you need to rebuild the chain follow the description in the post. .vmdk is the config file that point to the contain data flat file. Easiest way is full clone to new machine.

]]> By: Topper http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/comment-page-1/#comment-6983 Topper Sun, 06 Nov 2011 15:32:38 +0000 http://malaysiavm.com/blog/?p=942#comment-6983 But not works for me, snapshots isn't consolidated :( Now i'v got from 01 to 05 delta files. Please, advice how to consolidate it! ESXi 4.1u1 But not works for me, snapshots isn’t consolidated :(
Now i’v got from 01 to 05 delta files.
Please, advice how to consolidate it!
ESXi 4.1u1

]]> By: craig http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/comment-page-1/#comment-5859 craig Wed, 15 Jun 2011 06:10:38 +0000 http://malaysiavm.com/blog/?p=942#comment-5859 the procedure you use might work when the chain of the snapshot are not corrupted. The solution I posted here is mainly meant for those situation while the snapshot chain corrupted which you will need to rebuild manually. the procedure you use might work when the chain of the snapshot are not corrupted. The solution I posted here is mainly meant for those situation while the snapshot chain corrupted which you will need to rebuild manually.

]]> By: cyber7 http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/comment-page-1/#comment-5851 cyber7 Mon, 13 Jun 2011 09:00:46 +0000 http://malaysiavm.com/blog/?p=942#comment-5851 Just my 10c Background (ESXi 4.1): After deleting an unsuccessful VEEAM Snapshot I was left with a delta file that was taking up the entire disk space. This caused me not to be able to bring my VM up. Procedure to fix: 1. Shut VM down. 2. Take snapshot (created a tiny snapshot) 3. Delete all snapshots. All delta files got deleted and disk space released. Cheers cyber7 Just my 10c

Background (ESXi 4.1):
After deleting an unsuccessful VEEAM Snapshot I was left with a delta file that was taking up the entire disk space. This caused me not to be able to bring my VM up.

Procedure to fix:
1. Shut VM down.
2. Take snapshot (created a tiny snapshot)
3. Delete all snapshots.

All delta files got deleted and disk space released.

Cheers
cyber7

]]> By: sam http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/comment-page-1/#comment-5672 sam Mon, 11 Apr 2011 01:13:17 +0000 http://malaysiavm.com/blog/?p=942#comment-5672 Ya....so it kinda worked. I think what he was trying to say was: - Verify you have the two files associated with the original snapshot (computer-000001-delta.vmdk and computer-000001.vmdk) or more if you have multiple snapshots as in my case, I had 2 snapshots. This can be done through the console of your ESX server or if you SSH to the ESX server. (cd /vmfs/volumes/storage/computer - Create a new snap shot or 2, 3, 4, etc.... - Ensure the VM is powered off. - Go back to your ESX console or SSH to ESX server - Drill down to the folder containing the config and HD files again - delete the original .vmdk not -delta.vmdk for snapshot 1, 2, etc... ( I just renamed mine, computer-000001-original.vmdk.) - Rename the latest snapshot .vmdk file you just took (For me computer-000003.vmdk) to the original .vmdk file name. (For me computer-000001.vmdk) - Edit the file (computer-000001.vmdk) to point to the orignal -delta.vmdk. - do the same for any other snapshots. (for me it was change snapshot 4's .vmdk to snapshot 2's....so on and so forth.) - turn on the VM and yo should be good to go. Ya….so it kinda worked. I think what he was trying to say was:

- Verify you have the two files associated with the original snapshot (computer-000001-delta.vmdk and computer-000001.vmdk)
or more if you have multiple snapshots as in my case, I had 2 snapshots. This can be done through the console of your ESX server or if you SSH to the ESX server. (cd /vmfs/volumes/storage/computer
- Create a new snap shot or 2, 3, 4, etc….
- Ensure the VM is powered off.
- Go back to your ESX console or SSH to ESX server
- Drill down to the folder containing the config and HD files again
- delete the original .vmdk not -delta.vmdk for snapshot 1, 2, etc… ( I just renamed mine, computer-000001-original.vmdk.)
- Rename the latest snapshot .vmdk file you just took (For me computer-000003.vmdk) to the original .vmdk file name. (For me computer-000001.vmdk)
- Edit the file (computer-000001.vmdk) to point to the orignal -delta.vmdk.
- do the same for any other snapshots. (for me it was change snapshot 4′s .vmdk to snapshot 2′s….so on and so forth.)
- turn on the VM and yo should be good to go.

]]> By: Jas http://malaysiavm.com/blog/manual-commit-snapshots-delta-file-to-vmdk-flat-file/comment-page-1/#comment-1556 Jas Wed, 02 Sep 2009 08:40:51 +0000 http://malaysiavm.com/blog/?p=942#comment-1556 Check out this KB @ http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003743 Check out this KB @ http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003743

]]>