Data Aging for Oracle On Demand and Customized RMAN Script backup jobs uses days/time, and ignores cycles, as the determining factor for pruning the data. Therefore, once the retention time criteria has been met, all data (for both data and logs) is pruned that was backed up using the storage policy specified in the RMAN script that was run through the Command Line Interface.
For RMAN streaming selective online full jobs to be considered for extended retention, both the data and log files must be backed up. If you use a customized script to run the backup you must make sure that the RMAN script includes commands to back up the log files.
An effective storage policy strategy for Oracle On Demand and Customized RMAN Script backups is as follows:
-
The same storage policy should not be used for regular Oracle backups and Oracle On Demand backups or Customized RMAN Script backups.
-
The storage policy copy containing logs of Oracle On Demand backups or Customized RMAN Script backups should have a much longer retention time than other storage policies used by regular Oracle backups for the same instance. This is to prevent the logs of Oracle On Demand backups from being pruned before the data of regular Oracle backups, and to allow the database to be fully restored and recovered using the data of old regular Oracle backups and logs afterwards.