Hyper-V Snapshots

I am trying to rollback my VS using a snapshot but getting an error (cannot load the snaphsot file).

I had recently deleted some snapshots (via interface) to make more hdd space (foolishly i deleted them with the VM turned on so only the link was removed, not the AVHD files). After doing some research it appears i have broken the differencing chain as the server appears to have reverted to the original VHD file which was setup months ago, hence i have lost months worth of work.

I have all the AVHD files there but cannot work out how to apply any of these snapshots. Does anyone know how i can rectify this problem?

Thanks
AntikytheraAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
OliverLoConnect With a Mentor Commented:
Hello,

Please take a copy all VHD and AVHD and you could then try to merge the older AVHD with the one before until you can merge the resulting VHD with the parent VHD.
For instance if you have the following snapshot tree:
PARENT
     ---------SNAP1
                      ----------SNAP2
                                     ----------SNAP3

Let's say you want to restore the VM at stage SNAP2.
You could try to merge the disk SNAP2.avhd with the disk SNAP1.avhd.
Then you could merge the resulting disk SNAP1-2.avhd with the parent disk.
In this way you would save all changes that occurred between the creation of the VM and the time SNAP2 was taken… If you don’t merge SNAP3 then the change it contains will be lost which is what you wanted.

This article may help you:
http://zahirshahblog.com/2010/10/24/how-to-manually-merge-hyper-v-snapshots-into-a-single-vhd/

Let me know if it worked as expected.
0
 
James HaywoodCommented:
You can try doing an 'offline merge' by using the disk editor.
0
 
BillConnect With a Mentor Commented:
If you're unsure which differencing disk (AVHD) is related to each of the other disks in the chain you can inspect it in Hyper-V to determine the order.  Once you have the chain order you can set that as your hard disk(s).  Offline Merges have been somewhat problematic when the chain is corrupted, e.g. deleting one of the AVHD files in the chain.

1 - 'Inspect' the disks in Hyper-V to determine the parent / child relationships
2 - You can also figure out the parent / child relationships with the file date, unless you have your than one Snapshot tree.  (Inspect Disk> Select a disk > view where it fits into the chain > make a note of the relationships
3 - If your backup software is Hyper-V aware (often this requires purchasing a backup agent for Hyper-V) restore the backup.  You can also restore to a different VM.  I'd try this if you have disk space so as not to blow away your original, even if it is out of date.
4 - There are third utilities out there that allow you to edit these files.

You can create a new VM for all of the experimentation but it appears that you're already low on disk space.
0
 
AntikytheraAuthor Commented:
Thanks for the comments - TSG, you are right about the merge. It is a long winded process and didnt resolve any issues.

After 4 days working solid, i solved it. When creating a new VM using an existing VHD file, it still creates a new set of config files.  

I basically copied and pasted the old BIN and VSV file into the newly created config director and renamed the files to the new config names. I then had to edit the XML and put the pathname as the latest .avhd file i had restored. Started it up and worked a treat :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.