asked on

VMotion of VMs

I'm migrating machines from one SAN to another SAN using live migration.

A couple machines made it, but a couple have errored out. One complained of network issues, but when I looked at the two that failed, I see their VMDK is moved to the new SAN and the old location has a .png file in it as opposed to nothing for the successfull ones.

Is this a glitch in the GUI reporting the status of the virtual machine? It failed at 50% but is now using the new location. Not sure what issues down the line will be.

Thanks

SOLUTION

Luciano Patrão

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

chkdsk01

It's tough to say about the svMotion failure. Are the VMs functioning? Like "BestWay" said, check to see if any ISOs are connected. Although it wouldn't have let you continue with the svMotion if there were. Try going through the "tasks & events" in the client and see if it helps point to a reason.

Also, the .png file is a screenshot of the VM. If VMware senses a BSOD or the VM gets restarted, a screenshot is taken and dumped in the VMs folder on the storage.

snyderkv

ASKER

Chkdsk,

Yes the VM files and database were moved over to the new SAN despite the error message and it all still works.

So you're saying the .png file and folder (old database location) can safely be deleted? I was just making sure it wasn't some pointer required for the newly located VM to work.

BestWay, I did restart that ESX host after migrating the VMs to another HOST. Now the migrations have worked but I still have the .png of the couple that migrated over with error.

Thanks

ASKER CERTIFIED SOLUTION