Hi Rich, We do nightly fulls. Every Monday we do a "keep until time '31'" as part of the database backup command to keep that backup for the month. Expected behavior from me is that this would result in ~31days of archivelog backups stored on tape due to this. I would also expect the archivelog backups to go obsolete after the databases are past their keep time. I should add, the databases backups are turning obsolete and being deleted as expected In this case, my oldest archivelog backup is March 6th. This is actually the day this database was created. Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag ------- -- -- - ----------- --------------- ------- ------- ---------- --- 131 B A A SBT_TAPE 06-MAR-14 1 1 NO TAG20140306T132627 And now my oldest full backup is April 7th Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag ------- -- -- - ----------- --------------- ------- ------- ---------- --- 6650 B F A SBT_TAPE 07-APR-14 1 1 NO TAG20140407T080105 -----Original Message----- From: Rich Jesse [mailto:rjoralist3@xxxxxxxxxxxxxxxxxxxxx] Sent: Friday, May 02, 2014 2:36 PM To: Michael Schmitt Subject: RE: What am I missing with my RMAN archivelog backups Hey Mike, > CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS; CONFIGURE > DEFAULT DEVICE TYPE TO 'SBT_TAPE'; CONFIGURE ARCHIVELOG BACKUP COPIES > FOR DEVICE TYPE SBT_TAPE TO 1; # default CONFIGURE ARCHIVELOG DELETION > POLICY TO NONE; # default ........ > > * All of the database backups are full level 0 backups. > > * Archivelogs are backed up with the following command " backup format > 'XXXX_ARCH_%M%D_%u.bkp' archivelog all not backed up 3 times;" How far apart are the fulls done? If, for example, they are 6d23h apart, RMAN will keep 13d22h, since it will need that ~2week-old full to restore an archivelog that's 7d old. Rich -- //www.freelists.org/webpage/oracle-l