DR Testing

Prerequisites

• The production center communicates with the same-city and remote DR centers properly.
• At least one recovery plan has been created on UltraVR.
• If storage array-based replication is used for DR, remote replication secondary LUNs of the recovery plan have been mapped to VMs at the DR site.
• If networks of the production site and DR site are not isolated, you can configure different recovery IP addresses for test VMs and production VMs on the Protected Object tab page to avoid IP address conflicts and ensure service continuity at the production site.
• After adding or removing disks for a protected VM, refresh the information about the VM and manually enable DR for the protected group where the VM resides.
• If application data is automatically replicated by storage arrays instead of being periodically replicated based on the schedule specified upon the protected group creation, the data replication must be stopped before you start the DR test to prevent a possible test failure. You can use either of the following methods to stop array-based replication on the device management software:
  • When the remote replication pair for the protected applications is in synchronized state and the data is consistent, split the remote replication pair.
  • Change the remote replication policy to manual synchronization for the protected applications.
• If the information about storage devices or FusionCompute VMs is modified at the production or DR site, manually refresh the information. For details, see Refreshing Resource Information.

Context

Data test in the DR center is used to verify data availability. You are advised to configure application-based protection policies to support tests by one click.

In a DR test, snapshots at the DR site can only be mapped to the initiators. The port mapping mode is not supported.

Procedure

1. Log in to Fibre Channel switches one by one, check the information about each Fibre Channel port, and calculate the BER. If the BER is larger than 0.1%, check links and rectify link faults.

   BER = Total number of errors/(In bytes + Out bytes) x 100%

   

   A large BER may result in a remote replication failure in a specified window or an unexpected remote replication disconnection.

   

2. Log in to the UltraVR DR management server in the remote DR center.
3. Test a recovery plan.
   1. On the menu bar, select Recovery.
   2. Select the recovery plan to be tested, and click Test on the Operation list.
      

      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.

   3. Select a test network.

      The default test network is the network for resource mapping. If you want to change the default network, plan or select another network based on site requirements.

   4. Click Test.

4. After the test is complete, verify that applications are started in the remote DR center.

   Verify that applications are started and accessed successfully. If an application fails to be started or cannot execute read and write operations, contact Huawei technical support.

5. The test data generated at the DR site needs to be cleared and resources need to be restored to the status before the test to facilitate future DR or planned migration.
   

   • If the protected groups are FusionCompute VMs and deleting storage fails during test data clearing, check whether non-DR VMs or disks exist on the datastore. If non-DR VMs or disks exist, migrate or delete them from the datastore.
   • If the information about storage devices or FusionCompute VMs is modified at the production or DR site, manually refresh the information. For details, see Refreshing Resource Information.
   1. Select the recovery plan whose data needs to be cleared, and click More > Clear on the Operation list.
   2. Click OK.