MovingCopying rather than migrating VM disks

Home Forums Virtualization Microsoft Hyper-V Technology MovingCopying rather than migrating VM disks

This topic contains 3 replies, has 4 voices, and was last updated by Avatar Dext 2 years ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • Avatar


    I just wanted to check the best method for copying Hyper-V VM disks on Hyper-V 2012 R2. I know you can migrate within the Hyper-V Manager but I don’t want the old vhd(x) disks to go (just in case anything should go wrong).

    Will an export and import allow me to achieve my goal? Or another technique?



    Export will leave the existing VM on the server – you can stop it and set it not to auto start

    Copying VHDXs will work too


    If you’re copying the vhdx files to another server, try using Replication. That duplicates any vhdx files associated with the VM as well as the XML file that defines the VM (not that you appear to need it.) It does this while the VM is running or shut down. The time it takes to complete an initial repl is dependant on how much total volume is to be copied vs the size of the pipe this traffic moves through. My DR system includes a full cluster using replication to a second cluster in another location.


    Cheers guys, Im using Veeam to manage my replication but I need to move the storage of a VM from one folder to another (the folders physical location are on different disks).

    So I could export and import and then just delete the old VM which wont delete the disks? Or as you said [USER=”87″]Ossian[/USER] I could just manually copy the VHD(x) files and re-point the VM to those disks. There aren’t any checkpoints so all should be well.


Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.