Hyper-V virtual machine backup irregularities
Posted: Thu Dec 17, 2009 8:07 pm
Attempting to backup a Hyper-V virtual machine that uses a pass-through disk* results in some irregularities
(*i.e. not a VHD, but I don't know whether backup up a VHD would have the same problems)
First, the partition selection is out of whack, with drive letters mis-assigned and the C: drive, which is a 250 GB hard drive, is identified as:
127GB | C: 232GB NTFS "Volume label" | 100MB NTFS "System Reserved" (Active) | 127GB NTFS "Volume label"
obviously this is not correct, I have no idea why it concludes that the drive is 127 GB and then finds the same partition twice with two different sizes.
When a backup is attempted, taskeng.exe pops up and says "! Virtual HD1.1.0Partition at 206848 extends beyond disk bounds" twice, and cdrecord.exe pops up for a long time (the cd scan during task creation is also very long), and finally quits and then the backup continues, although it still lists the partition information incorrectly as before
I don't know whether to backup the whole drive, or manually select what appear to be the correct partitions, or if this backup is actually any good (I'm reluctant to test it)
will there be a fix in the pipeline to address this quirky behavior, and a test that it does backup hyper-v machines correctly?
(*i.e. not a VHD, but I don't know whether backup up a VHD would have the same problems)
First, the partition selection is out of whack, with drive letters mis-assigned and the C: drive, which is a 250 GB hard drive, is identified as:
127GB | C: 232GB NTFS "Volume label" | 100MB NTFS "System Reserved" (Active) | 127GB NTFS "Volume label"
obviously this is not correct, I have no idea why it concludes that the drive is 127 GB and then finds the same partition twice with two different sizes.
When a backup is attempted, taskeng.exe pops up and says "! Virtual HD1.1.0Partition at 206848 extends beyond disk bounds" twice, and cdrecord.exe pops up for a long time (the cd scan during task creation is also very long), and finally quits and then the backup continues, although it still lists the partition information incorrectly as before
I don't know whether to backup the whole drive, or manually select what appear to be the correct partitions, or if this backup is actually any good (I'm reluctant to test it)
will there be a fix in the pipeline to address this quirky behavior, and a test that it does backup hyper-v machines correctly?