Considerations for keeping RMAN Backup Retention to 1 Year

Dear All,
We are using 2-node 10gR2 RAC on Windows Server. We use Symentec Netbackup 7.5 for backing up Oracle databases. We want to change the retention period of RMAN backups to 1 year. Other than changing the RMAN Backup recovery window to 365, what are the other considerations (other configuration change, other point etc) we should be aware of?
Best regards,
Riaz

> Other than changing the RMAN Backup recovery window to 365, what are the other considerations (other configuration change, other point etc) we should be aware of?
Use RMAN Catalog.
How to restore your database if a storage failure occurs and all files on filesystem be lost and all rman files be at MML.
RMAN need a catalog to request files from MML (this catalog can be a controlfile, rman catalog or both), so if you lost your controlfile without RMAN Catalog you need manually find desired files on MML and restore it one by one if these files are not cataloged in that controlfile restored, since Oracle does not catalog files stored at MML. RMAN catalog files only stored on disk.

Similar Messages

E-business Suite RMAN backup retention

Hi,
i want to retain my backup for clone for 90 days. One parameter need to set at RMAN level is CONFIGURE RETENTION POLICY TO REDUNDANCY 90;
What other parameter need to set at DB level?
Thanks

i want to retain my backup for clone for 90 days. One parameter need to set at RMAN level is CONFIGURE RETENTION POLICY TO REDUNDANCY 90;
What other parameter need to set at DB level?Rman backup retention policy [ID 462978.1]
Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) [ID 360416.1]
RMAN : Consistent Backup, Restore and Recovery using RMAN [ID 162855.1]
Backup and Recovery
http://www.oracle.com/pls/db112/portal.portal_db?selected=4&frame=#backup_and_recovery
Thanks,
Hussein

Guidance for Implenting RMAN backup

I need to configure RMAN and Database parameters for implementing RMAN Incremental backups.
My strategy was to take a level 0 backup monthly once, cumulative level 1 backup and diff level 1 backup daily. I need to maintain 3 months backup.
What are all the parameters i should consider for doing this?
Retention policy to recovery window of 90 days.
control_file_record_keep_time 100 days
I am storing backups in a disk location apart from Flas recovery area.
plz advice...
TIA,

export is not a backup.Export is not a Physical backup but its a logical backup...:)
I agree sybrand it is recommended not to rely on Export because it is inconsistent...but it is still valid if an user acciedentaly drops the tables or objects..
Cheers
Maran

Best practice for RAC RMAN backup

I have a 10gR2 RAC db that is 3.5TB. It is a 2 node cluster on AIX. Each instance is db1 on node1, and db2 on node2, the "world" database name is db.
Currently we are doing our backup from 1 node of the cluster, specifying that it connect to to db2, so this instance is doing all of the backup work. We allocate 14 channels to back this database up to tape (yes, we have plenty of tape resources, connecting to a tape machine with > 20 physical tape drives). Would it be better to have our rman script connect to the general database db and let the listener decide which instance to send the channel allocation to, or keep all the work on one node.

I seem to remember that when I was reading up on RAC and RMAN a couple of years ago (maybe up to 4 years ago) that there was something about always doing backups from the same node in a RAC configuration i.e. you have logically 'db' in your network configuration and also direct names of 'db1' and 'db2', and you should always use one of 'db1' or 'db2' but never 'db'. And I also mean do not alternate between 'db1' and 'db2'. Pick one of them and always do your backups from that instance.
I think this was to do with things like the database identifier, and the instance identifier too, which RMAN reads and puts into the backup. It also affects things like reading the archive logs, which must be cross mounted to both nodes. I have this feeling that using the same node kept a kind of consistency within the backups, and meant that Oracle was getting all of the block images from one node i.e. from one of the SGAs. If you used both nodes simultaneously you could run into issues with their SGAs being out of sync. I know this does not make much sense, given that RAC is all about keeping the SGAs consistent with each other. But at the end of the day I do remember something about always using one node all the time to do your RMAN backups.
Not sure if these rules hold true if you are using ASM, which itself is shared in a RAC environment.
Things may have moved on since then, but that was still 10g Release 2 documentation, so I would guess it is still true. At the end of the day, it is not the backup that is important, but the recovery. You don't want to create any kind of inconsistent backup that RMAN cannot successfully recover, even though the backup may look good when you create it.
I'd check out the RMAN and RAC documentation further to see if this is supported.
John

Rman backup with different retention

