Personally I don't care for 'delete input'. Backup up and deleting archivelogs would probably best be done in separate operations. eg. BACKUP FORMAT 'arch_%d_T%T_s%s_p%p_t%t' ARCHIVELOG ALL NOT BACKED UP 2 TIMES; DELETE ARCHIVELOG ALL BACKED UP 2 TIMES TO DEVICE TYPE sbt; This allows you to backup only the archive logs that have not been backed up N times, and then to delete those that have been backed up N times. Alternatively, you may want to only remove archivelogs after they reach a certain age. The manual and some experimentation will help you out there. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com On Thu, Jul 7, 2011 at 8:03 AM, Schauss, Peter (ESS) <peter.schauss@xxxxxxx>wrote: > Oracle 11.2.0.1.0 on AIX 5.3 > > I am backing up a database with rman in nocatalog mode. > > When I tried to test my backups using the rman DUPLICATE command I got a > message that the backup contained no archivelogs. The information on > Metalink suggested using the command BACKUP DATABASE PLUS ARCHIVELOG. When > I ran that rman asked for > all of the archivelogs created since the database was created (luckily only > a week and a half ago). This despite the fact that that I had been backing > it up daily without the PLUS ARCHIVELOG option. > > Now that rman has backed up the archivelogs, what will determine which ones > it asks for the next time I run it? > > Ideally all that I need to restore a backup is the archivelogs which were > created during and after the backup. > > Thanks, > Peter Schauss > -- > //www.freelists.org/webpage/oracle-l > > >