RMAN Retention Policies

We are looking for two retention policies for our backups. 30 days retention for all backups on TAPE and 7 days retention on all backups on DISK. If we set retention policy to 30, disk couldn't accommodate all backups on disk at the same time, we need backups on tape for at least 30 days.
Any ideas?

You would have some block of code in your script to delete obsolete backups... replace that with two commands (one global and one for disk). You would still have retention policy for 30 days
RMAN TARGET /
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;
ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE SBT;
DELETE FORCE NOPROMPT OBSOLETE;
DELETE FORCE NOPROMPT OBSOLETE RECOVERY WINDOW OF 7 DAYS DEVICE TYPE DISK;

Similar Messages

NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES

제품 : RMAN
작성날짜 : 2004-05-20
NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES
=======================================================
오라클 9i RMAN 에서는 백업을 보다 효율적으로 할 수 있는 기능을 보강 했다.
지금 소개할 "Retention Policies" 기능을 통해서 보다 효율적인 RMAN 백업
전략을 세울 수 있다.
1. 백업 화일 최적화 방법 (Backup File Optimization)
백업 화일 최적화란 백업에 소요되는 공간을 최소화 하는 전략이다. RMAN
백업시에 같은 정보 (dbid, checkpoint, and resetlogs data 등등) 를 가지고 있는
화일이 이미 존재하는 백업 셋 내부에 있는지 체크하게 된다. 만일 같은 화일이
이미 백업 되어 있다면 BACK UP 명령은 해당 화일에 대해서는 백업을 하지 않게
된다.
이때 같은 화일이라고 판단하는 기준은 다음과 같다.
* Datafile: 같은 DBID, checkpoint SCN, resetlogs SCN 과 time. 데이타 화일은
반드시정상적으로 offline 되었거나, read-only 이거나, 또는 정상적 으로 close
되어야 함.
* Archived redo log: 같은 thread, sequence number, 그리고 같은 Resetlogs
SCN 과 time.
* Backup Set: 같은 Backup Set recid 와 stamp.
RMAN 이 백업을 수행하다가 위와 같은 조건의 화일이 이미 존재함을 확인하면
이것은 건너뛰게 될 화일의 대상이다. 하지만 이때 바로 Skip 을 결정하지 않고
정해진 Retention Policies 를 조사 한후에 Skip 여부를 결정 하게 된다.
만일 백업 명령에 DELETE INPUT option 이 사용되면 RMAN 은 백업이 Skip
되어도 화일을 지우게 된다.
RMAN 은 모든 화일에 대한 백업이 Skip 되어도 에러메시지나 경고를 보내지
않는다.
그러나 만일 데이터 화일에 대한 백업이 recovery policy window 보다 오래
된 것 이면 RMAN 은 새로운 백업 화일을 만들기 위해서 화일을 백업 하게 된다.
Note:
자체적인 expirations policy 를 가지고 있는 media manager 를 사용할 경우에는
이런 백업 최적화 정책을 사용하는 것에 신중을 기해야 한다.
백업 최적화 를 사용하기 위해서는 CONFIGURE 명령을 사용한다. CONFIGURE
명령은 명령 수행 이후에 이루어지는 모든 백업에 대해 적용이 된다.
예:
CONFIGURE BACKUP OPTIMIZATION ON; # default 는 OFF
2. Backup Optimization에 Retention Policies 적용 하기
Retention Policy 로 백업 최적화를 조절 할 수 있다. 그러나 retention policy를
사용하지 않기 위해서는 'CONFIGURE RETENTION POLICY TO NONE' 을
이용해서 명시적으로 retention policy를 사용하지 않는다고 해야 한다. 디폴트로
REDUNDANCY = 1 이 적용 된다.
a. Recovery Window 를 이용한 Backup Optimization
만일 백업 최적화가 enable 되어 있고 Recovery Window 가 retention policy
적용을 위해서 셋업 되어 있으면 RMAN 은 항상 가장 최근의 백업이 Recovery
Window 보다 오래된 데이터 화일을 백업한다.
예를 들면 다음과 같은 조건에서
o Today is February 21.
o The recovery window is 7 days.
o The most recent backup of tablespace tbs2 to tape is January 3.
o Tablespace tbs2 is read-only.
2월 21일에 tbs2 테이블 스페이스를 테이프로 백업을 하라는 명령을 내리면,
RMAN 은 이 화일이 1월3일 이후에 변경 사항이 없는데도 불구 하고 백업을 하게
된다. 이로써 RMAN 은 최근 7일 동안에 최소한 한번의 백업이 있어야 된다는
조건을 지키게 된다.
이러한 작동 방식은 media manager 가 오래된 테잎을 제거 해도 되도록 한다.
그렇지 않다면, media manager 는 1월 3일의 백업을 무한정 가지고 있게 된다.
2월 21일에 tbs2 테이블 스페이스의 보다 최근의 백업을 만듦으로 써, RMAN 은
media manager 가 1월 3일에 백업 했던 테입을 지워도 되도록 한다.
b. Redundancy 를 이용한 Backup Optimization
Retention policy 로 Redundancy 를 채택 한 경우에 RMAN 은 Redundancy
에 1을 더한 갯수를 초과하는 오프라인 또는 읽기 전용 화일의 백업을 건너뛴다.
이때 'CONFIGURE RETENTION POLICY TO REDUNDANCY n' 명령어로
Redundancy의 갯수를 정한다.
아래와 같은 백업 최적화 명령을 내린 경우를 예로 든다:
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
아카이브 테이블스페이스를 한번도 백업을 받은적이 없고 다음의 작업을 1주일
동안 한다고 하자.
Day Action Result Redundant Backup
Monday Take tablespace archive offline clean.
Tuesday Run BACKUP DATABASE. The archive tablespace is backed up.
Wednesday Run BACKUP DATABASE. The archive tablespace is backed up.
Thursday Run BACKUP DATABASE. The archive tablespace is backed up. Tuesday backup.
Friday Run BACKUP DATABASE. n/a Tuesday backup.
Saturday Run BACKUP DATABASE. n/a Tuesday backup.
Sunday Run DELETE OBSOLETE. The Tuesday backup is deleted.
Monday Run BACKUP DATABASE. The archive tablespace is backed up. Wednesday backup.
화요일, 수요일, 그리고 목요일의 백업은 아카이브 테이블 스페이스를 복사 해서
3개의 백업이 반드시 존재 해야 한다는 조건을 충촉 시킨다. (1+Redundancy)
금요일과 토요일에는 백업 최적화 조건에 의해서 아카이브 테이블 스페이스를
복사하지 않게 된다.
RMAN 은 일요일에는 유효기간이 지난 백업 화일을 지우게 된다. 따라서 화요일에
만든 백업은 삭제 된다. 월요일의 전체 백업은 3개의 백업이 존재 해야 한다는 조건
때문에 아카이브 테이블 스페이스를 또 다시 백업하게 된다. 이런 방식으로 백업
사이클이 진행 된다.
3. RETENTION POLICY NONE vs. DEFAULT
주의 사항:
'CONFIGURE RETENTION POLICY TO NONE' 과 'CONFIGURE RETENTION
POLICY TO DEFAULT' 는 그 의미가 같지 않다. 전자는 RETENTION POLICY
자체가 존재 하지 않는다는 의미 이며 백업은 expire 되지 않으며 'DELETE
OBSOLETE' 명령은 사용 할 수 없게 된다. 후자는 디폴트 RETENTION POLICY
(REDUNDANCY 1) 를 사용하게 된다는 의미 이다.
'DELETE OBSOLETE' 명령은 RETENTION POLICY 기준으로 expire 된 백업을
제거 하라는 명령이다.
보다 자세한 내용은 Oracle9i Recovery Manager User's Guide and
Reference의 Backup Optimization 부분을 참고 하시기 바랍니다.
--------------THE END----------------------------------------------

