You can use a local backup copy to restore production data if the production data is infected by viruses or unintentionally deleted, to minimize service downtime.
Usually, local backup copies protect data of several days. If production data is attacked by a virus or deleted or damaged unintentionally, the DR function cannot restore service data because the replication period may have started and data at the DR site has been modified. If the data of a short period of time, for example, several days, has been corrupted, you can suspend the protected group of the application on the CDM management platform. If you need to roll back data to a specific point in time, you must have the copy of the data at this point in time. In the case of a database application, you can restore the data to an earlier point in time and then restore the data to the correct point in time using logs.
With local recovery, data can be restored in seconds. Therefore, services can be quickly restored. Figure 1 shows how to use a local copy to restore data.
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 .
Utilization > Data Restore.
When the storage device model is OceanStor V3/V5 or OceanStor Dorado V3, you can set the restore rate. However, if the copy type is cloud backup copy, the restore rate cannot be set.
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.