Before you create a protection policy, note the following best practices:
In the
Protection Policies window, you can export protection policy data by using the
Export All functionality.
Understanding backup terminology and managing backup frequency
When scheduling backups in a protection policy, be aware of the following:
Different protection-policy types can use different terminology to describe available backup levels. This terminology can differ not only between protection-policy types, but also from traditional terminology.
To avoid high CPU usage that can lead to failure issues, do not schedule backups more often than recommended.
To understand the different backup levels to manage backup frequencies, see the following table.
Table 1. Backup terminology and frequencyTable of backup terminology and frequency
Protection-policy types
Available backup levels
Description
Equivalent traditional terminology
Recommended minimum backup interval
Oracle centralized (Application Direct)
Full
All the data is backed up.
Full
Daily
Incremental Cumulative
Only the data that has changed since the last level 0 full backup is backed up.
Differential
12 hours
Incremental Differential
Only the data that has changed since the last incremental differential backup or the last full backup if there are no other incremental differential backups is backed up.
Incremental
6 hours
Log
The archived logs are backed up.
-
30 minutes
Oracle centralized (Oracle Incremental Merge)
Full
All the data is backed up.
Full
Daily
Synthetic Full
Only the data that has changed since the last synthetic-full or full backup is backup up. An operation to merge these changes with the last synthetic-full or full backup produces a full backup in storage. Only the changed files are copied over the network, but the result is still a full backup in storage.
A differential backup is performed, followed by a merge operation that produces a full backup in storage.
12 hours
Log
The archived logs are backed up.
-
30 minutes
NOTE:In some situations, a full backup might be performed even though a synthetic-full backup was scheduled. Possible reasons for a full backup include the following:
There is no existing full backup.
The size of a volume has changed.
There has been a file path change.
The asset host has been rebooted.
You can increase the backup frequency of a protection policy by scheduling more full or synthetic-full backups with different retention times to meet your requirements.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\