I need help or confirmation on the migration of Virtual Machines in ESX 3.0 and Virtual Center 2.0. This is the setup: Two hosts each with their own separate local storage. The first ESX host is overloaded with sessions so I want to migrate some of the sessions from one host to another. Again there is NO SAN attached storage that the hosts are sharing, so the VMDK and VMX files reside on the local disk. I read different solutions in different places. One solution is to simply right click on the host in Virtual Center and choose migrate. Another is to use ftp or scp and re-register the vmx file. Which is the correct method? I am assuming that the ftp or scp method is for those that do not have Virtual Center? Is this correct? Or am I missing something. Does anyone know of a good tutorial for migrating Virtual Machines?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Migrating Virtual Machines on different local disks
- Thread starter Izzy77
- Start date
If you are using Virtual Center, the right click and migrate works. The VM needs to be powered down to change storage locations. Virtual Center will copy the VM over the network to the new host/storage.
This is a piece of cake. Second method is indeed the way to do it without VC.
This is a piece of cake. Second method is indeed the way to do it without VC.
It's important to understand that there are two different kind of migrations:
*the first is as you described used when there is no availability of a central storage: cold migration
*the second is a hot migration: migration of a live vm (central storage is needed)
Both options can be used with the right click - migrate in VC.
If no VC available, there is no one correct method (only best practices) in my opinion.
VMware's site is a good place to start:
*the first is as you described used when there is no availability of a central storage: cold migration
*the second is a hot migration: migration of a live vm (central storage is needed)
Both options can be used with the right click - migrate in VC.
If no VC available, there is no one correct method (only best practices) in my opinion.
VMware's site is a good place to start:
- Thread starter
- #5
I have tried to migrate, but the migration fails. During the post check I get the following error:
"Migration from Severname1 to servername2: Network interface 'Network Adapter 1' uses network '...', which is not accessible.
When I searched the file structures of both systems under /vmfs/volumes/.... a folder was created for the vm and a single flat.vmdk file was transferred to the destination machine. None of the other vmdks or vmx files were transferred. On the source machine the entire VM folder that contained all the vmdk and vmx files are gone.
I am trying to SCP the files of another test machine now. I know after I transfer all the files over I need to re-register the vmx file.
Is this the command?
vmware-cmd –s register /vmfs/volumes/.....
"Migration from Severname1 to servername2: Network interface 'Network Adapter 1' uses network '...', which is not accessible.
When I searched the file structures of both systems under /vmfs/volumes/.... a folder was created for the vm and a single flat.vmdk file was transferred to the destination machine. None of the other vmdks or vmx files were transferred. On the source machine the entire VM folder that contained all the vmdk and vmx files are gone.
I am trying to SCP the files of another test machine now. I know after I transfer all the files over I need to re-register the vmx file.
Is this the command?
vmware-cmd –s register /vmfs/volumes/.....
- Status
Similar threads
- Locked
- Question