Hi,
Backup optimisation = +- do not copy empty space.
So, when you issue your BACKUP statement, it backs up the datafile. dot. nothing more.
In order to achieve what you're testing, look into TFM for BACKUP INCREMENTAL LEVEL x .
Regards,
Yoann.

Different retention policies for RMAN

Hi@all,
on our DB Server with RHEL 6 and Oracle 11.2.0.3.0 we're creating the following backups with RMAN:
- every day at 11:00 pm Level 0 backup
- every day at 05:00 am, 11:00 am and 05:00 pm Level 1 backup
I've activated this retention policy:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
So every backup is obsolete after 7 days. We use the control file and no recovery catalog. We have to get so much backups in front of SLA's.
Now (in front of our physical disk space) i want to switch the retention policy to the following:
- Fullbackups (level 0)should be obsolete after 7 days
- incremental backups (level 1) should be obsolete after 2 days
- arch. redologs should be obsolete after 7 days (i like to use LogMiner and mostly i need the arch. redo logs from the last 7 days in our company)
Is it possible in RMAN to define different retention policies for the different types of backups?
Thanks for your help and regards,
David

David_Pasternak wrote:
Hi@all,
on our DB Server with RHEL 6 and Oracle 11.2.0.3.0 we're creating the following backups with RMAN:
- every day at 11:00 pm Level 0 backup
- every day at 05:00 am, 11:00 am and 05:00 pm Level 1 backup
I've activated this retention policy:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
So every backup is obsolete after 7 days. We use the control file and no recovery catalog. We have to get so much backups in front of SLA's.
Now (in front of our physical disk space) i want to switch the retention policy to the following:
- Fullbackups (level 0)should be obsolete after 7 days
- incremental backups (level 1) should be obsolete after 2 days
- arch. redologs should be obsolete after 7 days (i like to use LogMiner and mostly i need the arch. redo logs from the last 7 days in our company)
Is it possible in RMAN to define different retention policies for the different types of backups?
Thanks for your help and regards,
David
You misunderstand what retention policy is and how it works.
When you say 'retention policy 7 days' you are telling rman to keep everything -- all backups of all types -- that are necessary to recover to any point within the last 7 days. If you say 7 days, rman makes the decision on what he needs to recover, not you.
And note that all recovery begins with the most recent full backup prior to the requested point in time. So if you are taking a level 0 backup every seven days, with a 7 day retention, six days into the cycle, you will still need the level 0 backup from 13 days ago, so rman will not consider it obsolete.

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"

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

