RMAN policy

we are using rman and policy for backup is
we are running hot backup daily
RMAN>backup database plus archivelog;
archivelog daily
RMAN>backup archivelog all;
controlfile backup is happening daily as i set
CONFIGURE CONTROLFILE AUTOBACKUP ON;
Please suggest is this right method or needs to add something else
and cold backup we are taking on sunday without RMAN
Please suggest!

Am I right in thinking you do RMAN backups nightly, and then on a sunday the DB goes down and a full cold backup is done to tape?
you also havent mentioned what your retention period is, ie how long do you want RMAN to keep the backup files.
at an RMAN prompt; rman>show all
this will tell you what parameters you have set.

Similar Messages

About RMAN backup !!!!

Dear Friends,
Let my production server running starts from 1st June .
In 15 june , I take the First rman full (or level0) backup using the command :
RMAN> backup database plus archivelog;
In 20 June I take 2nd rman full backup using : RMAN> backup database plus archivelog;
Again in 30 June , I take the Third(3rd) rman full (or level 0) backup using the command :
RMAN> backup database plus archivelog;
And also my rman policy set as :
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
In the above scenario , I have the following questions :
1) When I take the Third(3rd) backup then is it the First RMAN backup goes to obsolete as per my rman policy ( RETENTION POLICY TO REDUNDANCY 1) ?
2) Is the above all RMAN backup make a link between them ?
3) If my first RMAN backup goes to obsolete and I have to delete the First RMAN backup , then which types of problem I face ? Can I go to previous state(suppose I need to back in 1st June) of my server if I delete First rman backup ?
4) when I take 3rd rman full backup , then is it all information from 1st january of the server are stored in the 3rd backup ? i.e., is the 3rd rman backup stores all the previous two rman backups information ?so that If I delete the previous two backup , then I get all information form 3rd rman backup .what is the actual scenario ......
plz help me to make clear concept about it .......
thx in advance .....

