Executing Reprotection

Prerequisites

If reprotection needs to be performed after fault recovery, clear the environment of the original primary end and the recover replications of the original DR site switch to production site before performing other operations.

• You have logged in to the UltraVR as a user with DR management permission.
• Planned migration or fault recovery has been performed for at least one recovery plan on UltraVR.
• Before performing reprotection, check whether protected groups at the original production site are in the Invalid state.
• Before reprotection, underlying storage links, remote replications, and consistency groups have been recovered.
• The FusionManager, FusionCompute, storage devices, and Virtual Replication Gateways (VRGs) at the original production site are in the normal state, and the original production site and original DR site communicate with each correctly.
• If execute reprotection after executing planned migration, in array-based replication for DR, the storage device configuration of the original production site and original DR site must be correct.
  • All underlying storage units corresonding to protected groups have remote replications.
  • All remote replications have secondary LUNs that belong to storage devices at the original production site.
  • If there are multiple remote replications, they must belong to a same consistency group.
• If execute reprotection after executing fault recovery, in array-based replication for DR, ensure that:
  • Add an available LUN to the remote replication on the storage at the original DR site.
    • Ensure that a new LUN or a LUN moved from other remote replication must have been mapped to the host.
    • For the primary LUN on the original remote replication, check whether the LUN has been mapped to the host. If it has been mapped to the host, delete the VM, disk and data storage from the LUN.
  • If the production environment before fault recovery is in active-active mode, the active-active mode at the active end must be suspended and relevant storage resources must be updated.
• If add or delete the disk in the protected VM, refresh the VM and execute this protected group of protected VMs reside manually.

Context

In order to ensure the previous configuration does not effect the execution of protected group and recovery plan, the system will automatically clear protection and recovery configuration (includes the protected policy, startup setting for recovery plan, self-defined execution script and execution steps) . Please re-configure protected policy and recovery policy after you execute reprotection to ensure the normal operation of DR services.

If the recovery plan is based on the snapshot protection policy template, reprotection cannot be performed.

Procedure

1. On the menu bar, select Recovery.
2. Select the remote recovery plan for which you want to execute reprotection and click More > Reprotection on the Operation list.
3. In the Warning dialog box that is displayed, read the content of the dialog box carefully and click OK.
   

   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

• After the reprotection starts, you can view the execution process and result. If the task is failed, you can solve the problem and execute the task again.
• After the reprotection, it protects data at the original DR site once devices at the original production site recover from disasters, the original DR site is production site.