Hello,
I am planing to migrate vms to ESX 3.0.1 using vmotion with datastore relocation.
Here I have some questions:
1- How many people have done this ? who had problems? who had not?
2- When migrating with vmotion, the vmdk file on the vmfs2 is deleted after the migration is complete? or it remains on the vmfs2?
3- What if the vmotion fails?
I know the requirement and I also know that I may have problems since 2.5.4 is not supported for this type off "live" migration.
So any comments and help would be appreciated.
Regards
Thanks for your help
I'm not sure that it is possible to VMotion with datastore relocation from 2.54 to 3.0.1.
On these versions of ESX, I believe that you are going to have to perform a cold migration (migrating a powered-off VM) if you want to move the VM to a different datastore. Even then, the different VMFS versions (VMFS2/VMFS3) may cause some issues...Then again, I'm not entirely sure from your description what you are trying to do.
Can the ESX 3.0.1 host "see" the datastore connected to the ESX 2.5.4? If not (and maybe if so) you may have to use WinSCP/FastSCP to move the .vmdk files, then import them with vmkfstools or perhaps use VM Converter.
I think you may want to use a tool called VMWare converter because you won't be able to vmotion.. This will help you migrate your vms better than using the vmkfstools -i format and copy. Also, VMware is now at ESX 3.0.2 Virtual Center 2.0.2. Just an FYI
You also may want to read this site before you begine.
http://www.vmware.com/support/vi3/doc/releasenotes_esx302.html#upgrading
Hope that helped. 
1- How many people have done this ? who had problems? who had not?
how many people --> I Dondt know
problems --> some
2- When migrating with vmotion, the vmdk file on the vmfs2 is deleted
after the migration is complete? or it remains on the vmfs2?
You mean DMotion
I dondt use this.
on Vi3
create a new VM, this creates the folder for the vm and than delete the new created VMDK Files (you will deen only this folder and the config files)
when the are able to see both SAN than
use vmkfstools -i /vmfs/sourcevmd.dsk /vmfs/newsan/newvm/newvm.vmdk
with this option you are copying this vmdk when it fails, try again
When the hosts are on different SAN than use fastscp from veeam
attach the vmdk files on your new VM and power on
migrate the VM Hardware, install VM Tools and be happy.
In one of my project i used the original vmx file from ESX 2.x there are some problems. its better when you create a new Vm on Vi3
i Hope this helps you
have a nice day
Nautilius
Well,
we tested it here without any problems, the only things is: Upgrade using Vmotion and datastore relocation is not supported for the ESX 2.5.4 by VMware, that said, it is for 2.5.3.
So we made test on 2.5.4 to 3.0.1 without problems.
We also tested 2.5.4 to 2.5.3 to 3.0.1 since 2.5.3 to 3.0.1 live migration is supported by VMware this could be the way.
But I don't know why 2.5.4 is not on supported list and not on unsupported list on their official website: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=8479101&sl...
Regards
Jon
1- Ho1- How many people have done this ? who had problems? who had not?
I did this and it worked so well 3 days after the migration was complete I was asked when I was going to start
2- When migrating with vmotion, the vmdk file on the vmfs2 is deleted after the migration is complete? or it remains on the vmfs2?
the files get moved so yes deleted on the VMFS2 partition. Vizioncore has a migrator tool that will leave the VM intact during and after the migration
3- What if the vmotion fails?
then the snapahot is applied and the systems keeps running until you can try again or do a cold migration
Steve Beaver
VMTN Forum Moderator
**Virtualization is a journey, not a project.**
Thanks for your help
Jon
This document was generated from the following thread: Migration from 2.5.4 to 3.0.1 using vmotion with datastore relocation.
