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

To implement a DR drill, migrate services from an HyperMetro data center to the remote DR center based on the recovery plan.

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.
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.
In a DR Star network, before performing planned migration, log in to DeviceManager and ensure that the running status of the DR Star network is Enabled.
The datastore name cannot contain Chinese characters.

Precautions

If the storage device is OceanStor Dorado 6.x and the networking is HyperMetro (NAS) + asynchronous replication (NAS), and multiple protected groups share the same HyperMetro domain, after planned migration is performed for any protected group, planned migration cannot be performed for other protected groups.

Context

During a planned migration, services in an HyperMetro data center are migrated to the DR center by one click after the HyperMetro data center stops working. Then reprotection is performed for the services. 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 switched back to it.

You are advised to configure application-based protection policies for Oracle, SQL Server, DB2, VMware vSphere VMs, FusionCompute VMs and NAS File System to support one-click Planned Migration.
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 customized scripts to start and test the applications.
Figure 1 shows the state of data replication between storage arrays before the planned migration.

Figure 1 Data replication before the planned migration

Procedure

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.
    1. 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 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.
Perform planned migration.
1. On the menu bar, select Utilization > Data Restore.
2. Select the recovery plan used to perform the planned migration and click More > Planned Migration on the Operation list.
3. Perform the planned migration based on protected objects.
  
  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 protected object type is Oracle, IBM DB2, or Microsoft SQL Server, perform the following operations:
    1. Select DR Site.
    2. Select Available DR Hosts or Host Groups.
      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:
    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 to the recovery cluster. Select DR Site, DR vCenter, and DR Cluster.
      
      Upon the first network recovery, you need to set the cluster information.
    1. 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.
    1. 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 HyperMetro (NAS) and asynchronous(NAS) replication DR solution is deployed, you need to set Access Settings.
    1. Stop non-critical VMs when executing recovery.
      In the Available VMs list, select non-critical VMs to stop them to release computing resources.
    2. Click Planned Migration.
  - If the protected object type is FusionCompute VM, stop services at the active-active sites and migrate services to the remote DR center. Figure 3 shows the status of data replication between storage arrays after the migration.
    Figure 2 Data replication after the planned migration
    The procedure is as follows:
    1. Select the cluster you want to recover.
      VMs will be recovered to the 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, 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. Then click OK.
    Stop services in the active-active data center and migrate them to the remote DR center. Figure 3 shows the status of data replication between storage arrays after the migration.
    
    Figure 3 Data replication after the planned migration
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.
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.

In HyperMetro (NAS) and asynchronous replication (NAS) scenarios, the reprotection operation is not supported delete data after migration.

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.
Check the environment before perform reprotection.
- Databases:
  Ensure that underlying storage links, remote replication pairs, and consistency groups have been recovered.
- 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.
- 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 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.
  NAS file system:
  
  Ensure that underlying storage links and remote replication have been recovered.
Perform reprotection to protect services migrated to the remote DR center.
After the planned migration is complete, the service system is working in the remote DR center and protected groups become Invalid. You must perform reprotection to recover the replication relationship between the remote DR center and the HyperMetro data center 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 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 through a planned migration, perform the following steps 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. Log in to the in the vCenter server at site A using vSphere Client. In the Storage list, right-click storage devices and select Rescan All from the drop-down list one by one, to ensure that no residuals exist on ESXi hosts in the cluster where the migrated VMs reside.
  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.
  
  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

Figure 4 shows the state of data replication between storage arrays after the reprotection.

Figure 4 Data replication after the reprotection