Backup Retention Policy?

hi All,
I'm planning my backup retention policy.
what is the best backup planning for this plan:
sunday - backuo level 0 (full)
monday - defferential backup level 1
tuesday - defferential backup level 1
wednesday - cumulative backup level 1
thrusday - defferential backup level 1
friday - defferential backup level 1
saturday - defferential backup level 1
sunday - backuo level 0 (full)
I was thinking about recovery window option of 4 days.
what do you think about it?
thanks!!!

We can not help you with the "best" plan because what is "best" is determined by your SLA (Service Level Agreement) with your customers and your management.
What you present is perfectly reasonable for some organizations and for others would be a non-starter.
Meet with your management and ask them to define your recovery window, expectations, and to put a monetary value, per minute, for downtime.
If a minute of downtime is $1.00 that is very different from a minute of downtime valued at $100,000.

Similar Messages

Backup retention policy check

Dear all,
I want to check rman catalog to confirm if the records are being removed as per the retention and backup policy we have implemented in our system.
which means; how many days of incremental backups are on FRA before oracle removes from controlfile catalog and from disk. How can I check that?
Our system is running in 11.2.0.2.3 version under Redhat linux 5 and we are using ASM.
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name ADVDB are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+ORAFLASH/sncforcl.ora';
RMAN>
sql > show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     31Thank you,
Diego

asifkabirdba wrote:
run {
crosscheck backup;
delete noprompt obsolete;
Run this on RMAN and check.
Regards
Asif Kabir
Handle:      899660
Status Level:      Newbie
Registered:      Nov 29, 2011
Total Posts:      22
Total Questions:      *6 (6 unresolved)*
-- If answered close the thread and mark your post as correct/helpfulHi Asif,
Thank you, but, I am asking how to check how many days of incremental backups are on Flash Recovery Area before oracle removes from controlfile catalog and from disk

Archive Log Backups Retention Policy

How can I define Retention Policy for archive log backups?

The question asked and answer you have marked as "Correct answer" is misleading.
For archived log deletion policy, look below.
Configuring the RMAN Environment
For the actual question posted "How can I define Retention Policy for archive log backups?", look below link.
http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmconfb.htm#i1019318
Also, did you start the thread to clear your doubt or test the other forum users?
Thank you!!

Backup with retention policy to recovery window of N days

Hello,
I've issued command to create database incremental backup with configuration:
run
configure retention policy to recovery window of 14 days;
backup incremental level 1 cumulative
tag daily_incr_14_days
database
plus archivelog delete all input;
All parameters are set to their default values and database backups goes to FRA. I've got recovery catalog connected and all RC_ views at my disposal.
1) Is there any way to find out, what recovery window was used for backup from any command in rman or query from RC_ views or local database views (information from control file)?
2) If I use other recovery window setting with configure command what would rman crosscheck or report commands do?
BR
Patrycjusz.

TenakaKhan wrote:
Mahir,
thanks for answer - this means that recovery window should be used mainly for maintenance purposes (crosscheck, delete obsolete, report need backup etc.) and it's not related to actual retention period with backup pieces like 'keep until' clause for backup ... database command (this information are saved with backup as I could check in rc_backup_set view from recovery catalog)?
Yes it is.
Maintaining RMAN Backups and Repository&nbsp;Records
keepOption
backup retention policy
A user-defined policy for determining how long backups and archived logs must be retained for media recovery. You can define a retention policy in terms of backup redundancy or a recovery window.
RMAN retains the data file backups required to satisfy the current retention policy, and any archived redo logs required for complete recovery of those data file backups.
recovery window
A recovery window is one type of RMAN backup retention policy, in which the DBA specifies a period of time and RMAN ensures retention of backups and archived redo logs required for point-in-time recovery to any time during the recovery window.
The interval always ends with the current time and extends back in time for the number of days specified by the user. For example, if the retention policy is set for a recovery window of seven days, and the current time is 11:00 AM on Tuesday,
RMAN retains the backups required to allow point-in-time recovery back to 11:00 AM on the previous Tuesday.
Regards
Mahir M. Quluzade

