Please integrate Storage vMotion awareness with Replication. I just replaced the disk array that provides storage for one of my VMware 6.0 clusters. Rather than migrate a large number of TB of data between old and new disk arrays, I created new datastores on the new disk array and used Storage vMotion to move my replica VMs to those datastores. Everything seemed fine until my replication jobs started failing after trying to use the old datastore as a target and not finding it since I had deleted it.
I opened a case (02127298) and based on the info from the support engineers, found that I had to either remove the configuration information from the database and rerun the replication job using the low latency option for replica seeding or delete all of the replicas and rebuild as new so that it would recognize the new datastore name. (On a practical basis, it is massively faster to delete the replica(s) and rebuild as new due to the time required to process through the disk digests; however you do lose all of the historical restore points.)
This is terrible since it means that I can't dynamically adjust the replica datastore locations without having to go through a messy process of rebuilding the replicas and losing the replica restore points.