Performing Planned Service Migration from an HyperMetro Data Center to the Remote DR Center

Prerequisites

• Recovery plans have been created for protected groups.
• Data has been tested and the data generated during tests has been cleared in the remote DR center.

Context

During planned migration, services in a HyperMetro data center are migrated to the DR center by one click after services of the HyperMetro data center are stopped. Then the services that are migrated to the DR center are reprotected. Planned migration must be implemented if data or applications in the HyperMetro data center need to be migrated to the DR center due to non-disaster reasons, such as power failure, upgrade, or maintenance. After the HyperMetro data center recovers, the services must be migrated back to it. You are advised to configure application-based protection policies to support planned migration by one click.

Procedure

1. Perform planned migration.
   1. On the menu bar, select Recovery.
   2. Select the recovery plan used to perform the planned migration and click More > Planned Migration on the Operation list.
   3. 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.
      

      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.

   4. Click OK.

2. After the migration is complete, verify that applications are started and data is consistent in the remote DR center.

   After the planned migration is complete, check whether the applications and data are normal. If an application or data encounters an exception, contact Huawei technical support.

3. Check the environment before starting the reprotection.
   • FusionCompute, FusionManager, storage devices, and VRGs at the production site are in the normal state, and the production site and DR site communicate with each other correctly.
   • In scenarios that uses storage array-based replication, ensure that storage configurations between the original production and DR sites are correct.
     • Ensure that all underlying storage units corresponding to protected groups have remote replication pairs.
     • Ensure that all remote replication pairs have secondary LUNs that belong to storage devices at the original production site.
     • If there are multiple remote replication pairs, they must belong to the same consistency group.
   • 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 in time.
   • Before reprotection, refresh storage resources and FusionCompute resources at the production and DR ends.

4. Perform reprotection to protect services migrated to the remote DR center.

   After you complete the planned migration, the service system is working in the remote DR center and protected groups become Invalid. You must perform reprotection to recover the replication status and synchronize data from the remote DR center to the HyperMetro data 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.

   1. On the menu bar, select Recovery.
   2. Select the recovery plan and click More > Reprotection on the Operation list.
   3. Carefully read the content of the Confirm dialog box that is displayed and click OK to confirm the information.
   

   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.