Control_file_record_keep_time vs retention policy

Its not thread nor question just read from documents and tried to imply the fact of documents and i think its written correct what i tried to do proof it practically ,neither i am trying to be smart just share with you guys is my observation correct or not.i am using FRA area for backup.
<quote>
Relation between RMAN retention period and control_file_record_keep_time
RMAN backup keeps the backup metadata information in the reusable section of the controlfile.Its depends on the parameter CONTROL_FILE_RECORD_KEEP_TIME. CONTROL_FILE_RECORD_KEEP_TIME specifies the minimum number of days before a reusable record in the control file can be reused.
In the event a new record needs to be added to a reusable section and there is not enough space then it will delete the oldest record, which are aged enough.
Backup retention policy is the rule to set regarding which backups must be retained (whether on disk or other backup media) to meet the recovery and other requirements.
If the CONTROL_FILE_RECORD_KEEP_TIME is less than the retention policy then it may overwrite reusable records prior to obsoleting them in the RMAN metadata. Therfor it is recommended that the CONTROL_FILE_RECORD_KEEP_TIME should set to a higher value than the retention policy.
Formula
CONTROL_FILE_RECORD_KEEP_TIME = retention period + level 0 backup interval + 1
For e.g.
e.q. level 0 backup once a week with retention policy of a recovery windows of 14 days then in this
case the CONTROL_FILE_RECORD_KEEP_TIME should be 14+7+1=22
<quote>
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
SQL>
SQL> alter system set control_file_record_keep_time=1
2 /
System altered.
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     1
RMAN> configure retention policy to redundancy 3
2> ;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
new RMAN configuration parameters are successfully stored
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=126 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T185951_3N5T2RTX_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:17
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169270_3N5T598C_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T190313_3N5T94SG_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:22
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169477_3N5TCPVW_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T190500_3N5TDGC9_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639169556_3N5TG65X_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
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          30     19-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_19\O1_MF_1_1_3N35QQX7_.ARC
Archive Log          31     19-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_19\O1_MF_1_2_3N39LR86_.ARC
Archive Log          32     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_3_3N4RZBXV_.ARC
Archive Log          33     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_4_3N4W8SLF_.ARC
Archive Log          34     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_5_3N4Y1CN7_.ARC
Archive Log          35     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_6_3N4Z6LGF_.ARC
Archive Log          36     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_7_3N53S4XK_.ARC
Archive Log          37     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_8_3N57XHYB_.ARC
Archive Log          38     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_9_3N5C52D8_.ARC
Archive Log          39     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_10_3N5C83YB_.ARC
Archive Log          40     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_11_3N5K9J2Z_.ARC
Archive Log          41     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_12_3N5MMXHO_.ARC
Archive Log          42     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_13_3N5N566W_.ARC
Archive Log          43     20-NOV-07          C:\ORACLE\FLASH_RECOVERY_AREA\ORC
\ORC\ARCHIVELOG\2007_11_20\O1_MF_1_14_3N5RVB4G_.ARC
RMAN>
Now i just delete alls backup and increase the control_file_record_keep_time 7 which will be more then retention policy redundancy 3
RMAN> list backup
2> ;
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
6       Full    512M       DISK        00:01:10     20-NOV-07
        BP Key: 6   Status: AVAILABLE Compressed: NO Tag: TAG20071120T185951
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP
List of Datafiles in backup set 6
File LV Type Ckp SCN    Ckp Time Name
1       Full 478504     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2       Full 478504     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3       Full 478504     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4       Full 478504     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size       Device Type Elapsed Time Completion Time
7       Full    2M         DISK        00:00:04     20-NOV-07
        BP Key: 7   Status: AVAILABLE Compressed: NO Tag: TAG20071120T190110
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169270_3N5T598C_.BKP
Controlfile Included: Ckp SCN: 478975       Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
BS Key Type LV Size       Device Type Elapsed Time Completion Time
8       Full    513M       DISK        00:01:15     20-NOV-07
        BP Key: 8   Status: AVAILABLE Compressed: NO Tag: TAG20071120T190313
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP
List of Datafiles in backup set 8
File LV Type Ckp SCN    Ckp Time Name
1       Full 480265     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2       Full 480265     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3       Full 480265     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4       Full 480265     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size       Device Type Elapsed Time Completion Time
9       Full    2M         DISK        00:00:02     20-NOV-07
        BP Key: 9   Status: AVAILABLE Compressed: NO Tag: TAG20071120T190437
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169477_3N5TCPVW_.BKP
Controlfile Included: Ckp SCN: 480346       Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
BS Key Type LV Size       Device Type Elapsed Time Completion Time
10      Full    513M       DISK        00:00:52     20-NOV-07
        BP Key: 10   Status: AVAILABLE Compressed: NO Tag: TAG20071120T190500
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP
List of Datafiles in backup set 10
File LV Type Ckp SCN    Ckp Time Name
1       Full 480415     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01
.DBF
2       Full 480415     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS0
1.DBF
3       Full 480415     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01
.DBF
4       Full 480415     20-NOV-07 C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.
DBF
BS Key Type LV Size       Device Type Elapsed Time Completion Time
11      Full    2M         DISK        00:00:02     20-NOV-07
        BP Key: 11   Status: AVAILABLE Compressed: NO Tag: TAG20071120T190556
        Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169556_3N5TG65X_.BKP
