If data or applications in the production center become unavailable due to disasters or faults, quickly recover the data or applications from the DR center. Before a fault recovery, at least one recovery plan test must be executed successfully. This operation can be performed only on UltraVR in the DR center.
If data or applications become unavailable due to disasters or faults in the production center, services will be quickly switched to and started in the DR center. After the production center recovers, the services will be switched back to it by performing planned migration.
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 V100R008C00 User Guide.
For protected groups of FusionCompute VMs that use host-based replication for DR, you can recover data using the latest data or snapshots.
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.
After the planned migration is complete, the application system is working at the DR site and protected groups become Invalid. You must perform reprotection to recover the replication status and synchronize the data from the DR site to the production site. Then, the original DR center becomes the new production center.
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, re-configuration of protection and recovery policies is recommended to ensure the continuity of DR services.
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.