Azure Hybrid & Cloud Migration Blog

Hi folks,

Leeme tell you a interesting story, recently I got a situation where I wanted to move the VM to another Hyper-V server, but I was not able to user export, and it was giving me lots of errors, so without being waste time into resolving this issue, I thought to move the VHD of the VM machine, but then I came to know that there are two snapshot (AVHD) files are there, and currently the VHD is set to AVHD, one of the latest snapshot, to be honest, I was not aware about AVHD, what is this crap J, but then I dig into the this that how I can move AVHD and set it as VHD.

So I found that following solution to fix this problem.

Move your all VHD and AVHD files to another server, and do the following:

1. Create a new VM on the second server, where you wanted to move the VM.

2. After all formalities RAM and processor, Hyper-V will ask you to either create a new VHD or go for existing one, so select the partent VHD which you moved on this host.

3. And after completing the wizard, donot turn on the VM.

4. Select the machine and on your right hand, in the action menu select edit disk.

5. Then select the most recent AVHD file (last snapshot) then reconnect it to the previous snapshot, if you are more than two snapshot, go in the same flow.

6. Once you have reconnect both snapshot, then go back and select th VM and click on edit the disk again.

7. This time select the second older snapshot, which you just got reconnected to the most recent snapshot, and merge this with your parent disk, it will take some time to finish.

And afterwards, dhan dahaaan J, you are back in business…

Thanks for reading my article, cheers!

Zahir Hussain Shah