Hi All,
I am trying to understand how backup retention policy based on redundancy and archivelog deletion policy based on redundancy differently impacts when it comes to archivelog deletion.
Assume that i am using FRA
configure backup retention policy to redundancy 3;
CONFIGURE ARCHIVELOG DELETION POLICY TO backed up 2 times to device type disk;
is set
question 1
I am trying to backup archivelog sequence here, you can see that it skips the archive log to satisfy the archive log deletion policy but not backup retention policy. I thought it would be other way. Also in this case if due to some space pressure in FRA if the archivelog deletion policy kicks in first to delete this backup then it will be that i may not honor retention policy of redundancy 3.
RMAN> backup archivelog sequence 35;
Starting backup at 19-MAY-14
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=35 RECID=25 STAMP=847994521
channel ORA_DISK_1: starting piece 1 at 19-MAY-14
channel ORA_DISK_1: finished piece 1 at 19-MAY-14
piece handle=/orafra1/db101/DB101/backupset/2014_05_19/o1_mf_annnn_TAG20140519T180231_9qnzvq5s_.bkp tag=TAG20140519T180231 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 19-MAY-14
RMAN> backup archivelog sequence 35;
Starting backup at 19-MAY-14
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=35 RECID=25 STAMP=847994521
channel ORA_DISK_1: starting piece 1 at 19-MAY-14
channel ORA_DISK_1: finished piece 1 at 19-MAY-14
piece handle=/orafra1/db101/DB101/backupset/2014_05_19/o1_mf_annnn_TAG20140519T180237_9qnzvxj9_.bkp tag=TAG20140519T180237 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 19-MAY-14
RMAN> backup archivelog sequence 35;
Starting backup at 19-MAY-14
using channel ORA_DISK_1
skipping archived log file /orafra1/archives101/1_35_846975384.dbf; already backed up 2 time(s)
Finished backup at 19-MAY-14
If i increase A.LOG deletion policy to 4 > than retention/redundancy 3 it works as intended
RMAN> list backup of archivelog sequence 33 summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
83 B A A DISK 19-MAY-14 1 1 NO TAG20140519T180517
84 B A A DISK 19-MAY-14 1 1 NO TAG20140519T180524
85 B A A DISK 19-MAY-14 1 1 NO TAG20140519T180529
86 B A A DISK 19-MAY-14 1 1 NO TAG20140519T180532
RMAN> backup archivelog sequence 33;
Starting backup at 19-MAY-14
using channel ORA_DISK_1
skipping archived log file /orafra1/archives101/1_33_846975384.dbf; already backed up 4 time(s)
Finished backup at 19-MAY-14
ok. This is as what I expected.
Q2.
Now try backing up database 3 times to satisfy redundancy, and all the archivelogs are reported obsolete here, but then archivelog deletion policy is not honored here.
So ideally what would be a number to satisfy that both the policies are honoured?
(edited for brevity)
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ --------------------
Archive Log 2 12-MAY-14 /orafra1/archives101/1_12_846975384.dbf
Archive Log 3 13-MAY-14 /orafra1/archives101/1_13_846975384.dbf
Archive Log 4 13-MAY-14 /orafra1/archives101/1_14_846975384.dbf
Archive Log 5 13-MAY-14 /orafra1/archives101/1_15_846975384.dbf
Archive Log 6 13-MAY-14 /orafra1/archives101/1_16_846975384.dbf
Archive Log 7 13-MAY-14 /orafra1/archives101/1_17_846975384.dbf
Archive Log 8 13-MAY-14 /orafra1/archives101/1_18_846975384.dbf
Archive Log 9 14-MAY-14 /orafra1/archives101/1_19_846975384.dbf
Archive Log 10 14-MAY-14 /orafra1/archives101/1_20_846975384.dbf
Archive Log 12 15-MAY-14 /orafra1/archives101/1_22_846975384.dbf
Archive Log 13 15-MAY-14 /orafra1/archives101/1_23_846975384.dbf
Archive Log 14 16-MAY-14 /orafra1/archives101/1_24_846975384.dbf
Archive Log 15 16-MAY-14 /orafra1/archives101/1_25_846975384.dbf
Archive Log 16 16-MAY-14 /orafra1/archives101/1_26_846975384.dbf
Archive Log 21 19-MAY-14 /orafra1/archives101/1_31_846975384.dbf
Archive Log 22 19-MAY-14 /orafra1/archives101/1_32_846975384.dbf
Archive Log 23 19-MAY-14 /orafra1/archives101/1_33_846975384.dbf
Archive Log 24 19-MAY-14 /orafra1/archives101/1_34_846975384.dbf
Archive Log 25 19-MAY-14 /orafra1/archives101/1_35_846975384.dbf