RMAN-05021 configuration pending retention policy

Similar Questions

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

• 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

• 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

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

• 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

• Backups RMAN does not match its retention policy

  Hello

  I have two or three instances of PROD on Windows environment with 11.2.0.3 version of DB. RMAN retention policy is set to 14 days, but I noticed that the backup is showing greater than that.

  For example: backups whows LIST BACKUP OF DATABASE since October 13. I also checked the elements of part of netapp backup and they are present.

  DELETE NOPROMPT OBSOLETE do not remove whatever it is like expired backup.

  I have clear and defined retention to 14 days over policy but doesn't seem to work.

  I would be grateful suggestion (s) about the strange.

  Thank you very much.

  Best regards

  John-MK wrote:

  Hello

  I have two or three instances of PROD on Windows environment with 11.2.0.3 version of DB. RMAN retention policy is set to 14 days, but I noticed that the backup is showing greater than that.

  For example: backups whows LIST BACKUP OF DATABASE since October 13. I also checked the elements of part of netapp backup and they are present.

  DELETE NOPROMPT OBSOLETE do not remove whatever it is like expired backup.

  I have clear and defined retention to 14 days over policy but doesn't seem to work.

  I would be grateful suggestion (s) about the strange.

  Thank you very much.

  Best regards

  We would need to know what kind of backups and where they were taken.  Imagine this scenario:

  7-day retention strategy.

  Level 0 incremental backup taken on Sunday

  Backup incremental level 1 taken Monday at Sam.

  Let's say that October 1 is a Sunday, so we take an Inc.-0 backup on October 1 and again on Oct. 8.

  Now let's say that we are at 10 Oct.  Our 7-day retention policy dicatates that we can recover any day of return to 3 Oct.

  The only way we can find to 3 Oct is to start with this backup Inc.-0 Oct. 1.

  Recovery all starts with last Inc.-0 backup before the point in time to be recovered.  In a normal life, regularly cycling calendar of backups, actually will end you with backups 1 day far twice also older than your retention period.

  A more extreme example.  Same period of retention of 7 days, but after a single backup Inc. - 0, you don't take any backups of 3 months.  That only a backup is always necessary to apply your window of recovery and therefore is not obsolete, despite the fact it is 3 months old and your recovery window is 7 days.

  Also, you mention "expiration".  Regarding backups oracle, 'expired' isn't the same as "obsolete".

  "Obsolète" means "is more necessary to apply the principle of recovery."

  "Expired" is a little more complex.

  When a backup is performed, or an archivelog is written, an account of which is written in the repository.  When you do a 'crossover' rman, these repository records are compared to reality - to see if the archivelog or saved backup file actually exists.  Maybe someone used an OS command to delete them.  Any file found "go walkabout" have their directory of files marked as "expired".  An rman "expiration to delete" then delete the records in the repository.

• Query on the RMAN retention policy

  
  Hi, I have my retention set to 2 redundancy policy

  I took 3 backups so far (2 sets of backup, 1 copy of the Image)

  When I check the obsolete report I get the following

  RMAN retention policy apply to the order

  RMAN retention policy is set to 2 redundancy

  Report of obsolete backups and copies

  Making key time filename/handle type

  -------------------- ------ ------------------ --------------------

  Backup 1 05-SEP-13 set

  Exhibit 1 backup /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T100934_92jllgn1_.bkp 13-SEP-05

  Backup 2 05-SEPT-13 set

  Exhibit 2 backup /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_nnndf_TAG20130905T100949_92jllycp_.bkp 13-SEP-05

  Backup 3 05-SEPT-13 set

  Save the song 3 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_ncsnf_TAG20130905T100949_92jln4d5_.bkp 13-SEP-05

  Backup 4 05-SEPT-13 set

  Save the 4-13-SEVEN piece. 05 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_05/o1_mf_annnn_TAG20130905T101030_92jln6cx_.bkp

  Backup 5 27-SEPT-13 set

  Save the song 5-/home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_annnn_TAG20130927T120734_94bsqrj6_.bkp 13-SEP-27

  Backup the value 7 13-SEP-27

  Save the song 7 /home/app/oracle/fast_recovery_area/PRIMARYP/backupset/2013_09_27/o1_mf_ncsnf_TAG20130927T120751_94bssf0j_.bkp 27-SEP-13

  Archive newspaper 305 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_138_95dv9okt_.arc

  Archive newspaper 306 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_139_95dv9px0_.arc

  Archive journal 307 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_140_95dv9r8f_.arc

  Archive newspaper 308 10 October 13 /home/app/oracle/fast_recovery_area/PRIMARYP/archivelog/2013_10_10/o1_mf_1_141_95dv9sk9_.arc

  Backup 1,2,3,4 set elements are essentially equivalent to my older backup - so under a redundancy of the 2, I can see why it is obsolete

  5 and 7 were simply command file/SPFILE AutoSave backups and the 2 most recent backups of them have since been taken (backupset parts 9 and 10)

  Q. what happens if I wanted to restore the database to the 27/09? What control and SPFILE he would use (assuming that OBSOLETE files had been removed from the FRA)?

  If I have to restore the backup set removed in the FRA, Cross Check and restore the database using RMAN to 27/09?

  Q. Why are some today (10/10/13) archival newspapers marked OBSOLETE?

  Q. If I wanted to be able to restore the database for 2 days, is perhaps a policy of conservation of a day 2 Recovery window might be better than my current redundancy = 2 policy (associated with a daily backup)?

  any advice appreciated,

  Jim

  Yes, the BackupPieces names.

  A BACKUP of the LIST would show the content of BackupSets and BackupPieces.

  Hemant K Collette

