Release notes
The requested article is not available. Either it doesn't apply to this version of the product or the relevant information is organized differently in this version of the docs. You can search, browse, or go back to the other version.
Types of restore strategies supported for manually added MySQL resources
Contributors
Suggest changes
-
PDF of this doc site
-
Protect Microsoft SQL Server databases
-
Protect SAP HANA databases
-
Protect IBM Db2
-
Protect PostgreSQL
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
You must define a strategy before you can successfully perform restore operations using SnapCenter. There are two types of restore strategies for manually added MySQL resources.
|
You cannot recover manually added MySQL resources. |
Complete resource restore
-
Restores all volumes, qtrees, and LUNs of a resource
|
|
If the resource contains volumes or qtrees, the snapshots taken after the snapshot selected for restore on such volumes or qtrees are deleted and cannot be recovered. Also, if any other resource is hosted on the same volumes or qtrees, then that resource is also deleted. |
