CONFIGURE REDUNDANCY RETENTION POLICY

Hello
in 10g R2, I have the following Setup for RMAN:
RMAN> show all;

paramtres de configuration RMAN :
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
1 it means that, after the backup completes before the first backup set boecomes obsolete/expired?
2. How can I check it in the repository of the catalog? Any question?
Thank you very much.

Published by: user522961 on November 20, 2008 05:07

1 - Yes
2 is 'obsolete report' in rman what you are looking for or you are looking for a sql query that you run against the cat. DB?

Tags: Database

Similar Questions

  • RMAN-05021 configuration pending retention policy

    Hi all.

    Running Oracle on Linux (x 64) 11.2.0.2; single node instance.

    We have the following configuration:

    bvlive (PRIMARY)
    bvstby2 (STANDBY)

    We currently have a 21-day retention policy, and backup on the waiting space begins to be a problem.

    At first, I thought I could reconfigure this on the day before - but RMAN will not allow this:

    STANDBY TIME:
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 days;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 10/15/2012 10:09:50
RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file
    Which makes sense when I think about it. I saw this thread retention policy is not configured , but get different results:

    PRIMARY:
    RMAN> configure retention policy to recovery window of 14 days;

old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
new RMAN configuration parameters are successfully stored

RMAN> show all;

RMAN configuration parameters for database with db_unique_name BVLIVE are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
    STANDBY TIME:
    RMAN> SHOW ALL;

