Executing Planned Migration

Prerequisites

• You have logged in to the UltraVR 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.
• If storage devices or VMs on production site or DR site change, storage devices or VMs at the site where a protected group resides must be refreshed, for details, refer to Refreshing Resource Information.
• If the IP address of VM recovery is not configured, the IP address of VM is same to production end. If you wan to configure different IP address for executing planned migration. After the recovery plan is created, you can configure IP address on the Protected Object tab page.
• If add or delete the disk in the protected VM, refresh the VM and execute this protected group of protected VMs reside manually.

Context

If you do not perform at least one successful DR test, the failure probability of the planned migration will increase, and executing planned migration failed will stop production service. Therefore, before performing planned migration, you are recommended 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 of planned migration is related to the migrated data, the greater the amount of data, the longer the planned migration time.

In disaster recovery data center solution (geo-redundant mode) scenario, the service can be migrated from production center to same-city DR center or remote DR center.

Procedure

1. On the menu bar, select Recovery.
2. Select the remote recovery plan for which you want to execute planned migration and click More > Planned Migration on the Operation list.

   The Planned Migration dialog box is displayed.

3. Perform planned migration.
   1. Select the cluster you want to recover.

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

   2. Optional: Select an available powered-on host.

      The available powered-on host can provide resources for VMs.

   3. Optional: Select non-critical VMs.

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

      

      If the non-essential VM fails to be stopped, manually stop the VM on the FusionCompute management portal.

   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.

Result

After the planned migration starts, you can view the execution process and result. If the task is failed, you can solve the problem and execute the task again.

Follow-up Procedure

After executing planned migration, the service is running in the DR sites. If the service is switched to original production sites, execute the following steps:

1. Execute the operation of Executing Reprotection

   Before switching service, executing reprotection can protects running data at the DR site and copy the service data as the specified protection policy in the DR sites during running to the original production sites.

2. Execute the operation of Testing a Recovery Plan.

   After executing reprotection, the service data, you need to test a recovery plan to verify the availability and ensure the service is switched successfully before data replicated to original production sites.

3. Execute the operation of Clearing Test Data.

   Delete the test data generated on the DR system and restore the DR environment to facilitate future switched DR.

4. Execute the operation of Executing Planned Migration.

   Executing planned migration, the service was migrated from DR sites to original production sites and the service is running in the production sites.

5. Execute the operation of Executing Reprotection.

   Ensure the in-plan and out-plan event occurs when service was switched to the original production sites and can be recovered in the DR sites, executing reprotection can protect the system service.

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. To export the configuration file, perform the following steps:

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.