Planned Migration of Services in the Production Center

Prerequisites

• The production and DR centers 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 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, hosts, or VMs is modified at the production or DR site, manually refresh the information. For details, see Refreshing Resource Information.
• The datastore name cannot contain Chinese characters.

Context

• You are advised to configure application-based protection policies for Oracle, SQL Server, DB2, VMware vSphere VMs, FusionCompute VMs, NAS file systems, and SAP HANA. One-click planned migration is supported.
• In the Oracle application, the database is disabled but the cluster is enabled by default on the eReplication Agent. If you need to disable clusters, modify the configuration of disabling clusters. For details, see Changing the Configuration of Stopping the Oracle Cluster.
• You are advised to configure LUN-based protection policies for other applications to enable automatic Planned Migration configuration on the storage system. You need to manually or use self-defined scripts to start and test applications.

Procedure

1. Perform pre-migration configurations.
   • When the protected objects are databases, pre-migration configurations can be performed in the following two modes.
     • Method 1: Manually stop applications and remove mappings.
       1. Manually stop the service system and database applications and uninstall disks on the production host.
       2. Delete LUN mappings (to application hosts at the production sites) from the storage array in the production center.
          

          • For the SQL Server cluster, you need to set the disks in the cluster to Maintenance mode and then remove the LUN mapping.
          • In the asynchronous replication scenario of the HANA database, you need to log in to the database to create a snapshot for restoring the database before stopping the service system and database applications. For details, see Creating a HANA Snapshot File.
       3. Log in to eReplication and refresh the production storage status at the site under Resources to ensure that LUN mappings have been removed.
     • Method 2: Edit the planned migration procedure. During planned migration, applications are stopped and mappings are removed by default. You can determine whether to stop applications and remove mappings as required.
       1. Log in to eReplication. On the menu bar, choose Utilization > Data Restore.
       2. Select the recovery plan that you want to execute and click the Procedure tab.
       3. Click Edit.
       4. Select Planned Migration from the drop-down list.
       5. Click Stop production service and determine whether to enable this step based on the site requirements.
       6. Click Apply.
   • When the type of protected objects is the FusionCompute VM, perform the following configurations:
     • Without configuration, the VM IP address for the planned migration is the same as that in the production center. You can configure one for the 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.
   • When the type of protected objects is VMware VMs, perform the following configurations:
     • Without configuration, the VM IP address for the planned migration is the same as that in the production center. You can configure one for the planned migration on the Protected Object tab page of the recovery plan. For details, see Self-defining Startup Parameters for a Protected Object.
     • When the asynchronous replication (NAS) DR solution is deployed, you need to create a share and configure permissions on DeviceManager of the storage array at the DR site. Permissions must be the same as those in the production center.
       

       If you fail to create a share and configure permissions, the planned migration will fail.

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

      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.

      • If the type of protected objects is LUN, Local File System, Oracle, IBM DB2, Microsoft SQL Server, SAP HANA, or Microsoft Exchange Server, perform the following operations:
        1. Select DR Site.
        2. Select Host (Group) > Available DR Hosts or Host Groups (This operation is optional when the protected object type is LUN).
           

           • If the storage array used at the DR site is flash storage 6.1.6 or later, the to-be-recovered host selected by a user can belong to only one host group on the storage array, and the host group can belong to only one mapping view. In addition, the remote replication secondary LUN corresponding to the storage LUN used by the protected application and the LUN to which the redo logs and archive logs of the DR cluster belong must belong to the same LUN group, and the LUN group and the host group must belong to the same mapping view. If the storage array version is flash storage 6.1.6 or later, deselect Enable Inband Command to change the mapping view attribute after the mapping view is created.

           • If the storage array is flash storage 6.1.6 or later, automatic host adding and storage mapping are provided. Ensure that the storage is connected to hosts' initiators properly. In this manner, the system can automatically create hosts, host groups, LUN groups, and mapping views on the storage. The creation principles are as follows:

             

           • If no DR host or DR host group is selected, you need to manually map DR LUNs to the DR host when the type of protected objects is LUN.
        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.
        5. Click OK.
      • If the type of protected objects is VMware VM, perform the following steps:
        1. Select a recovery cluster.

           VMs will be recovered in the recovery cluster. Select DR Site, DR vCenter, and DR Cluster.

           

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

        2. Select a recovery network.

           The recovery network is used to access recovered VMs.

           

           • If Production Resource and DR Resource are not paired, select Production Resource and DR Resource, and click Add to the mapping view to pair them.
           • If Keep the mac unchange is selected, the system checks whether the MAC addresses of production VMs conflict with those of all VMs in the DR vCenter. If the MAC addresses do not conflict, the system retains the MAC addresses of the VMs in the DR vCenter. Otherwise, the recovery task fails.
           • If Keep the mac unchange is not selected and the mounted VM is stopped, the MAC address of the VM mounted to the vCenter remains unchanged. After the VM is started, vCenter automatically assigns a MAC address to the VM.
        3. Access settings.

           Set Logical Port IP Address to recover hosts in the cluster to access DR file systems over the logical port.

           

           In scenarios where the asynchronous replication (NAS) DR solution is deployed, you need to set Access Settings.

        4. Stop non-critical VMs when executing recovery.

           In the Available VMs list, select non-critical VMs to stop them to release computing resources.

        5. Click Planned Migration.
        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.
      • If the protected object type is FusionCompute VM, perform the following steps:
        1. Select the cluster you want to recover.

           VMs will be recovered in the recovery cluster. Select DR Site.

        2. Select an available powered-on host.

           The host will provide resources for VMs.

        3. Select non-critical VMs.

           In the Available VMs list, select non-critical VMs you want to stop to release computing resources.

        4. Click Planned Migration.
        5. 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.
        6. Click OK.
        7. Wait until the migration progress reaches the step of Delete Production VM.
        8. Check application startup and data consistency in the DR center.
           

           If the application or data is abnormal, click Run and then Stop. Contact Huawei technical support for subsequent processing.

           • Note the following when checking application startup.
             • 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 DR centers. If the last entry of data is the same, the data consistency is ensured.
        9. If the applications and data at the DR site are running properly, click Run.
        10. Carefully read the contents of the Warning dialog box. Then click the check box next to the statement I have read and understand the consequences associated with performing this operation to confirm the information.
        11. Click Continue to complete the subsequent operations.
            

            After you click Continue, if the production VM fails to be deleted, you cannot pause the planned migration again.

        12. Wait until the migration is complete.
      • If the protected object type is NAS file system, perform the following operations:
        1. Carefully read the contents of the Warning dialog box. Then click the check box next to the statement I have read and understand the consequences associated with performing this operation to confirm the information.
        2. Click OK.

