migrate VM from ESX 2.5.1 to ESX 4.1

[sadguru]

We have few VMs in a ESX 2.5.1 13057 box with local storage. It is being managed using VC 2.5

Now we have installed a new ESX 4.1 server with local storage and it is being managed using VC 4.1

We want to migrate the VMs on ESX 2.5.1 to ESX 4.1

I tried copying the .vmdk file and creating a new VM on ESX 4.1 using that .vmdk. But it does not detect that vmdk file as compatible.

Is there any other idea for this migration? We may not be able to upgrade 2.5.1 to any higher version.

Thanks in advance

Regards,

Guru

[THP]

A straight copy will not work as ESX2.5 uses a different file format and virtual hardware version.

The simplest approach might be to join you ESX2.5 host to your VC4.1. Then cold migrate your VMs to an ESX4.1 host and onto new storage. You should then be able to upgrade the virtual hardware and start up the VM. (It's been a while since we did this so I may have skipped a step).

The other option is to copy the vmdk as you have done but to then import it into the new VC4.1 using the VM Converter plugin.

[PduPreez]

I would use Conerter Standalone or VC Converter to V2V this machines from the old hosts to the new.

Obviously stopping the necessary services for data consistency

After V2V the Virtual hardware will be up to date, you only need to upgrade/reinstall VMware Tools.

Regards

If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.

[sadguru]

But I think we cannot register ESX 2.5.1 in VC 4.1, can we? (I was referring to some compatibility pdf file from VMWare)

[PduPreez]

Easiest will be is to install Standalone Converter on the VM OS and run a convert to the new VSphere 4.x host

Regards

If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.

[THP]

Good point - in that case converter is the route to take.

[sadguru]

Thanks for the direction. However in my case the coverter is not able to connect to the ESX 205.1 as source ( it says the ESX is 2.5.x and it is not supported

[sadguru]

Thanks for the direction. However in my case the coverter is not able to connect to the ESX 205.1 as source ( it says the ESX is 2.5.x and it is not supported

[THP]

Yes, I was trying to mimic your dilemma and found the same problem.

I think you can get round this by not trying to point the convereter at the old virtual centre but instead using the 'Powered on Machine' as your source type. The you can follow the wizard through and set the destination as your new VC. I'm just trying it now and it is running without error so far.

It looks like you can also still grab version 3 of the converter which I think did work with the older version of VC but you'd probably be stuck with a two stage conversion which could be painful.

[PduPreez · Accepted solution]

Thanks for the direction. However in my case the coverter is not able to connect to the ESX 205.1 as source ( it says the ESX is 2.5.x and it is not supported <img class="jive-emoticon" border="0" alt=":(" />

You do not need to connect to the ESX 2.05 to convert

RDP to the Virtual Machine, install standalone Converter on the VM you want to convert, stop all neccesary services and run convert and point to new ESX 4.x server.

The OS does not care what hardware platform it runs on, it will just convert

Did you try the Standalone Converter with the VM running?

Regards

If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.

[sadguru]

I installed the VSphere converter standalone 4.3 on a test VM and converted all the VMs. Thanks a lot for your help.

[PduPreez]

Anytime

Don't be shy with points :smileycool:

Happy Visualizing