Help desk cannot assign retention policies to new mailboxes

I am running Exchange 2010 SP1. I would like to give my help desk the ability to create new mailboxes. When a new mailbox is created, we select the option to assign a Retention policy to it. I added the help desk members to the "Recipient
Management" group. They can now create new mailboxes but they get an access denied error when they select a retention policy to be assigned to it. As a member of the "Organization Management" group, I am able to assign retention policies to new
mailboxes.
With the RBAC editor, I created a custom management role group called "Mailbox Management" based on the "Recipient Management" group and added the "Retention Management" role to the group. I believe this will give them the permissions to apply retention
policies to new mailboxes but it also gives them the permissions to create/modify/delete retention policies themselves. I only want to give them the rights to add mailboxes to retention policies.
I assume I need to create a custom management role and assign this new role to my new management role group but can someone tell me the minimum role entries I need for my help desk to be able to assign rentention policies during the mailbox creation
wizard process?
Steve

Hi Steve,
Due to you post the issue in a wrong type, and we changed the type to give you a suggestion.
Please refer to below information:
http://technet.microsoft.com/en-us/library/dd638205.aspx
The permissions required to configure messaging policy and compliance vary depending on the procedure being performed or the cmdlet you want to run. For more information about messaging policy and compliance, see
Messaging Policy and Compliance, refer to above article you could find out what permissions you need to perform the procedure or run the cmdlet, then you coudl create a roleassignment
for the customized role group.
Regards!
Gavin
TechNet Community Support

How to use retentions policies in OWA

Please don't use acronyms without defining them first
I am trying to setup retention policies for my boss's email. He uses Outlook 2013 on his laptop. Am I correct in thinking that if I set up retention policies through his microsoft 365 Outlook Web App, the retention policies will be applied to Outlook
2013 client on his laptop? He does have exchange.
As I understand it, retention policies cannot be applied to default folders (Inbox, sent items, deleted items, and junk mail). Retention policies can only be applied to created custom folders. Is this true?
Are Deleted items and Junk Mail retained for a certain period and then deleted by default? If so, what is the default retention period? Can it be changed?
Does Office 365 back up emails? If so, how long does it retain emails? Can it be changed?
I did setup a Test folder with a retention policy that was a week long. A week later I check on an email I placed in the Test folder and the email said it had 0 days until expiration. I checked the Test folder again a week later and it was deleted.
Is the Test email recoverable? I would prefer that it is not. I did some research and found that the Managed Folder Assistant needs to run before expired items are deleted. How do I get Managed Folder Assistant to run every night? I don't know how to use Powershell
and only have access to OWA.
I need to figure this out pretty soon. If you need more info. just ask.

