Retention policy for specific backupset

Hi,
Actually I am envolved in a Proof Of Concept for Exadata. My customer wants to set a specific rentention for one backupset. These are the steps followed and the problem:
1. Perform a "backup as backupset" for database to disk.
2. Perform a "backup backupset" to tape for the backup of step 1.
3. Change the retention policy only for the backup of step 2 and set it to be kept until sysdate+x days.
Does anyone know how can be this done?
Best regards.

You will need to create two different backup one to device type DISK with default retention and another backup to device type SBT_TAPE with specific retention.
The SAME backup (backupset) cannot have two different retention (even if it's a copy). The copy of backupset belongs to a Backup which already has it own retention.
see this example:
RMAN> backup current controlfile ;
Starting backup at 17-OCT-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=10 device type=DISK
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 17-OCT-12
channel ORA_DISK_1: finished piece 1 at 17-OCT-12
piece handle=/u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_10_17/o1_mf_ncnnf_TAG20121017T145951_87xwjrjn_.bkp tag=TAG20121017T145951 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 17-OCT-12
RMAN> backup backupset from tag TAG20121017T145951 ;
Starting backup at 17-OCT-12
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=10 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
channel ORA_SBT_TAPE_1: input backup set: count=14735, stamp=796921191, piece=1
channel ORA_SBT_TAPE_1: starting piece 1 at 17-OCT-12
channel ORA_SBT_TAPE_1: backup piece /u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_10_17/o1_mf_ncnnf_TAG20121017T145951_87xwjrjn_.bkp
piece handle=BKP_CONTROL_ORCL_14735_1_20121017_2 comment=API Version 2.0,MMS Version 5.5.1.0
channel ORA_SBT_TAPE_1: finished piece 1 at 17-OCT-12
channel ORA_SBT_TAPE_1: backup piece complete, elapsed time: 00:00:04
Finished backup at 17-OCT-12
RMAN> list backup;
BS Key  Type LV Size
14667   Full    1.11M
  Control File Included: Ckp SCN: 142367578    Ckp time: 17-OCT-12
  Backup Set Copy #1 of backup set 14667
  Device Type Elapsed Time Completion Time Compressed Tag
  DISK        00:00:02     17-OCT-12       YES        TAG20121017T145951
    List of Backup Pieces for backup set 14667 Copy #1
    BP Key  Pc# Status      Piece Name
    14667   1   AVAILABLE   /u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_10_17/o1_mf_ncnnf_TAG20121017T145951_87xwjrjn_.bkp
  Backup Set Copy #2 of backup set 14667
  Device Type Elapsed Time Completion Time Compressed Tag
  SBT_TAPE    00:00:02     17-OCT-12       YES        TAG20121017T145951
    List of Backup Pieces for backup set 14667 Copy #2
    BP Key  Pc# Status      Media                   Piece Name
    14668   1   AVAILABLE   44531                   BKP_CONTROL_ORCL_14735_1_20121017_2
RMAN> change backuppiece 14668 keep forever logs;
using channel ORA_DISK_1
using channel ORA_SBT_TAPE_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of KEEP command at 10/17/2012 15:02:24
RMAN-06528: CHANGE ... KEEP not supported for BACKUPPIECEIn example above the BACKUPSET 14667 have two BACKUPPIECE (14667,14668) if you change retention of BACKUPSET 14667 you will change retention of both BACKUPPIECE.
I don't recommend do this ,but is a poor option:
RMAN> delete backuppiece 14667;
using channel ORA_DISK_1
using channel ORA_SBT_TAPE_1
List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
14667   14667   1   1   AVAILABLE   DISK        /u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_10_17/o1_mf_ncnnf_TAG20121017T145951_87xwjrjn_.bkp
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=/u01/app/oracle/flash_recovery_area/ORCL/backupset/2012_10_17/o1_mf_ncnnf_TAG20121017T145951_87xwjrjn_.bkp RECID=14667 STAMP=796921192
Deleted 1 objects
RMAN> list backup;
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
14667   Full    1.11M      SBT_TAPE    00:00:02     17-OCT-12
        BP Key: 14668   Status: AVAILABLE  Compressed: YES  Tag: TAG20121017T145951
        Handle: BKP_CONTROL_ORCL_14735_1_20121017_2   Media: 44531
  Control File Included: Ckp SCN: 142367578    Ckp time: 17-OCT-12
RMAN> change backupset 14667   keep forever;
using channel ORA_DISK_1
using channel ORA_SBT_TAPE_1
keep attributes for the backup are changed
backup will never be obsolete
backup set key=14667   RECID=14667 STAMP=796921193
RMAN > list backup;
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
14667    Full    1.11M      SBT_TAPE    00:00:02     17-OCT-12
        BP Key: 14667   Status: AVAILABLE  Compressed: YES  Tag: TAG20121017T145951
        Handle: BKP_CONTROL_ORCL_14735_1_20121017_2   Media: 44531
        Keep: BACKUP_LOGS        Until: FOREVER
  Control File Included: Ckp SCN: 142367578    Ckp time: 17-OCT-12Edited by: Levi Pereira on Oct 17, 2012 4:02 PM

Similar Messages

  • Retention policy for archivelogs in the flash recovery area

    I am using the flash recovery area for all my backup files (archive logs, data and control files). I want to use the redundancy retention policy because it is easy to calculate the space requirement. However, I am not clear how the retention policy applies to archive logs.
    Say I set the retention policy to be "keeping 3 backups". How does it affect the archive logs? Will archive logs in the flash recovery area be deleted automatically or I need to do it manually. If they are deleted automatically just like dataset files, what is the "retention policy" for them? I do not have a tape device so all archive logs are going to be stay in disk.
    Thanks.

    I am using the flash recovery area for all my backup
    files (archive logs, data and control files). I want
    to use the redundancy retention policy because it is
    easy to calculate the space requirement. However, I
    am not clear how the retention policy applies to
    archive logs.
    RMAN> show retention policy
    2> ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    no obsolete backups found
    RMAN> list backup
    2> ;
    RMAN>AS documentation says
    "Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups.
    First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
    log backups that are older than the oldest datafile or control file backup that must be retained."
    Now i connect to SQL and create two big table for filling the redo log file and then get it archived.Please
    consider it here that i am getting archived before any taking backup i.e backup database in order to make
    archive older then the oldest datafile.
    SQL> show parameter control_file_record_keep_time
    NAME                                 TYPE        VALUE
    control_file_record_keep_time        integer     7
    SQL> create table a1 as select * from all_objects
      2  /
    Table created.
    SQL> create table a2 as select * from all_objects
      2  /
    Table created.
    C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
    Volume in drive C is khurram
    Volume Serial Number is F49D-FF2B
    Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
    03/17/2008  03:44 PM    <DIR>          .
    03/17/2008  03:44 PM    <DIR>          ..
    03/17/2008  03:44 PM         9,750,528 O1_MF_1_15_3XWLVK6T_.ARC
                   1 File(s)      9,750,528 bytes
                   2 Dir(s)  62,714,875,904 bytes free
    Now i take backup
    RMAN> backup database
    2> ;
    Starting backup at 17-MAR-08
    using channel ORA_DISK_1
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    no obsolete backups found
    RMAN> backup database
    2> ;
    Starting backup at 17-MAR-08
    using channel ORA_DISK_1
    RMAN> report obsolete
    2> ;
    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
    Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARCYou can see the obsolete archived files which is the older then the oldest file which has been obsolete.It also
    does'nt make sense to keep the archived log files which is older then the oldest file cause it will no longer
    be useful for recovery process.
    now back to pavillion
    RMAN> delete obsolete
    2> ;
    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
    Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC
    Do you really want to delete the above objects (enter YES or NO)? yes
    deleted archive log
    archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
    G\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC recid=402 stamp=649611842
    Deleted 1 objects
    RMAN> delete backup
    2> ;
    using channel ORA_DISK_1
    RMAN> list backup
    2> ;
    C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
    Volume in drive C is khurram
    Volume Serial Number is F49D-FF2B
    Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
    03_17
    03/17/2008  03:59 PM    <DIR>          .
    03/17/2008  03:59 PM    <DIR>          ..
                   0 File(s)              0 bytes
                   2 Dir(s)  62,724,440,064 bytes freenow this time what i did i created the archived log files after first backup in order to not to make it older
    then the oldest datafile backup.
    RMAN> backup database
    2> ;
    Starting backup at 17-MAR-08
    using channel ORA_DISK_1
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    no obsolete backups foundnow i come to at SQL and make redo log file filled by creating 2 big tables in order to get it archived
    SQL> create table a3 as select * from all_objects
      2  /
    Table created.
    SQL> create table a4 as select * from all_objects
      2  /
    Table created.
    C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
    Volume in drive C is khurram
    Volume Serial Number is F49D-FF2B
    Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
    03_17
    03/17/2008  04:09 PM    <DIR>          .
    03/17/2008  04:09 PM    <DIR>          ..
    03/17/2008  04:09 PM         9,751,552 O1_MF_1_16_3XWNCGRS_.ARC
                   1 File(s)      9,751,552 bytes
                   2 Dir(s)  62,563,205,120 bytes free
    RMAN> backup database
    2> ;
    Starting backup at 17-MAR-08
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting compressed full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    RMAN> report obsolete
    2> ;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 2
    no obsolete backups foundYou can see no archived logs get obsolete yet cause the archivelog O1_MF_1_16_3XWNCGRS_.ARC
    is not older then oldest datafile backup.
    But this archivelog file will get obsolete if its beyond the retention policy,lest see how ,just take one more
    backup ,as i have already taken two time backup and the moment i go to take third backup it will cross ours
    retetnion policy from the period of 2.
    RMAN> backup database
    2> ;
    RMAN> report obsolete
    2> ;
    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           240    17-MAR-08
      Backup Piece       231    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NNNDF_TAG20080317T160604_3XWN4WTB_.B
    KP
    Backup Set           241    17-MAR-08
      Backup Piece       232    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NCSNF_TAG20080317T160604_3XWN6Z95_.B
    KP
    Archive Log          403    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_16_3XWNCGRS_.ARCKhurram

  • Retention policy for incremental cumulative backup question

    Hi,
    I have a production database configured with retention policy for 30 days window. No catalog is used.
    The backup plan is:
    Sunday - Level 0 backup.
    Weekdays - Incremental 1 cumulative backup.
    I also noticed that some archive logs since Mar 07 2010 has become obsolete in the recent few days.
    Cannot figure out why the backup of Mar 07 2010 is going to be obsolete today.
    Thanks for your help!
    RMAN> list backup summary;
    using target database control file instead of recovery catalog
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
    *14 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
    *15 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
    *17 B F A SBT_TAPE 07-MAR-10 1 1 NO*
    21 B F A SBT_TAPE 08-MAR-10 1 1 NO
    24 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    25 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    27 B F A SBT_TAPE 08-MAR-10 1 1 NO
    35 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    36 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    38 B F A SBT_TAPE 09-MAR-10 1 1 NO
    46 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    47 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    49 B F A SBT_TAPE 10-MAR-10 1 1 NO
    57 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    58 B 1 A SBT_TAPE 11-MAR-10 2 1 NO
    60 B F A SBT_TAPE 11-MAR-10 1 1 NO
    66 B A A SBT_TAPE 12-MAR-10 1 1 NO
    67 B A A SBT_TAPE 12-MAR-10 1 1 NO
    68 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    69 B 1 A SBT_TAPE 12-MAR-10 2 1 NO
    70 B A A SBT_TAPE 12-MAR-10 1 1 NO
    71 B F A SBT_TAPE 12-MAR-10 1 1 NO
    77 B A A SBT_TAPE 14-MAR-10 1 1 NO
    78 B A A SBT_TAPE 14-MAR-10 1 1 NO
    79 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
    80 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
    81 B A A SBT_TAPE 14-MAR-10 1 1 NO
    82 B F A SBT_TAPE 14-MAR-10 1 1 NO
    88 B A A SBT_TAPE 15-MAR-10 1 1 NO
    89 B A A SBT_TAPE 15-MAR-10 1 1 NO
    90 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    91 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    92 B A A SBT_TAPE 15-MAR-10 1 1 NO
    93 B F A SBT_TAPE 15-MAR-10 1 1 NO
    99 B A A SBT_TAPE 16-MAR-10 1 1 NO
    100 B A A SBT_TAPE 16-MAR-10 1 1 NO
    101 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    102 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    103 B A A SBT_TAPE 16-MAR-10 1 1 NO
    104 B F A SBT_TAPE 16-MAR-10 1 1 NO
    109 B A A SBT_TAPE 17-MAR-10 4 1 NO
    110 B F A SBT_TAPE 17-MAR-10 1 1 NO
    111 B A A SBT_TAPE 17-MAR-10 1 1 NO
    112 B F A SBT_TAPE 17-MAR-10 1 1 NO
    113 B A A SBT_TAPE 17-MAR-10 1 1 NO
    114 B A A SBT_TAPE 17-MAR-10 1 1 NO
    115 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    116 B 1 A SBT_TAPE 17-MAR-10 2 1 NO
    117 B A A SBT_TAPE 17-MAR-10 1 1 NO
    118 B F A SBT_TAPE 17-MAR-10 1 1 NO
    123 B A A SBT_TAPE 18-MAR-10 2 1 NO
    124 B F A SBT_TAPE 18-MAR-10 1 1 NO
    125 B A A SBT_TAPE 18-MAR-10 2 1 NO
    126 B F A SBT_TAPE 18-MAR-10 1 1 NO
    127 B A A SBT_TAPE 18-MAR-10 1 1 NO
    128 B F A SBT_TAPE 18-MAR-10 1 1 NO
    129 B A A SBT_TAPE 18-MAR-10 1 1 NO
    130 B F A SBT_TAPE 18-MAR-10 1 1 NO
    131 B A A SBT_TAPE 18-MAR-10 1 1 NO
    132 B A A SBT_TAPE 18-MAR-10 1 1 NO
    133 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    134 B 1 A SBT_TAPE 18-MAR-10 2 1 NO
    135 B A A SBT_TAPE 18-MAR-10 1 1 NO
    136 B F A SBT_TAPE 18-MAR-10 1 1 NO
    142 B A A SBT_TAPE 19-MAR-10 2 1 NO
    143 B F A SBT_TAPE 19-MAR-10 1 1 NO
    144 B A A SBT_TAPE 19-MAR-10 1 1 NO
    145 B F A SBT_TAPE 19-MAR-10 1 1 NO
    146 B A A SBT_TAPE 19-MAR-10 1 1 NO
    147 B F A SBT_TAPE 19-MAR-10 1 1 NO
    148 B A A SBT_TAPE 19-MAR-10 1 1 NO
    149 B F A SBT_TAPE 19-MAR-10 1 1 NO
    150 B A A SBT_TAPE 19-MAR-10 1 1 NO
    151 B A A SBT_TAPE 19-MAR-10 1 1 NO
    152 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    153 B 1 A SBT_TAPE 19-MAR-10 2 1 NO
    154 B A A SBT_TAPE 19-MAR-10 1 1 NO
    155 B F A SBT_TAPE 19-MAR-10 1 1 NO
    161 B A A SBT_TAPE 21-MAR-10 1 1 NO
    162 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
    163 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
    164 B A A SBT_TAPE 21-MAR-10 1 1 NO
    165 B F A SBT_TAPE 21-MAR-10 1 1 NO
    171 B A A SBT_TAPE 22-MAR-10 1 1 NO
    172 B F A SBT_TAPE 22-MAR-10 1 1 NO
    173 B A A SBT_TAPE 22-MAR-10 1 1 NO
    174 B F A SBT_TAPE 22-MAR-10 1 1 NO
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.ccbprod)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_ccbprod.f'; # default
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 30 days
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Control File Copy 108 19-FEB-10 /ccbprod/oradata/ccbprod/arc/control.bak.100219.21.21
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       19     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_5_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       18     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_4_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       17     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_3_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       16     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_2_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       15     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_1_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       14     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_5_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       13     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_4_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       12     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_3_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       11     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_2_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       10     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_1_1
    Backup Set 10 07-MAR-10 Backup Piece 21 07-MAR-10 c-2894189962-20100307-00
    Edited by: user12019850 on 22-Mar-2010 10:53 AM

    Another database with the same configuration and same plan seems fine:
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.cisconf)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_cisconf.f'; # default
    RMAN> list backup summary;
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
    774 B 0 A SBT_TAPE 19-FEB-10 1 1 NO
    775 B 0 A SBT_TAPE 19-FEB-10 2 1 NO
    795 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
    796 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
    797 B A A SBT_TAPE 20-FEB-10 1 1 NO
    803 B A A SBT_TAPE 20-FEB-10 1 1 NO
    804 B F A SBT_TAPE 20-FEB-10 1 1 NO
    805 B A A SBT_TAPE 20-FEB-10 1 1 NO
    806 B F A SBT_TAPE 20-FEB-10 1 1 NO
    807 B A A SBT_TAPE 20-FEB-10 1 1 NO
    808 B F A SBT_TAPE 20-FEB-10 1 1 NO
    809 B A A SBT_TAPE 21-FEB-10 1 1 NO
    810 B 0 A SBT_TAPE 21-FEB-10 1 1 NO
    811 B 0 A SBT_TAPE 21-FEB-10 2 1 NO
    812 B A A SBT_TAPE 21-FEB-10 1 1 NO
    813 B F A SBT_TAPE 21-FEB-10 1 1 NO
    818 B A A SBT_TAPE 21-FEB-10 1 1 NO
    819 B F A SBT_TAPE 21-FEB-10 1 1 NO
    820 B A A SBT_TAPE 21-FEB-10 1 1 NO
    821 B F A SBT_TAPE 21-FEB-10 1 1 NO
    822 B A A SBT_TAPE 21-FEB-10 1 1 NO
    823 B F A SBT_TAPE 21-FEB-10 1 1 NO
    824 B A A SBT_TAPE 22-FEB-10 1 1 NO
    825 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
    826 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
    827 B A A SBT_TAPE 22-FEB-10 1 1 NO
    828 B F A SBT_TAPE 22-FEB-10 1 1 NO
    833 B A A SBT_TAPE 22-FEB-10 1 1 NO
    834 B F A SBT_TAPE 22-FEB-10 1 1 NO
    835 B A A SBT_TAPE 22-FEB-10 1 1 NO
    836 B F A SBT_TAPE 22-FEB-10 1 1 NO
    837 B A A SBT_TAPE 22-FEB-10 1 1 NO
    838 B F A SBT_TAPE 22-FEB-10 1 1 NO
    839 B A A SBT_TAPE 22-FEB-10 1 1 NO
    840 B F A SBT_TAPE 22-FEB-10 1 1 NO
    841 B A A SBT_TAPE 23-FEB-10 1 1 NO
    842 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
    843 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
    844 B A A SBT_TAPE 23-FEB-10 1 1 NO
    845 B F A SBT_TAPE 23-FEB-10 1 1 NO
    850 B A A SBT_TAPE 23-FEB-10 1 1 NO
    851 B F A SBT_TAPE 23-FEB-10 1 1 NO
    852 B A A SBT_TAPE 23-FEB-10 1 1 NO
    853 B F A SBT_TAPE 23-FEB-10 1 1 NO
    854 B A A SBT_TAPE 23-FEB-10 1 1 NO
    855 B F A SBT_TAPE 23-FEB-10 1 1 NO
    856 B A A SBT_TAPE 24-FEB-10 1 1 NO
    857 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    858 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    859 B A A SBT_TAPE 24-FEB-10 1 1 NO
    860 B F A SBT_TAPE 24-FEB-10 1 1 NO
    865 B A A SBT_TAPE 24-FEB-10 1 1 NO
    866 B F A SBT_TAPE 24-FEB-10 1 1 NO
    867 B A A SBT_TAPE 24-FEB-10 1 1 NO
    868 B F A SBT_TAPE 24-FEB-10 1 1 NO
    869 B A A SBT_TAPE 24-FEB-10 1 1 NO
    870 B F A SBT_TAPE 24-FEB-10 1 1 NO
    871 B A A SBT_TAPE 24-FEB-10 1 1 NO
    872 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    873 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    874 B A A SBT_TAPE 24-FEB-10 1 1 NO
    875 B F A SBT_TAPE 24-FEB-10 1 1 NO
    880 B A A SBT_TAPE 24-FEB-10 1 1 NO
    881 B F A SBT_TAPE 24-FEB-10 1 1 NO
    882 B A A SBT_TAPE 25-FEB-10 1 1 NO
    883 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
    884 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
    885 B A A SBT_TAPE 25-FEB-10 1 1 NO
    886 B F A SBT_TAPE 25-FEB-10 1 1 NO
    891 B A A SBT_TAPE 25-FEB-10 1 1 NO
    892 B F A SBT_TAPE 25-FEB-10 1 1 NO
    893 B A A SBT_TAPE 25-FEB-10 1 1 NO
    894 B F A SBT_TAPE 25-FEB-10 1 1 NO
    895 B A A SBT_TAPE 25-FEB-10 1 1 NO
    896 B F A SBT_TAPE 25-FEB-10 1 1 NO
    897 B A A SBT_TAPE 25-FEB-10 1 1 NO
    898 B F A SBT_TAPE 25-FEB-10 1 1 NO
    899 B A A SBT_TAPE 25-FEB-10 1 1 NO
    900 B F A SBT_TAPE 25-FEB-10 1 1 NO
    901 B A A SBT_TAPE 25-FEB-10 1 1 NO
    902 B F A SBT_TAPE 25-FEB-10 1 1 NO
    903 B A A SBT_TAPE 26-FEB-10 1 1 NO
    904 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
    905 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
    906 B A A SBT_TAPE 26-FEB-10 1 1 NO
    907 B F A SBT_TAPE 26-FEB-10 1 1 NO
    912 B A A SBT_TAPE 26-FEB-10 1 1 NO
    913 B F A SBT_TAPE 26-FEB-10 1 1 NO
    914 B A A SBT_TAPE 26-FEB-10 1 1 NO
    915 B F A SBT_TAPE 26-FEB-10 1 1 NO
    916 B A A SBT_TAPE 26-FEB-10 1 1 NO
    917 B F A SBT_TAPE 26-FEB-10 1 1 NO
    918 B A A SBT_TAPE 27-FEB-10 1 1 NO
    919 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
    920 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
    921 B A A SBT_TAPE 27-FEB-10 1 1 NO
    922 B F A SBT_TAPE 27-FEB-10 1 1 NO
    927 B A A SBT_TAPE 27-FEB-10 1 1 NO
    928 B F A SBT_TAPE 27-FEB-10 1 1 NO
    929 B A A SBT_TAPE 27-FEB-10 1 1 NO
    930 B F A SBT_TAPE 27-FEB-10 1 1 NO
    931 B A A SBT_TAPE 27-FEB-10 1 1 NO
    932 B F A SBT_TAPE 27-FEB-10 1 1 NO
    933 B A A SBT_TAPE 28-FEB-10 1 1 NO
    934 B 0 A SBT_TAPE 28-FEB-10 1 1 NO
    935 B 0 A SBT_TAPE 28-FEB-10 2 1 NO
    936 B A A SBT_TAPE 28-FEB-10 1 1 NO
    937 B F A SBT_TAPE 28-FEB-10 1 1 NO
    942 B A A SBT_TAPE 28-FEB-10 1 1 NO
    943 B F A SBT_TAPE 28-FEB-10 1 1 NO
    944 B A A SBT_TAPE 28-FEB-10 1 1 NO
    945 B F A SBT_TAPE 28-FEB-10 1 1 NO
    946 B A A SBT_TAPE 28-FEB-10 1 1 NO
    947 B F A SBT_TAPE 28-FEB-10 1 1 NO
    948 B A A SBT_TAPE 01-MAR-10 1 1 NO
    949 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
    950 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
    951 B A A SBT_TAPE 01-MAR-10 1 1 NO
    952 B F A SBT_TAPE 01-MAR-10 1 1 NO
    957 B A A SBT_TAPE 01-MAR-10 1 1 NO
    958 B F A SBT_TAPE 01-MAR-10 1 1 NO
    959 B A A SBT_TAPE 01-MAR-10 1 1 NO
    960 B F A SBT_TAPE 01-MAR-10 1 1 NO
    961 B A A SBT_TAPE 01-MAR-10 1 1 NO
    962 B F A SBT_TAPE 01-MAR-10 1 1 NO
    963 B A A SBT_TAPE 02-MAR-10 1 1 NO
    964 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
    965 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
    966 B A A SBT_TAPE 02-MAR-10 1 1 NO
    967 B F A SBT_TAPE 02-MAR-10 1 1 NO
    970 B A A SBT_TAPE 02-MAR-10 1 1 NO
    971 B F A SBT_TAPE 02-MAR-10 1 1 NO
    972 B A A SBT_TAPE 02-MAR-10 1 1 NO
    973 B F A SBT_TAPE 02-MAR-10 1 1 NO
    974 B A A SBT_TAPE 02-MAR-10 1 1 NO
    975 B F A SBT_TAPE 02-MAR-10 1 1 NO
    976 B A A SBT_TAPE 03-MAR-10 1 1 NO
    977 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
    978 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
    979 B A A SBT_TAPE 03-MAR-10 1 1 NO
    980 B F A SBT_TAPE 03-MAR-10 1 1 NO
    983 B A A SBT_TAPE 03-MAR-10 1 1 NO
    984 B F A SBT_TAPE 03-MAR-10 1 1 NO
    985 B A A SBT_TAPE 03-MAR-10 1 1 NO
    986 B F A SBT_TAPE 03-MAR-10 1 1 NO
    987 B A A SBT_TAPE 03-MAR-10 1 1 NO
    988 B F A SBT_TAPE 03-MAR-10 1 1 NO
    989 B A A SBT_TAPE 04-MAR-10 1 1 NO
    990 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
    991 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
    992 B A A SBT_TAPE 04-MAR-10 1 1 NO
    993 B F A SBT_TAPE 04-MAR-10 1 1 NO
    996 B A A SBT_TAPE 04-MAR-10 1 1 NO
    997 B F A SBT_TAPE 04-MAR-10 1 1 NO
    998 B A A SBT_TAPE 04-MAR-10 1 1 NO
    999 B F A SBT_TAPE 04-MAR-10 1 1 NO
    1000 B A A SBT_TAPE 04-MAR-10 1 1 NO
    1001 B F A SBT_TAPE 04-MAR-10 1 1 NO
    1002 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1003 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
    1004 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
    1005 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1006 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1009 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1010 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1011 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1012 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1013 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1014 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1015 B A A SBT_TAPE 06-MAR-10 1 1 NO
    1016 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
    1017 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
    1018 B A A SBT_TAPE 06-MAR-10 1 1 NO
    1019 B F A SBT_TAPE 06-MAR-10 1 1 NO
    1022 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1023 B 0 A SBT_TAPE 07-MAR-10 1 1 NO
    1024 B 0 A SBT_TAPE 07-MAR-10 2 1 NO
    1025 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1026 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1029 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1030 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1031 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1032 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1033 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1034 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1035 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1036 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1037 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1038 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1039 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1042 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1043 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1044 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1045 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1046 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1047 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1048 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1054 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1055 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1056 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    1057 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    1058 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1059 B F A SBT_TAPE 09-MAR-10 1 1 NO
    1065 B A A SBT_TAPE 10-MAR-10 1 1 NO
    1066 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    1067 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    1068 B A A SBT_TAPE 10-MAR-10 1 1 NO
    1069 B F A SBT_TAPE 10-MAR-10 1 1 NO
    1075 B A A SBT_TAPE 11-MAR-10 1 1 NO
    1076 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    1077 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    1078 B A A SBT_TAPE 11-MAR-10 1 1 NO
    1079 B F A SBT_TAPE 11-MAR-10 1 1 NO
    1085 B A A SBT_TAPE 12-MAR-10 1 1 NO
    1086 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    1087 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    1088 B A A SBT_TAPE 12-MAR-10 1 1 NO
    1089 B F A SBT_TAPE 12-MAR-10 1 1 NO
    1094 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1095 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1096 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
    1097 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
    1098 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1099 B F A SBT_TAPE 13-MAR-10 1 1 NO
    1105 B A A SBT_TAPE 14-MAR-10 1 1 NO
    1106 B 0 A SBT_TAPE 14-MAR-10 1 1 NO
    1107 B 0 A SBT_TAPE 14-MAR-10 2 1 NO
    1108 B A A SBT_TAPE 14-MAR-10 1 1 NO
    1109 B F A SBT_TAPE 14-MAR-10 1 1 NO
    1115 B A A SBT_TAPE 15-MAR-10 1 1 NO
    1116 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    1117 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    1118 B A A SBT_TAPE 15-MAR-10 1 1 NO
    1119 B F A SBT_TAPE 15-MAR-10 1 1 NO
    1125 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1126 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1127 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    1128 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    1129 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1130 B F A SBT_TAPE 16-MAR-10 1 1 NO
    1136 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1137 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1138 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    1139 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    1140 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1141 B F A SBT_TAPE 17-MAR-10 1 1 NO
    1147 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1148 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1149 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    1150 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    1151 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1152 B F A SBT_TAPE 18-MAR-10 1 1 NO
    1158 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1159 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1160 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    1161 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    1162 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1163 B F A SBT_TAPE 19-MAR-10 1 1 NO
    1169 B A A SBT_TAPE 20-MAR-10 1 1 NO
    1170 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
    1171 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
    1172 B A A SBT_TAPE 20-MAR-10 1 1 NO
    1173 B F A SBT_TAPE 20-MAR-10 1 1 NO
    1179 B A A SBT_TAPE 21-MAR-10 1 1 NO
    1180 B 0 A SBT_TAPE 21-MAR-10 1 1 NO
    1181 B 0 A SBT_TAPE 21-MAR-10 2 1 NO
    1182 B A A SBT_TAPE 21-MAR-10 1 1 NO
    1183 B F A SBT_TAPE 21-MAR-10 1 1 NO
    1189 B A A SBT_TAPE 22-MAR-10 1 1 NO
    1190 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
    1191 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
    1192 B A A SBT_TAPE 22-MAR-10 1 1 NO
    1193 B F A SBT_TAPE 22-MAR-10 1 1 NO
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 30 days
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Control File Copy 47 20-FEB-10 /dbbackup/cisconf/control.bak.20100220
    Backup Set 804 20-FEB-10
    Backup Piece 551 20-FEB-10 c-3316101807-20100220-01
    Edited by: user12019850 on 22-Mar-2010 11:03 AM

  • Retention Policy for Tasks

    I am helping a client with their Exchange Online archiving policies.  Everything was working well until we realized that Tasks were getting archived according the default archiving policy.  I do not see the option to create a Default Retention
    Policy for Tasks.  It is not listed in the Default Folders drop down menu.  Another article indicated that they had the same issue and had to set the Default Policy to never archive and then setup individual policies for folders they did want archive
    in order to protect the Tasks folder.  However, I only seem to able to create "Archiving Policies" as a personal option.  I do not get the option to create an Archiving policy default folders.  The only option I see for Default folders
    is "Delete and Allow Recovery" or "Permanently Delete".  Move to Archive is not listed.   Please Help.

    The Default tag applies to Tasks folder as well. If you want to prevent items in that folder from being moved to the Archive mailbox, create a new Personal tag with the move to archive option, and apply it to the folder. As the retention options for the
    Tasks folder are not exposed to the end user either via Outlook or OWA, you will have to use EWS based script.
    You can refer to this article for more info:
    http://blogs.technet.com/b/exchange/archive/2013/05/20/using-exchange-web-services-to-apply-a-personal-tag-to-a-custom-folder.aspx

  • RMAN RETENTION POLICY FOR ORACLE8I

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

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

  • How to apply Software Restriction policy for specific user in local group policy object ?

    I am working on implementing user based software restriction policy programmatically for local group policy object.
    If i create a policy through Domain Controller,i do have option for software restriction policy in user configuration but in local group policy editor i don't have option for that.
    When i look for the changes made by policy applied from Domain Controller in registry, they modifies registry values for specific users on path HKEY_USERS\(SID of User)\Softwares\Policies\Microsoft\Windows\Safer\Codeidentifiers
    They also have registry.pol stored in SYSvol folder in Domain Controller. When i make the same changes in registry to block any other application, application is getting blocked.
    I achieved what i wanted but is it right to modify registry values ?  
    PS:- I am using Igrouppolicyobject API

    I achieved what I wanted but is it right to modify registry values ?
    You also can modify a registry programmatically based policy. Check this:
    http://blogs.msdn.com/b/dsadsi/archive/2009/07/23/working-with-group-policy-objects-programmatically-simple-c-example-illustrating-how-to-modify-a-registry-based-policy.aspx
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • OIM Authorization policy for specific resource

    Hi gurus,
    Can we create an authorization policy in OIM 11.1.1.5 for allowing resource administrators to add/modify a specific resource only?
    Example: For all users, Admin user-A should be able to add/modify AD resource only.
    Admin User-B should be able to add/Modify iPlanet resource only
    Thanks in advance.
    -J

    OIM 11.1.1.5 authorization policies do not extend to resource operations, only operations on OIM users and roles. For restricting operations on resources you can set data object permissions on the resource objects themselves. An alternative approach in OIM 11.1.1.5 is to provision resources via requests, where you can limit requests to work with specific allowed resources and be accessible to specific administrators.

  • How to force retention policy in Office365 for a mailbox

    Looking to run the MRM retention policy for a E3 mailbox and or Tenant.   I have an old PST file (2011 and older) that I have attached to their active Office365 mailbox Inbox Subfolder and have a policy in MRM to send the online Archive.  
    I know the MRM policy works because it has placed items in the "Online Archive" for the inbox and it's sub folders.
    The questions is how often does this MRM policy run on it's own?   Daily, hourly, weekly.
    How do I force the policy to take effect immediately?
    This is what I believe will do this via powershell:
    Set-executionpolicy remotesigned -force
    Set-executionpolicy unrestricted -force
    $LiveCred = Get-Credential
    Connect-msolservice -credential $LiveCred
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUrl
    https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection Import-PSSession $Session
      Set-Mailbox “mailbox name” -RetentionPolicy “Archive Policy”
     Start-ManagedFolderAssistant -Identity “mailbox name”

    Hi,
    In Exchange 2013, the Managed Folder Assistant is a throttle-based assistant.
    Throttle-based assistants are always running and don't need to be scheduled. The system resources they can consume are throttled. You can configure the Managed Folder Assistant to process all mailboxes on a Mailbox server within a certain period (known as
    a work cycle).
    You can use the following command to check work cycle.
    Get-MailboxServer –Identity ExServer | Format-List *WorkCycle*
    If you want to force the policy to take effect immediately, you can use the Start-ManagedFolderAssistant cmdlet.
    Here is an article for your reference, this article also applies to Exchange online.
    http://technet.microsoft.com/en-GB/library/dd297955(v=exchg.150).aspx
    Best regards,
    <o:p></o:p>
    Belinda Ma
    TechNet Community Support

  • Purpose of Retention Policy Recovery Window and Redundancy

    Hi,
    Good Evening,
    I have some queries regarding the RMAN Retention Policy Recovery Window and Redundancy.
    1. Any condition is there to set the Retention Policy Recovery Window and Redundancy and control_file_record_keep_time?What is the relationship between these 3 parameters?
    2. Explain the scenario if i set the control_file_record_keep_time=4 Redundancy=3 and Recovery Window=7?
    3. If i set the Redundancy=3 and Recovery Window=7 means my backup place only have 3 copies of backup based on the redundancy then what is the purpose of Recovery Window=7 please give some example.
    4. If i change the values for Recovery Window=3 and Redundancy=7 what will happened, how many days backup will be available in my FRA location?Explain with one scenario?
    Thanks in advance.
    Vijay.

    Hi,
    Take a look of the above doc contents:
    Configuring the Backup Retention Policy
    As explained in "Backup Retention Policies", the backup retention policy specifies which backups must be retained to meet your data recovery requirements. This policy can be based on a recovery window or redundancy. Use the CONFIGURE RETENTION POLICY command to specify the retention policy.
    so  you have option to choose either  recovery windows or redundancy based you can set the configuration like
    read in the Doc What it said for both:
    Recovery Window-Based Retention Policy ==>RMAN does not consider any full or level 0 incremental backup as obsolete if it falls within the recovery window.  Additionally, RMAN retains all archived logs and level 1 incremental backups that are needed to recover to a random point within the window.
    Redundancy-Based Retention Policy==>The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many full or level 0 backups of each datafile and control file that RMAN should keep. If the number of full or level 0 backups for a specific datafile or control file exceeds the REDUNDANCY setting, then RMAN considers the extra backups as obsolete. The default retention policy is REDUNDANCY 1.
    RMAN> show RETENTION POLICY;
    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name DDTEST are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    new RMAN configuration parameters are successfully stored
    RMAN> show RETENTION POLICY;
    RMAN configuration parameters for database with db_unique_name DDTEST are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters are successfully stored
    RMAN> show RETENTION POLICY;
    RMAN configuration parameters for database with db_unique_name DDTEST are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONTROL_FILE_RECORD_KEEP_TIME:This parameter applies only to records in the control file that are circularly reusable (such as archive log records and various backup records) ref Doc:CONTROL_FILE_RECORD_KEEP_TIME
    1. Any condition is there to set the Retention Policy Recovery Window and Redundancy and control_file_record_keep_time?What is the relationship between these 3 parameters?
    2. Explain the scenario if i set the control_file_record_keep_time=4 Redundancy=3 and Recovery Window=7?
    3. If i set the Redundancy=3 and Recovery Window=7 means my backup place only have 3 copies of backup based on the redundancy then what is the purpose of Recovery Window=7 please give some example.
    4. If i change the values for Recovery Window=3 and Redundancy=7 what will happened, how many days backup will be available in my FRA location?Explain with one scenario?
    so i believe you can get the Answer from Your Question from Above details.
    HTH

  • RETENTION POLICY TO REDUNDANCY value

    Hi,
    in 10g R2 on Win 2003,
    we do an incremental rman backup every night excepte sunday and every sunday a full rman backup. We want to be able to restore from last 3 weeks (I mean from 21 days before, if today is 25 of feb, to be able to restore/recover from 4 of Feb). Then what should be the value of RETENTION POLICY TO REDUNDANCY of RMAN catalog ?
    Many thanks.

    thank you . How about this :
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/setup005.htm#sthref261
    3.5.5.1 Configuring a Recovery Window-Based Retention Policy
    The RECOVERY WINDOW parameter of the CONFIGURE command specifies the number of days between the current time and the earliest point of recoverability. RMAN does not consider any full or level 0 incremental backup as obsolete if it falls within the recovery window. Additionally, RMAN retains all archived logs and level 1 incremental backups that are needed to recover to a random point within the window.
    Run the CONFIGURE RETENTION POLICY command at the RMAN prompt. This example ensures that you can recover the database to any point within the last week:
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    RMAN does not automatically delete backups rendered obsolete by the recovery window. Instead, RMAN shows them as OBSOLETE in the REPORT OBSOLETE output and in the OBSOLETE column of V$BACKUP_FILES. RMAN deletes obsolete files if you run the DELETE OBSOLETE command.
    3.5.5.2 Configuring a Redundancy-Based Retention Policy
    The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many backups of each datafile and control file that RMAN should keep. In other words, if the number of backups for a specific datafile or control file exceeds the REDUNDANCY setting, then RMAN considers the extra backups as obsolete. The default retention policy is REDUNDANCY=1.
    As you produce more backups, RMAN keeps track of which ones to retain and which are obsolete. RMAN retains all archived logs and incremental backups that are needed to recover the nonobsolete backups.
    Assume that you make a backup of datafile 7 on Monday, Tuesday, Wednesday, and Thursday. You now have four backups of the datafile. If REDUNDANCY is 2, then the Monday and Tuesday backups are obsolete. If you make another backup on Friday, then the Wednesday backup becomes obsolete.
    Run the CONFIGURE RETENTION POLICY command at the RMAN prompt, as in the following example:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    3.5.5.3 Showing the Current Retention Policy
    RMAN> SHOW RETENTION POLICY;
    see V$RMAN_CONFIGURATION

  • Performance Issue when turning on Retention Policy

    Hello,
    I am currently in the process of enabling retention policy for my organization. We have 18,000+ mailboxes. How much of a performance impact (if any) will it be to the end users if we were to enable retention polices for so many mailboxes at once?
    We have not had retentions enabled for about 3 years and the goals to basically delete/purge anything over 15 months. I tried doing some research on this and can't seem to find any topics pertaining to this particular question.
    Thanks,
    Emmanuel
    Emmanuel Fumero Exchange Administrator

    The user impact of enabling retention on this many mailboxes at once is not your primary issue - your primary issue will be how long it will take to complete the process on all of your mailboxes so it can "just keep up" from that point onward. 
    I'll give you some information about our own results and let you decide how you wish to implement retention for your users.
    We have 14,000+ mailboxes running on Exchange 2010, fully updated.  We migrated three years ago from "another messaging platform" well known for allowing users to have huge mailboxes with little or no capability to restrict how large the
    mailboxes grew - and they grew.  When I started here, our average mailbox size had just popped over 2GB, and our corporate target mailbox size limit was 2GB.  We had mailboxes over 30GB, and messages older than 10 years (our corporate retention policy
    states no emails older than 7 years is allowed).  We were tasked with implementing retention across the board, with the following settings:
    Daily emails will be kept only for 60 days, and can be recovered (if necessary) for another 60 days
    Working emails (things needed for projects, etc) can be kept for 2 years, and can be recovered (if necessary) for another 60 days
    Messages required for legal reasons can be kept for up to 7 years, and can't be recovered if they are deleted
    Messages saved for legal reasons do not count against the 2 GB mailbox size limit
    Due to my previous experience implementing retention (when I was a consultant focused on Microsoft Exchange), I knew that deploying to all users at once would cause a hit on our servers (your current fear, and well founded), but I had only deployed to smaller
    organizations, and never in so radical a manner - previously, size limits had been in effect, so retention was just to "maintain the status quo", rather than to hack huge amounts of stale data from the system.  However, we did have huge servers
    (72 GB RAM and 24CPUs, but multirole) that, early on, were not highly taxed (under 15% CPU average during the peak timeframe, and we are in only two time-zones, so all 13,000 users will connect during the 7:00-10:30 Eastern timeframe).  So we determined
    that we would ramp retention across the organization in the same manner that we migrated - each 1000 users would get retention enabled weekly in a phased manner.
    When we started our first group, the IT group (naturally), most users kept their mailboxes relatively small - only 1.8 GB average - so retention ran from Thursday (the day we kicked off the implementation) through the weekend.  However, as each subsequent
    group was placed into retention, we found that the retention task was taking longer and longer.  Toward the end, we had to slip some of our retention groups a day or so because retention for the previous mailboxes hadn't completed.  We attribute
    this to two factors - 1) the mailboxes were larger on average, and B) there were also more and more mailboxes in retention already that also had to be handled.
    In the end, we took 22 weeks to fully implement retention across the organization, and the process took another two weeks to get to the point that is was "running the status quo", rather than yanking huge volumes of stale email out of mailboxes. 
    During implementation, our servers' performance numbers were good - still under 30% CPU - and users weren't complaining about poor performance due to that (cached mode is a godsend), but getting the process to complete was our sticking point.  If
    you turn on retention for all 18,000 of your mailboxes at once, you will see some server performance degradation (especially if your servers aren't as beefy as ours), but the process may never have a chance to complete across the board.  Our 22 weeks
    may well take over a year for your mailboxes.
    HTH - you are going to need all the help you can get.  (-;

  • Retention Policy to delete both backup sets and archivelogs automatically

    I configured the Recovery Window-Based Retention Policy for my database for the window=14 days. I also set up a crontab to do a full backup every Monday. So say in a month, there will be 30 archive logs and 4 full DB backup sets.
    Now that I understand if the FRA gets filled up, older archive logs that are not needed for the 14 days recoverable window will be automatically deleted. My questions is what happen to the old backup sets? Will they get deleted automatically too if there is no space left in FRA? Or I need to use "DELETE OBSOLETE" to delete them?
    Thanks.

    One of the advantages of the FRA is, in case of space pressure obsolete objects (obsolete due to the defined retention policy) are deleted automatically. That's true for backups and archivelogs. The objects are NOT deleted automatically after the retention policy expires, but only when additional space is needed. That does not mean you don't have to care about FRA space consumption. You may have unusual amounts of archivelogs, additional backups and flashback logs (if flashback database is configured), which fill up the FRA.
    Werner

  • Archiving and different Retention period by  specific interface

    We want to specify different Retention period for different interfaces (audit reasons)... and based on search in SDN, it does not seem like this is  supported by SAP...
    Do any of you know if SAP intends to support this in future? Any ideas for overcoming this gap? or is this limitation deliberate (and has been kept in place for a reason)?

    Hi Krish,
    Actually I don't think we have this option of setting the retention period for specific interfaces,
    but for the global interfaces in the system.
    If you want to increase the time for Audit Log messages you need to change parameter 'messaging.auditLog.memoryCache' to false in order to persist the audit logs in PI 7.1 system. Take a look at note #1314974 for more details.
    And notice that after changing the parameter to false, audit logs are persisted till the corresponding messages are deleted. The default retention period of messages on AE is 30 days, keep in mind that it could have a little impact on the data volume.
    To increase the retention time in AFW, go to:
    Services -> XPI Adapter: XI:
    "xiadapter.outbound.persistDuration.default"
    "xiadapter.inbound.persistDuration.default"
    For the Integration Engine, it's under SXMB_ADM -> Integration Engine Configuration and Configuration.
    Regards,
    Caio Cagnani

  • Enforcing Retention Policy

    I have been asked by the head of the organization to enforce a 30 day retention policy for ALL emails in everyone's Outlook (Exchange 2010) - Inbox, Sent, Deleted, etc. (he deletes EVERY message as soon as he read it).    So I went into the EMC
    and following posted instructions, set and applied the policy.    Only NO emails are ever deleted in anyone's Outlook (except of course his, since he continues to manually delete everything).
    Need some help in figuring out WHY the policy is not working.   Thanks.
    Bill

    I guess I'm just going to have to start the process all over from the beginning - and hope it "takes" this time.  Yes, I did create the tags, etc with 30 days age limit and completely delete when reached - users were told to copy
    anything they wanted to keep to offline archive folders which are backed up.    Thanks - I'm just going to start from the top and see what happens.
    Well, it's months later - this wasn't a priority - and I did go back and following all the documentation, created the tags with 30 day delete for Inbox, Sent, Deleted, Junk; set a policy, included the addresses of all users; double checked that it was applied
    to all users.     And now, 3 days later, there is still email over 30 day old (WAY over for some - as much as 7 years!) still in their Inbox, Sent, Deleted; Junk.
    Now the only issue I can see that possibly makes this not work is a "warning" that says "Personal Tags are a premium
    feature. Mailboxes with policies that contain these tags (or as a result of users adding the tags to their mailbox) require an Exchange Enterprise Client Access License."
    But I'm not using the built in "Personal Tags," I created my own.  I'm not trying to set a policy on Personal Folders,
    just the Inbox, Sent, etc (and any subfolders they might have). Do I need "Enterprise CALs" to make these retention policies work?    I thought such CALs were just paper licenses, nothing to install (this is a 2010 Standard Exchange Service)
    and every where I search on line there's nothing about installing CALs in Exchange, it just says they are "paper" in case of an audit.
    Yet in Exchange it says I'm missing both Standard and Enterprise CALs.
    All too too confusing to accomplish what should be a relatively straightforward task - deleting messages after a set period of
    time.
    Any help appreciated.
    Bill

  • Retention Policy Tag on Outlook 2010/Exchange 2010 SP3

    While I still wanted to have the Retention Policies and Tags applied to mailboxes, would I just be able to "HIDE" or "SUPPRESS" the Tip that the Outlook 2010 client shows on the read-pane like...
    Retention Policy: xx Days Retention Inbox (xx days) Expires x/x/xxxx  ??
    Please suggest
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. Regards, Siva

    Hi,
    When a retention policy is applied to an item in user's mailbox, the retention policy for a message appears in the header in the Reading Pane under the recipient names and includes the expiration date. If no retention policy is applied, no information appears
    under the message recipient names.
    Based on my knowledge, I'm afraid there is no way to hide it in the Reading Pane.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

Maybe you are looking for

  • How can I embed a HTML document onto my webpage?

    What I am trying to do: I am trying to make an image that has links to urls from different parts of the image. What I have done so far: I have built a photoshop image to embed on my webpage, following the instructions offered by many online forums, b

  • Inspire 5.1 5700 digital

    IS IT POSSIBLE TO RUN MY TV /DVD ETC THROUGH THE SYSTEM AND HOW DO I CONNECT? THANX JOHN

  • KDE sounds are much too loud

    After doing a system update a few weeks ago, all of a sudden, no matter what the master volume currently is set to, KDE blares the notification noises at 100%. It is quite a bother. I have tried fiddling with the sound channel levels in alsamixer, bu

  • Why does mail quit unexpectedly when I type fast?

    After installing Lion, the Apple Mail program quits unexpectedly when I am typing fast. I type at least 90 wpm. this happens two or more times per day.

  • How to move statistical postings from one cost center to another

    Hi All, We have some statistical postings done to an incorrect cost center. Now we want to move them to the correct cost center. I know there is some way of doing it by making debit and credit entries to the G/L account in FI where the postings intia