1) When I take the Third(3rd) backup then is it the First RMAN backup goes to obsolete as per my rman policy ( RETENTION POLICY TO REDUNDANCY 1) ?The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many backups of each datafile and control file that RMAN should keep. In other words, if the number of backups for a specific datafile or control file exceeds the REDUNDANCY setting, then RMAN considers the extra backups as obsolete.So as in your case the redundancy is 1 so the 1st and 2nd backup are obsolete.
To check the obsolete backups run
rman> report obsolete;
To delete them
rman> delete obsolete;
Link:[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/setup005.htm#BRBSC400]
Is the above all RMAN backup make a link between them ?I am not very much clear with the question.The RMAN information is stored in the controlfile.You can also create a new recovery catalog and register the target database. The RMAN repository records in the control file will be copied to the new recovery catalog.
when I take 3rd rman full backup , then is it all information from 1st january of the server are stored in the 3rd backup ? i.e., is the 3rd rman backup stores all the previous two rman backups information ?so that If I delete the previous two backup , then I get all information form 3rd rman backupThe 3rd RMAN backup will contain all the information of the DB from the very 1st day.You will get all the information in the 3rd rman backup as its a level 0 or what we say a FULL DATABASE BACKUP.If suppose the 3rd rman backup would have been a incremental backup, then you would have required a full backup, previous to the incremental one, so that after restoring the full backup, you restore the incremental to recover the DB completely.
Link:[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/part1.htm#i996723]
[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#BRBSC133]
Forgot to answer the 3rd question
3) If my first RMAN backup goes to obsolete and I have to delete the First RMAN backup , then which types of problem I face ? Can I go to previous state(suppose I need to back in 1st June) of my server if I delete First rman backup ?well, i am not very much sure , but i think is , if you have the 1st rman backup pieces physically present on the disk, you can catalog it and then use the rman command to restore the data from it of till 1st june.
To catalog the backup pieces use
rman> catalog backuppiece 'filename';
Link: [http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/maint007.htm]
HTH
Anand
Edited by: Anand... on Oct 15, 2008 10:51 AM

Rman granularity backup

Hi all,
I have a question about the rman policy implementation. I do backups of one of my database via rman. I do a L0 backup on Sunday and a L1 every other days. I backup also the archivelog files. My retention policy is 14 days.
Now, due a space disk problem, I would delete the backupped archivelog older than 7 days.
I tried to add this line in the daily rman script:
"delete noprompt backup of archivelog until time 'SYSDATE-7' "
but in this way I delete also the needed archivelog to restore the L1 backup.
In other words: I would use 2 type of granularity backup:
- from now to 7 day: all archivelog (so I can restore the db in each SCN)
- from 7 days to 14 days: only the L0 and L1 with and only the needed archivelog. (I can restore only with the incremental backup).
Is there a way to resolve this problem?
thanks
Federico

Hi Khurram,
I cannot increase my retention policy due disk space problem.
I don't understand your advice. Consider this:
- backup tag "first" SCN 100 (10 day old)
- all archivelog from SCN 90 to 100 (10 day old)
- backup tag "second" SCN 110 (3 day old)
- all archivelog from SCN 101 110 (3 day old)
I would like to find a way (maybe an automatic way) to delete the older archivelog than 7 day but I must to keep the archivelog containing the SCN 100 because without it I cannot restore the DB to the 1° backup.
Federico

ARCHIVE_DELETEION_POLICY

Hi ,
Iam taking RMAN backup on SUNDAY and WEDNESDAY night Full backup as per my project policy . so i have the bewlo script to take backup to TAPE(netbackup veritas)
1. i want to delete all the archive logs after backed up to TAPE.?
2. Also is it possible to delete old backup from tape before taking NEW backup so that i can free some space from TAPE for NEW ONE.?
RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
send 'NB_ORA_POLICY=${NB_POLICY_NAME}' ;
BACKUP
    $BACKUP_TYPE
    SKIP INACCESSIBLE
    TAG hot_db_bk_level0
    FILESPERSET 5
# recommended format
FORMAT 'bk_%s_%p_%t'
DATABASE;
sql 'alter system archive log current';
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
# backup all archive logs
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
BACKUP
   filesperset 20
   FORMAT 'al_%s_%p_%t'
ARCHIVELOG ALL DELETE INPUT;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
Thanks ,

Hi,
> 1. i want to delete all the archive logs after backed up to TAPE.?
And what is the question here? You are already using the RMAN clause "ARCHIVELOG ALL DELETE INPUT".
> 2. Also is it possible to delete old backup from tape before taking NEW backup so that i can free some space from TAPE for NEW ONE.?
Yes, if you would use a RMAN policy driven third party software like IBM Tivoli Data Protection for Databases. NetBackup is based on the NetBackup catalog driven retention policies and so you don't need to think about it - your NetBackup admin has to care about it. You only have to crosscheck the RMAN backups (and delete the expired ones) to keep the RMAN catalog up-to-date. By the way it makes *NO* sense to delete the old backup BEFORE taking a new backup.
> But one of my senior got the below script from net
Then your senior is no senior, if he/she needs to download that basic stuff from the net.
> and wat it will do exactly, becos i need to explain the script before implement.
Are you serious?
Regards
Stefan

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

RMAN DB retention policy

Hi,
Does following command ONLY helpful in level 1 incremental?
RMAN>CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
I want to configure to have 30 days backup must be available on tape.I also have policy anually to have tape backup and send to IRON MOUNT.
If I use following command
RMAN>CONFIGURE RETENTION POLICY TO REDUNDANCY 30;
is there any diffrence?
If CROSSCHECK BACKUP shows expired and updated repository.Can we use expired backup for recovery purpose?
Thanks

see this link also
How to delete expired backupset with RMAN ?
Khurram

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-08591: WARNING: invalid archived log deletion policy

Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,

kkrm333 wrote:
Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,
bcm@bcm-laptop:~$ oerr rman 8591
8591, 3, "WARNING: invalid archived log deletion policy"
// *Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archived
//         log deletion policy was APPLIED but there was no mandatory
//         archived log destinations.
// *Action: One of the following:
//          1) Change archived log deletion policy using CONFIGURE command
//          2) Make one or more of standby destination as MANDATORY.

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

Backup policy on Grid, using RMAN and Recovery Catalog.

Hello Gurus,
I'm trying to move ahead the new features of Oracle 10g in my company. So I've already created Grid Control and will deploy Agents/Targets during the next week. I also want to switch the backup process from the archaic exp/imp to RMAN with the Recovery Catalog.
My question is such: could anybody suggest the best book or text with solutions and descriptions of backup policy, using the Grid, RMAN and Catalog? What I want to do is to create eventually the powerful and centralized storage of every database in a company and do all daily routine from there. But as long as I'm only in the very beginning I want to gain some knowledge before the bad experience, like crashed recovery catalog and no backups for all databases :-)))
Definitely I'll keep existing imp/exp and hotbackup for a long time. I'm not going to substitute all our backup strategy with one catalog. I just want to understand what will be the best practice in the backup perspective.
And at all, I wonder if you please could give me very brief answer to this question: Let's say I have a huge monster with 5 disks by 500Gb RAD0+1. Is it a bad idea to store all of them in one physical machine before they will tape to backup or it could make sense? For me it sounds a bit scary, but probably if all made with the brain it's not a bad idea?
Please, send me to some valuable and good source (like Tom Kyte or Don Burleson) Unfortunately, I didn't find anything regard the backups itself. Only pretty much general thought.
Thanks a lot in advance.
M.

great!
thanks a lot!
this is definitely valuable info and I'll read right away. but as far as understand they suggest to use Data Guard, Standby and RAC which are the best ways to prevent your environment from crash. But in reality (I mean in my company) nobody is going to move to RAC at this point and I'm not sure, that they will have a chance to do in the next year. they just aren't up to it.
what I'm looking for is probably some tips and hints about backups in more or less big environment, but not as big as Oracle itself :-) unfortunately, i'm the only DBA in my surrounding. i mean, i have no friends or mentors DBAs that could seat with me in a pub and pass theirs knowledge from generation to generation :-)))
but anyway, I'll devote this week-end to this link.
thanks a lot!

