When disks on a server are faulty, or server data is lost due to misoperations, you can use a backup to restore the server.
The historical data at the backup point in time will overwrite the current server data. The restoration cannot be undone.
Servers are shut down during restoration. It is therefore recommended that you perform restoration operations during off-peak hours.
If the number of disks to be restored is greater than the number of disks that are backed up, restoration may cause data inconsistency.
For example, if the data of Oracle is scattered across multiple disks and only some of them are restored, data inconsistency occurs after the restoration and the application may unable to start.
In the backup list, view the restoration status. When the backup enters the Available state and no new failed restoration tasks exist in Tasks, the restoration is successful. The resource is restored to the state at the time you took that backup.
For details about how to view failed restoration tasks, see Managing Tasks.
If a Windows server is restored, data disks may fail to be displayed due to Windows limitations.
After you use a cloud server backup to restore a logical volume group, the logical volume group needs to be attached again.
You need to manually online these data disks. For details, see Data Disks Are Not Displayed After a Windows Server Is Restored.