hi,
I have used upgrade vMotion to migrate about 25 machines from our esx 2.5 machines to our esx 3.5 machines and all have gone over smoothly except for the last one, our primary mail server
this machine failed after about 1 minute with the generic error "Failed to migrate Our Exchange from newhostname to newhostname" and a BSOD on the console.
I was presented with a warning to power the machine off and finish the migration cold, which i attempted to do by righclicking on the guest within the new host, and selecting "Complete Migration"
When I try this, i get a message after a few seconds " failed to relocate virtual machine 'Our Exchange' in 'Our datacenter'
I have sshd'd to the new server and that that the original vmdks are still on the old vmfs vm store, and the new vmstore has the following files:
-rw------- 1 root root 1627408384 May 29 22:15 DMotion-scsi0:00_AK DC Disk1-delta.vmdk
-rw------- 1 root root 291 May 29 23:43 DMotion-scsi0:00_AK DC Disk1.vmdk
-rw------- 1 root root 43008 May 29 22:13 DMotion-scsi0:01_AK DC Disk2-delta.vmdk
-rw------- 1 root root 291 May 30 07:43 DMotion-scsi0:01_AK DC Disk2.vmdk
-rw------- 1 root root 616448 May 29 22:13 DMotion-scsi0:02_AK DC-delta.vmdk
-rw------- 1 root root 280 May 30 07:43 DMotion-scsi0:02_AK DC.vmdk
-rw------- 1 root root 53248 May 29 22:13 DMotion-scsi0:03_AK DC Disk4-delta.vmdk
-rw------- 1 root root 291 May 30 07:43 DMotion-scsi0:03_AK DC Disk4.vmdk
-rw------- 1 root root 602112 May 29 22:13 DMotion-scsi0:04_JFEXCHANGE01_SG02_DB-delta.vmdk
-rw------- 1 root root 310 May 30 07:43 DMotion-scsi0:04_JFEXCHANGE01_SG02_DB.vmdk
-rw------- 1 root root 62464 May 29 22:13 DMotion-scsi0:05_JFEXCHANGE01_SG02_LOG-delta.vmdk
-rw------- 1 root root 311 May 30 07:43 DMotion-scsi0:05_JFEXCHANGE01_SG02_LOG.vmdk
-rw------- 1 root root 0 May 29 22:10 JF Exchange.vmsd
-rwxr-xr-x 1 root root 4003 May 30 00:00 JF Exchange.vmx
-rw------- 1 root root 271 May 30 00:00 JF Exchange.vmxf
-rw------- 1 root root 8684 May 30 00:00 nvram
-rw-r--r-- 1 root root 29213 May 29 22:10 vmware-0.log
-rw-r--r-- 1 root root 38057 May 29 22:10 vmware-1.log
-rw-r--r-- 1 root root 30548 May 29 22:10 vmware-2.log
-rw-r--r-- 1 root root 24574 May 29 22:10 vmware-3.log
-rw-r--r-- 1 root root 88737 May 29 22:15 vmware-4.log
-rw-r--r-- 1 root root 45904 May 30 00:00 vmware.log
I have read a number of posts such as
http://communities.vmware.com/message/999890
and tried the suggestions regarding creating and removing snapshots without success.
we are waiting for the renewal of our maintenance contract to go through, so calling vmware support is not an option at the moment.
I have used upgrade vMotion to migrate about 25 machines from our esx 2.5 machines to our esx 3.5 machines and all have gone over smoothly except for the last one, our primary mail server
this machine failed after about 1 minute with the generic error "Failed to migrate Our Exchange from newhostname to newhostname" and a BSOD on the console.
I was presented with a warning to power the machine off and finish the migration cold, which i attempted to do by righclicking on the guest within the new host, and selecting "Complete Migration"
When I try this, i get a message after a few seconds " failed to relocate virtual machine 'Our Exchange' in 'Our datacenter'
I have sshd'd to the new server and that that the original vmdks are still on the old vmfs vm store, and the new vmstore has the following files:
-rw------- 1 root root 1627408384 May 29 22:15 DMotion-scsi0:00_AK DC Disk1-delta.vmdk
-rw------- 1 root root 291 May 29 23:43 DMotion-scsi0:00_AK DC Disk1.vmdk
-rw------- 1 root root 43008 May 29 22:13 DMotion-scsi0:01_AK DC Disk2-delta.vmdk
-rw------- 1 root root 291 May 30 07:43 DMotion-scsi0:01_AK DC Disk2.vmdk
-rw------- 1 root root 616448 May 29 22:13 DMotion-scsi0:02_AK DC-delta.vmdk
-rw------- 1 root root 280 May 30 07:43 DMotion-scsi0:02_AK DC.vmdk
-rw------- 1 root root 53248 May 29 22:13 DMotion-scsi0:03_AK DC Disk4-delta.vmdk
-rw------- 1 root root 291 May 30 07:43 DMotion-scsi0:03_AK DC Disk4.vmdk
-rw------- 1 root root 602112 May 29 22:13 DMotion-scsi0:04_JFEXCHANGE01_SG02_DB-delta.vmdk
-rw------- 1 root root 310 May 30 07:43 DMotion-scsi0:04_JFEXCHANGE01_SG02_DB.vmdk
-rw------- 1 root root 62464 May 29 22:13 DMotion-scsi0:05_JFEXCHANGE01_SG02_LOG-delta.vmdk
-rw------- 1 root root 311 May 30 07:43 DMotion-scsi0:05_JFEXCHANGE01_SG02_LOG.vmdk
-rw------- 1 root root 0 May 29 22:10 JF Exchange.vmsd
-rwxr-xr-x 1 root root 4003 May 30 00:00 JF Exchange.vmx
-rw------- 1 root root 271 May 30 00:00 JF Exchange.vmxf
-rw------- 1 root root 8684 May 30 00:00 nvram
-rw-r--r-- 1 root root 29213 May 29 22:10 vmware-0.log
-rw-r--r-- 1 root root 38057 May 29 22:10 vmware-1.log
-rw-r--r-- 1 root root 30548 May 29 22:10 vmware-2.log
-rw-r--r-- 1 root root 24574 May 29 22:10 vmware-3.log
-rw-r--r-- 1 root root 88737 May 29 22:15 vmware-4.log
-rw-r--r-- 1 root root 45904 May 30 00:00 vmware.log
I have read a number of posts such as
http://communities.vmware.com/message/999890
and tried the suggestions regarding creating and removing snapshots without success.
we are waiting for the renewal of our maintenance contract to go through, so calling vmware support is not an option at the moment.
Tags:
upgrade_vmotion,
storage_vmotion,
vmotion,
vmfs3,
vmfs2,
failed,
upgrade,
esx3.5,
3.5,
2.5