RMAN configuration parameters for database with db_unique_name BVSTBY2 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;
    Which also makes sense; so I am not the original poster solved his problem. I saw a few discussions about this which involve:

    1. standby stop
    2. on the primary retention policy configuration
    3. take a backup controlfile elementary school
    4 copy transversely to the waiting
    5 restart the day before using backup controlfile

    But then, this seems to be for the CAR, which we do not.

    It dawned on me that I can use the option KEEP until when you take backups, but encountered; ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST attrbuts Dungeon (i.e. I can't use DUNGEON and store the backups in the FRA).

    Can someone please advise on the best way to go down the retention period in the waiting, ideally without having to rebuild the day before from scratch?

    Thank you
    Ray

    Published by: ray_h on October 15, 2012 03:33

    Take a look at this http://asanga-pradeep.blogspot.com/2011/07/changing-backup-policy-on-standby-db.html

    It could be that useful...

  • CONFIGURE REDUNDANCY 0 RETENTION POLICY

    Our 11 g R2 database, here's our RMAN script
    Currently, our retention policy is 1, so 1 backup is kept as well as the current backup.
    I just want to have 1 it is, RMAN backup should I take backup and delete the former bacup.
    Will it work if I change to 0 retention policy?
    RUN
{ 
  ALLOCATE CHANNEL ch1 DEVICE TYPE DISK;
  ALLOCATE CHANNEL ch2 DEVICE TYPE DISK;
  ALLOCATE CHANNEL ch3 DEVICE TYPE DISK;
  DELETE NOPROMPT OBSOLETE;
  BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
  SQL "ALTER SYSTEM ARCHIVE LOG CURRENT";
  BACKUP ARCHIVELOG ALL DELETE INPUT format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';

}

RMAN> show all
2> ;

using target database control file instead of recovery catalog
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
    Published by: user10243788 on April 24, 2012 01:14

    Not possible, see this

    RMAN > CONFIGURE REDUNDANCY 0 RETENTION POLICY;

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the command configures to 24/04/2012 14:44:33
    RMAN-06532: County of redundancy must be greater than zero

    I just want 1 backup,

    If you run your cmd 'DELETE NOPROMPT OBSOLETE;' after your backup command then it will delete previous backup and keep only 1 backup.

    Thank you
    Christian Christmas Pal Singh

  • What retention policy is defined as REDUNDANCY

    DB version: 10.2.0.4

    Just trying to understand the concept of redundancy.

    If I put my set on REDUNDANCY as retention policy
    CONFIGURE RETENTION POLICY TO REDUNDANCY 4;
    and all the backup files are stored in a place like ' / u04/rmanbkp /' (4 of them) multiple copies of the same data file with different names (a unique name generated using the parameter % U) will be created here. Right?

    The next day, all copies of data file will be obsolete. Right?

    Recovery window retention policy is more widespread than redundancy. Right?

    No, 'REDUNDANCY 4' does not 4 copies for backup generation.
    It shows only the last 4 backups (if more than 1 or more than 4 or more than 4 weeks) must be kept.

    Hemant K Collette

  • Basic question on redundancy as the retention policy enforcement

    DB version: 11 g

    I intend to implement a differential incremental backup of my database. My strategy is
    Sunday -->     Level 0 backup
Monday -->     Level 1 backup
Tuesday-->     Level 1 backup
Wednesday-->     Level 1 backup
Thursday-->     Level 1 backup
Friday-->     Level 1 backup
Saturday-->      Level 1 backup

Again, the new weekly backup cycle starts
Sunday -->     Level 0 backup
Monday -->     Level 1 backup
.
.
    Set on the Recovery window retention policy
    ==========================

    I understand that recovery window retention policy: If I set up
    'CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;'
    This means only these backups that are older than 7 days will be reported as obsolete when executing the command "remove obsolete.

    Retention set on redundancy policy
    =============================

    But I'm a little confused about the retention set to redundancy policy:

    Does
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    say that you keep 3 copies of backups on different locations on disk? How does this fit with my above mentioned incremental backup strategy?

    REDUNDANCY is 'Keep' copies

    The BACKUP is 'Create' copies of

    Copies which exceed the requirement of REDUNDANCY become OBSOLETE.

    Hemant K Collette

  • CONFIGURE REDUNDANCY 1 RETENTION STRATEGY;

    Hi all
    We would like to create one per week, a full backup of level 0, and every day a level 1 cumulative backup RMAN.
    We want to configure that he holds a cumulative RMAN and the full backup.
    We can use the parameter 1 of the RETENTION POLICY or RMAN also remove the full backup after a day?
    Otherwise, it must be set up for 7 days and delete other level 1 per script backups.
    Thank you
    * T

    >

    We want to configure that he holds a cumulative RMAN and the full backup.
    Thank you
    * T

    You can't do that. RMAN holds all cumulative level 1 backups is the relationship to the level 0 backup. But as soon as you make the level 0 backup at level 0 of the next week old and related cumulative backups will be obsolete.

    Unfortunately, you must remove manual cumulative backups previosly.

    You have not necessary STRATEGY OF RETENTION at 7. Leave it at 1. A level 0 and the last backup cumulative lvl 1 is enough to recover.

  • backup with the retention policy to recovery of N days window

    Hello

    I did command to create an incremental backup of database with the configuration:

    run

    {

    Configure retention policy to recovery of 14 days window;

    backup incremental level 1 cumulative

    tag daily_incr_14_days

    database

    more archivelog delete all input;

    }

    All parameters are set to their default values, and backups of data goes to FRA. I've got catalog recovery connected and all the views RC_ at my disposal.

    (1) is it possible to know which window of recovery has been used for any command in the rman backup or query view RC_ or local database (control file information)?

    (2) if I use other settings of window of recovery with command configures which would overlap or report rman commands do?

    BR

    Sandrine.

    TenakaKhan wrote:

    Mahir,

    Thanks for the reply - in other words, this window of recovery should be used mainly for maintenance purposes (overlap, remove obsolete, report need backup etc.) and he was not associated with the actual with backup items as retention period "keep until the" safeguard clause... command database (this information are saved with the backup as I could verify according to rc_backup_set of the recovery catalog)?

    Yes.

    Maintaining backups RMAN and repository & nbsp; Reviews

    keepOption

    backup retention policy

    A policy defined by the user to determine how long the backups and archived logs must be kept for the media recovery. You can define a retention policy in terms of redundancy backup or a recovery window.

    RMAN keeps backups of data files that are required to meet the current retention policy, and all logs archived redo necessary to a complete recovery of data files.

    Recovery window

    A recovery window is a type of RMAN backup retention policy, in which the ADMINISTRATOR specifies a period of time and RMAN ensures the retention of backups and Archives redo logs required for recovery to point-in-time at any time during the recovery window.

    The interval always ends at the present time and is extended in time for the number of days specified by the user. For example, if the retention policy is set for a window of recovery of seven days and the current time is 11:00 Tuesday

    RMAN maintains the necessary backups to recover point-in-time at 11:00 the previous Tuesday.

    Concerning

    Mr. Mahir Quluzade

  • last available retention policy backup RMAN

    Hi all

    I'm on 11.2 and had a question regarding the rman... my ploicy of retention is set to 22 days see below
    RMAN> show all;

RMAN configuration parameters for database with db_unique_name TEST are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 22 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default

List of Backup Sets
===
    Published by: user8363520 on September 28, 2011 15:08

    Published by: user8363520 on September 28, 2011 15:09

    user8363520 wrote:
    Hi all

    I'm on 11.2 and had a question regarding the rman... my ploicy of retention is set to 8 days see below

    RMAN> show all;

RMAN configuration parameters for database with db_unique_name TRGT are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/cont_spfile_%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_ctl_spfile_%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backups/%d_%t_%s_%p_%T';
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 2 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/112_64/dbs/snapcf_TRGT.f'; # default

RMAN>

    but when I login and backup list... back were taken log time back still shows as AVAILABLE... I thought that it would be marked obsolete or expired... any reason why his does not like that? I had to change my couple of time format is why it dose not match the above... but just that I do not understand why his watch available?

    They are not 'marked' as outdated. They are "evaluated" as obsolete when necessary to meet demand for obsolete series. Notice what happens when I take three backups with a REDUNDANCY 2 retention policy

    RMAN> show retention policy;

using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;

RMAN> backup database;

Starting backup at 27-SEP-11

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:25
Finished backup at 27-SEP-11

Starting Control File and SPFILE Autobackup at 27-SEP-11
piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 27-SEP-11

RMAN> backup database;

Starting backup at 27-SEP-11

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:45
Finished backup at 27-SEP-11

Starting Control File and SPFILE Autobackup at 27-SEP-11
piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 27-SEP-11

RMAN> backup database;

Starting backup at 27-SEP-11

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:55
Finished backup at 27-SEP-11

Starting Control File and SPFILE Autobackup at 27-SEP-11
piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 27-SEP-11

RMAN> list backup;

List of Backup Sets
===================

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
113     Full    94.59M     DISK        00:01:18     27-SEP-11
        BP Key: 113   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T194613
        Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
  List of Datafiles in backup set 113


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
114     Full    6.89M      DISK        00:00:01     27-SEP-11
        BP Key: 114   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T194739
        Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp
  Control File Included: Ckp SCN: 1185229      Ckp time: 27-SEP-11
  SPFILE Included: Modification time: 27-SEP-11

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
115     Full    94.59M     DISK        00:01:38     27-SEP-11
        BP Key: 115   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T194931
        Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
116     Full    6.89M      DISK        00:00:02     27-SEP-11
        BP Key: 116   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T195116
        Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp
  Control File Included: Ckp SCN: 1185400      Ckp time: 27-SEP-11
  SPFILE Included: Modification time: 27-SEP-11

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
117     Full    94.59M     DISK        00:01:50     27-SEP-11
        BP Key: 117   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T195228
        Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T195228_784vydks_.bkp


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
118     Full    6.89M      DISK        00:00:02     27-SEP-11
        BP Key: 118   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T195423
        Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp
  Control File Included: Ckp SCN: 1185555      Ckp time: 27-SEP-11
  SPFILE Included: Modification time: 27-SEP-11

RMAN> report obsolete;

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           113    27-SEP-11
  Backup Piece       113    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
Backup Set           114    27-SEP-11
  Backup Piece       114    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp

RMAN> delete obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           113    27-SEP-11
  Backup Piece       113    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
Backup Set           114    27-SEP-11
  Backup Piece       114    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp

Do you really want to delete the above objects (enter YES or NO)? y
deleted backup piece
backup piece handle=/orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp recid=113 stamp=762983174
deleted backup piece
backup piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp recid=114 stamp=762983260
Deleted 2 objects

RMAN> exit

    or note this:

    RMAN> report obsolete;

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           115    27-SEP-11
  Backup Piece       115    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp
Backup Set           116    27-SEP-11
  Backup Piece       116    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp

RMAN> CONFIGURE RETENTION POLICY TO REdundancy 6;

old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 6;
new RMAN configuration parameters are successfully stored

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 6
no obsolete backups found

RMAN> CONFIGURE RETENTION POLICY TO REdundancy 1;

old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 6;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored

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           115    27-SEP-11
  Backup Piece       115    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp
Backup Set           116    27-SEP-11
  Backup Piece       116    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp
Backup Set           117    27-SEP-11
  Backup Piece       117    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T195228_784vydks_.bkp
Backup Set           118    27-SEP-11
  Backup Piece       118    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp

RMAN> exit

  • Question on the implementation of the RMAN retention policy

    Version: 11 g
    OPERATING SYSTEM: AIX 5.3


    I intend to implement a differential incremental backup of my database. My strategy is
    Sunday -->     Level 0 backup
Monday -->     Level 1 backup
Tuesday-->     Level 1 backup
Wednesday-->     Level 1 backup
Thursday-->     Level 1 backup
Friday-->     Level 1 backup
Saturday-->      Level 1 backup

Again, the new weekly backup cycle starts
Sunday -->     Level 0 backup
Monday -->     Level 1 backup
.
.
    First script to perform the backup of level 0 - this script will be run by a cron job every Sunday morning 02:00
    ==================================================================
    run{
crosscheck backup;
crosscheck archivelog all;
crosscheck copy;
crosscheck backup of database;
crosscheck backup of controlfile;
delete noprompt obsolete device type disk;
}


run {
allocate channel ch1 device type disk;
backup incremental level 0 format '/u07/rman_backup/FULL_%d_%u' database tag "weekly_full";
backup format '/u07/rman_backup/RMAN_CTL%s:%t:%p.bkp' current controlfile;
--release channel ch1;
allocate channel ch1 device type disk;
backup (archivelog all  format='/u08/rman_backup/archbkp_dir/ARCH_%d_%T_%u_s%s_p%p' DELETE INPUT TAG "archivelogs");
release channel ch1;
}
    The second script for differential incremental backup at level 1 for the next 6 days. This script will run every day
    at 02:00 from Monday to Saturday by a cron job. I have 6 scripts like below, the only difference being the tag "Monday-level 1", "Tuesday-level1"... etc.
    =======================================================
    run{
crosscheck backup;
crosscheck archivelog all;
crosscheck copy;
crosscheck backup of database;
crosscheck backup of controlfile;
delete noprompt obsolete device type disk;
}


run {
allocate channel ch1 device type disk;
backup incremental level 1 format '/u07/rman_backup/RMAN_DBF_%s:%t:%p.bkp' database tag "Monday-level1";
backup format '/u07/rman_backup/RMAN_CTL<%s:%t:%p>.bkp' current controlfile;
--release channel ch1;
allocate channel ch1 device type disk;
backup (archivelog all  format='/u08/rman_backup/archbkp_dir/ARCH_%d_%T_%u_s%s_p%p' delete input tag "archivelogs");
release channel ch1;
}
    Question1.
    I want to as backups to become obsolete and deleted as below
    At the end of every week's backup cycle.ie Just after taking a new Sunday's level 0 backup, 
i need all the old level 1 and level 0 backups from the previous week to get deleted.
    The setting persist following should do the trick. Right?
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    Question2.
    Since
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    is defined. When the new backup cycle begins next Sunday, RMAN should delete the backup of level 0 of last Sunday. Ideally, RMAN should remove all its ' (child) of level 1 backups to Saturday because it makes no sense to keep these level 1 backups when its parent 0 level was obseleted and deleted. RMAN removes level 1 level 0 backup child deleted backups Sunday (when the new backup cycle begins)?

    Question3:
    Suggestions that you guys have about the scripts above?

    Published by: resistanceIsFruitful on October 30, 2009 06:04

    You have answered your question yourself in your question, when you understand

    Ideally RMAN should remove all its ' other (children) level 1 backups to Saturday because it makes no sense to keep these level 1 backups when its parent 0 level was obseleted and removed_

    Yes indeed RMAN done, did you check it yourself?

    Khurram

  • Problems with the retention policy that removes a Cumulative incremental backup

    Hello

    I have following two scripts:

    1 RMAN script runs the weekend and made a full backup of level 0.

    2 RMAN script works on a daily basis and a level 1 Cumulative backup.

    at the end of each script I delete noprompt obsolete redundancy 1; (I don't need a single copy of local disk)

    My problem is that it seems that remove obsolete handles only level 0 (full) backups.

    for example, my goal is:

    Saturday = > level 0 + delete obsolete (level 0 + all the incremental)

    Sunday = > obsolete level 1 cumulative + delete

    Monday = > level 1 cumulative + Delete obsolete (backup Sunday)

    etc...

    What happens in reality is rather that remove obsolete Monday, completely ignores Sunday 1 cumulative level.

    and he keeps all the up to the next level 0 backup

    its actually covered in the Oracle Documentation:

    http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV8400

    but it's just not make sense.

    in order to have redundancy of 1 copy I only need to level 0 + unique Level 1 cumulative backup.

    I don't have level 0 + all level 1 cumulative backups between full backups.


    so my question is there a way to make the retention policy to keep only the last level 1 cumulative?

    It's true window of 1 day recovery ignores several backups of cumulativ made the same day as being obsolete. Regular retention strategies rman probably cannot provide what you want. You can manually identify the backupset and delete them or change of cumulativ backups to incremental backups.

    That would save the space of several cumulative backups and and would work even for several backups on the same day. Of course with the disadvantage that you need all of the incremental backups and your recovery time may be longer

  • RMAN retention policy

    Hello everyone, I think to create a retention policy, but the problem is if I want to have the backup that ran daily from detention for 15 days and each backup run a monthly backup for a year which is the best option to set up the recovery window retention policy, because if I set with 365 days I'm going to keep daily backups for the whole year, suggest or advise

    Hello

    set the retention policy for 15 days (daily policy):

    RMAN > CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 60 DAYS;

    And add keep until 'sysdate + 365' monthly backup.

    RMAN > backup format incremental level 0 '% d.n0.%T.set_%s_%t' TAG data = 'BK_DATA_monthly_20150501' keep until 'SYSDATE + 365' opens a session;

    If you can make backup maintenance with delete obsolete;

    RMAN > remove force noprompt obsolete;


    It works with oracle 9i, 10g and 11g

  • Retention policy for archive logs.

    Retention policy is set to "REDUNDANCY 2".

    We do the complete disk backup without archive logs at 12:00.

    After that, we make full backup with newspapers to archive tape at 18:00.

    RMAN will consider newspapers to check-in after 12:00 as obsolete as it is backed up to tape?

    Thank you.

    REDUNDANCY applies only to the data files and control files. For archiving logs, there are POLICY of DELETE ARCHIVELOG. But "remove obsolete" won't use POLICY of DELETE ARCHIVELOG, so archiving logs should be removed separately if they meet this policy.

  • Retention policy for the grid control

    Hello

    One of our clients wants to change the retention policy of the Grid control to 2 years in order to check the statistics of the application of these last 2 years,

    Default purge policy is as follows:

    Raw metrics - 7 days

    An hour aggregate metrics data - 31 days

    A day aggregate metrics data - 365 days

    Having someone of you will never change these default policies to a great values?

    I'm afraid of performance issues

    Depends on what policy they want change, but I n ' tthink this will help you at all.  If they are looking for AWR data, it is not stored in MS, unless you configure CWA warehouse.   EM will be measures such as SQL response time, but it does not store the SQL query and the stats you'd see in an AWR report.   Storing so for 2 years will not help.  If you want just generic performance history, then changing strategies of purge will be fine, but you don't want to store the raw data for 2 years. Keep in mind that you will increase the size of your repository database as well.

  • RMAN: Deletion retention policy policy VS Archivelog

    I am a newbie to RMAN, so I did a lot of reading and experimentation, and I'm stuck on a problem.

    TASK: I want to keep two days of archived newspapers and a days worth of backups.

    SOLUTION: set 1 retention policy, set the deletion policy to archive 2

    (CONFIGURE ARCHIVELOG DELETION of SAVED POLICY 2 TIMES TO THE DISK.)

    and it's my simple backup script

    run

    {

    database backup "nightly_backup" tag more archivelog;

    delete noprompt obsolete;

    }

    PROBLEM: it does not work. Oracle documentation clearly (as clearly as possible the documentation) that "remove obsolete" uses the retention policy to clear logs archived. and deletion policy deletion archivelog to use "delete archivelog all;

    My tests verifies this.

    ISSUE. How remove the database obsolete backupsets ONLY by using the delete command?

    -Mark

    Just for clarity - if other people who have this issue will find this thread-I found the answer.

    Two policies are in effect only when you use the quick recovery for all your backup needs area. The database will automatically manage files according to policies. But as soon as you run manually ' rman > delete noprompt obsolete ' Oracle will only follow the retention policy.

    So as soon as FRA got up to about 78 percent full, he began to delete files, you can see in the alert.log

    Deleted Oracle managed file +FRA/sndbox/backupset/2014_07_23/annnf0_nightly_backup_0.435.853650191

    Deleted Oracle managed file +FRA/sndbox/archivelog/2014_07_23/thread_1_seq_204.439.853668327

    Deleted Oracle managed file +FRA/sndbox/autobackup/2014_07_23/s_853650247.441.853650249

    Deleted Oracle managed file +FRA/sndbox/archivelog/2014_07_23/thread_2_seq_189.434.853668653

    Another consequence of this fun is that Oracle will not automatically manage files outside of the FRA. So, if you save FRA on the disk, Oracle removes only files of FRA. If you must manually remove FRA backups, but which will also remove the FRA files according to the retention policies.

  • CONFIGURE ARCHIVELOG DELETION POLICY

    Hi all

    In this context:

    CONFIGURE ARCHIVELOG DELETION POLICY TO SAVE 2 TIMES TO THE DISK.

    I tell rman to consider the already saved archivelogs twice to be obsolete.

    I can then delete using:

    backup database more archivelog entry remove

    or manually as in

    cross-checking of backup;

    remove obsolete;

    My question is this: why would you wait until newspapers are saved twice? Why save twice on the drive?

    In my case, I saved them outside of the FRA and the FRA. I understand the process to remove them, I'm just not sure about the meaning of the "n TIMES" retention policy

    Thank you.

    11.2.0.2

    DA

    Hey Dan,

    Save your archivelogs twice is purely an exercise in belts and suspenders.

    So unless you have two backups RMAN will not remove the archivelog, you will get a warning of something like 'need to create another backup expiration deletion.

    Purely belts and suspenders and nothing more, in the case where a copy of one of the archivelogs is corrupt or something.

Maybe you are looking for

  • I forgot the password on ipod

    My son forgot his password for his iPod, I erased the device by iCloud, but I thought that this reset the iPod and return the Hello to the screen to select a new password, but the password screen is still there, then the unit displays on my iMac to e

  • Photos in the photo library iCloud - HELP Please!

    I have an iMac, iPad + iPhone with the same Apple ID and the same photo of iCloud library. Now, by mistake, IV ' e disable preferences APP Photos of the iMac of the iCloud (see photo) photo library and turn on again after a few seconds. It seems that

  • Satellite A-L50-1CU - loading of dam.sys problems and nvinitx.dll

    Hello During the last 20 days, not in relation to an update of nvidia driver, I find, each boot, the same 2 entries in the system log: Could not load the driver of dam and the custom of the dynamic libraries are bein loaded for each application (that

  • HP Pavilion Notebook - 15-ab20: HP Pavilion Notebook - 15-ab206no does not start

    Hi, bought my Pavilion Notebook 15-ab206no last week. Worked fine until I went to turn it on this morning... nothing! LED light is orange by the AC adapter cord but other than nothing. Tried to remove the battery, running only on the AC adapter / CC

  • How to add new person a\

    So, I want to add a new person\icon thing when you open a session. (Windows Vista) Like when you turn it on and you choose what file you want to go. For exe. John or Justin; A bit like that. How to make a new one? Can someone help me?