Testing a Recovery Plan

Prerequisites

• You have logged in to the UltraVR as a user with DR management permission.
• The production site and DR site communicate with each other correctly. The management system and the DR environment at the DR site are working correctly.
• At least one recovery plan has been created in the system.
• If verify the availability of data replicated to the DR site, a normal remote replication relationship has been established between the storage device in the production site and that at the DR site.
• The recovery plan's status is Ready, Reprotection completed, or Clear completed.
• If storage devices, hosts 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 application data is automatically replicated by the storage systems instead of being replicated based on the timetable specified upon the creation of protected groups, you need to suspend the data replication when performing a disaster recovery test in case of a test failure. You can use either of the following methods to suspend data replication in the device management software:
  • If the status of the remote replication pair for the protected applications is synchronized and data is consistent, split the remote replication to stop data replication.
  • Configure the replication policy of the remote replication for the protected applications to manual synchronization.
• In host-based replication DR, a correct matching relationship has been established between the VRG in the production site and that at the DR site.
• In host-based replication DR, a consistency snapshot exists on the DR-end VM. (You can log in to the DR-end FusionCompute to view the snapshot.)
• If the network between production and DR end is not insulated. After the recovery plan is created, you need to configure different IP addresses for production and DR end recovery on the Protected Object tab page, ensure production service is normal for IP address conflict.
• If add or delete the disk in the protected VM, refresh the VM and execute this protected group of protected VMs reside manually.
• The test recovery plan operation will generate test data in the system of the DR site. Reserve sufficient space in the DR storage pool.

Context

In the DR test, snapshot mappings can be created only in starter mode and port mapping is not supported.

For a FusionSphere VM protected group using host-based replication DR, the VRG must be used by the host to synchronize the data in the production site to the DR site. An unsatisfactory DR state or a VRG process fault may cause snapshot loss.

• Prevent all the system and service administrators from performing other maintenance operations.
• Clear the test data after a test; otherwise, you cannot perform the next test.
• Clear the test data after the test is completed. If the network is disconnected or the UltraVR environment is closed on purpose during the test, some test data may fail to be deleted after the environment is restored and an automatic clearance command is delivered. When this happens, manually clear the data before you run the automatic clearance command.

Procedure

1. On the menu bar, select Recovery.
2. Select the recovery plan that you want to test and click Test on the Operation list.

   The Test dialog box is displayed.

3. Perform either of the following operations based on the protected object type.
   

   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 a cluster to be tested.

      VMs will be recovered in the test cluster. Set Test Site.

      

      Upon the first test network selection, you need to set the test cluster information.

   2. Select the test network.

      The network used for resource mapping is used for the test by default. You may choose another network based on the onsite conditions.

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

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

   4. 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.

   5. Click Test.
   6. 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.
   7. Click OK.

Result

After the test starts, you can view the execution process and result. Clear failed recovery plans. If the test is failed, you can solve the problem and execute the test again after clearing the test data.