moving hype-v guest machine from one hyper-v server to another (without clustering/storage)

hi

until now i had one hype-v host with 5 gurst VM on this machine .

i just got new server and made that server hyper-v as well (windows server 2008 r2 enterprise addition )

i want to move some of the VM to the new hyper-v server

i dont have storage or any cluster, or SCVMM, so guess i can use live migration and etc...

how do i use the virtual machine from one host to another?

i tried to use the "import option" from the hyper v server but got error that i dont have premission even that i do have NTFS premissions

i tried to check if i can just copy the virtual hard disk file but i notice it's devided to several files, mybe by definision or becuase of snapshot not sure.

anyway, what is the recommended way to do that with the means that i have?

thanks
ymg800Asked:
Who is Participating?
 
NeilMMCommented:
Manually moving VMs between Hyper-V hosts means that you need to perform a manual export of each VM you wish to migrate, copy the files to the target Hyper-V host, and then import the VM on that host.

In order to export a virtual machine, you can simply right-click that VM within Hyper-V Manager and choose the "Export" option. On the new virtual host you want to import to, you can do the same process in reverse by choosing the "Import" option from the Action menu in Hyper-V Manager.
 
Performing a migration between hosts in this manner will assure all settings are copied along with the VHD file, and also ensure that network adapter settings are not lost.
 
However, this process takes time because it requires you to wait until the exporting process is done (unless the entire process is done by using a script), and only then copy the VHD and other files that make the VM to the target host. Once copied, you need to manually import the VM (or again, use a script to do it for you), which doesn't take as much time as the export operation, but still requires time. In addition, the migrated VM will experience a prolonged downtime. This is due to the fact that it must be shut down on the original host, exported in the shut down state, copied across the network to the target host, and then imported and booted.
0
 
Svet PaperovIT ManagerCommented:
Export the machines from the old server in a temporary location and import them in the new one. When importing, select to make a copy of the VM in order to move the VHD files into the new server, otherwise they will stay in the temporary location.
0
 
NeilMMCommented:
In addition : Some things you should do to make the import process go smoothly:

1) Make sure the same Virtual Network is defined on the import host - this means it will hook up the imported VM tot he correct network
 
2) Place the export directory of files EXACTLY where you want to be when you import - the import processes registers it at the currently location. If you import and want to move it somewhere else you must export it again.
 
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.