Controlfile Included: Ckp SCN: 480449       Ckp time: 20-NOV-07
SPFILE Included: Modification time: 20-NOV-07
RMAN> delete backup
2> ;
using channel ORA_DISK_1
List of Backup Pieces
BP Key BS Key Pc# Cp# Status      Device Type Piece Name
6       6       1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP
7       7       1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169270_3N5T598C_.BKP
8       8       1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP
9       9       1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169477_3N5TCPVW_.BKP
10      10      1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\BACKUPSET\2007_11_20\O1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP
11      11      1   1   AVAILABLE   DISK        C:\ORACLE\FLASH_RECOVERY_AREA\OR
C\ORC\AUTOBACKUP\2007_11_20\O1_MF_S_639169556_3N5TG65X_.BKP
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T185951_3N5T2RTX_.BKP recid=6 stamp=639169192
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169270_3N5T598C_.BKP recid=7 stamp=639169273
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190313_3N5T94SG_.BKP recid=8 stamp=639169396
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169477_3N5TCPVW_.BKP recid=9 stamp=639169478
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O
1_MF_NNNDF_TAG20071120T190500_3N5TDGC9_.BKP recid=10 stamp=639169502
deleted backup piece
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\
O1_MF_S_639169556_3N5TG65X_.BKP recid=11 stamp=639169558
Deleted 6 objects
RMAN> delete archivelog all
2> ;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=126 devtype=DISK
specification does not match any archive log in the recovery catalog
RMAN> list backup
2> ;
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     1
SQL> alter system set control_file_record_keep_time=7
2 /
System altered.
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
SQL>
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191412_3N5TXRSG_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170131_3N5V03YT_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191655_3N5V2S20_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170261_3N5V462Z_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 20-NOV-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORC\ORC\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-NOV-07
channel ORA_DISK_1: finished piece 1 at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\BACKUPSET\2007_11_20\O1_MF_NN
NDF_TAG20071120T191836_3N5V5X20_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 20-NOV-07
Starting Control File and SPFILE Autobackup at 20-NOV-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORC\ORC\AUTOBACKUP\2007_11_20\O1_MF_S
_639170362_3N5V7C1K_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-07
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
no obsolete backups foundnothing obsolete it means control_file_record_keep_time will not affect backups unless it will be less then or equal
to retention policy.
Note : Please agree or disagree with me may be i would be wrong
Khurram

