I'm using move-vm for storage vmotions. Assuming I don't hit the limits in this post at the host level or datastore level,
vSphere 5.5 Documentation Center
Are there any limits at the vCenter level to how many simultaneous svMotions can be performed?
what is the best way to maximize the concurrent svmotions using powercli?
Not on the vCenter level afaik, but there are svMotion limitations on the host and datastore level.
See the KB1003497 for links to the Configuration Maximums Guides for different vSphere versions
vSphere itself will handle these limits, so you could launch multiple svMotions, and the system will limit the maximum of active svMotion tasks.
You could also launch these svMotion tasks in the background (use the -RunAsync switch).
And handle the maximum active jobs in your script.
You can use the Get-Task cmdlet to query the background tasks.
There are multiple examples of such scripts available in this community.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Not on the vCenter level afaik, but there are svMotion limitations on the host and datastore level.
See the KB1003497 for links to the Configuration Maximums Guides for different vSphere versions
vSphere itself will handle these limits, so you could launch multiple svMotions, and the system will limit the maximum of active svMotion tasks.
You could also launch these svMotion tasks in the background (use the -RunAsync switch).
And handle the maximum active jobs in your script.
You can use the Get-Task cmdlet to query the background tasks.
There are multiple examples of such scripts available in this community.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
thanks again!