I was trying to storage vmotion my Exchange 2007 to a new datastore on a different SAN last night and it timed out 6% of the way in. Now it is showing as being on both datastores. There is also a VM with the same name showing up as "orphaned". I searched around but didn't see any conclusive answers. On the new SAN is a .vmx file and .vswp and some logs and other stuff. On the original SAN is also .vmx file, the regular vmdk's, the logs and 3 .vmdk's named DMotion-scsi0:00, DMotion-Scsi0:01 and DmotionScsi0:02.
I'm worried that my exchange server is in limbo right now. Any idea what I should do?
Thanks
When I have had SVMotion failures in the past, I have had to power off the guest, and choose Complete Migration from the VM's menu.
This was the same for Plug-in and RCLI based failures.
Jase McCarty
Co-Author of VMware ESX Essentials in the Virtual Data Center
(ISBN:1420070274) from Auerbach
Please consider awarding points if this post was helpful or correct
Are you using ESX 3.5 or ESX 4?
Do you have some snapshots on your VM?
Andre
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
I am using 3.5.
But you have strange file name that seems vSphere names.
Are you using the RCLI to perform the SVmotion?
Andre
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
I'm using the svmotion GUI plugin
http://akutz.wordpress.com/2008/06/15/vi-plug-in-svmotion-10-released/
I attached screen shots of the current datastore (Buffalo) and the new datastore (Exchange)
When I have had SVMotion failures in the past, I have had to power off the guest, and choose Complete Migration from the VM's menu.
This was the same for Plug-in and RCLI based failures.
Jase McCarty
Co-Author of VMware ESX Essentials in the Virtual Data Center
(ISBN:1420070274) from Auerbach
Please consider awarding points if this post was helpful or correct
I think I'll try that tonight. Do you think there will be a conflict with the .vmx files? Thanks!
I've seen that a few times.
First, check to see if you have any of you disks marked as independent disks, if so you'll have to power off the VM to unselect that option or go command-line commando ( unsupported ) to fix it without downtime.
If you don't have any independent disks, go ahead and add another snapshot, wait for it to finish and then delete it. That usually clears up the problem.
There shouldn't be any independant disks, but i can't verify because the edit settings option on the vm is greyed out.
Is it best to shut down the VM and do a migration and select the new datastore?
The snapshot trick should get rid of those extra files, but the VM will still be on 2 datastores right?
So I shut the VM down last night did the "Complete Migration" option. It took 3.5 hours and in the end the VM was on the original datastore with the VMX and Swap on the new datastore.
So all this and I'm back where I started. I guess next time I try to SVMotion the VM I will do it when it's off.
Thanks for the help. Points awarded..