Mr. Bomb Diggity
2. Policies are applied at the Mailbox Level. So if you apply a Retention Policy to his mailbox, it would indeed be "pushed" to his outlook.
3. Default Folders do have retention policies, however I believe the users can not change them. I will have to verify that. I do know that you can setup custom policies for other folders and the users can choose which policies they want on that folder.
4. Again you will have to find out which policy is applied to that mailbox and find out which retention tags are set for those folders.
5.
http://blogs.technet.com/b/uspartner_ts2team/archive/2011/12/16/office-365-backup-amp-recovery.aspx
http://community.office365.com/en-us/blogs/office_365_community_blog/archive/2011/09/28/how-does-exchange-online-back-up-my-data.aspx

Retention Policies without Recreation of mailboxes

Greetings,
i'm wondering if it's possible to create Retention Policy and with these tags:
Delete and Allow Recovery after 3 years
Move to archive after 1 year
without recreation of whole mailbox.
Because I've several Databases with around 200 Mailboxes.
Imagine how much bandwidth and time would it take to download new mailbox from server.
For example in three years one mailbox has around 3GB.
I tried applying this and it recreated all mailboxes, whole network went down because of download.
Thank you.

If I understood you correctly: it is possible to apply non-default retention policies to existing mailboxes,
http://technet.microsoft.com/en-us/library/dd298052(v=exchg.150).aspx
If I misunderstood you, please correct me. Hope it helps.
Robert Mandziarz | IT Administrator:
CodeTwo
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer
faster.

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 window doubt

Hello, i have RMAN backup in the way of backupsets on two node 11gR2 RAC on linux standard edition.
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name MGW are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_mgw2.f'; # default
RMAN>And now i dont understand why RMAN is not deleting backupsets that are older then 24 hours , although i have set
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS.
I have in my rman script that is executing every day @ 23:00 this:
backup as COMPRESSED BACKUPSET database FORMAT '/home/oracle/rman/%U' plus archivelog delete input;
delete noprompt obsolete;And now i see in my rman backup folder that there is backupset from yesterdey 23:00 ,and also from the day before yesterday 23:00.
[oracle@data02 rman]$ ls -l
total 51889864
-rw-r----- 1 oracle asmadmin 26454474752 Jul 14 00:19 0bmhcc1s_1_1
-rw-r----- 1 oracle asmadmin     1245184 Jul 14 00:19 0cmhcg84_1_1
-rw-r----- 1 oracle asmadmin 26626334720 Jul 15 00:18 0fmhf0ep_1_1
-rw-r----- 1 oracle asmadmin     1245184 Jul 15 00:18 0gmhf4ih_1_1
-rw-r--r-- 1 oracle oinstall           0 Jul 14 16:52 aa_1_1I thoght that if i have run my rman script today @ 23:00 , than that will do backup but also delete backup from the day before because i have set
retention to 1 day .
Can you please say why i am wrong in this ?

The RMAN retention policy doesn't just keep the amount of days specified. It calculates the interval from the end of the current time and extends back in time for the number of days specifed.
So for example if you set the backup retention policy to 1 day today. Then RMAN will keep the backups for 15th July, 16th July.
Then on the 17th July, the 15th July backup will be obsolete.
I.e.
Current date   Status                                 Recovery Point
15th July        available                               15-1 = 14th July
16th July        available                               16-1 = 15th July
17th July        backup of 15th July obsolete 17-1 = 16th July
So your backup for today wouldn't be marked as obsolete until the 17th July.
5 Configuring the RMAN Environment
However, if you have a fixed-date database then you should be setting the retention policy to redundancy instead of recovery window.
RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

Archived video retention policies

Wondering if anyone has good links to video archive retention policies.
We are probably going to institute some sort of retention policies in the near future.
We will be keeping orginal tapes, and archiving the straight captures of the tapes.
We obviously will also store the fcp projects.
Also, we will be archiving the finished products.
Looking for others' policies so we can see what other edu's and coms are setting as rules for how long stuff is stored in each format.
thanks

