I know - it depends. But assuming a storage array that is very up to the task (nowhere near fully utilized in terms of either throughput or IOPS) then how many storage vmotions can I hope to have going concurrently? Is there a defined limit like with standard vmotion? Can I start a bunch and just have the queue up, or do I need to baby-sit each one until I can begin the next?
Just curious - from a planning perspective. Will be doing this in the next couple weeks when new storage is online ...
You should check your Configuration Maximums guide for the version of ESX that you are using and do the math based on your cluster config and workload:
For Example, vSphere 5.1:
Concurrent Storage vMotion operations per datastore 8
Concurrent Storage vMotion operations per host 2