DR

Prerequisites

• At least one recovery plan has been created in the system.
• The status of the recovery plan is Ready, Clear completed, Backup and restore fail, or Backup and restore are complete.
• The relevant protected groups of the recovery plan have available copies.
• 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 Oracle applications, the database is disabled but the cluster is enabled by default on the eReplication Agent. In the backup (SAN) scenario, if Huawei distributed block storage is used, you are advised to disable the cluster configuration. For details, see Changing the Configuration of Stopping the Oracle Cluster.
• If you select VM restoration, ensure that the remaining space of the datastore group is sufficient to accommodate additional copies of disk files of any group of VMs in the existing protected group.
• The network configuration of the VMs in the protected group must be the same as that of the VMs in the copy.
• The VM name can contain a maximum of 50 characters.
• VM recovery can be performed only on the backup network, integrated DR and backup network, and active-active + integrated DR and backup network.
• The datastore on vCenter at the original production site must be mounted.
• After the upgrade of all-in-one backup and local networks, you need to refresh vCenter and use the new copy to restore the VM.
• The datastore name cannot contain Chinese characters.

Context

If copies, currently protected objects, and used storage resources are changed, risks may arise during copy-based recovery. For details about copy restoration scenarios and handling measures, see Copy-based Recovery and Risk Handling Measures.

In the Protected Object area of the recovery plan, click View. In the Associate protected objects dialog box that is displayed, you can view the changes of the copy and the protected object at the current point in time.

Procedure

1. On the menu bar, select Utilization > Data Restore.
2. Select the recovery plan that you want to use for data rollback. Then click Backup and Restore in the operation area.
3. In the displayed Backup and Restore dialog box, you can select Snapshot restoration or VM restoration.
   • Select Snapshot restoration, set the copy type, select a site, specify the time period for restoring the copy, select the copy to be restored based on the filtering result, and click Backup and Restore.
   • Select VM restoration, set the copy type, select a site, specify the time period for restoring the copy, select the copy to be restored based on the filtering result, click Select VM to select the VM to be restored, click OK, and click Backup and Restore.
     

     • If the storage device model is OceanStor V3/V5/6.x, you can select a copy of the local site for recovery. If the selected VM contains a shared disk, you need to select the VM together with the VM associated with the shared disk.
     • If the storage device model is OceanStor 6.x, you can also select a copy of the remote site for recovery. In this case, you can set the replication rate. If the selected VM contains a shared disk, you need to select the VM together with the VM associated with the shared disk.
     • VM restoration does not support RDM disks.
     • VMs cannot be restored to a specified resource pool.
     • During VM restoration, whether the virtual network configurations are consistent is not checked.
     • VMs cannot be restored using HyperCDP or snapshot second-level snapshots.
     • If a VM fails to be restored, the system automatically clears the generated temporary resources. The VM restoration task is complete only after the temporary resources are cleared.

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.

Result

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