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

Similar Messages

  • What's the difference between redundancy and recovery window for retention?

    Hello all,
    I'm still trying to get a grip on this concept for RMAN backup planning.
    I recently ran into a situation as follows.
    I have the backups set to a redundancy of 1.
    I have instance1, which had GRID jobs to run RMAN backups as follows
    Incremental database level=0 weekly at Wed at 2:30am
    I have daily backups, incremental level=1 each evening
    I have archive log backups through the day.
    What happened, was that apparently on a Tues some time, the development team deleted data from almost every table in their schema.
    The didn't discover this till midday or so on Wednesday.
    I went to try to restore...and RMAN couldn't do it. I had found a SCN for early the Tues they did it...but I got the following error:
    RMAN> RUN
    2> {
    3> SET UNTIL SCN 4590383198282;
    4> RESTORE DATABASE;
    5> RECOVER DATABASE;
    6> }
    executing command: SET until clause
    Starting restore at 28-APR-10
    allocated channel: ORA_SBT_TAPE_1
    channel ORA_SBT_TAPE_1: SID=639 device type=SBT_TAPE
    channel ORA_SBT_TAPE_1: NMO v4.5.0.0
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=638 device type=DISK
    creating datafile file number=1 name=+DATADG/instance1/datafile/system.284.697137287
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 04/28/2010 15:53:00
    ORA-01180: can not create datafile 1
    ORA-01110: data file 1: '+DATADG/instance1/datafile/system.284.697137287'
    From what research I did...it appears that since I did not have a level=0 incremental from before, it could not reset the database back in time. The previous one had been deleted since, I guess I had a redundancy of 1.
    So, I thought I had a week backup they way I have it set..but that assumes that errors are found pretty quickly before the next level=0 backup.
    I want at least 1 to 1.5 weeks worth of backups. I do have the problem that we do not have many tapes in rotation, so I cannot go for too long...may 2x weeks tops.
    I'm trying to rethink my strategy, but I'm confused as I read as to the difference between setting RMAN retention with redundancy vs recovery window.
    Can someone give me an explanation how you understand it? I'm reading on the web and in oracle books, and for some reason, it just isn't clear to me what is the best way to go....especially when I see that redundancy and recovery window might both be set??
    Thank you in advance,
    cayenne

    Dear Cayenne
    AFAIK RMAN doesn't claim that "you haven't enough backup". Please read the error you got carefully
    ORA-01180: can not create datafile 1
    ORA-01110: data file 1: '+DATADG/instance1/datafile/system.284.697137287'
    and check the following link:
    ORA-01180: Cannot create datafile 1 when doing RMAN restore onto 2nd server
    Moreover, could you please use LIST BACKUP command and see whether you have enough backups?
    Read "Redundancy Based Backup Retention Policy" from the following link:
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/strategy003.htm#sthref139

  • 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 Retention Policy - redundancy vs recovery window

    Hi All,
    I'm wondering what the most commonly used rman retention policy is, to provide point-in-time recovery. We have 2 oracle servers, one using redundancy policy (3) and the other using recovery window (2 days). I would like to standardize them but am not confident in which direction I should go in.
    I'm tempted to lean towards redundancy but wanted to pose the question to a wider, experienced audience for any things to think about/watch out for. Also, I assume the restore process would the same for either.
    Thanks in advance.

    Redundancy based retention policy means how many backups of each datafile must be retained and Recovery windows based retention policy is a period of time which starts with current time and goes backward in time upto the point of recoverability.
    Oracle suggests and its Best practice is "Recovery Window" .( I don't know the reason though)
    Two things you need to consider:
    1) You might need more space in case of "recovery window" because it depends upon the schedule of the backup. In "redundancy" , your space consumption will be same.
    2) You need to keep "recovery window" time less than the value of "control_file_Record_keep_time" so your backup records won't be overwritten in controlfile.
    We use "Recovery Window"

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

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

  • 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

  • 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

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

  • 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

  • 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

  • Difference between redundancy & recovery window, rman

    Hi All,
    i want to know the difference between following two commands i.e.
    1. configure retention policy to redundancy 1;
    2. configure retention policy to recovery window of 1 days;
    we are taking rman based FULL backup every night, so just want to keep one day old backup, would like to know which one of the above is more appropriate.
    Regards,

    Nayyares,
    You should read this section of the docs,
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1008093
    Redundanc is nothing but the number of copies. So you decide that you want to keep all the time , 3 copies of the backup of your db, you are going to use this. This serves the purpose that you can use this backup for whatever period of time in the past. Any copies before than these mentioned copies, will be marked obsolete by oracle. So if the number is 2 and , for example, you took first backups with tags A, B. Now when you will take the next backup with TAG C , A will be marked as obsolete. The most recent number of copies are kept irrespective of the time.
    Recovery window is that for how long , you want to go back in the past and be assured that the backup you have is sufficient for the recovery of db. This puts no limitations on the number of copies as like the Redundancy setting. So depending on your SLA, you may use the window timings.
    Both the settings are mutually exclusive so you don't have the liberty to go for both of them. As per your requirement, recovery window should work.
    As Sybrand mentioned, this all what I wrote is already in the docs(link mentioned by me above) so take some time and read it. Also, I would like to point you to this presentation which should make use of RMAN more clear.
    http://blogs.oracle.com/alejandroVargas/gems/RmanHandsOn.pdf
    HTH
    Aman....

  • RMAN Recovery window and Redundancy

    Hi,
    I am using Oracle 11g (11.2.0.1) in windows 2003 server. In RMAN is it possible to set both the below mentioned configuration in effect or anyone of the configuration can only be used?
    RMAN>CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    RMAN>CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    Regards,
    007

    No it is not possible.
    007 wrote:
    hi oradb,
    Thanks for your reply. i want both the RMAN configuration policy to be applied. Is the possible???
    regards,
    007hi oradb,
    Thanks for your reply. i want both the RMAN configuration policy to be applied. Is the possible???
    regards,
    007

  • My mac book air can't start installation, because i use windows installation in DOS to make partion, now no mac os on it. How to get back the mac os? i have a window based iso image from a friend, because in my country there is no Apple service.

    my mac book air can't start installation, because i use windows installation in DOS to make partion, now no mac os on it. How to get back the mac os? i have a window based iso image from a friend, because in my country there is no Apple service.

    It sounds like you destroyed your boot partition and the recovery partition.  Depending on it's age, your MacBook Air might be able to do a net boot.  Plug and ethernet connection into it and attempt to boot.  If it has the right firmware, it will find a net boot configuration on the net and boot that.  Then it will give you a Recovery Partition like display and allow you to reinstall the OS X version that came with it.... assuming that it was Lion or ML.  If your computer came with Snow Leopard, then even the net boot won't work. 
    At that point you need a bootable USB Key, or an external DVD drive AND a Snow Leopard installation DVD. 
    An Apple Store, if there is one nearby, MAY be able to get you going again.  However, whatever is on the SSD now will be toast too.

  • How can I convert an outlook pst file to mac mail without using a windows based computer

    I recently bought the new iMac as my older Windows based computer crashed with a bad motherboard.  I have been trying to find a way to convert Outlook 2007 pst files to Mac Mail without the need to use a Windows based computer since all I have now is a Mac.  I have the copies of the pst files on my Mac, so I am looking for the most efficient way to convert them to the format that I can then open them in the Mac Mail.  Any suggestions would be greatly appreciated.

    Hi - thanks for the instructions but where do you get the option for Quicktime. If I do File - Export I only get the options for File name, place and size but no option that allows to select quicktime:-(
    Have you got any more tips?

Maybe you are looking for