If data or applications in the same-city DR center become unavailable due to disasters or faults, you must quickly recover the data or applications from the remote DR center.
Prerequisites
- LUN-based protection policies and recovery plans have been configured for other applications.
- For protected groups that use asynchronous remote replication, there is at least one copy of intact service data in remote DR center.
Context
When data or applications in the same-city DR center are abnormally stopped, services can be quickly started in the remote DR center. Figure 1 shows the state of data replication between storage arrays before the migration.
Procedure
- Log in to eReplication in the remote DR center.
- Perform a fault recovery.
If Huawei UltraPath has been installed on the Linux-based DR host, ensure that I/O suspension time is not 0 and all virtual devices generated by UltraPath have corresponding physical devices. For details, see the OceanStor UltraPath for Linux xxx User Guide.
- On the menu bar, select Utilization > Data Restore.
- Select the recovery plan used for fault recovery and click More > Fault Recovery on the Operation list.
- Perform fault recovery based on the protected object type.
- In the production center, check the application startup status.
After the fault recovery is complete, check whether the applications and data are normal. If an application or data encounters an exception, contact Huawei technical support.
- Note the following when checking the startup status of applications.
- If the protection policies are based on applications, check whether the applications are started successfully and data can be read and written correctly.
- If the protection policies are based on LUNs, you need to log in to the application host in the disaster recovery center, scan for disks, and start applications. Then check whether the applications are started successfully and data can be read and written correctly.
You can use self-developed scripts to scan for disks, start applications, and test applications.
Result
Figure 2 shows the state of data replication between storage arrays after the migration.
