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

Similar Messages

Problem restoring from tape a backup with different retention days

As part of our procedure to test data restore for the SAP platform, recently we tried to restore a backup of the QAS SAP database from tape but had problems . During the analysis we think this problem happened because the retention of the backup on tape differs from the one in the configuration of SAP initSID.utl file; originally, the backup was made to a virtual tape using the brbackup tool /expiration parameter of 3 days, then cloned to a physical tape with a longer retention (30 days).
As a temporary solution to restore the data, we extended the u2018expirationu2019 parameter in the brbackup/brrestore configuration file (.utl) and since we still had the logs of the original backup (.anf file), we were able to complete the restore succesfully. We then changed back to the original the expiration time in the .utl file
We need to run the restore option in Production (PRO) environment but still we are not sure if this workaround is acceptable. Does anyone know if this option is correct or if thereu2019s another known solution for this case

Hi Julio
I believe you have posted your query in the wrong forum and hence you might not be getting the responses you would want.
This forum is for Operational Performance Management Business Applications like Spend Performance Management and SCPM.
Regards
Rajesh

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.

Rman backup with standby database

Hi All,
I am looking for some suggestions for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';
sql statement: alter system archive log current noswitch
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
ORA-01109: database not open
Recovery Manager: Release 11.2.0.1.0
Oracle databaes Release 11.2.0.1.0 64 bit
OS:RHEL 6 x86-64 bit
Secondly, do I need to cancel manged recovery while taking rman backups on standby.
I scanned thru MOS but could find solutions for rman with active DG.
Thanks in advance

726d07e6-b870-431f-8c22-a499c3ec4e0c wrote:
Hi All,
I am looking for some suggestions for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';
sql statement: alter system archive log current noswitch
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
ORA-01109: database not open
Recovery Manager: Release 11.2.0.1.0
Oracle databaes Release 11.2.0.1.0 64 bit
OS:RHEL 6 x86-64 bit
Secondly, do I need to cancel manged recovery while taking rman backups on standby.
I scanned thru MOS but could find solutions for rman with active DG.
Thanks in advance
"I scanned thru MOS but could find solutions for rman with active DG."
Howto make a consistent RMAN backup in an Standby database in Active DataGuard mode (Doc ID 1419923.1)

RMAN backup with smallest backup size

Oralce 11g2 on Redhat 5. The diskspace is our tightest resource, and we want to an incremental backup with level0 on Sunday and level 1 every week days and Saturday. I am to use the comamnds to do the job--Sunday
backup incremental level 0 tag 'level_0' database plus archivelog;
--Other days
backup incremental level 1 database plus archivelog delete all input;I do not think this is the best practice nor produce smallest backup files.
What are you comments and opinions. Thanks

Pavan, Thank you for reply. Here are the info requested
what is size of DB ??
~250GB, including UNDO and TEMP. It is a dev database and not very big. But we have total 800GB disk space. After setting some housekeeoing folders, and allow some space for data growth, it leaves 180GB for flash_recovery_area.
what would be max size of archive logs generated per day ??
Variable from less than 1 GB to 12 GB
Are you taking backups to tape or Disk ??
Disk. In the 180GB flash_recovery_area, Current backup size is 152GB. If a backup fails to delete obsolete files, the next backup will fill the flash_recovery_area.
Provide the Rman configuration information ??
RMAN> show all;
RMAN configuration parameters for database with db_unique_name TDEV2 are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%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 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_tdev2.f'; # default

Create a database from 32bit rman backup with NEW name on a 64bit system

