Storage Vmotion question

[lucheman]

Hello -

Can somebody provide me with a high level overview of what needs to be done in order to perform a storage vmotion?

Thanks Guys,

[saunders]

From what I understand, you just need two things. Your Vmotion needs to be working completely fine, and you need to have to visible data stores for your data. As long as the ESX host server can "see" both data stores, the Virtual Center should be able to Storage Vmotion the VM without a problem.

[dominic7]

And it's currently only supported for FC LUN -> FC LUN moves, requires the use ot the remote command line and suffers from a couple of bugs:

http://kb.vmware.com/selfservice/dynamickc.do?externalId=1003874&sliceId=1&command=show&forward=nont...

[thickclouds]

you should check out the remotecli appliance. there are some great perl scripts to help with it. let me know if you want me to send some.

[thickclouds]

oh by the way - we suffred the bug in the above link as well...

[lpenrod]

We were hit by the bug too.

[hugopeeters]

I'va just found out the hard way that you need to have sufficient free space on your destination ánd source datastores.

I had insufficient space on one source datastore. I received the error: insufficient space for the redo log on <datastore>: Abort / Retry. Upon clicking abort, the VM was powered down! Storage VMotion of the other disks is still in progress.

[ruffy]

Do I have to configure something special for Storage VMotion?

I have only 3.5 hosts, but only when a VM is powered off, I have the chance to migrate it to another datastore. Although I have only FC LUNS and every host can access avery LUN.

Is there a setting at "Advanced Settings" I have to set?`

Best regards

[Roman_Romano]

Storage Vmotion is not performed via the Virtual Infrastructure Client. As mentioned earlier you need to use the Remote Command Line Interface (rcli). Install that and execute the svmotion.pl script