If a fault occurs in the HyperMetro data center, the fault can be rectified and cannot be rectified based on the original configuration. The corresponding DR switchback operations are different.
- Case 1: If a recoverable disaster (such as unexpected power failure) occurs in the HyperMetro data center, rectify the fault based on the original configuration. After the fault is rectified, the storage and service hosts can still run properly. In this case, you need to perform active/standby switchover and data synchronization on the DR center, and then perform a reprotection task to switch the data protection direction from the DR center to the HyperMetro data center. Then, migrate services from the DR center back to the HyperMetro data center.
- Case 2: If the HyperMetro data center cannot be recovered based on the original configuration, rebuild the data center. After the HyperMetro data center is rebuilt, delete the original protection task from eReplication, reconfigure the DR relationship between the DR center and the HyperMetro data center, and perform planned migration to switch services to the HyperMetro data center. After the planned migration is complete, you need to perform reprotection to reset the replication relationship, that is, data is replicated from the HyperMetro center to the DR center. In this way, DR protection is provided for production services again. This section describes how to migrate services back in Case 1. For case 2, contact Huawei technical support to provide a detailed technical solution.
After HyperMetro data centers recover from a fault, services will be migrated back to them.
Prerequisites
- Application-based protection policies and recovery plans have been configured for database applications and FusionSphere deployed on physical machines.
- LUN-based protection policies and recovery plans have been configured for other applications.
- For protected groups that use asynchronous remote replication, the DR center has at least one copy of intact service data.
- The fault recovery has been successfully executed based on the recovery plan on the original DR center.
In the Oracle application, the cluster is not stoppd by default. To stop the cluster, you need to open the configuration for stopping the cluster and then perform the next step. For details about how to stop the cluster, see 4.2 Stopping the Oracle Cluster.
Procedure
- Check the environment before starting the reprotection.
- Log in to a service host in a HyperMetro data center and stop services. Manually stop applications in the HyperMetro center and unmount host disks. Then log in to the storage array management software of the HyperMetro data center, and remove mappings of LUNs used by applications from hosts.
- Suspend HyperMetro pairs of storage arrays in the HyperMetro data centers.
- Perform reprotection to protect services migrated to the remote DR center.
After the fault recovery is complete, the application system is working at the remote DR site and protected groups become Invalid. You must perform reprotection to recover the replication status and synchronize data from the remote DR center to the HyperMetro data centers.
To ensure the normal running of protected groups and recovery plans after reprotection, the system automatically clears protected and recovered configurations, including startup configurations of protection policies and recovery plans, self-defined execution scripts, and self-defined execution steps. In addition, reconfiguration of protection and recovery policies is recommended to ensure the continuity of DR services.
- On the menu bar, choose
Utilization > Data Restore. - Select the recovery plan and click More > Reprotection on the Operation list.
- Carefully read the content in the Confirm dialog box that is displayed and click OK to confirm the information.
If Save user configuration data is selected, self-defined protection policies and recovery settings, such as self-defined recovery steps, will be retained. Ensure that the configuration data has no adverse impact on service running after reprotection.
- On the menu bar, choose
- Test recovery plans and clear data generated during tests.
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 Test/Clearance.
Log in to the storage in the DR center and perform an active/standby switchover on the remote replication or consistency group that is in split status.
- Perform planned migration.
Migrate services back to the HyperMetro data centers. After the migration, check data and clear test data. For details, see 1 to 3 in Performing Planned Service Migration in a HyperMetro Data 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.
- You can select Synchronize HyperMetro to enable HyperMetro synchronization.
- Perform reprotection again.
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 4 to 5 in Performing Planned Service Migration in a HyperMetro Data Center.