vMotioning Protected VM to different Cluster - Will SRM auto reconfigure the Compute/Datastore changes?

[Peter Tosney]

Hi All,

I've recently been tasked with creating a new ESX Cluster and moving across all our Production VMs to that cluster, which is working fine from a vMotion perspective, eg all Datastores are visible to all Hosts and the same from the Networking aspect, however I was wondering if anyone can confirm that my Protected Production VMs, in SRM, will automatically have their DR counterparts/placeholders updated to reflect that their Datastore "source" has consequently changed etc? Or will I need to manually "reconfigure" the Replication instance/s for each VM that is SRM Protected once its been moved to the new Cluster?

Any advice or info would be greatly appreciated.

(vCenter v8.0.3 and SRM 9.x are in use btw)

Thanks,

Pete

[David Nixon]

In my testing, since it's on the same protected datastore, the failover plan will still work since the source doesn't matter.  However, you will not be able to fail back to the correct location.  After creating new resource mappings, you should unprotect and reproject the VMs so that the plans get rebuilt with the correct source and destinations.

------------------------------
-FrostByteVA
------------------------------

[Peter Tosney]

Hi, thanks for the reply :)

With the testing I performed, I received the attached error, however when I ignored the error and still went ahead with the vMotion, I found that it vMotioned successfully, however it kicked of an "Initial Sync" in SRM... so I guess there are little benefits to doing this other than not having to manually break the VM replication and protecting it back up again.