• RMAN retention policy does not log source archive

  Oracle 11.2
  Windows server 2008
  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED 1 TIME TO THE DISK.
  
  I ran after command
  TIME BACKUP ARCHIVELOG ' SYSDATE-6' UNTIL ' SYSDATE-1';
  
  RMAN > ARCHIVELOG BACKUP OF TIME ' SYSDATE-6' until ' SYSDATE-1';
  
  From backup may 29, 13
  using the control file of the target instead of recovery catalog database
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID = 386 type device = DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: SID = 773 type device = DISK
  jump the C:\ARC\ARC0000000564_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000564_0808506935.0001; already saved 1 time
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000565_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000565_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000566_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000566_0808506935.0001 archived log file; already supported
  up to 1 times
  jump the C:\ARC\ARC0000000567_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000567_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000568_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000568_0808506935.0001; already saved 1 time
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000569_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000569_0808506935.0001 archived log file; already supported
  up to 1 times
  \\172.16.1.2\DATABASE_BACKUP\RMAN\ARCHIVE_34\ARC00 of the archived log file skipping
  00000570_0808506935.0001; already saved 1 time
  jump the C:\ARC\ARC0000000570_0808506935.0001 archived log file; already supported
  up to 1 times
  Backup finished 29 May 13
  
  RMAN >
  
  
  According to policy to delete rman does not delete source archive logs.

  This is the backup... command where the delete command

  obsolete report;

  Confirm if the archivelog you want to remove, then

  remove obsolete;

  so if you had manually deleted archivelogs use below to remove the entry of records controlfile

  overlap archivelog all;

  list expired archivelog all;

  REMOVE EXPIRED ARCHIVELOG ALL;

  edited part-

  read [url http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG]

  This plocy deletion makes these archivelog eligible for deletion. They will be deleted automatocally if they are inside the FRA FRA is short of space.

  Published by: Patricia kebe on May 29, 2013 01:16

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

• 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

• The Archive Log backup retention policy

  How can I define retention policy for backups of the log of the Archives?

  The question and the answer that you have marked as "Right answer" is misleading.

  For removal of journal policy archived, see below.

  Configuration of RMAN environment

  For the real question displayed "How can I define retention policy for backups of the log of the archives?", see link below. ""

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

  Also, have you started the thread to clear your doubts or test other users of the forum?

  Thank you!!

• Retention policy

  We had a database of Oracle 9i, configured with a Hot Standby. For the moment, we have the following rman script, configured to run every night at 22:00:
  Run {}
  backup database;
  delete noprompt archivelog all completed before ' SYSDATE-7 ";
  delete noprompt backupset completed before "Trunc (sysdate);
  }
  By separate thread, I realized that "backup database" should be replaced by 'backup database more archivelog' however I am also considering the component to delete.
  My idea is that I still want to have a value of weeks of recovery archived newspapers available on the machine, just in case the emergency breaks down and in addition at least a full backup of database available online at any time.
  My understanding is that the script above should be secure, as if the backup database should fail, the next steps would not run. However in reviewing it I'm afraid we have a case where the backup ends just before midnight, causing the backup finished just to be deleted.
  I know that I can change the "TRUNC(SYSDATE-2/24)", but I wonder if there is a cleaner to do this way?
  What I think I want is a retention policy of 1 OBSOLETE on database backups, but a WINDOW OF 7 DAYS on the archived redo logs. However, I understand that the same retention policy should apply to these two newspapers of recovery and that the two options are mutually exclusive.
  Any thoughts on the issue of whether what I'm trying to achieve is logical, and if so how I can best achieve this?

  PatHK wrote:
  OK, thanks, but as I am running Oracle 9i for now, you are able to comment first find out if it makes sense for me to keep a value a week of archived redo logs and the most recent full backup and also whether the script below every night at 22:00 is the best way to do this?

  Run {}
  backup database archivelog;
  delete noprompt archivelog all completed before ' SYSDATE-7 ";
  delete noprompt backupset completed before "TRUNC(SYSDATE-2/24)";
  }

  It depends on your backup strategy. You can automatically delete all archive redo log files that were created 7 days ago
  But if you

  -Save all the archived redo log files using any backup of database
  -Have Standby database which keeps even long archived redo log file when it is created

  so why keep a value of 7 days to restore archived log files? What is the meaning behind this policy?

  The following script will delete backupsets that were created two days ago

• 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