Performing Planned Migration from the Intra-City DR Center to the Production Center

Prerequisites

• Planned migration and reprotection have been performed for the service system according to a recovery plan.
• The production host is working properly and the service system in the original production center is in the standby state.
• In the Oracle application, the database is disabled but the cluster is enabled by default on the eReplication Agent. If you need to disable clusters, modify the configuration of disabling clusters. For details, see Changing the Configuration of Stopping the Oracle Cluster.
• In a DR Star network, before performing planned migration, log in to DeviceManager and ensure that the running status of the DR Star network is Enabled.
• The datastore name cannot contain Chinese characters.

Procedure

1. On eReplication in the remote DR center, select a recovery plan used to perform a failback, test the recovery plan, and clear data generated during the test.

   Before the services are switched back, you need to perform a DR test to verify the data availability to ensure success rate of service failback. After the test, clear test data to avoid failback failures caused by the test data. For details, see DR Testing in the DR Center.

2. On eReplication in the same-city DR center, select recovery plans to be switched back, and perform a planned migration.

   This step aims to switch services back to the production center. After migration, data must be checked and test data must be cleared. For details, see 1 to 4 in Planned Migration from the Production Center to the Same-City DR Center.

   

   If the protected object type is LUN, Local File System, Oracle, IBM DB2, Microsoft SQL Server, SAP HANA, or Microsoft Exchange Server, select hosts or host groups in the production center as the recovery target.

   • If the protected object type is VMware VM, select vCenter and clusters in the production center as the recovery target.
   • If the protected object type is FusionCompute VM, select site in the production center as the recovery target.

3. On eReplication in the same-city DR center, select the recovery plans that have been switched back and perform reprotection.

   After you complete the planned migration, the application systems are working in the original production center and protected groups become Invalid. To ensure that the production center can be recovered from the DR center when an event (planned or unplanned) happens on it after failback, reprotection must be performed. The replication status from it to the same-city DR center must be established again to synchronize data and ensure services are protected. For details, see 5 to 6 in Planned Migration from the Production Center to the Same-City DR Center.

Result

After the reprotection is complete, the protected groups become normal. The solution network has been restored to the original state.