I keep the tapes.
The FCP project files, stills, created graphics, project files and assets from applications like Motion and AE, music and sound effects...those I burn to DVD and archive. I also export a self contained movie of the final show...texted and textless and archive those to hard drive...and keep copies of the final output tapes.
I never back up the captured footage that I have the tapes for. I either keep the tapes, or if required by the network, send the tapes back to them....since they own them. If they want the project revisited and rebuilt, they need to send them back.
Shane

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

Custom Retention policies for default folders in Outlook

Hello,
The following are the steps I've taken to create a retention policy for a user.Exchange 2013, outlook 2013
The problem is that even if I create a retention tag for a default folder, I cannot implement it. I've gotten retention tags for user created folders to work, but not the default folders.
Login to microsoft 365 as exchange Administrator
Click Admin > Exchange
Click ‘Compliance Management’ on left side
Click ‘Retention Tags’
Create desired retention tag by folder (choose default folder or user created folder)
Save each tag as it is created
Click ‘Retention Policies’
Click ‘New’ to create a new policy
Add desired tags to policy and click save
To apply Retention Policy click ‘Recipients’ on left side
Click ‘mail boxes’
12.
Select user and click edit > mailbox features
13.
Select desired retention policy
14.
Save
Using this method I created a retention tag to delete mail in the junk mail folder after 14 days. I added the 14 day junk mail retention tag to a retention policy and applied
it to a user. But whenever I look at the junk mail folder it shows that the email will be deleted in 30 days --- not 14.
What am I doing wrong?

Hi,
We can try to use managed folders to specify retention settings for default folders such as Inbox, Deleted Items, and Sent Items. See:
http://technet.microsoft.com/en-us/library/ee364744(v=exchg.141).aspx
Also check this:
http://blogs.technet.com/b/theexchangeguy/archive/2012/06/04/retention-polices-and-tags-101.aspx
Since this question is more related to Exchange server, it's better to post your question to Exchange forum:
http://social.technet.microsoft.com/Forums/en-US/category/exchangeserver/
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents,
and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.
Thank you for your understanding.
Best Regards,
Steve Fan
TechNet Community Support

Retention policies not working

We are in the progress of migrating from Exchange 2007 to 2010, and I can't seem to get retention policies working in 2010. I want to delete everything in a mailbox at 180 days old. I have set a simple Retention tag via the EMC for "all other
folders in the mailbox" with an Action of "Permanently Delete". I have assigned this tag to a retention policy via the EMC, and then assigned mailboxes to the policy via the EMC. I then run Start-ManagedFolderAssistant -identity
"Last, First" from the command shell.
The process does not seem to delete items over 180 days. What am I doing wrong?

Hi,
Please check whether there is the Event ID 9017 and 9018, make sure the MRM works well.
And please restart the Microsoft Exchange Mailbox Assistants service to check the result.
If possible, please create a new test user and apply retention policy to this user to check the result.
If the issue persists, I recommend you increase the diagnostic logging level for the MRM, and then monitor the events in the application log to check if there is related events.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 CU3 - Problem with Retention Policies

Hello, I configured a retention policy for mailbox and assigned it to the mailbox iwth the set-mailbox cmdled. I issued the Start-ManagedFolderAssitant [mailbox] to force the immediate processing for the mailbox but the maibox items are not moved.
The ManagedFolderWorkCycle is set to 1 day so i waited 24 hours but no effect.
I also noticed that connecting through OWA the tab Retention Policies does not appear.
Am i missing something? Hope someione could help.
Thnaks

Hi, and thank you for your help. No I did not set the personal tag in the retention policy.
Now I added a personal tag but still i can't see the tags available in the right-click menu. The starnge thing is i see the default MRM policy tags instead. I found Event ID 9017 and 9018 but no errors are reported.
Best regards,
Raffaele
Hi,
Did you have a personal tag in this retention policy and assign it to the mailbox?
Only when you add a personal tag to retention policy and apply to user mailbox, you can see the Retention Policy option by right-clicking the message items in OWA.
For this issue, I recommend you check whether there is the Event ID 9017 and 9018 in the application log, make sure the MRM works well.
And please check if you can see the retention policy description in the Reading Pane when you click on the message items.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

RMAN Retention Policies

Similar Messages

Maybe you are looking for