Question on the implementation of the RMAN retention policy

Similar Questions

• 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

  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

• Question on the Adobe trial policy

  Hello

  If I download Dreamweaver trial then download Illustrator at trial next month and so forth?

  Thank you

  Hi Lawlesszero,

  Welcome to the Adobe Forum,

  You can download any product as trial & use for 30 days, it can be at the same time or at different times.

  Please refer to

  http://www.Adobe.com/products/CS6/FAQ.html#trial-Info

  Kind regards

  Baudier

• 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

• Purge the rman backup

  Hello, since the alert.log file find this error:
  
  Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc3_25352.trc file:
  ORA-19809: limit exceeded for file recovery
  ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
  ARC3: 19809 creation error archive log file ' DATA01'+.
  Sea 25 09:51:58 Jan 2012
  Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
  ORA-19815: WARNING: 59055800320 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.
  ************************************************************************
  You have choice to free up space in the recovery area:
  + 1. Consider changing the RMAN RETENTION POLICY. If you are using Data Guard +.
  then consider changing POLICY of DELETE ARCHIVELOG RMAN.
  + 2. Back up files on a tertiary device such as a tape using RMAN.
  SAFEGUARDING RECOVERY AREA command.
  + 3. Add disk space and increase the db_recovery_file_dest_size setting to +.
  reflect the new space.
  + 4. Delete unnecessary files by using the RMAN DELETE command. If operation +.
  the system control has been used to remove the files, and then use the RMAN DUPLICATION and
  Commands DELETE has EXPIRED.
  ************************************************************************
  Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
  ORA-19809: limit exceeded for file recovery
  ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
  ARC0: error creating 19809 archive log file ' DATA01'+.
  
  So I'm trying to purge the rman backup, but I have an error message:
  
  
  rman target = oratest@oraprdlnx1:~$ /+.
  Recovery Manager: release 11.2.0.1.0 - Production on sea Jan 25 09:47:30 2012
  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
  connected to target database: TEST (DBID = 2044700519)
  
  + RMAN > show all; +.
  
  using the control file of the target instead of recovery catalog database
  RMAN settings for database with db_unique_name TEST are:
  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
  CONFIGURE BACKUP OPTIMIZATION # by default
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE ENCRYPTION OF DATABASE # by default
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/oratest/product/11.2.0/dbhome_1/dbs/snapcf_TEST1.f'; # by default
  
  + RMAN > allocate channel for maintenance of type; disc +.
  
  allocated channel: ORA_MAINT_DISK_1
  channel ORA_MAINT_DISK_1: SID = 237 instance = type of TEST1 = DISK
  
  + RMAN > crosscheck backup; +.
  
  "" element of verified backup: turned out to be "AVAILABLE"
  backup handle piece = RECID = 68 = 758320264 STAMP DATA01/test/autobackup/2011_08_04/s_758320263.794.758320265 +.
  Cut objects 1
  
  RMAN > delete obsolete; ** +
  
  RMAN retention policy apply to the order
  RMAN retention policy is set to 1 redundancy
  Remove the following obsolete backups and copies:
  Making key time filename/handle type
  -------------------- ------ ------------------ --------------------
  Backup Set 25 July 4, 11
  Backup total 25 4 July 11 1omgk64v_1_1
  Backup Set 26 July 4, 11
  Backup total 26 July 4, 11 1pmgk650_1_1
  Backup Set 24 July 4, 11
  Total backup, 24 4 July 11 1qmgk650_1_1
  Backup Set 21 July 4, 11
  Backup total 21 4 July 11 1rmgk650_1_1
  Backup Set 28 July 4, 11
  28 1vmgk69v_1_1 July 4, 11 total backup
  Save game 29 July 4, 11
  Backup total 29 July 4, 11 20mgk6a0_1_1
  Backup Set 30 July 4, 11
  Backup total 30 4 July 11 21mgk6a0_1_1
  Save game 31 July 4, 11
  Backup total 31 July 4, 11 22mgk6a0_1_1
  Backup Set 34 4 July 11
  Backup total 34 4 July 11 c-2044700519-20110704-07
  Backup Set 35 July 4, 11
  Total backup, 35 26mgk8ib_1_1 4 July 11
  Backup Set 36 4 July 11
  Backup total 36 4 July 11 c-2044700519-20110704-08
  Backup Set 41 4 July 11
  Backup total 41 4 July 11 28mgk94i_1_1
  Backup Set 42 4 July 11
  Backup total 42 4 July 11 29mgk94j_1_1
  Backup Set 37 July 4, 11
  Backup total 37 4 July 11 2amgk94j_1_1
  Backup Set 40 July 4, 11
  Backup total 40 July 4, 11 2bmgk94j_1_1
  Backup Set 38 July 4, 11
  Backup total 38 4 July 11 2cmgk95c_1_1
  Backup Set 39 July 4, 11
  Backup total 39 4 July 11 2dmgk95k_1_1
  Backup Set 43 July 4, 11
  Backup total 43 July 4, 11 c-2044700519-20110704-09
  Backup Set 46 4 July 11
  Backup total 46 4 July 11 2fmgk99f_1_1
  Backup Set 47 July 4, 11
  Backup total 47 4 July 11 2gmgk99g_1_1
  Backup Set 44 4 July 11
  Backup total 44 4 July 11 2hmgk99g_1_1
  Backup Set 48 4 July 11
  Backup total 48 4 July 11 2imgk99g_1_1
  Backup Set 45 4 July 11
  Backup total 45 4 July 11 2jmgk9a9_1_1
  Backup Set 50 4 July 11
  Backup total 50 4 July 11 2kmgk9aq_1_1
  Backup Set 49 July 4, 11
  Backup total 49 4 July 11 2lmgk9aq_1_1
  Backup Set 51 4 July 11
  51 4 July total backup has 11 c-2044700519-20110704-0
  Backup Set 56 4 July 11
  Total backup 56 2rmgk9qb_1_1 July 4, 11
  Backup Set 55 July 4, 11
  Backup total 55 4 July 11 2smgk9qb_1_1
  Backup Set 58 4 July 11
  Backup total 58 4 July 11 b c-2044700519-20110704-0
  Backup Set 60 4 July 11
  Total backup 60 2umgk9tb_1_1 July 4, 11
  Backup Set 61 4 July 11
  Backup total 61 4 July 11 2vmgk9tc_1_1
  Backs up the entire 62 4 July 11
  Backup total 62 4 July 11 30mgk9tc_1_1
  Backup Set 66 4 July 11
  Backup total 66 4 July 11 34mgk9ua_1_1
  Backs up the entire 65 4 July 11
  Backup total 65 4 July 11 35mgk9ua_1_1
  Backup Set 67 4 July 11
  Total backup, July 4, 11 c-2044700519-20110704-0 67C
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
  RMAN-06091: any string allocated for maintenance (of a suitable type)
  
  How can I purge the db dest file recovery?
  
  Thank you!!!

  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
  RMAN-06091: any string allocated for maintenance (of a suitable type)

  There is a metalink note that talks about this error.

  Met RMAN-03002 and RMAN-06091 when deleting obsolete backups [567555.1 ID]
  RMAN could not remove obsolete in right Backupsets change Sbt_tape to disk and again Server [ID 1287755.1]

  HTH

  Kind regards
  Nagendra Chillale

  Published by: NC on January 25, 2012 17:00

