Performing Planned Migration

Prerequisites

• You have logged in to the eReplication as a user with DR management permission.
• The production site and DR site communicate with each other correctly. The management system and the DR environment at the DR site are working correctly.
• At least one recovery plan has been created in the system.
• In the geo-redundant DR solution, before performing planned migration in a DR Star network, log in to DeviceManager and ensure that the running status of the protected group on the DR Star network is Enabled.
• Storage devices, hosts, or VMs at the site where a protected group resides have been refreshed, if storage devices, hosts, or VMs at the production site or DR site change. For details, see Refreshing Resource Information.
• 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.

The following table describes requirements for each protected object type.

Context

If the VM where the production site resides is configured with an IP address but without any network adapter, after the planned migration, the IP address of the VM where the DR site resides is:

• Windows
• Dynamically obtained when VM specifications already configured.
• Consistent with that of the VM where the production site resides when VM specifications not configured.
• Linux

  Dynamically obtained.

If you do not perform at least one successful DR test before planned migration, the failure probability of the planned migration will increase, and planned migration failure will stop the running of DR services. Therefore, before performing planned migration, you are advised to perform at least one successful DR test.

If the recovery plan is based on the snapshot or clone protection policy template, planned migration cannot be performed.

The time spent on planned migration is related to the data volume. Larger data volume indicates longer time.

In DR DC solutions (geo-redundant mode), services can be migrated from the production center to the same-city or remote DR center.

Procedure

1. On the menu bar, select Utilization > Data Restore.
2. Select the remote recovery plan for which you want to perform planned migration and click More > Planned Migration on the Operation list.
3. Perform planned migration based on the protected object type.
   

   If Huawei multipathing software has been installed on the Linux DR host, ensure the configured I/O suspension time is not 0 and all virtual devices generated by the software have corresponding physical devices. For details, see the OceanStor UltraPath for Linux xxx User Guide.

   • If the protected object type is LUN, Local File System, Oracle, IBM DB2, Microsoft SQL Server, FusionCompute VM, or Microsoft Exchange Server,SAP HANA, perform the following:
     1. When the protected objects are databases, manually close applications running at the production site, ensure disks are in the offline state, and unmap LUNs relevant to the applications from production storage arrays. Alternatively, you can customize the planned migration procedure to enable the Stop production service step.
     2. Select DR Site.
     3. Select Host (Group) > Available DR Hosts or Host Groups (This operation is optional when the protected object type is LUN).
        

        • If T series V2 or a later version is deployed at the DR site, the DR host whose services you want to recover can belong to only one host group that belongs to only one mapping view. The secondary LUN of the remote replication pair that corresponds to the storage LUN used by the protected applications can belong to only one LUN group, and the LUN group must belong to the same mapping view as the host group. If T series V200R001C00 is deployed, after creating mapping view, you cannot select the Enable Inband Command to modify the properties of the mapping view.
        • If the storage is T series V2R2 or a later version or 18000 series, the storage support automatic host adding and storage mapping. If the connection between the storage device and the host initiator is normal, the hosts, host groups, LUN mappings, and mapping views will be created in the storage device automatically. 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.
     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.
   • If the protected object type is VMware VM, perform the following:
     1. Select the cluster you want to recover.

        VMs will be recovered to the cluster. You need to set DR Site, DR vCenter, and DR Cluster.

        

        Upon your first test network selection, you need to set the cluster information.

     2. Select a network.

        The default recovery network is the network relevant to the resource mapping. If you want to change it, plan or select another network based on site requirements.

        

        • If Production Resource and DR Resource are not mapped, select Production Resource and DR Resource and click Add to the mapping view for mapping.
        • 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. Select non-critical VMs.

        In the Non-Critical VM 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.
   • If the protected object type is FusionCompute VM, perform the following steps:
     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.
   • If the protected object type is NAS File System, perform the following:
     1. 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.
     2. Click OK.

Result

After the planned migration is being started, you can view the execution process and result. If the planned migration fails, you can resolve the problem and try again.

Follow-up Procedure

If the DR technology in use is remote replication, the system automatically creates snapshots at the DR end to protect the data during the planned migration. After the planned migration is complete, if the created snapshots cannot be automatically deleted, manually delete them to release storage space.

A snapshot name is a string of 31 characters in the following format: DRdata_LUNID_YYYYMMDDHHMMSS_BAK. YYYYMMDDHHMMSS means the point in time when data starts to be backed up; LUNID indicates the snapshot ID, whose value is an integer between 1 and 65,535. This naming format enables you to quickly find the desired snapshots at the DR end.

After executing planned migration, services are running at the DR site. If you want to switch the services back to the original production site, perform the following::

1. Executing Reprotection

   Before switching back services, performing reprotection can protect running data at the DR site and automatically recover the service data generated at the DR site to the original protection site based on the specified policy.

2. Testing a Recovery Plan.

   After reprotection, the service data at the DR site is recovered to the production site. Before service failback, you need to perform a DR test to ensure data usability.

3. Clearing Test Data.

   This operation will automatically clear the test data generated during the DR test to ensure the successful rate of service failback.

4. 6.6.3 Performing Planned Migration.

   This operation will automatically migrate services back to the original production site.

5. Executing Reprotection.

   To ensure that services can be recovered at the DR site during failback, reprotection needs to be performed again.

For recovery plans whose protected object type is FusionCompute VM (non-OpenStack architecture), after the planned migration is successfully executed, you can export the configuration file, and view information about the FusionCompute VMs before and after the planned migration, such as resource mappings. The configuration file can be exported by performing the following:

1. Select the recovery plan used to perform the planned migration and click the Protected Object tab in the lower area.
2. Click Export to save the exported configuration file locally.