Sorry for alls readers after a long practical observation at my own database server i came across that my observation was wrong and absurd in this first post, the above observation is not due to control_file_record_keep_time ,its due to something obvious which i am going to share you guys here.
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> list backup
2> ;
RMAN>AS documentation says
"Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups.
First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
log backups that are older than the oldest datafile or control file backup that must be retained."
Now i connect to SQL and create two big table for filling the redo log file and then get it archived.Please
consider it here that i am getting archived before any taking backup i.e backup database in order to make
archive older then the oldest datafile.
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
SQL> create table a1 as select * from all_objects
2 /
Table created.
SQL> create table a2 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
03/17/2008 03:44 PM    <DIR>          .
03/17/2008 03:44 PM    <DIR>          ..
03/17/2008 03:44 PM         9,750,528 O1_MF_1_15_3XWLVK6T_.ARC
               1 File(s)      9,750,528 bytes
               2 Dir(s) 62,714,875,904 bytes free
Now i take backup
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARCYou can see the obsolete archived files which is the older then the oldest file which has been obsolete.It also
does'nt make sense to keep the archived log files which is older then the oldest file cause it will no longer
be useful for recovery process.
now back to pavillion
RMAN> delete obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC
Do you really want to delete the above objects (enter YES or NO)? yes
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC recid=402 stamp=649611842
Deleted 1 objects
RMAN> delete backup
2> ;
using channel ORA_DISK_1
RMAN> list backup
2> ;
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 03:59 PM    <DIR>          .
03/17/2008 03:59 PM    <DIR>          ..
               0 File(s)              0 bytes
               2 Dir(s) 62,724,440,064 bytes freenow this time what i did i created the archived log files after first backup in order to not to make it older
then the oldest datafile backup.
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundnow i come to at SQL and make redo log file filled by creating 2 big tables in order to get it archived
SQL> create table a3 as select * from all_objects
2 /
Table created.
SQL> create table a4 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 04:09 PM    <DIR>          .
03/17/2008 04:09 PM    <DIR>          ..
03/17/2008 04:09 PM         9,751,552 O1_MF_1_16_3XWNCGRS_.ARC
               1 File(s)      9,751,552 bytes
               2 Dir(s) 62,563,205,120 bytes free
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundYou can see no archived logs get obsolete yet cause the archivelog O1_MF_1_16_3XWNCGRS_.ARC
is not older then oldest datafile backup.
But this archivelog file will get obsolete if its beyond the retention policy,lest see how ,just take one more
backup ,as i have already taken two time backup and the moment i go to take third backup it will cross ours
retetnion policy from the period of 2.
RMAN> backup database
2> ;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           240    17-MAR-08
Backup Piece       231    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NNNDF_TAG20080317T160604_3XWN4WTB_.B
KP
Backup Set           241    17-MAR-08
Backup Piece       232    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NCSNF_TAG20080317T160604_3XWN6Z95_.B
KP
Archive Log          403    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_16_3XWNCGRS_.ARCKhurram

Purpose of Retention Policy Recovery Window and Redundancy

Hi,
Good Evening,
I have some queries regarding the RMAN Retention Policy Recovery Window and Redundancy.
1. Any condition is there to set the Retention Policy Recovery Window and Redundancy and control_file_record_keep_time?What is the relationship between these 3 parameters?
2. Explain the scenario if i set the control_file_record_keep_time=4 Redundancy=3 and Recovery Window=7?
3. If i set the Redundancy=3 and Recovery Window=7 means my backup place only have 3 copies of backup based on the redundancy then what is the purpose of Recovery Window=7 please give some example.
4. If i change the values for Recovery Window=3 and Redundancy=7 what will happened, how many days backup will be available in my FRA location?Explain with one scenario?
Thanks in advance.
Vijay.