• When the RMAN brand is backup incremental level1 obsolete?

  Hi all
  
  On a server Oracle 10.2.0.2 particular (with ODG), I implemented a strategy of incremental backup. A level 0 backup is available and all level 1 next backups are getting recovered to this first copy of data file. So far so good.
  
  The problem is that all these incremental backups at level 1 stay in my box of flashback and are not cleaned by RMAN. The retention policy is set on a window of 1 day.
  
  When the RMAN will start scoring these backups to level 1 as being obsolete? I guess that these backups are obsolete right after that they were applied to the copy of the data file? This has something to do with the size of the parameter area flashback, which means that it will not begin to remove level 1 backups when RMAN runs into problems of free space on the disk?
  
  Any help is appreciated!
  
  JM

  Hi JM,

  This is expected behavior, because you have changed the default retention of redundancy strategy 1.
  You can find this on My Oracle Support note + incremental backup strategies: Merge [ID 745798.1] +.

  The extract of this says:
  >
  When using Oracle-Suggested policy or a daily incremental backup merged and using a Flash recovery area and then keep the retention policy of RMAN for redundancy 1. This will ensure that the Oracle space management will automatically remove incremental backups at level 1 of the FRA after they have been applied to the image based on the pressure of space in the FRA copy. If you increase the redundancy or set a window of recovery space is is automatically retrieved by Oracle. This works only when the retention policy is set to the default value of redundancy = 1. If the configured retention policy is set to the window of recovery or > 1 redundancy, RMAN cannot satisfy the retention policy if there is only one copy of database and it's at a later point in time. Thus, in order to satisfy political retention Oracle keeps all the incremental backups and archivelogs since the creation of the database because ideally a data file can be re-created and archivelogs can be applied to meet the retention policy (although not followed in the practical case).
  >

  To have made them obsolete automatically, you must add the 'UNTIL TIME 'SYSDATE-2' ' clause to the COPY of RECOVER sentence, for a 1-day recovery window.

  The order having to RETRIEVE it after the BACKUP, you will have the current copy image, and you should only apply the archivelogs if you need to recover instead of use the last day of Level0 backup now level1.

  Kind regards.
  Nelson

