Move VMDK files to different datastore

Here are storage vMotion Req's/Limitations:
http://www.vmware.com/pdf/vsphere4/r40/vsp_40_admin_guide.pdf, pg. 196

Storage VMotion is subject to the following requirements and limitations:
* Virtual machines with snapshots cannot be migrated using Storage VMotion.
* Virtual machine disks must be in persistent mode or be raw device mappings (RDMs). For virtual
compatibility mode RDMs, you can migrate the mapping file or convert to thick-provisioned or thinprovisioned disks during migration as long as the destination is not an NFS datastore. For physical
compatibility mode RDMs, you can migrate the mapping file only.
* Migration of virtual machines during VMware Tools installation is not supported.
* The host on which the virtual machine is running must have a license that includes Storage VMotion.
* ESX/ESXi 3.5 hosts must be licensed and configured for VMotion. ESX/ESXi 4.0 and later hosts do not
require VMotion configuration in order to perform migration with Storage VMotion.
* The host on which the virtual machine is running must have access to both the source and target datastores.
* A particular host can be involved in up to two migrations with VMotion or Storage VMotion at one time.
* vSphere supports a maximum of eight simultaneous VMotion, cloning, deployment, or Storage VMotion
accesses to a single VMFS3 datastore, and a maximum of four simultaneous VMotion, cloning,
deployment, or Storage VMotion accesses to a single NFS or VMFS2 datastore. A migration with VMotion
involves one access to the datastore. A migration with Storage VMotion involves one access to the source datastore and one access to the destination datastore.

The more applicable req is the 3rd to last bullet item. What VMware version do you have? It obviously sounds like you have the applicable license edition (Ent or Ent+). Also, I assume you want to move the VM's data while powered on? If that isn't necessarily a req, you can cold migrate it or use vCenter Converter to do so.

Hope that helps.

Regards,
~coolsport00

yes I did a cold migration. But even with a cold migration I thought it was not possible since the move is going from 1 competely separate storage array to another storage array.

Yes we have the license for storage migration. Virtual center is 4.1, 2 ESX host is 3.02 and 1 is 3.5

No, with cold migration, you can move the VM to wherever you'd like as long as all hosts are in vCenter (all hosts don't have to be in a cluster of shared storage). vCenter Converter does the same thing as cold migration in vCenter.

Regards,
~coolsport00

I assume that whatever storage I send it to the ESX host has to at least see the storage or it won't work correct?

Correct; another 'potential' issue in moving VM data to a different datastore between hosts of diff versions is file format (VMFS). But, since VMware kept the same format in 4.x as it had in 3.x, you're golden.

~coolsport00

Specifically, VMFS3 (not VMFS) :)

~coolsport00

here's one more question, if I have2 different blade cabinets with 2 different controllers and storage arrays can I do vmotion storage? As it is right now both cabinets are independent of each other and neither cabinet can see each the others storage array. But both cabinets are being managed by vcenter 4.1  and vcenter can see everything. I was told by a consultant that it's possible in front of my boss and I want to be sure before I say that it's not possible and look like an ass.

No...you have to be able to see the storage on all hosts involved in the VMotion process...1 of the requirements. But, you can of course do a cold migration. If this consultant can do it, I'd like to know how....just Google (or go to VMware's site to search) on VMotion requirements. You'll have all the "ammo" you need against this consultant. :)

Regards,
~coolsport00

The consultant was referring to cold migration of the datastore and from what I understand you can't do a cold migration from one data store to another neither unless the host can see each other's datastore. In my case since each cabinet is independent of the other, none of the hosts can see the other host's datastore. unless I can do a cold migratation from 1 datastore to the vcenter computer local storage back over another datastore.

Migration is a vCenter task, not host. VMotion DOES need the storage to be seen by every host in the migration process, but cold migration does not have that requirement.

~coolsport00

See: http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf, pg. 188

okay so in other words:

I have a vcenter that sees all the storage arrays in Cabinet A and Cabinet B

Cabinet A and all it's components does not see anything in cabinet B (and vice versa)

However if i shutdown a VM in cabinet A I can do a cold migration from whatever data store that the VM is on (in cabinet A) over to another Datastore on Cabinet B.

So basically if the above is correct then the consultant is correct

Yes, that is correct. So, if the consultant said that, then yes. Either you explained it wrong above, or my age is showing and I read it wrong :P hahaha

~coolsport00

Forget about all the above, here is all you need:

1) if you are licensed properly Storage Vmotion will move the vmdk files live, this requires enterprise licensing or VMware's 60 day trial licenses. This process is launched from vCenter Management server only.

2)  Cold migration can always be done with any licensing model, it requires downtime for the VM. This also requires vCenter management server.  

3)  If you don't have vCenter, this is now is about what brand of ESX you are running, service console version or ESXi.  

a.  if you have the service console install of ESX, use Veeam free utility fastSCP, nothing can migrate VMDKs faster, period.  you can also simply use native SCP in with the following syntax to move the VM folder and all its contents it just takes much longer (assuming you have navigated to VMFS volume where vm folder exists):  scp -r vmfolder_name%  remote_esx_server_name/path to vmfs volume      Then you need to log into ESX with vi client, browse datastore and right click .vmx file and select add to inventory (or register it from command line with proper syntax with used to be vmware-cmd –s register vm_name.vmx but I think its now esxcfg -s register)

b.  If you have ESXi, you have to enable remote support to connect with fastSCP or use SCP.  or you can browse the datastore and download the files with the download icon in the browse window and then once you've downloaded them to you workstation you can upload them to the new hosts \ datastore.  

So I have Vcenter 4.1,  so I can download all the files for my VM (vm is down) to the vcenter system and them upload them another datastore using Vcenter

You can, but you don't need to...VMwareGuy was just giving alternatives; you can do a cold migration as mentioned and you're good to go.

~coolsport00