Hi,
Take a look of the above doc contents:
Configuring the Backup Retention Policy
As explained in "Backup Retention Policies", the backup retention policy specifies which backups must be retained to meet your data recovery requirements. This policy can be based on a recovery window or redundancy. Use the CONFIGURE RETENTION POLICY command to specify the retention policy.
so you have option to choose either recovery windows or redundancy based you can set the configuration like
read in the Doc What it said for both:
Recovery Window-Based Retention Policy ==>RMAN does not consider any full or level 0 incremental backup as obsolete if it falls within the recovery window. Additionally, RMAN retains all archived logs and level 1 incremental backups that are needed to recover to a random point within the window.
Redundancy-Based Retention Policy==>The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many full or level 0 backups of each datafile and control file that RMAN should keep. If the number of full or level 0 backups for a specific datafile or control file exceeds the REDUNDANCY setting, then RMAN considers the extra backups as obsolete. The default retention policy is REDUNDANCY 1.
RMAN> show RETENTION POLICY;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name DDTEST are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
new RMAN configuration parameters are successfully stored
RMAN> show RETENTION POLICY;
RMAN configuration parameters for database with db_unique_name DDTEST are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
RMAN> show RETENTION POLICY;
RMAN configuration parameters for database with db_unique_name DDTEST are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONTROL_FILE_RECORD_KEEP_TIME:This parameter applies only to records in the control file that are circularly reusable (such as archive log records and various backup records) ref Doc:CONTROL_FILE_RECORD_KEEP_TIME
1. Any condition is there to set the Retention Policy Recovery Window and Redundancy and control_file_record_keep_time?What is the relationship between these 3 parameters?
2. Explain the scenario if i set the control_file_record_keep_time=4 Redundancy=3 and Recovery Window=7?
3. If i set the Redundancy=3 and Recovery Window=7 means my backup place only have 3 copies of backup based on the redundancy then what is the purpose of Recovery Window=7 please give some example.
4. If i change the values for Recovery Window=3 and Redundancy=7 what will happened, how many days backup will be available in my FRA location?Explain with one scenario?
so i believe you can get the Answer from Your Question from Above details.
HTH

Basic question on setting Redundancy as the Retention policy

DB version:11g
I am planning to implement Differential Incremental Backup for my database. My strategy is
Sunday -->     Level 0 backup
Monday -->     Level 1 backup
Tuesday-->     Level 1 backup
Wednesday-->     Level 1 backup
Thursday-->     Level 1 backup
Friday-->     Level 1 backup
Saturday-->      Level 1 backup
Again, the new weekly backup cycle starts
Sunday -->     Level 0 backup
Monday -->     Level 1 backup
.Retention Policy set to Recovery Window
==========================
I understand What Recovery window retention policy means.If i configure
'CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;' This means only those backups which are older than 7 days will be reported as obsolete when the 'delete obsolete' command is executed.
Retention Policy set to Redundancy
=============================
But i am a bit confused about Retention Policy set to Redundancy:
Does
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;mean that you maintain 3 copies of backups on different disk locations ? How does this fit in with my above mentioned incremental backup strategy?

Thank you Centinul.
If REDUNDANY simply means maintain N number of copies of datafiles then what does
BACKUP DEVICE TYPE DISK COPIES 3 DATAFILE 7 FORMAT '/u02/orabkp/%U','/u01/oradata/%U';command do?Are they both the same?

Rman Retention policy to recovery window

Hi,
I have few basic doubts in RMAN backup policy
1 . Is that possible to set Retention policy to recovery window in minutes??
2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
Regards,
007

1) Syntax is .... TO RECOVERY WINDOW OF integer DAYS ... no other time statement.
2) Backups become obsolete when no longer needed to fulfil a retention policy. In a (theoretical) scenario, you perform a level 0 backup and then only incremental backups, the starting level 0 backup must be kept for ever (even if it WOULD be possible to define a recovery window in minutes).
Werner

E-business Suite RMAN backup retention

Hi,
i want to retain my backup for clone for 90 days. One parameter need to set at RMAN level is CONFIGURE RETENTION POLICY TO REDUNDANCY 90;
What other parameter need to set at DB level?
Thanks