Hello,
i'm more programmer than database admin but i need to set up a 10gR2 apex development server based on our productive instance in a short time.
For that i want to use a rman backup of the productive machine (SLES 10 32bit, DB10GR2+ASM, APEX 3.1).
Because of the less time i got, i want to use an existing machine (SLES 11 64bit, DB10GR2+ASM) as destination.
On this machine i want to create a new instance from the backup i took. I Already read note 881395.1 but i'm quite unsure about 2 things
a) It's VERY IMPORTANT that the development instance has another name than the productive instance.
When i follow 881395.1 and set the enviromental variable ORACLE_SID to another new name. Will this be all? Or will there be problems using another SID because of references in the controlfile or sth. like that?
b) It's VERY IMPORTANT that the datafiles aren't stored in the same path and with the same names as the productive instance. It is another server but there is already a copy of the database (our dba tried to set up a standby solution on this machine) and i don't want to bother this!
How can i rename the datafiles before restoring the backup from scatch?
I found this: set newname for datafile 1 to '<filesystem based filename>';
Will this help? Do i need to rename every single file? Or is it possible to set a path in which all datafiles will be restored?
c) What about the 32bit to 64 bit thing? Will this work? Or do i need to convert the database? How? RMAN Convert?
Or could RMAN convert anyhow used to realize the whole thing?
Thank you very much for your support!
Regards
Daniel

Hello,
i'm more programmer than database admin but i need to set up a 10gR2 apex development server based on our productive instance in a short time.
For that i want to use a rman backup of the productive machine (SLES 10 32bit, DB10GR2+ASM, APEX 3.1).
Because of the less time i got, i want to use an existing machine (SLES 11 64bit, DB10GR2+ASM) as destination.
On this machine i want to create a new instance from the backup i took. I Already read note 881395.1 but i'm quite unsure about 2 things
a) It's VERY IMPORTANT that the development instance has another name than the productive instance.
When i follow 881395.1 and set the enviromental variable ORACLE_SID to another new name. Will this be all? Or will there be problems using another SID because of references in the controlfile or sth. like that?
b) It's VERY IMPORTANT that the datafiles aren't stored in the same path and with the same names as the productive instance. It is another server but there is already a copy of the database (our dba tried to set up a standby solution on this machine) and i don't want to bother this!
How can i rename the datafiles before restoring the backup from scatch?
I found this: set newname for datafile 1 to '<filesystem based filename>';
Will this help? Do i need to rename every single file? Or is it possible to set a path in which all datafiles will be restored?
c) What about the 32bit to 64 bit thing? Will this work? Or do i need to convert the database? How? RMAN Convert?
Or could RMAN convert anyhow used to realize the whole thing?
Thank you very much for your support!
Regards
Daniel

Manually register rman backup with oracle database 10g

Dear All.
I want to restore full backup of database.
I have not configure flash_recovery_area.
how i can manually register full rman backup of database with oracle database 10g.?
Please help me.
Thanks & Regards
Ravi Kumar

This is the 10gR2 documentation on the CATALOG command :
http://docs.oracle.com/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
You must be specific when stating the version you are running. Commands may be limited or unavailable in older versions versus more recent versions of Oracle.
Hemant K Chitale

Rman backup with nocatalog

hi,
if i take backup by rman nocatalog ,where it cud be problematic if take backup in nocatalog & wt should i do to resolve them.
thxs

Hi,
As you said that you are rman is with nocatalog, then its going to use the Control file for storing the informaiton about the backups.
Could not able to understand "where it cud be problematic if take backup in nocatalog "
Got, Control file is going to store the information for a period time "CONTROL_FILE_RECORD_KEEP_TIME " specifies the minimum age in days of a record before it can be reused. Manily it will fall under the "Circular reuse records".
Problem will as the if you are want to go for more than one DB, it would be problematic and cases where Control file got corrupted. Try to go Recovery Catalog.
- Pavan Kumar N
Edited by: Pavan Kumar on Feb 9, 2009 3:53 PM
For your reference :
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmmaint.htm
Edited by: Pavan Kumar on Feb 9, 2009 3:57 PM

RMAN backup with archivelogs.

Dear all,
Can i delete all archivels after the RMAN backup. Why do we backup archivelogs with RMAN backup. I think it is useless.
Please can somebody explane this.
Regards
upul indika

Why do we backup archivelogs with RMAN backup. I
think it is useless. You think backing up archivelogs is useless ? Did you ever recover a database ? Did you ever simulate a disaster recovery ? If yes, how did you do it ? If not, then you should have a look at the documentation
Anyway, you can (or even you should) delete archivelogs after the RMAN backup.

