Understanding enabling or disabling of data protection in profile
You can enable or disable data protection while creating or updating a database profile.
To create a protected backup of a database on the secondary storage resources, database administrators and storage administrators perform the following actions.
If you want to… | Then… | ||
---|---|---|---|
Create or edit a profile |
To create or edit a profile, perform the following:
When you disable backup protection, a warning message is displayed stating that the dataset will be deleted and restoring or cloning backups for this profile will not be possible. |
||
View the profile |
Because the storage administrator has not yet assigned storage resources to implement the protection policy, the profile shows up as nonconformant in both the SnapManager graphical user interface and the |
||
Assign storage resources in the Protection Manager Management Console |
In the Protection Manager Management Console, the storage administrator views the unprotected dataset and assigns a resource pool for each node of the dataset that is associated with the profile. The storage administrator then makes sure that secondary volumes are provisioned and protection relationships are initialized. |
||
View the conformant profile in SnapManager |
In SnapManager, the database administrator sees that the profile has changed to conformant state in both the graphical user interface and in the |
||
Create the backup |
|
||
View the backup |
The new backup is shown as scheduled for protection, but not yet protected (in the SnapManager interface and in the |
||
View the backup list |
After the storage administrator verifies that the backup has been copied to secondary storage, SnapManager changes the backup Protection state from “Not protected” to “Protected”. |