i want to retain my backup for clone for 90 days. One parameter need to set at RMAN level is CONFIGURE RETENTION POLICY TO REDUNDANCY 90;
What other parameter need to set at DB level?Rman backup retention policy [ID 462978.1]
Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) [ID 360416.1]
RMAN : Consistent Backup, Restore and Recovery using RMAN [ID 162855.1]
Backup and Recovery
http://www.oracle.com/pls/db112/portal.portal_db?selected=4&frame=#backup_and_recovery
Thanks,
Hussein

RMAN retention policy - backup spfile and then redundancy = 5 removes it.

I have a database that is Oracle Standard Edition and it is version 9.2.0.6.
The spfile has not changed since November, 2005. A list backup does not show an spfile backup with a tag of "hot_database_spfile_backup_full". I took a close look at the RMAN script log and was shocked to discover that the spfile backup from the current day is being deleted. Is that because of the redundancy = 5? I'm trying to figure out why a backup piece from the current day is being deleted?
Examples follow.
The script deletes obsolete with redundancy = 5, however, I believe the intent was to keep 25 days because one of the configure clauses is set to a recovery window of 25 days. I realize that the redundancy overrides the configure retention policy command. I can fix the script and remove the redundancy = 5.
In the RMAN run statement, I first resync the catalog, backup the spfile, a full backup of the database including current controlfile plus archive log (delete input), resync catalog, switch logfile, and backup any additional archive logs. The backup looks fine.
Then, I allocate a channel for maintenance type sbt. The script then has a "delete noprompt expired backup;" a "delete noprompt obsolete redundancy = 5;" and finally, a crosscheck;
example of backup piece that is later deleted:
Starting backup at 07/18/2006 20:00:14
channel t1: starting full datafile backupset
channel t1: specifying datafile(s) in backupset
including current SPFILE in backupset
channel t1: starting piece 1 at 07/18/2006 20:00:14
channel t1: finished piece 1 at 07/18/2006 20:00:15
piece handle=P*****_2338_1_596145614_FULL comment=API Version 2.0,MMS Version 5.2.0.0
channel t1: backup set complete, elapsed time: 00:00:01
Finished backup at 07/18/2006 20:00:15
deletion:
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
<other lines deleted>
Backup Set 27453 07/18/2006 20:00:14
Backup Piece 27454 07/18/2006 20:00:14
P*****_2338_1_596145614_FULL
deleted backup piece
backup piece handle=P*****_2338_1_596145614_FULL recid=2039 stamp=596145614
Deleted 12 objects
Why is a backup piece created on 7/18 being deleted in the maintenance step?
Thanks in advance!

In the next step in the script, the controlfile and spfile are backed up:
backup
full
skip inaccessible
tag hot_database_backup_full
format '%d_%s_%p_%t_FULL'
(Database
include current controlfile)
Plus Archivelog delete input;
Even though my backup script is redundant by backing up the spfile twice, when I list the backup of the spfile, I would have expected to find 5 backups with a tag of hot_database_spfile_backup_full and 5 with a tag of hot_database_backup_full. That is not the case. I only find spfiles with a tag of hot_database_backup_full. i am still perplexed by RMAN.
I will modify my script - remove the backup of the spfile, and crosscheck before the delete commands. I will also remove the redundancy = 5. The intent is to keep 25 days of backups.
Thanks for your comments

Retention Policy to delete both backup sets and archivelogs automatically

I configured the Recovery Window-Based Retention Policy for my database for the window=14 days. I also set up a crontab to do a full backup every Monday. So say in a month, there will be 30 archive logs and 4 full DB backup sets.
Now that I understand if the FRA gets filled up, older archive logs that are not needed for the 14 days recoverable window will be automatically deleted. My questions is what happen to the old backup sets? Will they get deleted automatically too if there is no space left in FRA? Or I need to use "DELETE OBSOLETE" to delete them?
Thanks.