Hi,
I have to write script on RMAN backup retentions and policies.
My requirement is as below:
Daily backup Name and retentions : db_daily_bkp_sun,db_daily_bkp_mon...with 7 days retension
Weekly backup Name and retentions : db_wkly_bkp_01,db_wkly_bkp_02...with 4 backup retension
Monthly backup Name and retentions : db_mnth_bkp_jan,db_mnth_bkp_feb...with 12 backups
Yearly backup Name and retentions : db_yearly_bkp_2010,db_yearly_bkp_2011,db_yearly_bkp_2012
All backups will be full online. We have to store backups in local disk.
We have created backup locations on disk as below.
Daily : /orabackup/daily
Weekly : /orabackup/weekly
Monthly: /orabackup/monthly
Yearly : /orabackup/yearly
So is it possible to take such backups in RMAN without using any third party software ? If possible then please provide me such script.
With Regards,
Khokhar Murtuja S
Database Administrator

Hi,
RMAN will make you have only one retention.
You can have more kind of retention using the option "keep until" in your backup command.
It'll certainly do what you need.
Greets,
Loïc

RMAN Backup keep forever

Hi all,
I want to keep Rman backup for forever.
But i dnt want to retian archive log .
Kindly suggest.
Regards

RMAN> BACKUP TAG Q107 DATABASE KEEP FOREVER;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "consistent, logs, nologs"
RMAN-01007: at line 1 column 38 file: standard input

RMAN Backup in RAC

Dear DBAs,
Is there a V$VIEW that maintains information about the node that was used for taking RMAN backup.
I have a 3 node RAC database, and would like to know which node db backup was run from? These are OEM scheduled backup jobs.
Thanks

Hi;
1. There is seeded RMAN forum site:
Forum Home » High Availability » RMAN
2. Please see:
LIST and REPORT Commands in RMAN [ID 114284.1]
http://docs.oracle.com/cd/B19306_01/backup.102/b14194/rcviews001.htm
PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
Regard
Helios

WHAT IS BEST STRATEGY FOR RMAN BACKUP CONFIGURATION

Hi all,
my database size is 50GB I want TAKe WEEKLY FULL BACKUP AND INCREMENTAL BACKUP
WITHOUT RECOVERY CATALOG.by follwing commands
weekly full database backup
run
backup as compressed backupset
incremental level=0
device type disk
tag "weekly_database"
format '/sw/weekly_database_%d_t%t_c%c_s%s_p%p'
database;
I want do CONFIGURE RMAN BY FOLLWING stragtegy
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 days.
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO
'\SW\AUTOCFILE_'%F';
and other is by default
sql>alter system set control_file_record_keep_time=15 days;
os--aix6 and for two database 10g2 and 11g2
what is best configuration strategy for rman backup.AND BACKUP WITH RECOVERY CATALOG OR WITHOUT RECOVERY CATALOG
PLEASE TELL ME
Edited by: afzal on Feb 26, 2011 1:45 AM

For simply two databases, there really wouldn't be a need for a recovery catalog. You can still restore/recover without a controlfile and without a recovery catalog.
From this:
afzal wrote:
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 days.I am assuming you want to keep two weeks worth of backups, therefore these:
alter system set control_file_record_keep_time=15 days;
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 daysShould be:
RMAN> sql 'alter system set control_file_record_keep_time=22';
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14;22 would give you that extra layer of protection for instances when a problem occurs with a backup and you want to ensure that data doesn't get aged out.

RMAN backup for TDPO without catalog not working

Hi all,
We have configured IBM tivoli storage for Oracle backup(using RMAN).We did not configure Recovery catalog. Will tivoli support to keep the backups in tape without a catalog?
OS : IBM AIX 5.3
Database Version : 10.2.0.4
Tivoli client version : 5.5.0.0
Tivoli server version : 5.5.4.0
oracle API : 5.4.1.0
Regards.

Hi Rajesh,
Thanks for the reply.The script contains the controlfile autobackup option.I have deleted the SBT tape's old backups using RMAN. But the volume space not reduced. This is the script we are using for backup.
run
configure controlfile autobackup on;
crosscheck archivelog all;
allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/cli
ent/oracle/bin64/tdpo.opt)';
#allocate channel t2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/cl
ient/oracle/bin64/tdpo.opt)';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
backup incremental level 1
filesperset 25
format 'full_%d.%t.bkp'
database;
backup
format 'arch_%d.%t.bkp'
archivelog all;
release channel t1;
regards.

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.

Need inputs on RMAN Backup n Recovery for multiple restore of clean backup

I will explain my scenario below:
We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
Please suggest me the best way forward...
Many Thanks
Nukesh

