Rman Multiple Retention

Question

Hi All,
I'm new in RMAN and Currently we have 14 days retention policy for daily and weekly backup.
In the same time we also will have 186days retention for monthly backup, that's mean its should be recoverable around that 3 month (for monthly).
My question is, What should I put the scripts for monthly backup ?
I saw some example its for offline backup:
BACKUP DATABASE UNTIL 'SYSDATE+365' NOLOGS;
But I want the backup should be online ?
Currently our weekly backup like this
#!/bin/bash
# SID= env | grep ORACLE_SID | cut -c12-15
export ORACLE_HOME=/oracle/BWD/112_64
export ORACLE_SID=BWD
LOGFILE=/tmp/BWD-weekly-`date +%y%m%d%H%M`.out
echo>> $LOGFILE
chmod 666 $LOGFILE
echo Script $0>> $LOGFILE
echo ==== started on `date` ====>> $LOGFILE
echo>> $LOGFILE
rman target / << !EOF >> $LOGFILE
allocate channel for maintenance type 'sbt_tape' parms
'ENV=(tdpo_optfile=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
crosscheck archivelog all;
release channel;
run
allocate channel t1 type 'sbt_tape' parms
'ENV=(tdpo_optfile=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
backup as compressed backupset
incremental level 0 cumulative
TAG SMQ_LEVEL0_WEEKLY_BACKUP
format 'weekly_%d_set%s_piece%p_%T_%U'
filesperset 5
database plus archivelog delete input;
sql 'alter system archive log current';
crosscheck backup;
release channel t1;
And Daily backup:
#!/bin/bash
SID=EPD
export ORACLE_HOME=/oracle/$SID/112_64
export ORACLE_SID=$SID
#LOGFILE=/tmp/EPD-weekly-`date +%y%m%d%H%M`.out
LOGFILE=/tmp/$SID-daily-`date +%y%m%d%H%M`.out
echo>> $LOGFILE
chmod 666 $LOGFILE
echo Script $0>> $LOGFILE
echo ==== started on `date` ====>> $LOGFILE
echo>> $LOGFILE
rman target / << !EOF >> $LOGFILE
allocate channel for maintenance type 'sbt_tape' parms
'ENV=(tdpo_optfile=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
crosscheck archivelog all;
release channel;
run
allocate channel t1 type 'sbt_tape' parms
'ENV=(tdpo_optfile=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
backup as compressed backupset
incremental level 1 cumulative
TAG EPD_LEVEL1_DAILY_BACKUP
format 'daily_%d_set%s_piece%p_%T_%U'
filesperset 5
database plus archivelog delete input;
sql 'alter system archive log current';
crosscheck backup;
release channel t1;
Appreciate if anyone has more experience to share with me the best aproach for this.

Answer 1

Hi,
I would change some things in your script.
It would create a routine for the backup of archivelogs separately ... every X hours (this is highly recommended).
When you perform a backup with the option 'LOGS' the archivelogs required to restore that backup will be maintained automatically. (ie The archivelogs will obey the policy Backup FULL with KEEP option).
rman target / << !EOF >> $LOGFILE
allocate channel for maintenance type 'sbt_tape' parms
'ENV=(tdpo_optfile=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
crosscheck archivelog all;
release channel;Why you are executing CROSSCHECK of ARCHIVELOG on each backup execution?
I recommend you run this command only when necessary and manually. Because the ARCHVELOGS must be there. If archivelog is not on directory this can compromise your backup.
If you run the crosscheck automatically you can invalidade your backup if you don't know where is that archivelog wich is missing. Because CROSSCHECK will mark the missing ARCHIVELOG as EXPIRED and the BACKUP will execute successful but during RESTORE you will need that ARCHIVELOG and during recover database may fail.
I recommend execute crosscheck command manually and only after the error was raised on the logs. i.e Backup must fail to know what's going on. As maintenance operation if necessary we should run CROSSCHECK manually.
run
allocate channel t1 type 'sbt_tape' parms
'ENV=(tdpo_optfile=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
backup as compressed backupset
incremental level 0 cumulative
TAG SMQ_LEVEL0_WEEKLY_BACKUP
format 'weekly_%d_set%s_piece%p_%T_%U'
filesperset 5
database plus archivelog delete input;
sql 'alter system archive log current';
crosscheck backup;
release channel t1;
}The command "sql 'alter system archive log current';" is not required since RMAN do it automatically when start backup of archivelogs. And even if this was necessary this command should be executed before start backup of archivelogs. So you should execute BACKUP DATABASE ... separately from PLUS ARCHVELOG...
e.g :
1° (BACKUP DATABASE ... )
2° (sql 'Alter system archivelog...)
3° (Backup Archivelog all delete...)
I recommend also you format the Backup (BACKUPPIECE) of ARCHIVELOG.
backup as compressed backupset
incremental level 0 cumulative
TAG SMQ_LEVEL0_WEEKLY_BACKUP
format 'weekly_%d_set%s_piece%p_%T_%U'
filesperset 5
database plus archivelog
format 'ARC_%d_set%s_piece%p_%T_%U'  delete input;Create a script to do Backup of Archivelgos at least each 3 hours
Backup ARCHIVELOG ALL TAG 'ARC_DATE' FORMAT  'ARC_%d_set%s_piece%p_%T_%U'  delete input;As you need recover database in any point time in a window of 3 month you can do that:
backup database tag monthly_SMQ  keep until time 'sysdate+168';The all archivelogs required for recover this backup will automatically be maintained.
Regards,
Levi Pereira