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 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

Similar Messages

  • CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;

    Hi Guys
    Can you please put some light on the 0 days. what is the meaning on 0 days and how does this work.
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS; If I take full backup every night how many backup will it contain and how will it obsolete the backup.
    RMan 9i R2
    Soalris 5.9
    I understand the concept if recover window is 1 or more days but confuse with 0 days.
    Thank you in advance.

    RECOVERY WINDOW OF 0 DAYS is effective like REDUNDANCY 1.
    RMAN> configure retention policy to recovery window of 0 days;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
    new RMAN configuration parameters are successfully stored
    RMAN> backup datafile 4;
    Starting backup at 09-SEP-07
    using target database controlfile instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=15 devtype=DISK
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
    channel ORA_DISK_1: starting piece 1 at 09-SEP-07
    channel ORA_DISK_1: finished piece 1 at 09-SEP-07
    piece handle=E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 09-SEP-07
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 0 days
    no obsolete backups found
    RMAN> backup datafile 4;
    Starting backup at 09-SEP-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=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
    channel ORA_DISK_1: starting piece 1 at 09-SEP-07
    channel ORA_DISK_1: finished piece 1 at 09-SEP-07
    piece handle=E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 09-SEP-07
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 0 days
    Report of obsolete backups and copies
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           10     09-SEP-07
      Backup Piece       10     09-SEP-07          E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1
    RMAN> delete backup;
    using channel ORA_DISK_1
    List of Backup Pieces
    BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
    10      10      1   1   AVAILABLE   DISK        E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1
    11      11      1   1   AVAILABLE   DISK        E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1
    Do you really want to delete the above objects (enter YES or NO)? yes
    deleted backup piece
    backup piece handle=E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1 recid=10 stamp=632859727
    deleted backup piece
    backup piece handle=E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1 recid=11 stamp=632859802
    Deleted 2 objects
    RMAN> configure retention policy to redundancy 1;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    new RMAN configuration parameters are successfully stored
    RMAN> backup datafile 4;
    Starting backup at 09-SEP-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=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
    channel ORA_DISK_1: starting piece 1 at 09-SEP-07
    channel ORA_DISK_1: finished piece 1 at 09-SEP-07
    piece handle=E:\ORACLE\ORA92\DATABASE\0DIRHB90_1_1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 09-SEP-07
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    no obsolete backups found
    RMAN> backup datafile 4;
    Starting backup at 09-SEP-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=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
    channel ORA_DISK_1: starting piece 1 at 09-SEP-07
    channel ORA_DISK_1: finished piece 1 at 09-SEP-07
    piece handle=E:\ORACLE\ORA92\DATABASE\0EIRHB9H_1_1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 09-SEP-07
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    Report of obsolete backups and copies
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           12     09-SEP-07
      Backup Piece       12     09-SEP-07          E:\ORACLE\ORA92\DATABASE\0DIRHB90_1_1
    RMAN>

  • Not set configure retention policy to recovery window of 7 days

    HI all,
    if parameter "" configure retention policy to recovery window of 7 days "" is not set
    then i am taking weekly and inreamental cumulative backup any effect of backup
    i think in this case delete obsolete is not working.
    currently parameter set is CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

    HI all,
    if parameter "" configure retention policy to recovery window of 7 days "" is not set
    then i am taking weekly and inreamental cumulative backup any effect of backup
    i think in this case delete obsolete is not working.
    currently parameter set is CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

  • Retention policy to recovery window of 31 days means

    HI all,
    according to our company policy we need to restore database from last 7year.
    backup happen on SBT  TAPE.. we freez that tape for next 7 year.
    my doubt is we are taking backup using recovery catalog...daily basis we are taking backup using recovery catalog...but i have one doubt while configuring we have configure retention policy of recovery window 31 days..
    i m very much confused about this policy ..if we use this policy then can we able to recover database before 7 year or not..
    becacuse we are not firing any delete obsulate backup command on recovery catalog.
    we are only deleting archivelog by using delete nopromt archive log sysdate-3..
    so please suggest does it possible if renrtion policy to recovery window 31 days...i can able to restore this database before 31 days.
    Thanks,

    Hi there user12009184
    If you do not delete old backups through your rman script, then old backups will have to be deleted through your tape backup software. Unless you have endlessly large tapes ;-)
    So, yes you could theoretically restore from backups older than your retention window of 31 days.
    You should ensure that your control_file_record_keep_time is set to a value of 31 or larger (set it to your retention window period plus 1). Otherwise your control files will now know about your older backups.
    If you want to restore a very old backup, than you will need to restore a spfile and a control file first, then restore, then recover your database.
    You really, really need to test this. So that you know exactly how to do it and you have it documented.
    hope this helped,
    Andrew

  • 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

  • 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'.

  • Setting the retention Policy to recovery window.

    We are using Netbackup as a our third party tool for corporate backups and have used brbackup with backint on Windows for many years with great success.We would like to incorporate RMAN incremental backups for our backup strategy. Currently our retention policies through netbackup are:
    Backup              Retention
    Daily Online        2 weeks.
    Weekly Online     4 weeks.
    Monthly Online   12 months.
    Redologs            4 weeks.
    We would like to continue to retain the monthly backup. Other than setting the retention policy window to 365, how could we do this???? We would like to avoid growing a huge control file.
    Regards
    Scott

    Hello Scott,
    > We would like to avoid growing a huge control file.
    Ok nice approach, but the (RMAN) data in the control file is reused after the value of the init parameter CONTROL_FILE_RECORD_KEEP_TIME. (has nothing todo with the retention policy)
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams029.htm#CHDDBCDB
    > Other than setting the retention policy window to 365, how could we do this????
    You can use the KEEP clause with the command BACKUP or CHANGE.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta035.htm#i97063
    Regards
    Stefan

  • Control_file_record_time -retention policy to recover window

    Hi:
    If i have control_file_record_time=7 and retention policy to recover window=3 can i still go back and recover upto the last 5th day provided the backups are available.If i have run delete obsolete at the end of 5th day it will delete obsolete backups from the disk but i have the copies stored on some othere disks ...how does rman deal with obsolete but control file still having backup information.
    Are they related in anyway or just the obsolete command is for DBA convinence to delete the obsolete backups and does not play a factor during recovery
    Thanks,
    Ganesh

    Hi there user12009184
    If you do not delete old backups through your rman script, then old backups will have to be deleted through your tape backup software. Unless you have endlessly large tapes ;-)
    So, yes you could theoretically restore from backups older than your retention window of 31 days.
    You should ensure that your control_file_record_keep_time is set to a value of 31 or larger (set it to your retention window period plus 1). Otherwise your control files will now know about your older backups.
    If you want to restore a very old backup, than you will need to restore a spfile and a control file first, then restore, then recover your database.
    You really, really need to test this. So that you know exactly how to do it and you have it documented.
    hope this helped,
    Andrew

  • Retention policy not removing items after 14 days?

    Hello and good day all.
    I hope some one can help with this. I have an Exchange 2013 server and i need to set a Retention policy to delete items from select mailboxes after 14 days. These boxes get automated log emails that are only needed if a problem is reported that day. Otherwise
    they are trash.  no users check these boxes and so they tend to fill up.
    The following was all done in the web interface.
    In "Retention tags" screen I have a policy called "14Days" and it is set "Delete and allow Recovery" then period is "In Days" 14
    This is then in the "Retention Policy" Screen added to a policy called "2Weeks"
    I then added this in "Mailbox Features" screen to the select boxes.
    All this done 26 days ago. I figured i need to wait the 14 days for the cycle to come around.  However these boxes still have items from September in them.  I used a command line to verify the policy is on the mail boxes.
    Some items are in the in-boxes and some are in deleted items.
    Steven Davis of Parabit Systems

    Hello and good morning.  The mystery continues.
    in event log is have items 9017 saying the work cycle started and there are 14 boxes on this data base. Then i have an event 9018 saying 14 were processed. 
    Does it matter that I have 4 Mailbox databases? the ones to have this policy are all in a single data base.
    There are no other policy's created or defined other then the ones that came with exchange that we don't use.
    I created a new policy with a 15 day retention and applied it to a box.
    Next i cleared the entire event log and then ran "Start-ManagedFolderAssistant" to force it on
    the mailbox.
    so then just to check i ran "Get-RetentionPolicyTag
    -Identity "15 day retention " | fl"
    And it looks okay.
    RunspaceId                            : b9b594a6-9e08-4ddd-aa68-5998e687388c
    MessageClassDisplayName               : All Mailbox Content
    MessageClass                          : *
    Description                           : Managed Content Settings
    RetentionEnabled                      : True
    RetentionAction                       : DeleteAndAllowRecovery
    AgeLimitForRetention                  : 15.00:00:00
    MoveToDestinationFolder               : 
    TriggerForRetention                   : WhenDelivered
    MessageFormatForJournaling            : UseTnef
    JournalingEnabled                     : False
    AddressForJournaling                  : 
    LabelForJournaling                    : 
    Type                                  : All
    IsDefaultAutoGroupPolicyTag           : False
    IsDefaultModeratedRecipientsPolicyTag : False
    SystemTag                             : False
    LocalizedRetentionPolicyTagName       : {}
    Comment                               : for field techs retention and a test to see why 14 day is not working
    RetentionId                           : a61c470b-367b-4cb9-b955-b02ff9c5a1c3
    LocalizedComment                      : {}
    MustDisplayCommentEnabled             : False
    LegacyManagedFolder                   : 
    AdminDisplayName                      : 
    ExchangeVersion                       : 1.0 (14.0.100.0)
    Name                                  : 15 day retention
    DistinguishedName                     : CN=15 day retention,CN=Retention Policy Tag Container,CN=First 
                                            Organization,CN=Microsoft 
                                            Exchange,CN=Services,CN=Configuration,DC=parabit,DC=com
    Identity                              : 15 day retention
    Guid                                  : a61c470b-367b-4cb9-b955-b02ff9c5a1c3
    ObjectCategory                        : parabit.com/Configuration/Schema/ms-Exch-ELC-Folder
    ObjectClass                           : {top, msExchELCFolder}
    WhenChanged                           : 1/7/2015 12:18:29 PM
    WhenCreated                           : 1/7/2015 12:18:29 PM
    WhenChangedUTC                        : 1/7/2015 5:18:29 PM
    WhenCreatedUTC                        : 1/7/2015 5:18:29 PM
    OrganizationId                        : 
    OriginatingServer                     : DMZAD.parabit.com
    IsValid                               : True
    ObjectState                           : Unchanged
    Steven Davis of Parabit Systems

  • 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

  • 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

  • RMAN Recovery Window 7 days setting - shows no obsolete backups

    Hi All. Quick question about RMAN retention policy....
    I have the current backup strategy:
    Full backup (0) -> Sunday
    Incremental backup (1) -> Monday - Saturday
    Archive log backups -> every hour
    This is a new database I just started taking backups on last month. (1st full backup was run October 4th)
    I currently have not deleted any of them.
    The old RMAN RETENTION POLICY was set to REDUNDANCY = 1
    REPORT OBSOLETE lists all of them up to the last full which ran this past Sunday (Nov 1st)
    I just switched the RMAN RETENTION POLICY to RECOVERY WINDOW of 7 DAYS
    REPORT OBSOLETE lists no backups obsolete...
    Shouldn't I see all the backups prior to a week ago or does it only take affect for backups run under the new policy?
    Any help/replies are apprecitaed.
    Thanks

    Ran crosscheck with no problems:
    Crosschecked 200 objects
    But still same results for:
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    no obsolete backups found
    Am I missing something here? Or like I mentioned is this expected behaviour because all of my other backups were run with REDUNDANCY = 1 retention policy?
    Thanks

  • Retention policy for incremental cumulative backup question

    Hi,
    I have a production database configured with retention policy for 30 days window. No catalog is used.
    The backup plan is:
    Sunday - Level 0 backup.
    Weekdays - Incremental 1 cumulative backup.
    I also noticed that some archive logs since Mar 07 2010 has become obsolete in the recent few days.
    Cannot figure out why the backup of Mar 07 2010 is going to be obsolete today.
    Thanks for your help!
    RMAN> list backup summary;
    using target database control file instead of recovery catalog
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
    *14 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
    *15 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
    *17 B F A SBT_TAPE 07-MAR-10 1 1 NO*
    21 B F A SBT_TAPE 08-MAR-10 1 1 NO
    24 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    25 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    27 B F A SBT_TAPE 08-MAR-10 1 1 NO
    35 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    36 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    38 B F A SBT_TAPE 09-MAR-10 1 1 NO
    46 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    47 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    49 B F A SBT_TAPE 10-MAR-10 1 1 NO
    57 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    58 B 1 A SBT_TAPE 11-MAR-10 2 1 NO
    60 B F A SBT_TAPE 11-MAR-10 1 1 NO
    66 B A A SBT_TAPE 12-MAR-10 1 1 NO
    67 B A A SBT_TAPE 12-MAR-10 1 1 NO
    68 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    69 B 1 A SBT_TAPE 12-MAR-10 2 1 NO
    70 B A A SBT_TAPE 12-MAR-10 1 1 NO
    71 B F A SBT_TAPE 12-MAR-10 1 1 NO
    77 B A A SBT_TAPE 14-MAR-10 1 1 NO
    78 B A A SBT_TAPE 14-MAR-10 1 1 NO
    79 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
    80 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
    81 B A A SBT_TAPE 14-MAR-10 1 1 NO
    82 B F A SBT_TAPE 14-MAR-10 1 1 NO
    88 B A A SBT_TAPE 15-MAR-10 1 1 NO
    89 B A A SBT_TAPE 15-MAR-10 1 1 NO
    90 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    91 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    92 B A A SBT_TAPE 15-MAR-10 1 1 NO
    93 B F A SBT_TAPE 15-MAR-10 1 1 NO
    99 B A A SBT_TAPE 16-MAR-10 1 1 NO
    100 B A A SBT_TAPE 16-MAR-10 1 1 NO
    101 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    102 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    103 B A A SBT_TAPE 16-MAR-10 1 1 NO
    104 B F A SBT_TAPE 16-MAR-10 1 1 NO
    109 B A A SBT_TAPE 17-MAR-10 4 1 NO
    110 B F A SBT_TAPE 17-MAR-10 1 1 NO
    111 B A A SBT_TAPE 17-MAR-10 1 1 NO
    112 B F A SBT_TAPE 17-MAR-10 1 1 NO
    113 B A A SBT_TAPE 17-MAR-10 1 1 NO
    114 B A A SBT_TAPE 17-MAR-10 1 1 NO
    115 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    116 B 1 A SBT_TAPE 17-MAR-10 2 1 NO
    117 B A A SBT_TAPE 17-MAR-10 1 1 NO
    118 B F A SBT_TAPE 17-MAR-10 1 1 NO
    123 B A A SBT_TAPE 18-MAR-10 2 1 NO
    124 B F A SBT_TAPE 18-MAR-10 1 1 NO
    125 B A A SBT_TAPE 18-MAR-10 2 1 NO
    126 B F A SBT_TAPE 18-MAR-10 1 1 NO
    127 B A A SBT_TAPE 18-MAR-10 1 1 NO
    128 B F A SBT_TAPE 18-MAR-10 1 1 NO
    129 B A A SBT_TAPE 18-MAR-10 1 1 NO
    130 B F A SBT_TAPE 18-MAR-10 1 1 NO
    131 B A A SBT_TAPE 18-MAR-10 1 1 NO
    132 B A A SBT_TAPE 18-MAR-10 1 1 NO
    133 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    134 B 1 A SBT_TAPE 18-MAR-10 2 1 NO
    135 B A A SBT_TAPE 18-MAR-10 1 1 NO
    136 B F A SBT_TAPE 18-MAR-10 1 1 NO
    142 B A A SBT_TAPE 19-MAR-10 2 1 NO
    143 B F A SBT_TAPE 19-MAR-10 1 1 NO
    144 B A A SBT_TAPE 19-MAR-10 1 1 NO
    145 B F A SBT_TAPE 19-MAR-10 1 1 NO
    146 B A A SBT_TAPE 19-MAR-10 1 1 NO
    147 B F A SBT_TAPE 19-MAR-10 1 1 NO
    148 B A A SBT_TAPE 19-MAR-10 1 1 NO
    149 B F A SBT_TAPE 19-MAR-10 1 1 NO
    150 B A A SBT_TAPE 19-MAR-10 1 1 NO
    151 B A A SBT_TAPE 19-MAR-10 1 1 NO
    152 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    153 B 1 A SBT_TAPE 19-MAR-10 2 1 NO
    154 B A A SBT_TAPE 19-MAR-10 1 1 NO
    155 B F A SBT_TAPE 19-MAR-10 1 1 NO
    161 B A A SBT_TAPE 21-MAR-10 1 1 NO
    162 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
    163 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
    164 B A A SBT_TAPE 21-MAR-10 1 1 NO
    165 B F A SBT_TAPE 21-MAR-10 1 1 NO
    171 B A A SBT_TAPE 22-MAR-10 1 1 NO
    172 B F A SBT_TAPE 22-MAR-10 1 1 NO
    173 B A A SBT_TAPE 22-MAR-10 1 1 NO
    174 B F A SBT_TAPE 22-MAR-10 1 1 NO
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.ccbprod)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_ccbprod.f'; # default
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 30 days
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Control File Copy 108 19-FEB-10 /ccbprod/oradata/ccbprod/arc/control.bak.100219.21.21
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       19     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_5_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       18     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_4_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       17     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_3_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       16     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_2_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       15     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_1_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       14     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_5_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       13     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_4_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       12     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_3_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       11     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_2_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       10     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_1_1
    Backup Set 10 07-MAR-10 Backup Piece 21 07-MAR-10 c-2894189962-20100307-00
    Edited by: user12019850 on 22-Mar-2010 10:53 AM

    Another database with the same configuration and same plan seems fine:
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.cisconf)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_cisconf.f'; # default
    RMAN> list backup summary;
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
    774 B 0 A SBT_TAPE 19-FEB-10 1 1 NO
    775 B 0 A SBT_TAPE 19-FEB-10 2 1 NO
    795 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
    796 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
    797 B A A SBT_TAPE 20-FEB-10 1 1 NO
    803 B A A SBT_TAPE 20-FEB-10 1 1 NO
    804 B F A SBT_TAPE 20-FEB-10 1 1 NO
    805 B A A SBT_TAPE 20-FEB-10 1 1 NO
    806 B F A SBT_TAPE 20-FEB-10 1 1 NO
    807 B A A SBT_TAPE 20-FEB-10 1 1 NO
    808 B F A SBT_TAPE 20-FEB-10 1 1 NO
    809 B A A SBT_TAPE 21-FEB-10 1 1 NO
    810 B 0 A SBT_TAPE 21-FEB-10 1 1 NO
    811 B 0 A SBT_TAPE 21-FEB-10 2 1 NO
    812 B A A SBT_TAPE 21-FEB-10 1 1 NO
    813 B F A SBT_TAPE 21-FEB-10 1 1 NO
    818 B A A SBT_TAPE 21-FEB-10 1 1 NO
    819 B F A SBT_TAPE 21-FEB-10 1 1 NO
    820 B A A SBT_TAPE 21-FEB-10 1 1 NO
    821 B F A SBT_TAPE 21-FEB-10 1 1 NO
    822 B A A SBT_TAPE 21-FEB-10 1 1 NO
    823 B F A SBT_TAPE 21-FEB-10 1 1 NO
    824 B A A SBT_TAPE 22-FEB-10 1 1 NO
    825 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
    826 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
    827 B A A SBT_TAPE 22-FEB-10 1 1 NO
    828 B F A SBT_TAPE 22-FEB-10 1 1 NO
    833 B A A SBT_TAPE 22-FEB-10 1 1 NO
    834 B F A SBT_TAPE 22-FEB-10 1 1 NO
    835 B A A SBT_TAPE 22-FEB-10 1 1 NO
    836 B F A SBT_TAPE 22-FEB-10 1 1 NO
    837 B A A SBT_TAPE 22-FEB-10 1 1 NO
    838 B F A SBT_TAPE 22-FEB-10 1 1 NO
    839 B A A SBT_TAPE 22-FEB-10 1 1 NO
    840 B F A SBT_TAPE 22-FEB-10 1 1 NO
    841 B A A SBT_TAPE 23-FEB-10 1 1 NO
    842 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
    843 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
    844 B A A SBT_TAPE 23-FEB-10 1 1 NO
    845 B F A SBT_TAPE 23-FEB-10 1 1 NO
    850 B A A SBT_TAPE 23-FEB-10 1 1 NO
    851 B F A SBT_TAPE 23-FEB-10 1 1 NO
    852 B A A SBT_TAPE 23-FEB-10 1 1 NO
    853 B F A SBT_TAPE 23-FEB-10 1 1 NO
    854 B A A SBT_TAPE 23-FEB-10 1 1 NO
    855 B F A SBT_TAPE 23-FEB-10 1 1 NO
    856 B A A SBT_TAPE 24-FEB-10 1 1 NO
    857 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    858 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    859 B A A SBT_TAPE 24-FEB-10 1 1 NO
    860 B F A SBT_TAPE 24-FEB-10 1 1 NO
    865 B A A SBT_TAPE 24-FEB-10 1 1 NO
    866 B F A SBT_TAPE 24-FEB-10 1 1 NO
    867 B A A SBT_TAPE 24-FEB-10 1 1 NO
    868 B F A SBT_TAPE 24-FEB-10 1 1 NO
    869 B A A SBT_TAPE 24-FEB-10 1 1 NO
    870 B F A SBT_TAPE 24-FEB-10 1 1 NO
    871 B A A SBT_TAPE 24-FEB-10 1 1 NO
    872 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    873 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    874 B A A SBT_TAPE 24-FEB-10 1 1 NO
    875 B F A SBT_TAPE 24-FEB-10 1 1 NO
    880 B A A SBT_TAPE 24-FEB-10 1 1 NO
    881 B F A SBT_TAPE 24-FEB-10 1 1 NO
    882 B A A SBT_TAPE 25-FEB-10 1 1 NO
    883 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
    884 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
    885 B A A SBT_TAPE 25-FEB-10 1 1 NO
    886 B F A SBT_TAPE 25-FEB-10 1 1 NO
    891 B A A SBT_TAPE 25-FEB-10 1 1 NO
    892 B F A SBT_TAPE 25-FEB-10 1 1 NO
    893 B A A SBT_TAPE 25-FEB-10 1 1 NO
    894 B F A SBT_TAPE 25-FEB-10 1 1 NO
    895 B A A SBT_TAPE 25-FEB-10 1 1 NO
    896 B F A SBT_TAPE 25-FEB-10 1 1 NO
    897 B A A SBT_TAPE 25-FEB-10 1 1 NO
    898 B F A SBT_TAPE 25-FEB-10 1 1 NO
    899 B A A SBT_TAPE 25-FEB-10 1 1 NO
    900 B F A SBT_TAPE 25-FEB-10 1 1 NO
    901 B A A SBT_TAPE 25-FEB-10 1 1 NO
    902 B F A SBT_TAPE 25-FEB-10 1 1 NO
    903 B A A SBT_TAPE 26-FEB-10 1 1 NO
    904 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
    905 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
    906 B A A SBT_TAPE 26-FEB-10 1 1 NO
    907 B F A SBT_TAPE 26-FEB-10 1 1 NO
    912 B A A SBT_TAPE 26-FEB-10 1 1 NO
    913 B F A SBT_TAPE 26-FEB-10 1 1 NO
    914 B A A SBT_TAPE 26-FEB-10 1 1 NO
    915 B F A SBT_TAPE 26-FEB-10 1 1 NO
    916 B A A SBT_TAPE 26-FEB-10 1 1 NO
    917 B F A SBT_TAPE 26-FEB-10 1 1 NO
    918 B A A SBT_TAPE 27-FEB-10 1 1 NO
    919 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
    920 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
    921 B A A SBT_TAPE 27-FEB-10 1 1 NO
    922 B F A SBT_TAPE 27-FEB-10 1 1 NO
    927 B A A SBT_TAPE 27-FEB-10 1 1 NO
    928 B F A SBT_TAPE 27-FEB-10 1 1 NO
    929 B A A SBT_TAPE 27-FEB-10 1 1 NO
    930 B F A SBT_TAPE 27-FEB-10 1 1 NO
    931 B A A SBT_TAPE 27-FEB-10 1 1 NO
    932 B F A SBT_TAPE 27-FEB-10 1 1 NO
    933 B A A SBT_TAPE 28-FEB-10 1 1 NO
    934 B 0 A SBT_TAPE 28-FEB-10 1 1 NO
    935 B 0 A SBT_TAPE 28-FEB-10 2 1 NO
    936 B A A SBT_TAPE 28-FEB-10 1 1 NO
    937 B F A SBT_TAPE 28-FEB-10 1 1 NO
    942 B A A SBT_TAPE 28-FEB-10 1 1 NO
    943 B F A SBT_TAPE 28-FEB-10 1 1 NO
    944 B A A SBT_TAPE 28-FEB-10 1 1 NO
    945 B F A SBT_TAPE 28-FEB-10 1 1 NO
    946 B A A SBT_TAPE 28-FEB-10 1 1 NO
    947 B F A SBT_TAPE 28-FEB-10 1 1 NO
    948 B A A SBT_TAPE 01-MAR-10 1 1 NO
    949 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
    950 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
    951 B A A SBT_TAPE 01-MAR-10 1 1 NO
    952 B F A SBT_TAPE 01-MAR-10 1 1 NO
    957 B A A SBT_TAPE 01-MAR-10 1 1 NO
    958 B F A SBT_TAPE 01-MAR-10 1 1 NO
    959 B A A SBT_TAPE 01-MAR-10 1 1 NO
    960 B F A SBT_TAPE 01-MAR-10 1 1 NO
    961 B A A SBT_TAPE 01-MAR-10 1 1 NO
    962 B F A SBT_TAPE 01-MAR-10 1 1 NO
    963 B A A SBT_TAPE 02-MAR-10 1 1 NO
    964 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
    965 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
    966 B A A SBT_TAPE 02-MAR-10 1 1 NO
    967 B F A SBT_TAPE 02-MAR-10 1 1 NO
    970 B A A SBT_TAPE 02-MAR-10 1 1 NO
    971 B F A SBT_TAPE 02-MAR-10 1 1 NO
    972 B A A SBT_TAPE 02-MAR-10 1 1 NO
    973 B F A SBT_TAPE 02-MAR-10 1 1 NO
    974 B A A SBT_TAPE 02-MAR-10 1 1 NO
    975 B F A SBT_TAPE 02-MAR-10 1 1 NO
    976 B A A SBT_TAPE 03-MAR-10 1 1 NO
    977 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
    978 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
    979 B A A SBT_TAPE 03-MAR-10 1 1 NO
    980 B F A SBT_TAPE 03-MAR-10 1 1 NO
    983 B A A SBT_TAPE 03-MAR-10 1 1 NO
    984 B F A SBT_TAPE 03-MAR-10 1 1 NO
    985 B A A SBT_TAPE 03-MAR-10 1 1 NO
    986 B F A SBT_TAPE 03-MAR-10 1 1 NO
    987 B A A SBT_TAPE 03-MAR-10 1 1 NO
    988 B F A SBT_TAPE 03-MAR-10 1 1 NO
    989 B A A SBT_TAPE 04-MAR-10 1 1 NO
    990 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
    991 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
    992 B A A SBT_TAPE 04-MAR-10 1 1 NO
    993 B F A SBT_TAPE 04-MAR-10 1 1 NO
    996 B A A SBT_TAPE 04-MAR-10 1 1 NO
    997 B F A SBT_TAPE 04-MAR-10 1 1 NO
    998 B A A SBT_TAPE 04-MAR-10 1 1 NO
    999 B F A SBT_TAPE 04-MAR-10 1 1 NO
    1000 B A A SBT_TAPE 04-MAR-10 1 1 NO
    1001 B F A SBT_TAPE 04-MAR-10 1 1 NO
    1002 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1003 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
    1004 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
    1005 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1006 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1009 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1010 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1011 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1012 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1013 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1014 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1015 B A A SBT_TAPE 06-MAR-10 1 1 NO
    1016 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
    1017 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
    1018 B A A SBT_TAPE 06-MAR-10 1 1 NO
    1019 B F A SBT_TAPE 06-MAR-10 1 1 NO
    1022 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1023 B 0 A SBT_TAPE 07-MAR-10 1 1 NO
    1024 B 0 A SBT_TAPE 07-MAR-10 2 1 NO
    1025 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1026 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1029 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1030 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1031 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1032 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1033 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1034 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1035 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1036 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1037 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1038 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1039 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1042 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1043 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1044 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1045 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1046 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1047 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1048 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1054 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1055 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1056 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    1057 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    1058 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1059 B F A SBT_TAPE 09-MAR-10 1 1 NO
    1065 B A A SBT_TAPE 10-MAR-10 1 1 NO
    1066 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    1067 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    1068 B A A SBT_TAPE 10-MAR-10 1 1 NO
    1069 B F A SBT_TAPE 10-MAR-10 1 1 NO
    1075 B A A SBT_TAPE 11-MAR-10 1 1 NO
    1076 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    1077 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    1078 B A A SBT_TAPE 11-MAR-10 1 1 NO
    1079 B F A SBT_TAPE 11-MAR-10 1 1 NO
    1085 B A A SBT_TAPE 12-MAR-10 1 1 NO
    1086 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    1087 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    1088 B A A SBT_TAPE 12-MAR-10 1 1 NO
    1089 B F A SBT_TAPE 12-MAR-10 1 1 NO
    1094 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1095 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1096 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
    1097 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
    1098 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1099 B F A SBT_TAPE 13-MAR-10 1 1 NO
    1105 B A A SBT_TAPE 14-MAR-10 1 1 NO
    1106 B 0 A SBT_TAPE 14-MAR-10 1 1 NO
    1107 B 0 A SBT_TAPE 14-MAR-10 2 1 NO
    1108 B A A SBT_TAPE 14-MAR-10 1 1 NO
    1109 B F A SBT_TAPE 14-MAR-10 1 1 NO
    1115 B A A SBT_TAPE 15-MAR-10 1 1 NO
    1116 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    1117 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    1118 B A A SBT_TAPE 15-MAR-10 1 1 NO
    1119 B F A SBT_TAPE 15-MAR-10 1 1 NO
    1125 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1126 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1127 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    1128 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    1129 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1130 B F A SBT_TAPE 16-MAR-10 1 1 NO
    1136 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1137 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1138 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    1139 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    1140 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1141 B F A SBT_TAPE 17-MAR-10 1 1 NO
    1147 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1148 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1149 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    1150 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    1151 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1152 B F A SBT_TAPE 18-MAR-10 1 1 NO
    1158 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1159 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1160 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    1161 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    1162 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1163 B F A SBT_TAPE 19-MAR-10 1 1 NO
    1169 B A A SBT_TAPE 20-MAR-10 1 1 NO
    1170 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
    1171 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
    1172 B A A SBT_TAPE 20-MAR-10 1 1 NO
    1173 B F A SBT_TAPE 20-MAR-10 1 1 NO
    1179 B A A SBT_TAPE 21-MAR-10 1 1 NO
    1180 B 0 A SBT_TAPE 21-MAR-10 1 1 NO
    1181 B 0 A SBT_TAPE 21-MAR-10 2 1 NO
    1182 B A A SBT_TAPE 21-MAR-10 1 1 NO
    1183 B F A SBT_TAPE 21-MAR-10 1 1 NO
    1189 B A A SBT_TAPE 22-MAR-10 1 1 NO
    1190 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
    1191 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
    1192 B A A SBT_TAPE 22-MAR-10 1 1 NO
    1193 B F A SBT_TAPE 22-MAR-10 1 1 NO
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 30 days
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Control File Copy 47 20-FEB-10 /dbbackup/cisconf/control.bak.20100220
    Backup Set 804 20-FEB-10
    Backup Piece 551 20-FEB-10 c-3316101807-20100220-01
    Edited by: user12019850 on 22-Mar-2010 11:03 AM

  • Recovery Window-Based Retention VS Redundancy-Based Retention

    Hi Experts,
    We'd like to know your take on the use of Recovery Window-Based Retention Policy e.g.
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;against the use of Redundancy-Based Retention Policy, e.g.
    CONFIGURE RETENTION POLICY TO REDUNDANCY 7;Do you have any recommendations or preferences to which should be used? Is there a preferred method by oracle?
    We're currently setting up RMAN for a client that's using Oracle 11.1.0.7 standard edition, so is there a preference to what's better suited for the standard edition? The plan is to back up data to Disk, and this data will be then backed up to tape.
    Thanks

    REDUNDANCY 7 is 7 backups -- irrespective of the number of days.
    If you are running only 1 backup a day, you'd assume that it is equivalent to 7 days. However, if one day you run a backup twice, then the 7-day old backup becomes redundant ! If, the next day, you again run the backup twice, the 5-day old backup becomes redundant ! (Conversely, if you don't run a backup for 2 days, then even the 9 day old backup is not redundant !).
    So, be aware (or beware) that any adhoc backup runs or changes to the backup frequency would change your retention duration (and if this happens 6 months from now, the IT Manager / DBA onsite may not know that retention has changed !)
    Hemant K Chitae

  • Understanding report need backup recovery window ..

    Hello,
    I have a big database which backed up within several days at night time. The retention policy is "recovery window of 3 days". I've tried to analyze the results of
    report need backup;But I noticed than this command return just the list of datafiles having latest backup older than 3 days. I've tried to read again the docs:
    >
    Reports data files for which there are not sufficient backups to satisfy a recovery window-based retention policy for the specified number of days, that is, data files without sufficient backups for point-in-time recovery to any point back to the time SYSDATE - integer.
    >
    Please correct me if I'm wrong, but I consider that the ability to make recover to any point in time within 3 days require the backup taken earlier than 3 days ago and archivelogs from the time when backup was taken to the recover PIT. Im I right? If so then how I should interprete the results of report need backup ? I can't find the detailed explanations of this in the docs :(
    Thanks in advance,
    Constantine

    You are correct in your appreciations.
    This report is about the need of backups, without considering archivelog backups.
    It does not mean that listed files are in an unrecoverable situation.
    Regards.

Maybe you are looking for

  • How to delete duplicate songs in ipod "recently added" folder

    Hi, For some reason I have multiple duplicate entries of the same songs in my iPod. How do i clean these up? iTunes will not let me delete these (in the Edit menu the "Delete" option is grayed out). TIA!

  • Real Estate Lock Box Key

    I have owned three Palms and now on my 4th.  The very first one,second one and third was able to be integrated with the software/programming to be installed into my phone for the ability to open realtor lock boxes.  ALL Palms have infrared  so once i

  • Workbook Printing Issues???

    Most of the clients work on Discoverer Plus so that they can develop & manage workbooks. But when it comes to printing Plus is missing a vital feature of Print Preview. I checked its available in Desktop version & Viewer but why its missing in Plus??

  • Doubt in message monitoring

    Hi, For a file-file scenario, in sxmb_moni, the message has AENGINE as both inbound and outbound. But should it not be AENGINE-IENGINE and IENGINE-AENGINE, since the message is transferred from sender adapter to IE (where mapping is done) and then tr

  • B1DE namespace support

    I understand that from January 2009, SAP are only letting partners register for namespaces over 5 characters.  The installation of the B1DE does not support namespaces longer that 4 characters.  Does anyone know when the B1DE will be updated to suppo