Hi Asif,
I tried to make it work but seems there are still issue with my recovery, can you have a look and point out the shortcommings. i am totally lost here
RMAN> list incarnation;
using target database control file instead of recovery catalog
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 MYTEST 2433328848 PARENT 1 19-DEC-06
2 2 MYTEST 2433328848 PARENT 564488 04-NOV-10
3 3 MYTEST 2433328848 CURRENT 693719 06-NOV-10
RMAN> exit
TEST1DB-> rman target sys@MYTEST1
Recovery Manager: Release 10.2.0.3.0 - Production on Sun Nov 7 11:43:01 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
target database Password:
connected to target database: MYTEST (DBID=2433328848, not open)
RMAN> reset database to incarnation 2;
using target database control file instead of recovery catalog
database reset to incarnation 2
RMAN> run {
2> restore database until scn 10000;
3> recover database until scn 10000;
4> alter database open resetlogs;
5> };
Starting restore at 07-NOV-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=191 instance=MYTEST1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=190 instance=MYTEST1 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/07/2010 11:45:18
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, c onnect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, l ibrary, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rm an, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, va lidate"
RMAN-01007: at line 0 column 2 file: standard input
RMAN>
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanbackup/MYTEST/ora_cf%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanbackup/MYTEST/ora_df%t_s%s_s%p';
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 '/u01/app/oracle/product/10g/dbs/snapcf_MYTEST1.f'; # default
RMAN> exit
SQL> select name from v$database;
NAME
MYTEST
SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL>

Volume Duplication Policy for RMAN Backups

Hi,
I wish to configure a volume duplication policy for RMAN backups. Both the source media family and duplicate media family are 'content managed' as per the documentation. However, the duplication policy 'trigger' is defined as if the media family is 'time managed', which does not seem to make sense in 'content-managed' media families used by RMAN.
Does anyone have any guidelines on how RMAN volume duplication can be set up so that my duplicates are valid?
Thanks

Yes. I understand. The reason I used time-managed volumes in the tutorial is that with time-managed volumes a duplicate may have different retention and rotation than the original. The procedure for time or content managed duplicates are the same.
A content managed tape may be duplicated to the same or different media family. If to a different media family, the retention would be same...since content managed but it could have a different rotation policy...if desired. For example, if you wanted original tapes left onsite but the duplicates to go offsite for "x" time, then create a new content managed media family and a desired rotation policy...associate that rotation policy to new media family and duplicate tapes to that media family with desired rotation policy. In that scenario, your original media family would have a duplication policy and possible a rotation policy. The new media family would just have a rotation policy.
Donna

Write a ms dos script for rman backup

Hi all,
i wanna write a dos batch file to take the rman backup..
i have written one...actually there are 2 files. one is for login purpose...other one is for sql commands
rman.bat-->
rman target sys/sysadmin@hnbhrm @'c:\rm.sql'
==============================
rm.sql-->
configure retention policy to recovery window of 7 days;
configure controlfile autobackup on;
run {
alter system switch logfile;
crosscheck archivelog all;
crosscheck backupset;
backup database plus archivelog;
DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'sysdate -1';
DELETE NOPROMPT OBSOLETE REDUNDANCY = 1;
========================================
but i have problem in first file rman.bat. it doesnt run at all. but if i write sqlplus / as sysdba instead of rman thing.. then it works fine.
can anybody tell me whats happening over there please..? Have i done this correctly? or u have some other simple way to do this...
both files are located in C drive.. and oracle is installed to E drive... oracle path has set already.
can anybody please give me a hand to solve this issue please...
Thanks in Advance,
Max

write a ms dos script for rman backupImpossible. rman does not support MS-DOS. It is not a 16bit real mode application that can be run inside the MS-DOS operating system.
So get your terminology straight - the Windows console is a character based 32bit virtual machine. It is not MS-DOS. It never was MS-DOS. Do not confuse the two simply because of superficial similarities. A stick-it note can be yellow - but because it is yellow does not mean it is a banana.

Will RMAN backup all the needed files for me automatically ?

I have execued the following command:RMAN>CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
I want to know: Will RMAN backup all the needed files for me automatically every 14 days and delete the metadata of the files older than 14 days automatically?---------No.158

Short answer is No.
What's the definition of all needed files ? datafiles, control files, archive logs and/or online redo? and perhaps spfiles?
RMAN>CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;This is RMAN configure command, it won't do any backup by itself. You need to issue backup command to backup files needed.
You also need to delete obsolete files. The files will become obsolete after 14days but they will not remove themselves automatically.

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.

Considerations for keeping RMAN Backup Retention to 1 Year

Similar Messages

Maybe you are looking for