Rman backup with a missing archivelog.

hello,
I backed my database up yesterday after you guys helped me fix few problems I had on it. I used RMAN with the following command in a run block:
*run {*
allocate channel t1 type disk;
backup current controlfile ;
backup database;
backup archivelog all delete input;
release channel c1;
At the end of the operation, RMAN indicates that and archivelog is missing and it couldn't find it. As a result, recover operation can be compromised. Now am confused because I do not know whether the command executed successfully or not and how to fix the missing archivelog.
Below is the entire output of the operation along with error message:
canal affectÚ : t1
canal t1 : sid=131 typedev=DISK
DÚmarrage de backup dans 16/04/09
canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncnnf0_tag20090416t211049_0.334.684
*364257 Útiquette=TAG20090416T211049 commentaire=NONE*
canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:14
Fin de backup dans 16/04/09
DÚmarrage de backup dans 16/04/09
canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
fichier de donnÚes en entrÚe fno=00008 nom=+ASMTEST/meta4/m4prod.dbf
fichier de donnÚes en entrÚe fno=00010 nom=H:\ORADATA\M4REC.DBF
fichier de donnÚes en entrÚe fno=00009 nom=E:\DATAFILEMETA4\M4PROD02.DBF
fichier de donnÚes en entrÚe fno=00001 nom=+ASMTEST/meta4/system01.dbf
fichier de donnÚes en entrÚe fno=00003 nom=+ASMTEST/meta4/sysaux01.dbf
fichier de donnÚes en entrÚe fno=00006 nom=C:\TEST.DBF
fichier de donnÚes en entrÚe fno=00007 nom=+ASMTEST/meta4/meta4.dbf
fichier de donnÚes en entrÚe fno=00005 nom=+ASMTEST/meta4/example01.dbf
fichier de donnÚes en entrÚe fno=00002 nom=+ASMTEST/meta4/undotbs01.dbf
fichier de donnÚes en entrÚe fno=00004 nom=+ASMTEST/meta4/users01.dbf
canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
pointeur=+ASMTEST/meta4/backupset/2009_04_16/nnndf0_tag20090416t211107_0.333.684
*364271 Útiquette=TAG20090416T211107 commentaire=NONE*
canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:51:10
canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
inclusion du SPFILE en cours dans l'ensemble de sauvegarde
canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncsnf0_tag20090416t211107_0.345.684
*367351 Útiquette=TAG20090416T211107 commentaire=NONE*
canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:26
Fin de backup dans 16/04/09
DÚmarrage de backup dans 16/04/09
journal en cours archivÚ
canal libÚrÚ : t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Úchec de la commande backup Ó 04/16/2009 22:04:03
RMAN-06059: journal d'archivage attendu introuvable ; la perte du journal d'arch
ivage compromet la possibilitÚ de rÚcupÚration
ORA-19625: erreur lors de l'identification du fichier H:\ARCHIVEMETA4\ARC00001_0
*682674928.001*
ORA-27041: ouverture du fichier impossible
OSD-04002: ouverture impossible du fichier
O/S-Error: (OS 2) Le fichier spÚcifiÚ est introuvable.
Here's my nderstanding and please correct me if am wrong:
The first 3 instructions of the run block executed successfully, but
the last one didn't. Is that so?
Whatever the understanding, do I have a backup? WHat can I do to have a consistent backup?
Thanks in advance.

Adomi,
It is sad to see you are still running RMAN in 8i fashion where you are on 10g.
The script is bs, sorry
run {
allocate channel t1 type disk; -- not required
backup current controlfile ; -- not required, as this is already done by backup database
backup database;
backup archivelog all delete input;
release channel c1; -- not required.
If you have controlfile autobackup on, you could just
backup database plus archivelog
and be done with it.
As you didn't make a RMAN backup from the start, your backup archivelog statement should have read
backup archivelog all skip inaccessible delete input;
Once that succeeds Oracle shouldn't need the archivelog anymore, and you should make a second backup without the skip inaccessible clause.
Sybrand Bakker
Senior Oracle DBA

Rman backup with archivelog from tape

Hi,
We are doing a level 0 backup on sunday and then level1 backup on all the weekdays.
The archive logs generated are 1GB each and are more in number.
IF we include archivelog in level1 backup , its taking around 12hrs to complete.
So we are thinking of not including the archivelog in level 1 backup,but then we can daily move the archive logs to another location .
So archivelogs will not be in the rman backup.
So in case of restore, how can we apply the archive logs required? rman will not identify the archive logs...how can we manually apply the required archive logs
Please help

Information about ArchiveLogs is available in the controlfile as I outlined in my response post in the thread How to find out which archived logs needed to recover a hot backup?
However, if your CONTROLFILE_RECORD_KEEP_TIME is 7 days and you are attempting a restore of a backup 14 days or 28 days or 35 days old ... you may be out of luck.
You'd need to maintain a listing of ArchiveLogs in some manner (e.g. a log file outside the database that you periodically update with information about ArchiveLogs).
It is much better to also backup the ArchiveLogs using RMAN. Don't forget to ensure that controlfile backups or autobackups are also taken and retained.
Hemant K Chitale

DBID for RMAN backup with format '%u'

Hi all:
(I've post this at c.d.o.s. too, but no answers...)
This is Oracle 10.2.0.3 on Enterprise Linux 5.
I've been given two backups from an Oracle Database: one 'cold' and
one 'hot'. They both come from a lost server.
The fact is that they have been made with the format '%u' (eight
alphanumerics) and I must recover the database on a new server. I
cannot get the DBID from the backup files name because of this format
'%u'.
The backups have been made with CONTROLFILE AUTOBACKUP ON (or so I'm told).
How can I get the DBID to recover the DB on a new server?
Thanks in advance.
Cheers.
Carlos.

"I don't know where you read this, it's wrong. "Oracle® Database Backup and Recovery Advanced User's Guide
10g Release 2 (10.2)
2 RMAN Backups Concepts
Control File and Server Parameter File Autobackups
How RMAN Performs Control File Autobackups
"The RMAN behavior when the BACKUP command includes datafile 1 depends on the CONFIGURE CONTROLFILE AUTOBACKUP setting. If control file autobackups are ON and the backup includes datafile 1, RMAN writes the control file and SPFILE to a separate autobackup backup set. If control file autobackups are OFF and the backup includes datafile 1, then RMAN includes the current control file and SPFILE in the same backup set as the datafiles."
Cheers.
Carlos.

Rman backup with corrupted block

Hello,
Firstly - I have problem on non-production database 11.2.0.1.0, so I am not deeply worried about data. But I need to understand what happened with database backups and how to prevent such things in future.
So - I have EM scheduled weekly full backup and daily incremental backups. Later there was problem with hardware and some corrupted blocks in database were found. The weekly backup ran without error and obsolete backups were deleted. Now it is not possible to "recover corruption list" because no backup without corruption exists (RMAN-06023: no backup or copy of datafile 6 found to restore). I am not worried about the lost data, but I need to find out how come the backup contains corrupted block.
I have checked the data file using dbv utility
DBVERIFY - Verification starting : FILE = /opt/oracle/oradata/orcl/users03.dbf
DBV-00200: Block, DBA 27525766, already marked corrupt
csc(0x0001.7b01729f) higher than block scn(0x0000.00000000)
Page 2359942 failed with check code 6054
DBVERIFY - Verification complete
Total Pages Examined         : 3840000
Total Pages Processed (Data) : 453896
Total Pages Failing   (Data) : 1
Total Pages Processed (Index): 2959104
Total Pages Failing   (Index): 0
Total Pages Processed (Other): 424025
Total Pages Processed (Seg) : 0
Total Pages Failing   (Seg) : 0
Total Pages Empty            : 2975
Total Pages Marked Corrupt   : 1
Total Pages Influx           : 0
Total Pages Encrypted        : 0
Highest block SCN            : 2156227446 (1.2156227446)As you can see the datafile 6 - user03.dbf has errors. Also backups now contain errors.
1) So how is it possible that the EM scheduled backup ran without problems and the backup now contains corrupted blocks. How to prevent this in future ? I know there is setting MAXCORRUPT. How can I check its current value ? How can I configure it using EM scheduled backups ?
2) Secondly, meanwhile I studied the RMAN commands. So I have suspended EM backup jobs, and executed follwing command. And backup ran without error again. How is this possible, if data file users06.dbf has corrupted block ?
Thanks !
RMAN> run {
set MAXCORRUPT for datafile 6 to 0;
backup as compressed backupset datafile 6;
2> 3> 4>
executing command: SET MAX CORRUPT
Starting backup at 07-NOV-12
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
channel ORA_DISK_1: starting piece 1 at 07-NOV-12
channel ORA_DISK_1: finished piece 1 at 07-NOV-12
piece handle=/opt/oraBackup/rman/nrnpo0sg_1_1 tag=TAG20121107T200120 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 01:13:05
Finished backup at 07-NOV-12
Starting Control File and SPFILE Autobackup at 07-NOV-12
piece handle=/opt/oraBackup/rman/c-1253245572-20121107-03 comment=NONE
Finished Control File and SPFILE Autobackup at 07-NOV-12

I have updated database to 11.2.0.3
However, the problem still persists. rman backup went ok on broken file
oracle@orcl-cluster:~> sqlplus
SQL*Plus: Release 11.2.0.3.0 Production on Tue Nov 20 09:24:11 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Enter user-name: system
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select * from V$DATABASE_BLOCK_CORRUPTION;
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         6    2359942          1                  0 FRACTURED
        25    1855622          1                  0 FRACTURED
oracle@orcl-cluster:~> rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Nov 20 08:04:57 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1253245572)
RMAN> backup as compressed backupset datafile 6;
Starting backup at 20-NOV-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1596 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=1568 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=2357 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=2341 device type=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: SID=86 device type=DISK
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
channel ORA_DISK_1: starting piece 1 at 20-NOV-12
channel ORA_DISK_1: finished piece 1 at 20-NOV-12
piece handle=/opt/oraBackup/rman/2rnqovpp_1_1 tag=TAG20121120T080513 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 01:10:35
Finished backup at 20-NOV-12
Starting Control File and SPFILE Autobackup at 20-NOV-12
piece handle=/opt/oraBackup/rman/c-1253245572-20121120-00 comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-12
RMAN> backup validate datafile 6;
Starting backup at 20-NOV-12
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
channel ORA_DISK_1: backup set complete, elapsed time: 00:03:05
List of Datafiles
=================
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
6    OK     1              2975         3840000         6489027926
File Name: /opt/oracle/oradata/orcl/users03.dbf
Block Type Blocks Failing Blocks Processed
Data       0              453912
Index      0              2959091
Other      0              424022
Finished backup at 20-NOV-12Edited by: kamilp on Nov 20, 2012 12:23 AM

RMAN backup with no expiry

Hi,
We are using oracle 11gR2 on AIX 6.1,
We have to take the RMAN backup which should be never expired and we dont have any catalog,
for "KEEP FOREVER" option we require catalog,
any other way not to expire RMAN backup?
Thanks

Assuming this is a once off requirement, it is just a case of taking a cold backup of the database including the controlfile and any archivelogs and then storing these offline.
A copy of the pfile as well as a text copy of the controlfile (backup controlfile to trace) should also be taken.
As long as you have all of this , it should be possible to restore/recover your database to the start point.

Rman backups in different OS?

Can we take rman backups from production and use them in developemnt database ?
The Os of production is Hp-UX and for develpment is windows.

Take care: Cross platform transportable tablespaces are only available in 10g. Prior to this it was only possible when both platforms used the same OS.

Rman backup with different retention

Similar Messages

Maybe you are looking for