Escolar Documentos
Profissional Documentos
Cultura Documentos
When a log backup runs at the same time as a full backup, they are linked even when the full backup
included data only. These backups follow the standard data aging rules.
If a full backup job includes the data and the logs, then the next log backup is not linked to this full backup
job. These are unlinked log backups and by default and follow these log backup data aging rules:
The log backups that are not copied to secondary copies are not aged on both the primary and non-
primary source copy.
Log backups that exist on only one copy are aged when they are older than the oldest basic retention
data.
Log backups that exist on multiple copies are retained on the copy with longest retention days and are
aged after the oldest basic retention data. The log backup jobs on the remaining copies are aged by
using the copy retention days There is no check to see if the oldest basic retention data exists.
Partial, disabled logs are aged when they are older than the oldest basic retention data.
If a full backup job includes just the data then the next log backup job is linked to this full backup job. These
are considered as linked or chained log backups and are not aged until the linked data is aged. In addition,
these log backups follow the unique data aging rules for log backups.
Selective online full backups and all logs linked with it must be retained together on the same storage policy
copy.
http://documentation.commvault.com/commvault/v10/article?p=products/oracle/c_ora_retention_rules.htm 1/5
10/16/2017 Data Retention Rules for Oracle Backups
The logs that are linked with a selective online full (and the logs of the selective online full) can be aged only
if they are older than the oldest data that can be aged and the corresponding data of the selective online full
that can be or have been aged.
Selective online full backup jobs that are completed with errors are not retained by extended retention rules
during the data aging operation.
You can configure the software to allow selective online incremental backups to be eligible for selective copy. For
more information, see Allowing Incremental Jobs to Be Eligible for Selective Copy.
You can run a script after you run a selective online full or incremental backup to enable the full cycle retention of
selective jobs on the selective copy. For more information, see Enabling Extended Retention of Selective Jobs on
the Selective Copy.
You can copy a full cycle of jobs to a selective copy. The cycle includes the selective online full and incremental
jobs. For additional information, see Copying a Full Cycle of Jobs to a Selective Copy.
You can run a script after you run a selective online full or incremental backup to enable the full cycle retention of
selective jobs on the selective copy. For more information, see Enabling Extended Retention of Selective Jobs on
the Selective Copy.
You can copy a full cycle of jobs to a selective copy. The cycle includes the offline full and incremental jobs. For
additional information, see Copying a Full Cycle of Jobs to a Selective Copy.
If the last full backup includes a partial database, then data in a previous full backup might be lost.
http://documentation.commvault.com/commvault/v10/article?p=products/oracle/c_ora_retention_rules.htm 2/5
10/16/2017 Data Retention Rules for Oracle Backups
Example
If the storage policy retention is 3 days, this makes Backup 1 and Backup 2 eligible for pruning. Backup 2 is
retained because incremental jobs Backup 3 and Backup 4 are not eligible for pruning. Backup 1, which contains
the entire database, is pruned and thus the entire database backup is lost.
When you perform an On-Demand full backup job (that includes data and logs), the next log backup job will get
linked to this job, since the job type for Full backup is data for both the data and log phase.
An effective storage policy strategy for Oracle On-Demand and customized RMAN Script backups is as follows:
The same storage policy must not be used for regular Oracle backups and Oracle On-Demand and
customized RMAN Script backup.
The storage policy copy containing logs of Oracle On-Demand and customized RMAN Script backups must
have a longer retention time than other storage policies used by regular Oracle backups for the same
instance. This prevents the logs of Oracle On-Demand backups from being pruned before the data of regular
Oracle backups and allows the database to be fully restored and recovered using the data of old regular
Oracle backups and logs.
Oracle selective online full and offline full jobs performed by using the On-Demand configuration and
customized script will not be copied to selective copy and are not eligible for extended retention.
1. From the CommCell Console ribbon, click the Home tab, and then click Control Panel.
2. Under the Storage section, click the Media Management icon.
http://documentation.commvault.com/commvault/v10/article?p=products/oracle/c_ora_retention_rules.htm 3/5
10/16/2017 Data Retention Rules for Oracle Backups
3. On the Data Aging tab of the Media Management Configuration dialog box, change the value for the
Ignore Completed With Errors job option for Extended Retention calculations option from 1 to 0.
4. Click OK to close the Media Management Configuration dialog box.
Related Topics
Data Aging for Oracle
Data Aging
1997- 2017 Commvault Systems Inc. All Rights Reserved.
http://documentation.commvault.com/commvault/v10/article?p=products/oracle/c_ora_retention_rules.htm 4/5
10/16/2017 Data Retention Rules for Oracle Backups
http://documentation.commvault.com/commvault/v10/article?p=products/oracle/c_ora_retention_rules.htm 5/5