Performing Planned Failback of Services in the Remote DR Center

After services are switched from the production center to the DR center through planned migration, the services must be switched back to the production center based on a drill plan.

Prerequisites

Procedure

  1. Test the recovery plan and clear the test data on eReplication.

    Before the services are switched back, you need to perform a DR test to verify the data availability to ensure that services can be switched back successfully. After the test, you must clear the test data to avoid switchback failure caused by test data. For details, see DR Test/Clearance.

  2. On eReplication of the DR center, perform a planned migration.

    This step aims to switch services back to the production center from the DR center. After the migration, check the data and clear the test data. For details, see 1 to 3 in Performing Planned Service Migration in a HyperMetro Data Center.

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

  3. Perform reprotection on eReplication at the DR center. After planned migration, the application system is working in the 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 switchback, reprotection must be performed and the replication status from it to the DR center must be established again to synchronize data and ensure services are protected. For details, see 4 to 5 in Performing Planned Service Migration in a HyperMetro Data Center.

Result

After the heavy protection execution is complete, the protection group state automatically returns to normal.


Copyright © Huawei Technologies Co., Ltd.