Moving VMDK files on ESXi

[dawks]

Right now I have an ESXi 4.1 Server with a VMDK thats running out of space and needs to be moved. I have a nice hefty ESXi 5.5 server waiting for it but i need to find the quickest way to migrate it. We could go with a few hours of downtime over Saturday night if need be. I'm looking for the best way to move VMDK files. I've never had success with the vCenter client. is SFTP the best way? I dont suppose I can do a direct transfer with an FTP client (ESXi to ESXi)?

 

[dave_the_nerd]

Can't you just connect to both with VCenter and migrate datastores?

I've never had that not work. :\

 

[dawks]

I dont have a vCenter server or license, but I could obtain one, provided I know that will work.

I'm nervous about the client because whenever I've tried to download a large file from an ESXi Server, it would always crash the client or just drop the download, and it would run super slow.

 

[imagoon]

VMware Standalone Converter 5.5 is all you need. Install it on a computer in the office, source from 4.1 -> destination 5.5 click go and come back in a few hours.

 

[yinan]

That is the long way to do it. The way I would move an individual hard disk on a standlone ESXi host is to sue PowercLI adn the move-harddisk cmdlet.

 

[sourceninja]

You have a 5.5 server and a 4.1 server? I'd install the vcenter appliance on 5.5, use the 90 day trial license, add the 4.1 server to vcenter and do a storage vmotion.

 

[seepy83]

You have a 5.5 server and a 4.1 server? I'd install the vcenter appliance on 5.5, use the 90 day trial license, add the 4.1 server to vcenter and do a storage vmotion.

That's what I was thinking, as well. Much easier to use Storage vMotion if you have access to it...even if only on a trial basis.

 

[MiniDoom]

you could also export the vm as an ovf (single file) copy the file to the new datastore and re-import it to the new host.

 

[imagoon]

That's what I was thinking, as well. Much easier to use Storage vMotion if you have access to it...even if only on a trial basis.

I would need to check but I am pretty sure that just adding vcenter doesn't give you all the parts you need for Storage vMotion. I am pretty sure you need the host licenses also and for 4.1 I think that was at least ESXi Enterprise. I know for a fact that it doesn't work on the free licenses. I might be making an assumption here but if you don't have vCenter, most people won't have a high tier host license. I would also need to check the to see if the newer "shared nothing" storage vMotion even works with 4.1 as a source.

 

[imagoon]

That is the long way to do it. The way I would move an individual hard disk on a standlone ESXi host is to sue PowercLI adn the move-harddisk cmdlet.

Pretty sure powerCLI needs host licenses above free, maybe if the OP can say what his host license level is...

 

[yinan]

PowerCLI does not need a license.

Storage vMotion does not need shared storage to be done offline. If the VM is off and there is no shared storage then the files are simply copied across the network.

 

[imagoon]

PowerCLI does not need a license.

Storage vMotion does not need shared storage to be done offline. If the VM is off and there is no shared storage then the files are simply copied across the network.

PowerCLI does need a license to utilize "write" commands. I just tried to boot a VM with it on my test server running a free edition :

The operation for the entity xxxxx failed with the following message: “License not available to
perform the operation.”

What you are talking about is not storage vMotion. It is just a file copy.

 

[yinan]

Wow, you learn something every day.

 

[sourceninja]

I would need to check but I am pretty sure that just adding vcenter doesn't give you all the parts you need for Storage vMotion. I am pretty sure you need the host licenses also and for 4.1 I think that was at least ESXi Enterprise. I know for a fact that it doesn't work on the free licenses. I might be making an assumption here but if you don't have vCenter, most people won't have a high tier host license. I would also need to check the to see if the newer "shared nothing" storage vMotion even works with 4.1 as a source.

Right you need to use a vSphere trial license as well. If that is not possible, you can simply use http://www.veeam.com/virtual-machine-backup-solution-free.html for their quick migration feature.

Ultimately, if you intend to keep using vmware in the 5.5 world, I recommend getting a license to vcenter (vmware essentials at a minimum). Because you can't manage version 10 VM's without vcenter's web client.

Otherwise look at other hypervisor options.

 

[imagoon]

Right you need to use a vSphere trial license as well. If that is not possible, you can simply use http://www.veeam.com/virtual-machine-backup-solution-free.html for their quick migration feature.

Ultimately, if you intend to keep using vmware in the 5.5 world, I recommend getting a license to vcenter (vmware essentials at a minimum). Because you can't manage version 10 VM's without vcenter's web client.

Otherwise look at other hypervisor options.

True but at that point you might as well grab converter 5.5 and let it do the move. If you are doing a esxi host to esxi host it it happens at wire speed. I use it a lot to move machine in and out of Dev, dev -> prod etc. I personally use the "server" install and have it shared off the vcenter server so I get basically SAN to SAN performance with it.