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"

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

  • Query on RMAN Retention Policy

    Hi, I have my Retention policy set to Redundancy 2
    I have taken 3 backups so far ( 2 Backup Sets, 1 Image Copy )
    When I check report obsolete I get the following
    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           1      05-SEP-13
      Backup Piece       1      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T100934_92jllgn1_.bkp
    Backup Set           2      05-SEP-13
      Backup Piece       2      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_nnndf_TAG20130905T100949_92jllycp_.bkp
    Backup Set           3      05-SEP-13
      Backup Piece       3      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_ncsnf_TAG20130905T100949_92jln4d5_.bkp
    Backup Set           4      05-SEP-13
      Backup Piece       4      05-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T101030_92jln6cx_.bkp
    Backup Set           5      27-SEP-13
      Backup Piece       5      27-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_annnn_TAG20130927T120734_94bsqrj6_.bkp
    Backup Set           7      27-SEP-13
      Backup Piece       7      27-SEP-13          /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_ncsnf_TAG20130927T120751_94bssf0j_.bkp
    Archive Log          305    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_138_95dv9okt_.arc
    Archive Log          306    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_139_95dv9px0_.arc
    Archive Log          307    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_140_95dv9r8f_.arc
    Archive Log          308    10-OCT-13          /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_141_95dv9sk9_.arc
    Backup Set pieces 1,2,3,4 basically equate to my oldest backup - hence under redundancy of 2, I can see why that is obsolete
    5 and 7 were simply Control File/SPFILE backups from Auto Backup and the 2 newer backups of these have been taken since ( i.e. backupset pieces 9 and 10 )
    Q. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
    Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
    Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
    Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
    any advice appreciated,
    Jim

    Q. What happens if I wanted to restore the database to the 27/09 ? What SPFILE and Control would it use ( presuming the OBSOLETE files had been removed out of the FRA ) ?
    Would I have to restore the removed backup set into the FRA, Cross Check and then restore the database via RMAN to the 27/09 ?
    - Yes you can get the database to the date which ever you want , using recover database until time.
    Q. Why are some of today's ( 10/10/13 ) archive logs marked as OBSOLETE ?
    - can you please provide the output of below command
    RMAN> show all;
    Q. If I wanted to have the ability to restore the database to 2 days ago, is perhaps a Rentention Policy of a 2 day Recovery Window perhaps better than my current Redundancy=2 policy ( combined with taking a daily backup ) ?
    - You can restore the database back  to two days or 5 days based on your requirement. You nee to recover the database using  until time option.
    Thanks,
    http://gssdba.wordpress.com

  • RMAN retention policy

    Hi,
    on 10g R2 on AIX6.1 , I have the followings :
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;My backup script :
    RMAN> run
          allocate channel t1 type disk;
          backup as compressed backupset format '$dir/df_%d_%T_%s_%p' database;
          sql 'alter system switch logfile';
          backup as compressed backupset format '$dir/al_%d_%T_%s_%p' archivelog all delete input;
          backup as compressed backupset format '$dir/ctl_%d_%T_%s_%p' current controlfile;
    crosscheck backup;
    delete noprompt obsolete;
    delete noprompt expired backup of database;But I have the backup files of 3th of March yet :
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1 recid=171 stamp=744800219And the only file it deletes is :
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 14 days
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           13404  18-MAR-11
      Backup Piece       13408  18-MAR-11          /appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1
    deleted backup piece
    backup piece handle=/appli/oracle/BACKUP/RMAN/INCR/MYDB/ctl_MYDB_20110318_339_1 recid=331 stamp=746072971
    Deleted 1 objectsShould not RMAN delete the backup files of before 15 of March ? Why it does not ?
    Thank for explanation ? Or more.

    Thank to all.
    We backup it every night (FULL at WE and incremental in week).
    list backup of database;
    List of Backup Sets
    ===================
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    7145    Full    571.86M    DISK        00:01:55     03-MAR-11
            BP Key: 7151   Status: AVAILABLE  Compressed: YES  Tag: TAG20110303T085658
            Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110303_179_1
      List of Datafiles in backup set 7145
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 75445711   03-MAR-11 /data01/bases/MYDB/system01.dbf
      2       Full 75445711   03-MAR-11 /data01/bases/MYDB/psundots01.dbf
      4       Full 75445711   03-MAR-11 /data01/bases/MYDB/psdefault.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    19112   Full    772.42M    DISK        00:03:05     01-APR-11
            BP Key: 19118   Status: AVAILABLE  Compressed: YES  Tag: TAG20110401T121403
            Piece Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110401_60_1
      List of Datafiles in backup set 19112
      File LV Type Ckp SCN    Ckp Time  Name
      8       Full 152751106  01-APR-11 /data01/bases/MYDB/ptprc.dbf
      10      Full 152751106  01-APR-11 /index01/bases/MYDB/pttbl.dbf
      15      Full 152751106  01-APR-11 /data01/bases/MYDB/pttlrg.dbf
      19      Full 152751106  01-APR-11 /data01/bases/MYDB/ptprjwk.dbf
      20      Full 152751106  01-APR-11 /data01/bases/MYDB/ptaudit.dbf
      24      Full 152751106  01-APR-11 /data01/bases/MYDB/amlarge.dbf
      26      Full 152751106  01-APR-11 /data01/bases/MYDB/apapp.dbf
      27      Full 152751106  01-APR-11 /data01/bases/MYDB/aparch.dbf
      34      Full 152751106  01-APR-11 /data01/bases/MYDB/aucapp.dbf
      35      Full 152751106  01-APR-11 /data01/bases/MYDB/auclrge.dbf
      37      Full 152751106  01-APR-11 /data01/bases/MYDB/bdapp.dbf
      38      Full 152751106  01-APR-11 /data01/bases/MYDB/bdlarge.dbf
      40      Full 152751106  01-APR-11 /data01/bases/MYDB/bilarge.dbf
      42      Full 152751106  01-APR-11 /data01/bases/MYDB/caapp.dbf
      50      Full 152751106  01-APR-11 /data01/bases/MYDB/cuaudit.dbf
      54      Full 152751106  01-APR-11 /data01/bases/MYDB/cularge.dbf
      58      Full 152751106  01-APR-11 /data01/bases/MYDB/dpwork.dbf
      60      Full 152751106  01-APR-11 /data01/bases/MYDB/eobfapp.dbf
      64      Full 152751106  01-APR-11 /data01/bases/MYDB/eocmwrk.dbf
      71      Full 152751106  01-APR-11 /data01/bases/MYDB/eoecwrk.dbf
      74      Full 152751106  01-APR-11 /data01/bases/MYDB/eoepapp.dbf
      75      Full 152751106  01-APR-11 /data01/bases/MYDB/eoeplrg.dbf
      77      Full 152751106  01-APR-11 /data01/bases/MYDB/eoewapp.dbf
      81      Full 152751106  01-APR-11 /data01/bases/MYDB/eoiulrg.dbf
      84      Full 152751106  01-APR-11 /data01/bases/MYDB/eoltapp.dbf
      85      Full 152751106  01-APR-11 /data01/bases/MYDB/eoppapp.dbf
      88      Full 152751106  01-APR-11 /data01/bases/MYDB/eotplrg.dbf
      93      Full 152751106  01-APR-11 /data01/bases/MYDB/faapp.dbf
      95      Full 152751106  01-APR-11 /data01/bases/MYDB/fawork.dbf
      101     Full 152751106  01-APR-11 /data01/bases/MYDB/fgwork.dbf
      107     Full 152751106  01-APR-11 /data01/bases/MYDB/fowork.dbf
      109     Full 152751106  01-APR-11 /data01/bases/MYDB/fsapp1.dbf
      112     Full 152751106  01-APR-11 /data01/bases/MYDB/glapp.dbf
      122     Full 152751106  01-APR-11 /data01/bases/MYDB/inlarge.dbf

  • RMAN -Retention policy doubt

    Hi,
    I have doubt on RMAN retention policy.
    we are taking daily cumulative backup and weekly Full database backup.
    And our retention policy is "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS"
    My assumption is that RECOVERY window of 3 days will hold the backups of 3 days and delete the previous backups,since we are taking cumulative backups,and using them database can be recovered.
    we used below commands to take cumulative backup.
    backup incremental level 1 cumulative as COMPRESSED BACKUPSET tag '%TAG' database include current controlfile;
    backup as COMPRESSED BACKUPSET tag '%TAG' archivelog all not backed up;
    Regards,
    mannu

    Thanks for reply.
    A recovery window is a period of time that begins with the current time and extends backward in time to the point of recoverability. The point of recoverability is the earliest time for a hypothetical point-in-time recovery, that is, the earliest point to which you can recover following a media failure. For example, if you implement a recovery window of one week, then this window of time must extend back exactly seven days from the present so that you can restore a backup and recover it to this point. You implement this retention policy as follows:
    In our case:
    Jan 24---Level 0 Full backup
    Jan 25-Cumulative backup
    Jan 26-Cumulative backup
    Jan 27--->Cumulative backup
    Jan-28 ----->cumulative backup
    What would be my point of recoverability? How my recovery window period of 3 days work here.
    Regards,
    Mannu

  • RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time

    Hello,
    i am working for a scenerio and you can see my restore script below,
    RMAN> RUN
    2> {
    3> SET UNTIL TIME "to_date('24-05-2010 18:00:00','DD-MM-YYYY HH24:MI:SS')";
    4> RESTORE DATABASE;
    5> RECOVER DATABASE;
    6> }
    executing command: SET until clause
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of set command at 05/26/2010 11:23:24
    RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time
    also you can see my backups,
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
    89 B 1 A DISK 24-05-2010 15:36:04 1 1 NO BACKU
    P_BISE1DB_000_052410030823
    90 B 1 A DISK 24-05-2010 15:36:13 1 1 NO BACKU
    P_BISE1DB_000_052410030823
    91 B 0 A DISK 25-05-2010 12:01:09 1 1 NO TAG20
    100525T113815
    92 B 0 A DISK 25-05-2010 12:01:13 1 1 NO TAG20
    100525T113815
    93 B 1 A DISK 25-05-2010 12:01:55 1 1 NO TAG20
    100525T120152
    94 B 1 A DISK 25-05-2010 12:04:55 1 1 NO TAG20
    100525T120451
    95 B 1 A DISK 25-05-2010 13:55:00 1 1 NO TAG20
    100525T134431
    96 B 1 A DISK 25-05-2010 13:55:09 1 1 NO TAG20
    100525T134431
    97 B 1 A DISK 25-05-2010 14:01:43 1 1 NO TAG20
    100525T140139
    98 B 1 A DISK 25-05-2010 14:55:33 1 1 NO TAG20
    100525T140356
    so i am trying to understand that what is the earliest date that i can restore my database and avoid tihs error, according to the my backup sets?
    thank you
    Ugur

    Please query the following query and specify the RESETLOGS time
    SELECT RESETLOGS_TIME FROM v$database;
    i cant have result with this, because database is mount state,
    And post the result of the following command to provide an information about database incarnations:
    RMAN>LIST INCARNATION
    RMAN> list incarnation;
    using target database control file instead of recovery catalog
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 BISE1DB 4092555014 PARENT 1116016 01-05-2007 16:22:55
    2 2 BISE1DB 4092555014 PARENT 1226717 14-12-2007 15:28:11
    3 3 BISE1DB 4092555014 PARENT 5783997202 04-05-2010 09:59:11
    4 4 BISE1DB 4092555014 CURRENT 5785721070 26-05-2010 10:59:32
    thank you

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

  • RMAN RETENTION POLICY configuration.

    Currently I am doing RMAN backup once a day and save the copy to tapes through TSM. If I want to keep 15 copies of the db (NOT 15 same copies. It will be one copy from every day backup, so each copy will be different). How should I configure the RETENTION POLICY? Shall I do
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 15 DAYS;
    Or shall I do
    RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    Also do I need to configure anything on the TSM side?
    Thanks.

    To keep the last 15 full backups use redundancy 15.
    You don't need to do anything on TSM if:
    - you use RMAN to backup directly to tape device and
    - you use RMAN DELETE OBSOLETE statements to purge old backups.
    See http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV8400

  • RMAN Retention Policy Dilemma

    The RECOVERY WINDOW and REDUNDANCY options of the RETENTION POLICY parameter are mutually exclusive. I have to set one or the other. However, if I set REDUNDANCY = 3 and then RECOVERY WINDOW = 21 DAYS, I've been told that the recovery window of 21 days will be enforced and RMAN will keep only 3 backup copies within this window period? Is this correct?
    Can you specify a maximum number of backups to keep within a window period of N amount of days?

    You can not set them both. It is one or the other.
    If you set recovery window = 21 days, then it will keep as many backups as necessary to restore back to 21 days.
    If you set redundany=3, then it will only keep the most recent 3 backups.

  • RMAN RETENTION POLICY FOR ORACLE8I

    Dear all,
    How to config RETENTION POLICY for oracle8i(CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;), same 9i ?
    Thanks for advance !
    Chara

    In ORACLE 8i, there are NO stored RMAN parameters (I believe, 9i was the first version to add this feature).
    Instead, in ORACLE 8i you had to specify all channel parameters, formats etc in a run block ... So, the good news is, in ORACLE 8i these parameters should be already "hardcoded" in the RMAN scripts ... in other words, nothing to transfer on a database level ...

  • Appropriate RMAN Retention Policy

    Hi All,
    We have enabled ARCHIVELOG on a Production database, and the size allocated for the same is 4GB. There are situations when the archivelog size touches the maximum point, which results in no-connectivity to the database untill we delete old logs via RMAN.
    At the moment, we have scheduled a task to delete archivelogs on a daily basis, but I agree, this is not an appropriate practice to follow.
    I will really appreciate it, if someone can help me in defining a retention policy, or any other appropriate method, where we can handle this over-flow in a much better way.
    Specs are as follows:
    ===========================================
    OS: Windows Server 2003 Standard Edition
    Oracle Database 10g Enterprise Edition Release 10.1.0.2.0
    ===========================================
    Thanks
    Noman Amir Jamil

    Thats nice you are moving the archivelogs to antoher partition ,i presume you had
    archivelogs at the same destination where database resides isnt?
    neednt to schedule turn the retetnion policy which match to yours own policy ,you just have to include delete obsolete within yours backup scripts and as i laredy given you link that
    "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."
    run
    backup database;
    backup archivelog all;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    release channel;
    Please advise me, if my approach(logic) here is
    appropriate, or is there any other way of doing this
    more efficiently.it alls depend on yours SLA
    i would rather suggest you move yours alls FRA area to another drive which is seperate from yours database residence.
    Khurram

  • RMAN retention policy really long

    Hi,
    we are planning to have an RMAN backup policy really long, around 7 years, with all the backup piece stored on a shared drive.
    I would like to ask if there are problems or concern to have a recovery windows of around 2500 days, and if I have to change other Oracle parameter like control_file_record_keep_time.
    The oracle version is 10.2.0.4, on a Solaris box, the customer don't want you a Catalog.
    thanks for your time
    Nunzio

    I Nikolay,
    thanks for you answer.
    Nikolay Ivankin  wrote:
    Nunzio Cafarelli wrote:
    What do you mean for huge!? and, in your experience, we should expect some hi decrease of performance, or are we speaking of something like 1%.I can't say - I don't know db size, user's activity, amount of redo information, backup strategy.
    You are right, it's not easy to have an idea of what will happen.
    Except that 2 points, there are no other functionality concerns!?Aren't enough? I would say, those 2 points are enough to refuse to keep rman info in CF, but catalog db.
    Honestly no, if I will have a big (supposing 40 Mb) control file, and I'll have a performance decrease of around 1% or 2% is my opinion that that 2 points are not enough to refuse to proceed in this way.
    I'll be scared if I know that ORACLE can't manage that amount of days as recovery window, and I'll have problem if I need to recover the database in a point in time that, for example, is more than 3 years ago.
    Anyway, thanks.
    Regards
    Nunzio

  • RMAN Retention policy 5 days but v$backup_set shows unexpected return

    ORACLE 10.2
    RMAN NOCATALOG
    Windows Server 2003
    Hi All,
    Just trying to get to grips with RMAN.
    I have the Retention policy set to 5 with Auto Backup Control File.
    I use a scheduled task to take a full backup every night due to small size of database.
    With a 'delete noprompt obsolete' after the backup to remove old backups.
    When I query the v$backup_set I get a return from a backupset from over 10 days ago? (this does not exist in my backup location) other than that the return is as expected.
    Can any one tell me why this is displaying and how to remove the invalid returns.
    Best Regards and Happy Xmas
    Neil
    Message was edited by: removed para due to believe it was incorrect statement
    So i beieve this is stored in the control file which has a default retention of 7 days (CONTROL_FILE_RECORD_KEEP_TIME)
    Neil Hunter

    Hi,
    Slimmed down RMAN report shows me the following, Sorry struggling with layout...
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    26 Full 6.80M DISK 00:00:00 14-DEC-07
    28 Full 6.80M DISK 00:00:00 15-DEC-07
    30 Full 6.86M DISK 00:00:00 16-DEC-07
    32 Full 6.86M DISK 00:00:01 17-DEC-07
    34 Full 6.86M DISK 00:00:01 18-DEC-07
    I have dates when selecting from v$backup_set from the 7,12,13 Dec? as well as the above..... extract as below
    COUNT B CON INCREMENTAL_LEVEL PIECES START_TIM COMPLETIO ELAPSED_SECONDS BLOCK_SIZE INP KEE KEEP_UNTI KEEP_OPTIO
    1 640712259 640712258 2 D NO 1 07-DEC-07 07-DEC-07 1 8192 NO NO
    2 640712260 640712259 3 D YES 1 07-DEC-07 07-DEC-07 1 16384 NO NO
    3 640712625 640712625 4 D NO 1 07-DEC-07 07-DEC-07 0 8192 NO NO
    4 640712626 640712626 5 D YES 1 07-DEC-07 07-DEC-07 0 16384 NO NO
    5 640712648 640712648 6 D NO 1 07-DEC-07 07-DEC-07 0 8192 NO NO
    6 640712649 640712649 7 D YES 1 07-DEC-07 07-DEC-07 0 16384 NO NO
    7 640713224 640713223 8 D NO 1 07-DEC-07 07-DEC-07 1 8192 NO NO
    8 640713225 640713225 9 D YES 1 07-DEC-07 07-DEC-07 0 16384 NO NO
    9 640713657 640713282 10 D NO 1 07-DEC-07 07-DEC-07 375 8192 NO NO
    10 640713668 640713667 11 D YES 1 07-DEC-07 07-DEC-07 1 16384 NO NO
    This could have been when I was setting up RMAN and testing taking a backup? how do I delete or will they expire....
    Reference you previous emails the KEEP fields are blank......
    Regards
    Neil
    Message was edited by:
    Neil Hunter
    Message was edited by:
    Neil Hunter

  • Retention policy and deletion of archived files

    hello, I 'am a novice DBA having a backup question.
    Our retention policy is set to 14 days; weekly we have full database backup; daily we have an incremental backup.
    See scripts below.
    The drive "\\is003s012\rhea\rman" where the backup files reside has files older than 2 months.
    I expected these files to be deleted already by rman.
    I can't find the cause why these files are not removed.
    The database backup jobs are running fine ; logs file do not contain any errors and once and a while you see that rman removes obsolete files.
    list expired / report obsolete do not return any files.
    thanks for the assistance
    chris
    ================= full db
    c$rman_script="backup incremental level 0 cumulative device type disk tag '%TAG' database;
    backup device type disk tag '%TAG' archivelog all not backed up delete all input;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    release channel;
    &br_save_agent_env();
    &br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
    my $result = &br_backup();
    exit($result);
    ================ incr db
    $rman_script="backup incremental level 1 cumulative device type disk tag '%TAG' database;
    recover copy of database;
    backup device type disk tag '%TAG' archivelog all not backed up delete all input;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    release channel;
    &br_save_agent_env();
    &br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
    my $result = &br_backup();
    exit($result);
    ================== rman setting
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name RHEA are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 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 '\\is003s012\rhea\rman\%F';
    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 CHANNEL DEVICE TYPE DISK FORMAT '\\is003s012\rhea\rman\%U';
    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 BACKED UP 1 TIMES TO 'SBT_TAPE';
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFRHEA.ORA'; # default

    Chris,
    Thanks for the info; my current setting for this parameter:
    SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME;
    NAME                                 TYPE        VALUE
    control_file_record_keep_time        integer     7
    I found another thread that elaborated on this: Re: CONTROL_FILE_RECORD_KEEP_TIME vs Retention Policy in RMAN
    a) RMAN Retention Policy set to recovery window of 30 days means backups and archivelogs that you need to do a Point in Time Recovery to before 30 days do not get obsolete.
    b) CONTROLFILE_RECORD_KEEP_TIME=7 will keep (potentially, if space pressure in the controlfile) the records of these files for only 7 days
    Effect: Your old backups and archivelogs (+7 days) are no longer known by the system and will not get deleted (automatically or by delete obsolete) and your recovery area/backup location/archive destination will get filled up with old files.
    Therefore set b) > a)
    Based on this I changed the parameter:
    alter system set CONTROL_FILE_RECORD_KEEP_TIME=35 scope=both;
    Even tho the 'stale' backupsets are still invisible (still getting 'no obsolete backups found' when doing REPORT OBSOLETE), I guess that's because it will take a while (23 days?) for the CONTROL_FILE_RECORD_KEEP to catch up to the RMAN Retention Policy of 30 days)....
    Barry

Maybe you are looking for

  • Xpath result nodes not returned in document order

    An XPath expression over a mixed text element does not return the result nodes in document order (see example below). I am using dbxml 2.3.0. let $x := <a>this <i>is</i> <b>mixed</b> text</a> return $x/node()} dbxml> query {let $x := <a>this <i>is</i

  • Problem in unzipping a file : ZipInputStream

    Hi All, I am having some issues in unzipping a zip file using ZipInputStream. Following is the code : public class ZipInputStreamExample {       * @param args      public static void main(String[] args) {           // TODO Auto-generated method stub

  • Case sensitive table names

    Hi all, I create a table named "Organism" on my marvel schema. When I do a SELECT * FROM "Organism", I get correct results, but when I try to do DESC "Organism" I get an error message saying the table doesn't exist. Is there something I am missing ?

  • I can't adjust the duration of iMovie videos and images with precision on iPhone. It gets back at 0,3 seconds.

    During my iMovie project, after 2 minutes. I can't adjust the length of images or videos with precision as normal. If I sweep it a little bit, it gets to 20 or more minutes. Can you help me out?

  • Webservice to file

    Hi ..     I want detailed step by step guide for "webservice to file" scenario. Kindly help me out in this.