Performing Planned Service Migration in a Production Center

Prerequisites

• The production and remote DR center communicate properly. The management system and the DR environment in the DR center are working properly.
• Recovery plans for services to be migrated have been created on eReplication, which have succeeded 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.
• In the Oracle application, the cluster is not stoppd by default. To stop the cluster, you need to open the configuration for stopping the cluster and then perform the next step. For details about how to stop the cluster, see 4.2 Stopping the Oracle Cluster.

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

Context

You are advised to configure application-based protection policies for Oracle, SQL Server, DB2, SAP HANA, streamlining the Planned Migration to only a few clicks.

During planned migration, the original backup policy of CDM becomes invalid and the production data is not backed up. After the DR drill is complete, services are switched back to the original roduction center. The original backup policy takes effect. Figure 1 shows the planned migration.

Figure 1 Planned migration

Procedure

1. Perform the planned migration to migrate services from the production center to the DR center.
   1. On the menu bar, choose Utilization > Data Restore.
   2. Select the recovery plan and click More > Planned Migration on the Operation list.
   3. Perform the planned migration.
      

      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.

      1. Select a DR site.
      2. Select a DR host or host group.
      3. Click Planned Migration.
      4. 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. Click OK.
         

         If the policy of the local end is a second policy, the timing snapshot schedule will be suspended when you perform planned migration.

2. After the migration is complete, verify that applications are started and data is consistent in the 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.

   • Note the following when checking the startup status of applications.
     • If the protection policies are based on applications, check whether the applications are started successfully and data can be read and written correctly.
     • If the protection policies are based on LUNs, log in to the application host in the DR center, scan for disks, and start applications. Then check whether the applications are started successfully and data can be read and written correctly.
       

       You can use self-developed scripts to scan for disks, start applications, and test applications.

   • You can check data consistency by viewing the last entry of data written to the production and Remote DR center. If the last entry of data written to the production and Remote DR center is the same, the data consistency is ensured.

3. Delete data after migration.

   If storage array-based remote replication DR is used, snapshots are created automatically on the storage array at the DR site to back up DR data during the planned migration. If snapshots are not automatically deleted after the planned migration is complete, manually delete them to release storage space.

   

   A snapshot name is a string of 31 characters named in the following format: DRdata_LUNID_YYYYMMDDHHMMSS_BAK, where YYYYMMDDHHMMSS is the backup time and LUNID may be the snapshot ID (a number ranging from 1 to 65535). This naming format enables you to quickly find the snapshots that you want to delete from the storage array at the DR site.

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.

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 Utilization > Data Restore.
   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.

Result

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