3. 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 DR centers. If the last entry of data written to the production and DR centers is the same, the data consistency is ensured.

4. 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 following naming 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.
   • When the protection type is SAP HANA, you do not need to clear the data after the planned migration is complete.

5. Check the environment before starting reprotection.
   • Databases:

     Ensure that underlying storage links, remote replication pairs, and consistency groups have been recovered.

   • FusionCompute VMs:
     • Ensure that the FusionCompute storage status at the original production site is normal and the communication between the original DR site and the original production site is normal.
     • In scenarios that use 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.
   • VMware VMs:
     • Ensure that underlying storage links, remote replication pairs, and consistency groups have been recovered.
     • On the original production array, unmap the volumes corresponding to the applications to be restored.

6. 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. After performing reprotection, reconfigure the protection and recovery policies to ensure that DR services are running properly.
   • If you choose to retain the user configuration data, the self-defined protection policy and recovery settings, such as the self-defined recovery procedure, will be retained. Ensure that the configuration data has no adverse impact on service running after reprotection.
   1. On the menu bar, select Utilization > Data Restore.
   2. Select the recovery plan and click More > Reprotection on the Operation list.

      If the protected objects are VMware VMs and services are recovered from site A to site B through a planned migration, perform the following operations to clear redundant and incorrect data in the virtualization environment before and after the reprotection.

      1. If reprotection was performed, use vSphere Client to log in to vCenter at site B. Click Storage list, and click Rescan All of storage devices one by one, to ensure that no datastore exists on ESXi hosts. Otherwise, skip this step.
      2. On eReplication, perform reprotection.
      3. Use vSphere Client to log in to the vCenter server at site A. On the Storage tab page of all ESXi hosts in the cluster where the migrated VMs reside, click Rescan All to ensure that no residual datastore information exists on the ESXi hosts.
      4. Return to eReplication, and update vCenter servers and storage resources of site A to obtain the latest VM environment information.
   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.