Performing Planned Failback of Services in the Remote DR Center

After services are migrated from an HyperMetro data center to the remote DR center through planned migration, the services must be migrated back to the HyperMetro data center based on a DR testing plan.

Prerequisites

Planned migration and reprotection have been successfully performed for service systems according to a recovery plan.
The production hosts are working properly and the service system in the original production center is in the standby state.
If the information about storage devices, hosts, or VMs is modified at the production or DR site, manually refresh the information. For details, see Refreshing Resource Information.
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.

Context

Figure 1 shows the state of data replication between storage arrays before failback.

Figure 1 Data replication before failback

Procedure

In HyperMetro (SAN) and asynchronous replication (SAN) scenarios, you can use eReplication to migrate back services as follows:
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 services are migrated back, perform a DR test to verify data availability to ensure service failback success rate. After the test, clear test data to avoid failback failures caused by the test data. For details, see DR Testing.
2. On eReplication in the remote DR center, select the recovery plan to perform a planned migration.
  Migrate services back to the HyperMetro data centers. After the migration, check data and clear test data. For details, see 1 to 4 in Performing Planned Service Migration from an HyperMetro Data Center to the Remote DR Center.
  - When the protected object type is Oracle, IBM DB2, or Microsoft SQL Server, select hosts or host groups in the original production center as recovery targets.
  - If the protected object type is VMware VM, select vCenter and clusters in the original production center as recovery targets.
    You can select Synchronize HyperMetro to enable HyperMetro synchronization.
  Figure 2 shows the state of data replication between storage arrays after the migration.
  
  Figure 2 Data replication after the migration
1. On eReplication at the remote DR center, select the recovery plan and perform reprotection.
  After the planned migration is complete, application systems are working in HyperMetro data centers and protected groups become Invalid. To ensure that services migrated back to the original HyperMetro data centers can be recovered at the remote DR center after an event (planned or unplanned) happens, reprotection must be performed and the replication status from HyperMetro data centers to the remote DR center must be recovered to synchronize data generated at the HyperMetro data centers to the remote DR site and to ensure that services are protected. For details, see 5 to 6 in Performing Planned Service Migration from an HyperMetro Data Center to the Remote DR Center.
  
  Figure 3 shows the state of data replication between storage arrays after the reprotection.
  
  Figure 3 Data replication after the reprotection
1. Ensure that communication among sites is normal.
  1. Log in to the storage array management software at active data center B, and ensure that the status of the HyperMetro pair between active data center B and active data center A is normal and that asynchronous replication links between active data center B and site C are normal.
  2. Log in to eReplication at active data center B, and ensure that status of HyperMetro (SAN) and asynchronous replication (SAN) protected groups is normal and the topology structure has been restored to the original networking status.
In HyperMetro (NAS) and asynchronous replication (NAS) scenarios, you can use eReplication to migrate back services as follows:
1. On eReplication in the remote DR center, select the recovery plan to perform a planned migration.
  Migrate services back to the HyperMetro data centers. After the migration, check data and clear test data. For details, see 1 to 4 in Performing Planned Service Migration from an HyperMetro Data Center to the Remote DR Center.
  
  Figure 4 shows the state of data replication between storage arrays after the migration.
  
  Figure 4 Data replication after the migration
1. On eReplication at the remote DR center, select the recovery plan and perform reprotection.
  After the planned migration is complete, application systems are working in HyperMetro data centers and protected groups become Invalid. ensure that services migrated back to the original HyperMetro data centers can be recovered at the remote DR center after an event (planned or unplanned) happens, reprotection must be performed and the replication status from HyperMetro data centers to the remote DR center must be recovered to synchronize data generated at the HyperMetro data centers to the remote DR site and to ensure that services are protected. For details, see 5 to 6 in Performing Planned Service Migration from an HyperMetro Data Center to the Remote DR Center.
  
  Figure 5 shows the state of data replication between storage arrays after the reprotection.
  
  Figure 5 Data replication after the reprotection
1. Ensure that communication among sites is normal.
  1. Log in to the storage array management software at active data center B, and ensure that the status of the HyperMetro pair between active data center B and active data center A is normal and that asynchronous replication links between active data center B and site C are normal.
  2. Log in to eReplication at active data center B, and ensure that status of HyperMetro (NAS) and asynchronous replication (NAS) protected groups is normal and the topology structure has been restored to the original networking status.