A selective online full operation that consists of archive logs and oracle data can also be linked to the logs of a separate job, which was initiated within the time frame of the selective online full operation. These logs and the selective online full are then considered as one entity within the software, regardless of whether or not separate jobs have the same job ID. Therefore, they are copied to synchronous and selective copies together during auxiliary copy operations and are aged together. If any part of the selective online full is missing from a copy, the full will not be considered as a valid full and will not be counted as a cycle during data aging. Consider the following:
-
Data from selective online full backups are considered the same as regular full and offline full backups for each subclient in terms of basic retention rules of cycles and days. However, if any logs on a primary copy have not been fully copied to a secondary copy, the selective online full cannot be aged.
-
Data from selective online full backups are considered the same as offline full backups for each subclient in terms of extended retention rules of days. Selective online full backups and all logs linked with it must be retained together on the same storage policy copy.
-
Those 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 will not be retained by extended retention rules during data aging operation.