RMAN Backups with retention policy to redundancy 1 doesn't work fine.

Hi experts,
I have a Oracle database with the following system backups:
Monday:       ArchiveLog Backup
Tuesday:      Full Backup
Wednesday: ArchiveLog Backup
Thursday:     ArchiveLog Backup
Friday :         Full Backup
Saturday:      ArchiveLog Backup
Sunday:       ArchiveLog Backup
ArchiveLog Backup = backup tag 'ARCHIVELOG_BACKUP' device type disk archivelog all not backed up delete all input;
Full Backup = backup tag 'FULL_BACKUP' device type disk database skip readonly plus archivelog tag 'FULL_BACKUP_ARCHIVELOGS';
                     crosscheck backup;
                     crosscheck copy;
                     delete noprompt obsolete;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 8;
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 ARCHIVELOG DELETION POLICY TO NONE; # default
What this system has done until last two weeks? For example:
Tuesday :     Full Backup
Wednesday: ArchiveLog Backup
Thursday:     ArchiveLog Backup
Friday :         Full Backup - > After that, Full backup from Tuesday and ArchiveLog backups from Wed, and Thurs, are deleted. (Thanks to Retention policy) .
What this system do now?
Tuesday :     Full Backup
Wednesday: ArchiveLog Backup
Thursday:     ArchiveLog Backup
Friday :         Full Backup - > After that, Full backup from Tuesday are deleted but not ArchiveLog backups from Wed, and Thurs.
When I execute a crosscheck on RMAN return that all are AVAILABLE.
My question is: What is right? The system backups before or after?
Thanks for your help!

You are confused about the purpose of crosscheck.
There are two concepts for which you must grasp the distinction.
- Expired
- Obsolete
Expired
When an archive log is written, or rman makes a backup, a record of that archivelog or backupset is written to the repository in the control file.
Crosscheck simply checks the existence of the archivelogs or backupsets that are recorded in the repository. If something went missing (say, if you used an OS command to delete archivelogs), the record of the missing file is marked as 'expired'. If you follow the crosscheck command with a 'delete expired' command, the repository records that have been marked 'expired' are deleted from the repository, so rman has no more memory of those files. Note that 'expired' has nothing to do with retention policy. Also note that if you do not actually issue the 'delete expired' command, the expired records will remain in the repository.
Obsolete
The retention policy deals with when a backupset is obsolete, meaning it is no longer needed to protect the retention period. Backupset are not marked as obsolete. They are evaluated for obsolescence at the time of a command that needs it -- "report obsolete" or "delete obsolete", or when FRA maintenance requires an implied 'delete obsolete'.

RMAN on Oracle 8i and 10g Retention Policy

I have several Oracle 8i and Oracle 10g database instances on a Windows 2003 server. We use RMAN backups on these servers. We run a batch job daily to database backups. We create RMAN level 0 on Sunday, Thursday level 1, Tuesday, Thursday, Friday, and Saturday level 2 backups.
I would like to keep the backup files for 7 days. Oracle 9i has the CONFIGURE RETENTION POLICY TO RECOVERY WINDOWS OF 7 DAYS parameter.
What parameter can I use on the Oracle 8i database to keep only 7 days of backup files on disk?
Should I add the CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS parameter to RMAN parameter list below or to the Oracle parameter list?
Oracle 9i parameter
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
RMAN parameter list:
set logdir=\\ta\WIN_ORABACKUP\DATA\W004\PRD6\LOGS
set logdirbak=\\ta\WIN_ORABACKUP\LOGS
set backupdir=\\ta\WIN_ORABACKUP\DATA\W004\PRD6\HOTBACKUP
set scriptdir=\\ngacelerra\WIN_ORABACKUP\SCRIPTS
set logname=%Year%%Month%%Day%%Hour%%Minute%%Second%_PRD6_rman.log
set scriptname=PRD6_LVL%1%.rmn
mkdir %logdir%
mkdir %backupdir%
rman target sys/password@PRD6 nocatalog log %logdir%\%logname% @%scriptdir%\%scriptname%
copy %logdir%\%logname% %logdirbak%\%logname%

Hi,
there is no CONFIGURE command in RMAN in ORACLE 8i.
It was a 9i new feature!
Also, in Oracle 10g there are no incremental level 2 backups available any more.
We only have level 0 and 1 in 10g!
If you want to read about the new backup strategy of ORACLE 10g pls refer to my weblog:
http://luhartma.blogspot.com/2006/02/why-restore-before-recover-new-oracle.html
Hope this helps for the first.
Regards,
Lutz

RMAN policy

Similar Messages

Maybe you are looking for