One of the advantages of the FRA is, in case of space pressure obsolete objects (obsolete due to the defined retention policy) are deleted automatically. That's true for backups and archivelogs. The objects are NOT deleted automatically after the retention policy expires, but only when additional space is needed. That does not mean you don't have to care about FRA space consumption. You may have unusual amounts of archivelogs, additional backups and flashback logs (if flashback database is configured), which fill up the FRA.
Werner

Recovery window retention policy deletes archive logs before a backup?

Hi All,
Oracle 11G on Windows 2008 R2
This afternoon, I changed my RMAN retention policy from 'RETENTION POLICY REDUNDANCY 3' to RETENTION POLICY RECOVERY WINDOW OF 3 DAYS'
However, i checked tonight and after my daily backup ran, all the archive logs prior to the backup had been deleted! Thus meaning i dont think i can restore to any point in time, prior to my daily backup. All the .arc logs were there after the backup. So i tried another test and kicked off the daily backup again. During the backup process, the archive logs got deleted again! Now i don't have any archive logs..
Is this proper behaviour of RETENTION POLICY RECOVERY WINDOW?? I thought it would keep all the files needed for me to restore to any point in time for the previous 3 days. When i used REDUNDANCY, with my daily backups, it kept 3 days worth of backups+ archive logs so i could restore point-in-time to any point. How can i use RECOVERY WINDOW so that i can actually restore to any point-in-time for the 3 days??
I wanted to change to RECOVERY WINDOW since i read that by using REDUNDANCY it only keeps X copies of a backup (so if i ran the backup 3 times in a day, i would only have those 3).
Thanks in advance.

Hi All,
Here is the SHOW ALL output:
RMAN> show all;
RMAN configuration parameters for database with db_unique_name MMSPRD7 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOA
D TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\DATABASE\ORA11G\DATABASE\SNCFM
MSPRD7.ORA'; # default
Here is the RMAN script:
Recovery Manager: Release 11.2.0.3.0 - Production on Mon Jan 20 23:03:12 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: XXX (DBID=)
RMAN> CROSSCHECK ARCHIVELOG ALL;
2> CROSSCHECK BACKUPSET;
3> CROSSCHECK BACKUP;
4> CROSSCHECK COPY;
5> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
6> DELETE NOPROMPT EXPIRED BACKUPSET;
7> DELETE NOPROMPT OBSOLETE;
8> BACKUP CURRENT CONTROLFILE;
9> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG DELETE INPUT;
Also, not sure if you needed the whole RMAN output, but here is the deletion part:
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 3 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           1392   15-JAN-14
Backup Piece       1392   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP
Backup Set           1393   15-JAN-14
Backup Piece       1393   15-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP
Backup Set           1397   16-JAN-14
Backup Piece       1397   16-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP
Backup Set           1400   17-JAN-14
Backup Piece       1400   17-JAN-14          F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_NNNDF_TAG20140115T190054_9FG89R8N_.BKP RECID=1392 STAMP=836938856
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_15\O1_MF_ANNNN_TAG20140115T192204_9FG9KDHX_.BKP RECID=1393 STAMP=836940124
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_16\O1_MF_ANNNN_TAG20140116T190027_9FJWNW6L_.BKP RECID=1397 STAMP=837025228
deleted backup piece
backup piece handle=F:\ORAFRA\MMSPRD7\BACKUPSET\2014_01_17\O1_MF_ANNNN_TAG20140117T190138_9FMK349M_.BKP RECID=1400 STAMP=837111700
Deleted 4 objects

RMAN Backups with retention policy to redundancy 1 doesn't work fine.

Hi experts,
I have a Oracle database with the following system backups:
Monday:       ArchiveLog Backup
Tuesday:      Full Backup
Wednesday: ArchiveLog Backup
Thursday:     ArchiveLog Backup
Friday :         Full Backup
Saturday:      ArchiveLog Backup
Sunday:       ArchiveLog Backup
ArchiveLog Backup = backup tag 'ARCHIVELOG_BACKUP' device type disk archivelog all not backed up delete all input;
Full Backup = backup tag 'FULL_BACKUP' device type disk database skip readonly plus archivelog tag 'FULL_BACKUP_ARCHIVELOGS';
                     crosscheck backup;
                     crosscheck copy;
                     delete noprompt obsolete;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 8;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
