Executing Fault Recovery

Prerequisites

• You have logged in to the DR management system at the DR end.
• The management system and the DR environment at the DR site are working correctly.
• A recovery plan has been created in the system and the DR test has been completed.
• If storage devices or VMs on production site or DR site change, storage devices or VMs at the site where a protected group resides must be refreshed, for details, refer to Refreshing Resource Information.
• If the IP address of VM recovery is not configured, the IP address of VM is same to production end. If you wan to configure different IP address for executing fault recovery. After the recovery plan is created, you can configure IP address on the Protected Object tab page.
• If add or delete the disk in the protected VM or change datastore or lun before the Fault Recovery, refresh the VM and execute this protected group of protected VMs reside manually.

Context

If the recovery plan is based on the snapshot protection policy template, fault recovery cannot be performed.

In disaster recovery data center solution (geo-redundant mode) scenario, if production center becomes unavailable due to disasters, recover data from same-city DR center and the service is running on same-city DR center; if production center and same-city DR center become unavailable due to disasters, recover data from remote DR center and the service is running on remote DR center.

Precautions

If the active-standby DR solution and geo-redundant DR solution use two UltraVR servers, you must perform fault recovery on UltraVR at the DR site.

Procedure

1. On the menu bar, select Recovery.
2. Select the remote recovery plan for which you want to fault recovery and click More > Fault Recovery on the Operation list.

   The Fault Recovery dialog box is displayed.

3. Perform fault recovery.
   

   If Huawei multipath software has been installed on the Linux-based DR host, ensure the configured I/O hanging time is not 0 and all virtual devices generated by the software have corresponding physical devices. For more details, see the OceanStor UltraPath for Linux V100R008C00 User Guide.

   1. Select the cluster you want to recover.

      VMs will be recovered in the test cluster. Select DR Site.

      

      For a FusionSphere virtual machine (VM) protected group that uses host-based replication for DR, you can recover data using the latest data or snapshots.

   2. Optional: Select an available powered-on host.

      The available powered-on host can provide resources for VMs.

   3. Optional: Select non-critical VMs.

      In the Available VMs list, select non-critical VMs you want to stop to release computing resources.

      

      If the non-essential VM fails to be stopped, manually stop the VM on the FusionCompute management portal.

   4. Click Fault Recovery.
   5. In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.
   6. Click OK.

Result

After fault recovery starts, you can view the execution process and result. If the task is failed, you can solve the problem and execute the task again.

Follow-up Procedure

After executing fault recovery, the service is running in the DR sites. If original production sites reconstruct in non-site level (power failure and then power on) and the service is needed to switch to original production sites, execute the following steps:

1. Execute the operation of Executing Reprotection.

   Before switching service, executing reprotection can protects running data at the DR site and copy the service data as the specified protection policy in the DR sites during running to the original production sites.

2. Execute the operation of Testing a Recovery Plan.

   After executing reprotection, the service data, you need to test a recovery plan to verify the availability and ensure the service is switched successfully before data replicated to original production sites.

3. Execute the operation of Clearing Test Data.

   Delete the test data generated on the DR system and restore the DR environment to facilitate future switched DR.

4. Execute the operation of Executing Planned Migration.

   Executing planned migration, the service was migrated from DR sites to original production sites and the service is running in the production sites.

5. Execute the operation of Executing Reprotection.

   Ensure the in-plan and out-plan event occurs when service was switched to the original production sites and can be recovered in the DR sites, executing reprotection can protect the system service.

After the fault recovery is successfully executed, you can export the configuration file, and view information about the FusionCompute VMs before and after the fault recovery, such as resource mappings. To export the configuration file, perform the following steps:

1. Select the recovery plan used to perform the fault recovery and click the Protected Object tab in the lower area.
2. Click Export to save the exported configuration file locally.