Planned Migration of Services in the Production Center

Prerequisites

• The production and DR centers communicate with each other properly. The management system and the DR environment in the DR center are working normally.
• Recovery plans for services to be migrated have been created on UltraVR and succeed in at least one test.

If no DR test is performed before the planned migration, the migration has a higher rate to fail. A migration failure will interrupt DR services. For this reason, at least one recovery plan test must be executed successfully before the planned migration.

• If the information about storage devices or VMs is modified at the production or DR site, manually refresh the information. For details, see Refreshing Resource Information.

Context

Configure application-based protection policies for VMs to support one-click Planned Migration.

Procedure

1. Perform pre-migration configurations.
   • Without configuration, the VM IP address for planned migration is the same as that in the production center. You can configure one for planned migration on the Protected Object tab page of the recovery plan. For details, see Self-defining Startup Parameters for a Protected Object.
   • 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.

2. Perform the planned migration to migrate services from the production center to the DR center.
   1. On the menu bar, select Recovery.
   2. Select the recovery plan 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 xxx User Guide.

      

      For a FusionSphere VM protected group that implements host-based replication for DR, when its planned migration progress stays at Stop the VM for a long time, internal programs of the operating system may not be stopped. In this case, administrators can log in to FusionCompute, use VNC to log in to the VMs, troubleshoot faults, and then stop the VMs safely. If the fault persists, forcibly stop the VMs in FusionCompute. Note that a forcible shutdown may cause a planned migration failure. After stopping the VMs, select the protected group for the VMs on the Recovery page and click the Protected Object tab. On the tab page that is displayed, click Start and select Consistency verification to synchronize data. Then, perform the planned migration again.

   4. Click OK.

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

4. Check the environment before starting 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.

5. Perform reprotection to protect services switched to the DR center.

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

   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.

Result

After the reprotection is complete, the protected groups become normal.