• Recovery window retention policy removes the archive logs before backup?

  Hi all

  Oracle 11G on Windows 2008 R2

  This afternoon, I've changed my retention policy RMAN "RETENTION POLICY 3 REDUNDANCY"on RECOVERY WINDOW OF 3 DAYS RETENTION POLICY

  However, I checked tonight and after that my daily backup, all the archive before backup logs had been removed! So that means I don't think I can restore to any point in time, before my daily backup. All newspapers .arc were there after the backup. Then I tried another test and began the daily backup again. During the backup process, archive logs were deleted again! Now, I don't have any archives of newspapers...

  Is this good behavior OF RETENTION POLICY RECOVERY WINDOW? I thought that she would keep all the files needed for to restore me to any point in time for the previous 3 days. When I used a REDUNDANCY, with my daily backups, he kept 3 days of backups + archiving logs so that I could restore point-in-time at any point. How can I use WINDOW RECOVERY so that I can actually restore to any point in time for the 3 days?

  I wanted to change WINDOW of recovery, since I read that using the REDUNDANCY, it keeps only X copy a backup (so if I ran the backup 3 times a day, I would have only these 3).

  Thanks in advance.

  After a database RESTORE, Oracle tries to RECOVER a DATABASE.  He tries to 'find' the archivelogs for this phase in the location expected archivelog.  If they are NOT present in the location expected archivelog, it attempts to restore backups before applying them.

  Since your BACKUP... DELETE ENTRY deletes the archivelogs after that that they are saved, Oracle will have to use backups to recover the archivelogs.

  Hemant K Collette

• 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

• Moving the RMAN catalog

  Hello
  My question concerns the RMAN catalog. A few months ago we moved from solaris zones linux servers. A new catalog of recovery was created on linux servers (same name as the catalog of recovery on solaris zones). There are a few databases that couldn't be moved on the linux server and I would like to re - run databases on solaris zones to use the linux RMAN catalog. Should what steps I follow? Thank you.
  
  J

  A new catalog of recovery was created on linux servers (same name as the catalog of recovery on solaris zones).

  Since its new catalogue, then you will need to register your database in this catalogue and use this database schema name while making the connection to this rman catalog.

• 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
  

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

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

• Retention policy does not work

  Hello
  
  I have 2 node RAC 10 g 2 db. Operating system is 5.8 RHEL. I'm with RMAN for full backups every night. The problem is the old backups not automatically deleted through the retention policy, which is 7 days. For example, now, I have at least one backup set that is about 1 month. Here is a part of the log RMAN:
  
  delete noprompt obsolete device type disk;
  RMAN retention policy apply to the order
  channel ORA_MAINT_DISK_1: sid = 4327 instance = MYYRAC1 devtype = DISK
  allocated channel: ORA_MAINT_DISK_1
  output channel: ORA_DISK_1
  RMAN retention policy is set to 7 days recovery window
  not found obsolete backups
  output channel;
  
  Thus, the final problem which is the disc will sooner or later totally old full backups.

  Hello;

  Obsolete backups can be complex. Watch the incremental backups that extend the retention period. This simple command can help:

  RMAN > OBSOLETE REPORT.

  Otherwise, I have this note:

  http://www.Visi.com/~mseberg/RMAN/obsolete_backups.html

  If the catalog has no problem and retention policy is set, it almost always works:

  RMAN > DELETE noprompt obsolete;

  More information

  http://www.Visi.com/~mseberg/RMAN/backup_redundancy.html

  http://www.Visi.com/~mseberg/RMAN/recovery_window.html

  Best regards

  mseberg

• 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