Query on RMAN Retention Policy

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

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

Similar Messages

  • RMAN Retention Policy - redundancy vs recovery window

    Hi All,
    I'm wondering what the most commonly used rman retention policy is, to provide point-in-time recovery. We have 2 oracle servers, one using redundancy policy (3) and the other using recovery window (2 days). I would like to standardize them but am not confident in which direction I should go in.
    I'm tempted to lean towards redundancy but wanted to pose the question to a wider, experienced audience for any things to think about/watch out for. Also, I assume the restore process would the same for either.
    Thanks in advance.

    Redundancy based retention policy means how many backups of each datafile must be retained and Recovery windows based retention policy is a period of time which starts with current time and goes backward in time upto the point of recoverability.
    Oracle suggests and its Best practice is "Recovery Window" .( I don't know the reason though)
    Two things you need to consider:
    1) You might need more space in case of "recovery window" because it depends upon the schedule of the backup. In "redundancy" , your space consumption will be same.
    2) You need to keep "recovery window" time less than the value of "control_file_Record_keep_time" so your backup records won't be overwritten in controlfile.
    We use "Recovery Window"

  • RMAN retention policy

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

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

  • RMAN -Retention policy doubt

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

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

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

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

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

  • RMAN retention policy - backup spfile and then redundancy = 5 removes it.

    I have a database that is Oracle Standard Edition and it is version 9.2.0.6.
    The spfile has not changed since November, 2005. A list backup does not show an spfile backup with a tag of "hot_database_spfile_backup_full". I took a close look at the RMAN script log and was shocked to discover that the spfile backup from the current day is being deleted. Is that because of the redundancy = 5? I'm trying to figure out why a backup piece from the current day is being deleted?
    Examples follow.
    The script deletes obsolete with redundancy = 5, however, I believe the intent was to keep 25 days because one of the configure clauses is set to a recovery window of 25 days. I realize that the redundancy overrides the configure retention policy command. I can fix the script and remove the redundancy = 5.
    In the RMAN run statement, I first resync the catalog, backup the spfile, a full backup of the database including current controlfile plus archive log (delete input), resync catalog, switch logfile, and backup any additional archive logs. The backup looks fine.
    Then, I allocate a channel for maintenance type sbt. The script then has a "delete noprompt expired backup;" a "delete noprompt obsolete redundancy = 5;" and finally, a crosscheck;
    example of backup piece that is later deleted:
    Starting backup at 07/18/2006 20:00:14
    channel t1: starting full datafile backupset
    channel t1: specifying datafile(s) in backupset
    including current SPFILE in backupset
    channel t1: starting piece 1 at 07/18/2006 20:00:14
    channel t1: finished piece 1 at 07/18/2006 20:00:15
    piece handle=P*****_2338_1_596145614_FULL comment=API Version 2.0,MMS Version 5.2.0.0
    channel t1: backup set complete, elapsed time: 00:00:01
    Finished backup at 07/18/2006 20:00:15
    deletion:
    Deleting the following obsolete backups and copies:
    Type Key Completion Time Filename/Handle
    <other lines deleted>
    Backup Set 27453 07/18/2006 20:00:14
    Backup Piece 27454 07/18/2006 20:00:14
    P*****_2338_1_596145614_FULL
    deleted backup piece
    backup piece handle=P*****_2338_1_596145614_FULL recid=2039 stamp=596145614
    Deleted 12 objects
    Why is a backup piece created on 7/18 being deleted in the maintenance step?
    Thanks in advance!

    In the next step in the script, the controlfile and spfile are backed up:
    backup
    full
    skip inaccessible
    tag hot_database_backup_full
    format '%d_%s_%p_%t_FULL'
    (Database
    include current controlfile)
    Plus Archivelog delete input;
    Even though my backup script is redundant by backing up the spfile twice, when I list the backup of the spfile, I would have expected to find 5 backups with a tag of hot_database_spfile_backup_full and 5 with a tag of hot_database_backup_full. That is not the case. I only find spfiles with a tag of hot_database_backup_full. i am still perplexed by RMAN.
    I will modify my script - remove the backup of the spfile, and crosscheck before the delete commands. I will also remove the redundancy = 5. The intent is to keep 25 days of backups.
    Thanks for your comments

  • RMAN RETENTION POLICY configuration.

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

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

  • RMAN Retention Policy Dilemma

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

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

  • Rman Retention policy to recovery window

    Hi,
    I have few basic doubts in RMAN backup policy
    1 . Is that possible to set Retention policy to recovery window in minutes??
    2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
    Regards,
    007

    1) Syntax is .... TO RECOVERY WINDOW OF integer DAYS ... no other time statement.
    2) Backups become obsolete when no longer needed to fulfil a retention policy. In a (theoretical) scenario, you perform a level 0 backup and then only incremental backups, the starting level 0 backup must be kept for ever (even if it WOULD be possible to define a recovery window in minutes).
    Werner

  • Appropriate RMAN Retention Policy

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

    Thats nice you are moving the archivelogs to antoher partition ,i presume you had
    archivelogs at the same destination where database resides isnt?
    neednt to schedule turn the retetnion policy which match to yours own policy ,you just have to include delete obsolete within yours backup scripts and as i laredy given you link that
    "Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups. First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
    log backups that are older than the oldest datafile or control file backup that must be retained."
    run
    backup database;
    backup archivelog all;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    release channel;
    Please advise me, if my approach(logic) here is
    appropriate, or is there any other way of doing this
    more efficiently.it alls depend on yours SLA
    i would rather suggest you move yours alls FRA area to another drive which is seperate from yours database residence.
    Khurram

  • RMAN RETENTION POLICY 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 ...

  • RMAN retention policy really long

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

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

  • Query For Retention Policy On All Folders

    I am looking for a way to query for the retention policy assigned to all user folders (per folder/per user). My client allows the user to set the folder retention policy per folder and would like to know how each user has that configured. This is for
    a 700 user environment. I know any CSV generated as output could have thousands of rows.
    thanks.
     

    You will have to use EWS for that. Here's an example (for 2013):
    $getRTResp=$exchangeService.GetUserRetentionPolicyTags()
    function GetTagName($tagGUID) {
    if (!$tagGUID) { return ($getRTResp.RetentionPolicyTags | ? {$_.Type -eq "All"}).DisplayName }
    foreach ($tag in $getRTResp.RetentionPolicyTags) {
    if ($tag.RetentionId -eq $tagGUID) { return $tag.DisplayName }
    $FpageSize =100
    $FOffset = 0
    $folderView = new-object Microsoft.Exchange.WebServices.Data.FolderView($FpageSize,$FOffset,[Microsoft.Exchange.WebServices.Data.OffsetBasePoint]::Beginning)
    $folderView.Traversal = [Microsoft.Exchange.WebServices.Data.FolderTraversal]::Deep
    $folderView.PropertySet = new-object Microsoft.Exchange.WebServices.Data.PropertySet(
    [Microsoft.Exchange.WebServices.Data.BasePropertySet]::IdOnly,
    [Microsoft.Exchange.WebServices.Data.FolderSchema]::DisplayName,
    [Microsoft.Exchange.WebServices.Data.FolderSchema]::ArchiveTag,
    [Microsoft.Exchange.WebServices.Data.FolderSchema]::PolicyTag,
    [Microsoft.Exchange.WebServices.Data.FolderSchema]::FolderClass);
    $oFindFolders = $exchangeService.FindFolders([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::MsgFolderRoot,$null,$folderView)
    foreach ($folder in $oFindFolders.Folders) {
    Write-host $folder.DisplayName "has Policy:" $(GetTagName $folder.ArchiveTag.RetentionId)
    Obviously, it needs some work, a loop for all 700 users, proper error handling, etc. But hopefully it illustrates the idea. For older versions, its a bit more work to get the Name of the tag, but you can also use Get-RetentionPolicyTag for that.
    Code adapted from:
    http://blogs.msdn.com/b/akashb/archive/2012/01/12/stamping-retention-policy-tag-on-items-using-ews-managed-api-1-1-from-powershell-exchange-2010-part-2.aspx
    http://blogs.msdn.com/b/mvpawardprogram/archive/2013/04/08/5-lesser-known-operations-in-exchange-web-services-on-exchange-2013.aspx

  • RMAN backups does not match its retention policy

    Hello,
    I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
    For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
    DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
    I have clear retention policy and set to 14 days again but does not seem to work.
    I would appreciate suggestion(s) regarding the strange issue.
    Thanks a lot.
    Best Regards

    John-MK wrote:
    Hello,
    I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
    For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
    DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
    I have clear retention policy and set to 14 days again but does not seem to work.
    I would appreciate suggestion(s) regarding the strange issue.
    Thanks a lot.
    Best Regards
    We would need to know what kind of backups and when they were taken.  Consider this scenario:
    retention policy of 7 days.
    Incremental level 0 backup taken on Sundays
    Incremental level 1 backups taken Mon through Sat.
    Let's say Oct 1 is a Sunday, so we take an inc-0 backup on Oct 1, and again on Oct 8.
    Now let's say we are at Oct 10.  Our 7 day retention policy dicatates that we be able to recover to any day back to Oct 3.
    The only way we can recover to Oct 3 is to begin with that inc-0 backup from Oct 1.
    All recovery begins with the last inc-0 backup prior to the point in time to be recovered.  In a normal, regularly cycling schedule of backups,  you will actually end up with backups 1 day short of being twice as old as your retention period.
    Let's take a more extreme example.  Same 7-day retention period, but after a single inc-0 backup, you don't take any more backups for 3 months.  That one single backup is still needed to enforce your recovery window, and so is not obsolete, despite the fact it is 3 months old and your recovery window is only 7 days.
    Also, you mention 'expired'.  In terms of oracle backups, 'expired' is not the same as 'obsolete'.
    "Obsolete" means 'no longer needed to enforce recovery policy'.
    "Expired" is a bit more complex.
    when a backup is taken, or an archivelog is written, a record of that is written to the repository.  when you do an rman 'crosscheck', those repository records are compared to reality -- to see if the recorded backup file or archivelog file actually exists.  Maybe someone used an OS command to delete them.  Any file found to have 'gone walkabout' have their repository records marked as 'expired'.  An rman 'delete expired' then removes those records from the repository.

  • Can i use the retention policy without using the Flash Recovery area?

    Yes ,lets see here
    RMAN>list backup summary
    C:\>dir *.bus
    Volume in drive C is khurram
    Volume Serial Number is F49D-FF2B
    Directory of C:\
    File Not Found
    C:\>dir *.arc
    Volume in drive C is khurram
    Volume Serial Number is F49D-FF2B
    Directory of C:\
    File Not Found
    RMAN> crosscheck backup
    2> ;
    using channel ORA_DISK_1
    RMAN> list backup summary
    2> ;
    RMAN> show retention policy
    2> ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    RMAN> run {
    2>   allocate channel ch0 type disk;
    3>   backup as compressed backupset database format
    4>   'c:\rman_%s_%d_%T.bus'
    5>   plus archivelog format 'c:\arch_%s_%d_%T.arc';
    6>   release channel ch0;
    7>   allocate channel ch1 device type disk format 'c:\arch_%s_%d_%T.arc';
    8>   release channel ch1;
    9>   delete force noprompt obsolete;
    10>   allocate channel ch2 device type disk format 'c:\rman_%s_%d_%T.bus';
    11>   release channel ch2;
    12>   delete force noprompt obsolete;
    13> }
    released channel: ORA_DISK_1
    allocated channel: ch0
    channel ch0: sid=146 devtype=DISK
    Starting backup at 15-APR-08
    current log archived
    channel ch0: starting compressed archive log backupset
    channel ch0: specifying archive log(s) in backup set
    input archive log thread=1 sequence=24 recid=79 stamp=652108461
    input archive log thread=1 sequence=25 recid=80 stamp=652112650
    channel ch0: starting piece 1 at 15-APR-08
    channel ch0: finished piece 1 at 15-APR-08
    piece handle=C:\ARCH_130_ORCL1_20080415.ARC comment=NONE
    channel ch0: backup set complete, elapsed time: 00:00:05
    Finished backup at 15-APR-08
    Starting backup at 15-APR-08
    channel ch0: starting compressed full datafile backupset
    channel ch0: specifying datafile(s) in backupset
    input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSTEM01.DB
    F
    input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSAUX01.DB
    F
    input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\USERS01.DBF
    input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\UNDOTBS01.D
    BF
    channel ch0: starting piece 1 at 15-APR-08
    channel ch0: finished piece 1 at 15-APR-08
    piece handle=C:\RMAN_131_ORCL1_20080415.BUS comment=NONE
    channel ch0: backup set complete, elapsed time: 00:00:45
    Finished backup at 15-APR-08
    Starting backup at 15-APR-08
    current log archived
    channel ch0: starting compressed archive log backupset
    channel ch0: specifying archive log(s) in backup set
    input archive log thread=1 sequence=26 recid=81 stamp=652112703
    channel ch0: starting piece 1 at 15-APR-08
    channel ch0: finished piece 1 at 15-APR-08
    piece handle=C:\ARCH_132_ORCL1_20080415.ARC comment=NONE
    channel ch0: backup set complete, elapsed time: 00:00:02
    Finished backup at 15-APR-08
    Starting Control File and SPFILE Autobackup at 15-APR-08
    piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\AUTOBACKUP\2008_
    04_15\O1_MF_S_652112718_408X3ZVJ_.BKP comment=NONE
    Finished Control File and SPFILE Autobackup at 15-APR-08
    released channel: ch0
    allocated channel: ch1
    channel ch1: sid=146 devtype=DISK
    released channel: ch1
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=146 devtype=DISK
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    Backup Set           128    15-APR-08
      Backup Piece       128    15-APR-08          C:\ARCH_130_ORCL1_20080415.ARC
    Archive Log          79     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_24_408RYXDF_.ARC
    Archive Log          80     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_25_408X1SCR_.ARC
    deleted backup piece
    backup piece handle=C:\ARCH_130_ORCL1_20080415.ARC recid=128 stamp=652112652
    deleted archive log
    archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\ARCHIVEL
    OG\2008_04_15\O1_MF_1_24_408RYXDF_.ARC recid=79 stamp=652108461
    deleted archive log
    archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\ARCHIVEL
    OG\2008_04_15\O1_MF_1_25_408X1SCR_.ARC recid=80 stamp=652112650
    Deleted 3 objects
    released channel: ORA_DISK_1
    allocated channel: ch2
    channel ch2: sid=146 devtype=DISK
    released channel: ch2
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=146 devtype=DISK
    no obsolete backups found
    RMAN>
    C:\>dir *.bus
    Volume in drive C is khurram
    Volume Serial Number is F49D-FF2B
    Directory of C:\
    04/15/2008  02:24 PM        96,813,056 RMAN_131_ORCL1_20080415.BUS
                   1 File(s)     96,813,056 bytes
                   0 Dir(s)  61,960,724,480 bytes free
    C:\>dir *.arc
    Volume in drive C is khurram
    Volume Serial Number is F49D-FF2B
    Directory of C:\
    04/15/2008  02:25 PM            56,832 ARCH_132_ORCL1_20080415.ARC
                   1 File(s)         56,832 bytes
                   0 Dir(s)  61,960,724,480 bytes free
    C:\>
    RMAN> run {
    2>   allocate channel ch0 type disk;
    3>   backup as compressed backupset database format
    4>   'c:\rman_%s_%d_%T.bus'
    5>   plus archivelog format 'c:\arch_%s_%d_%T.arc';
    6>   release channel ch0;
    7>  }
    released channel: ORA_DISK_1
    allocated channel: ch0
    channel ch0: sid=146 devtype=DISK
    Starting backup at 15-APR-08
    current log archived
    channel ch0: starting compressed archive log backupset
    channel ch0: specifying archive log(s) in backup set
    input archive log thread=1 sequence=26 recid=81 stamp=652112703
    input archive log thread=1 sequence=27 recid=82 stamp=652112873
    channel ch0: starting piece 1 at 15-APR-08
    channel ch0: finished piece 1 at 15-APR-08
    piece handle=C:\ARCH_134_ORCL1_20080415.ARC comment=NONE
    channel ch0: backup set complete, elapsed time: 00:00:02
    Finished backup at 15-APR-08
    Starting backup at 15-APR-08
    channel ch0: starting compressed full datafile backupset
    channel ch0: specifying datafile(s) in backupset
    input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSTEM01.DB
    F
    input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\SYSAUX01.DB
    F
    input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\USERS01.DBF
    input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL1\UNDOTBS01.D
    BF
    channel ch0: starting piece 1 at 15-APR-08
    channel ch0: finished piece 1 at 15-APR-08
    piece handle=C:\RMAN_135_ORCL1_20080415.BUS comment=NONE
    channel ch0: backup set complete, elapsed time: 00:00:45
    Finished backup at 15-APR-08
    Starting backup at 15-APR-08
    current log archived
    channel ch0: starting compressed archive log backupset
    channel ch0: specifying archive log(s) in backup set
    input archive log thread=1 sequence=28 recid=83 stamp=652112925
    channel ch0: starting piece 1 at 15-APR-08
    channel ch0: finished piece 1 at 15-APR-08
    piece handle=C:\ARCH_136_ORCL1_20080415.ARC comment=NONE
    channel ch0: backup set complete, elapsed time: 00:00:02
    Finished backup at 15-APR-08
    Starting Control File and SPFILE Autobackup at 15-APR-08
    piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL1\AUTOBACKUP\2008_
    04_15\O1_MF_S_652112928_408XBKCZ_.BKP comment=NONE
    Finished Control File and SPFILE Autobackup at 15-APR-08
    released channel: ch0
    RMAN> report obsolete
    2> ;
    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           129    15-APR-08
      Backup Piece       129    15-APR-08          C:\RMAN_131_ORCL1_20080415.BUS
    Backup Set           130    15-APR-08
      Backup Piece       130    15-APR-08          C:\ARCH_132_ORCL1_20080415.ARC
    Backup Set           131    15-APR-08
      Backup Piece       131    15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL1\AUTOBACKUP\2008_04_15\O1_MF_S_652112718_408X3ZVJ_.BKP
    Backup Set           132    15-APR-08
      Backup Piece       132    15-APR-08          C:\ARCH_134_ORCL1_20080415.ARC
    Archive Log          81     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_26_408X3HRP_.ARC
    Archive Log          82     15-APR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
    COVERY_AREA\ORCL1\ARCHIVELOG\2008_04_15\O1_MF_1_27_408X8RXN_.ARC
    RMAN>Note: i have archivelog which is at FRA ,it also apply there and as well yours own defined backupsets path.
    Yours comments are wellcome.
    http://oraware.blogspot.com/2008/04/can-i-use-retention-policy-without.htmlKhurram

    Hmmm, I can't see where the confusion originates. The table near the bottom of www.apple.com/timecapsule/specs.html has one row labelled "For backup using Time Machine" and another row labelled "For AirPort Disk with a USB hard drive".
    The requirement for backup via Time Machine is OS 10.5.1 or better. Time Machine is not supported in pre-Leopard (OS 10.5) nor in Windows.
    The requirement for using Time Capsule as a remote disk is identified as "Mac with Mac OS X v10.4.8 or later" or "PC with Windows XP (SP2) or Windows Vista; Bonjour for Windows (included on Time Capsule CD)".
    Doesn't that pretty much spell out that Time Capsule works as a network drive without the need for Time Machine?
    Also Joe (the OP) never indicated any desire to use it with Windows so I'm not sure why all the discussion about Windows compatibility. ??
    Also the quote posted by Henry seems pretty clear:
    "Time Capsule with Time Machine in Leopard is the ideal backup solution. But that doesn’t mean Tiger, Windows XP, and Windows Vista users can’t enjoy the benefits of Time Capsule, too. Because it mounts as a wireless hard drive, Tiger and Windows users simply access Time Capsule directly from the wireless network for exchanging and storing files quickly and easily."

Maybe you are looking for