The CDM solution uses BCManager eReplication to implement process-based cloud backup and recovery without manual intervention. It automatically invokes and coordinates hosts and storage devices throughout the entire process. Compared with the traditional backup and recovery mode, data can be restored from the cloud backup copy to the production LUN only by transmitting incremental data. The recovery efficiency is much higher than that of the traditional backup solution.
Context
It is not suitable to use a large amount of space on the production storage to store historical data for a long time. You can save copies of historical data that is not used frequently to the DR storage. If you want to use such historical data, you can use the copies on the DR end to restore the desired data.
Common data recovery scenarios are as follows:
- Data at the production end can be restored by overwriting.
- Only specific data or records need to be restored at the production end, and rollback is not allowed.
Figure 1 shows the process of retrieving historical data.
Prerequisites
- The status of the recovery plan is Ready, Rollback failed, or Rollback completed.
- The local copy of the protected group corresponding to the recovery plan is available.
- When information on storage devices and hosts at the production end changes, manually refresh device information. For details about the change items and operations, see Refreshing Resource Information.
- The application that needs to be restored has been stopped.
- The desired copy has been mounted to the host.
Precautions
If copies, currently protected objects, and used storage resources are changed, risks may arise during copy-based recovery. For details about the copy-based recovery scenarios and handling measures, see Copy-based Recovery and Risk Handling Measures.
- Choose Backup and Restore, click the Protected Object tab, and then click View. In the displayed Associated Protected Object dialog box, you can view the change information about the protected objects protected by the copy and at the current time.
- In the Oracle application, the cluster is not stoppd by default. To stop the cluster, you need to open the configuration for stopping the cluster and then perform the next step. For details about how to stop the cluster, see 4.2 Stopping the Oracle Cluster .
Procedure
- On the menu bar, choose
Utilization > Data Restore. - Select the desired recovery plan. In the Operation area, click Backup and Restore.
- In the displayed Backup and Restore window, set the copy type, select the site, specify the time segment for copy restore, and select the cloud backup copy to be restored based on the filtering result.
If the copy type is cloud backup copy, the restore rate cannot be set.
- Click Backup and Restore.
- 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.
- Click OK.
Operation Result
After the recovery starts, you can view the execution process and result. If a recovery task fails to be executed, troubleshoot the problem and reexecute the task.