What this system has done until last two weeks? For example:
Tuesday :     Full Backup
Wednesday: ArchiveLog Backup
Thursday:     ArchiveLog Backup
Friday :         Full Backup - > After that, Full backup from Tuesday and ArchiveLog backups from Wed, and Thurs, are deleted. (Thanks to Retention policy) .
What this system do now?
Tuesday :     Full Backup
Wednesday: ArchiveLog Backup
Thursday:     ArchiveLog Backup
Friday :         Full Backup - > After that, Full backup from Tuesday are deleted but not ArchiveLog backups from Wed, and Thurs.
When I execute a crosscheck on RMAN return that all are AVAILABLE.
My question is: What is right? The system backups before or after?
Thanks for your help!

You are confused about the purpose of crosscheck.
There are two concepts for which you must grasp the distinction.
- Expired
- Obsolete
Expired
When an archive log is written, or rman makes a backup, a record of that archivelog or backupset is written to the repository in the control file.
Crosscheck simply checks the existence of the archivelogs or backupsets that are recorded in the repository. If something went missing (say, if you used an OS command to delete archivelogs), the record of the missing file is marked as 'expired'. If you follow the crosscheck command with a 'delete expired' command, the repository records that have been marked 'expired' are deleted from the repository, so rman has no more memory of those files. Note that 'expired' has nothing to do with retention policy. Also note that if you do not actually issue the 'delete expired' command, the expired records will remain in the repository.
Obsolete
The retention policy deals with when a backupset is obsolete, meaning it is no longer needed to protect the retention period. Backupset are not marked as obsolete. They are evaluated for obsolescence at the time of a command that needs it -- "report obsolete" or "delete obsolete", or when FRA maintenance requires an implied 'delete obsolete'.

Restoring RMAN backup from tape beyond retention policy ??

Hello Friends,
I just stuck in some basic finding. Need your help to resolve the questions.
How we can use RMAN backup to restore oracle database when the RMAN backup pushed to tape already and being a OLD backup ( before retention policy date).
Just to elaborate a more.. Say my retention policy is 3 days. I want to restore from a old backup like 30 days old.
So surely the requesting backup is behind retention date and has been pushed to tape.
Please suggest.
Thanks in advance.
Regards
Sinha.

dba.arnab wrote:
Hello Friends,
I just stuck in some basic finding. Need your help to resolve the questions.
How we can use RMAN backup to restore oracle database when the RMAN backup pushed to tape already and being a OLD backup ( before retention policy date).
Just to elaborate a more.. Say my retention policy is 3 days. I want to restore from a old backup like 30 days old.
So surely the requesting backup is behind retention date and has been pushed to tape.
Please suggest.
Thanks in advance.
Regards
Sinha.
Assuming the actual backup files still exist (the only thing actually deleted is the record of them in the catalog), you can make those files available and use the rman 'catalog' command to re-catalog them.

Reg retention policy in Windows server Backup

Please let me know how long time the backups will be maintained in Windows server Backup.
Is there any place where I can go and modify the retention policy?

The statements
"If the backup storage location is full, Windows Server Backup automatically deletes the oldest backup"
and
"If you do not delete the corresponding shadow copy, the backup sets will be always reserved."
are contradictory. As explained in the "Overview" section of the source you linked, the first statement is correct. It is not necessary that the server admin take any action to delete shadow copies in order to implement a retention
policy. When the backup destination drive gets full, WSB "automatically deletes the oldest backup version" (http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.aspx)
This all said, this behavior and the source cited are for Windows Server 2008.
The automatic disk space management behavior seems to have changed in Server 2012 (for example see this link: http://technet.microsoft.com/en-us/library/jj614621.aspx). Unfortunately I've not been able to determine
specifically how it is different.

Backup Retention Policy?

Similar Messages

Maybe you are looking for