Building new datacenter. Will have all production VM's running at what will be DR site. We have SRM and are thinking of setting up replication from OLD site to NEW site. Once everything has been replicated and the delta's are managable we will shut down all running VM's. At that point we will run the DR plan with SRM. This should bring all the VM's up at the NEW site. From there we will have to reconfigure replication in the reverse direction, and reconfigure SRM for the other direction as well.
Anyone care to share any other ideas or past experiences?
Regards...
Jamie
If you found this information useful, please consider awarding points for "Correct" or "Helpful".
Remember, if it's not one thing, it's your mother...
Jamie,
Datacenter migrations are an excellent use case for SRM. I would recommend:
Setup protection to the new site as you would do for any DR setup
Test migrations to the new site using the test workflow as you would for any DR setup.
Refine the protection/recovery setups until you are happy with the test results.
During a scheduled downtime, actually run the recovery.
This process will do an automated shutdown of the production services as its first step
If your replication is async (as opposed to synchronous), place a message step after the "shutdown primary site VMs" step so that the recovery/migration pauses while you allow the writes to drain. Only after the storage tells you you are synched should you hit "continue" in the recovery plan. This will ensure no data loss with the migration.
After the failover setup protection to the old site
This part is not turnkey, but basically includes some teardown and setup of DR configuration.
See the "failback" chapter of the admin guide and eval guide which you would want to follow more or less exactly except for the part about actually executing the failback. It's the prep work you'll be looking for guidance for.
Hope this helps.
Thanks,
Jay
Jamie,
Datacenter migrations are an excellent use case for SRM. I would recommend:
Setup protection to the new site as you would do for any DR setup
Test migrations to the new site using the test workflow as you would for any DR setup.
Refine the protection/recovery setups until you are happy with the test results.
During a scheduled downtime, actually run the recovery.
This process will do an automated shutdown of the production services as its first step
If your replication is async (as opposed to synchronous), place a message step after the "shutdown primary site VMs" step so that the recovery/migration pauses while you allow the writes to drain. Only after the storage tells you you are synched should you hit "continue" in the recovery plan. This will ensure no data loss with the migration.
After the failover setup protection to the old site
This part is not turnkey, but basically includes some teardown and setup of DR configuration.
See the "failback" chapter of the admin guide and eval guide which you would want to follow more or less exactly except for the part about actually executing the failback. It's the prep work you'll be looking for guidance for.
Hope this helps.
Thanks,
Jay
Thanks Jay, I think the steps you outline are exactly what I was hoping for. It seems a very safe and documented process to do this. I will let you know how it turns out!!
Regards...
Jamie
If you found this information useful, please consider awarding points for "Correct" or "Helpful".
Remember, if it's not one thing, it's your mother...