Exclude a tablespace in rman backup

Data Guard with primary and physical standby both on Oracle 11.2.0.1 on redhat 5.2. I am to duplicate the primary to the standby. The primary has an offline tablespace and I want exclude it from the data guard. Using RMAN to make backup like BACKUP DEVICE TYPE DISK FORMAT '/u01/flash/dg/%d_%U' DATABASE PLUS ARCHIVELOG; Questions
1) How to make RMAN report what source objects (files, tablespaces) to be included in the backup command before perform a real backup?
2) How can I make the command exclude the offline tablespace I do not want to copy?
Thanks

Daniel is correct. What you were thinking of was:
SKIP TABLESPACE MYOFFLINETBS;
However, standbys play by different rules and regardless of whether or not a tablespace is offline the standby has to be prepared for it to come back on line.
I normally wouldn't bother with a redundant post, but I had this in my notes:
Rman DUPLICATE FOR STANDBY doesn't work with SKIP or EXCLUDE TABLESPACE [ID 1174944.1]
Cheers.

Similar Messages

Unable to restore TABLESPACE using RMAN backups

Hi,
I am not able to restore tablespace using RMAN (TSPITR).
I have full backup of database,
While try to restore it's failed.
RMAN> recover tablespace TEST1 until logseq 706 auxiliary destination '/tmp';
Starting recover at 16-OCT-13
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS2
Creating automatic instance, with SID='CsFz'
initialization parameters used for automatic instance:
db_name=TRAINEE
db_unique_name=CsFz_tspitr_TRAINEE
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/tmp
log_archive_dest_1='location=/tmp'
#No auxiliary parameter file used
starting up automatic instance TRAINEE
Oracle instance started
Total System Global Area     292933632 bytes
Fixed Size                     1336092 bytes
Variable Size                100666596 bytes
Database Buffers             184549376 bytes
Redo Buffers                   6381568 bytes
Automatic instance created
List of tablespaces that have been dropped from the target database:
Tablespace TEST1
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 16-OCT-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=81 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/product/11.2.0/dbhome_1/dbs/c-332232391-20131016-09
channel ORA_AUX_DISK_1: piece handle=/oracle/product/11.2.0/dbhome_1/dbs/c-332232391-20131016-09 tag=TAG20131016T144951
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/tmp/TRAINEE/controlfile/o1_mf_95wbkpvj_.ctl
Finished restore at 16-OCT-13
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 7 to new;
set newname for clone datafile 2 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 6 to
"/oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 7, 2, 6;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to /tmp/TRAINEE/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 16-OCT-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /tmp/TRAINEE/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00007 to /tmp/TRAINEE/datafile/o1_mf_undotbs2_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00002 to /tmp/TRAINEE/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /tmp/1iomi9rv_1_1
channel ORA_AUX_DISK_1: piece handle=/tmp/1iomi9rv_1_1 tag=TAG20131016T144935
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:15
Finished restore at 16-OCT-13
datafile 1 switched to datafile copy
input datafile copy RECID=11 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_system_95wbkybb_.dbf
datafile 7 switched to datafile copy
input datafile copy RECID=12 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_undotbs2_95wbkycy_.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=13 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_sysaux_95wbkybz_.dbf
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
sql clone "alter database datafile 7 online";
sql clone "alter database datafile 2 online";
sql clone "alter database datafile 6 online";
# recover and open resetlogs
recover clone database tablespace "TEST1", "SYSTEM", "UNDOTBS2", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
executing Memory Script
executing command: SET until clause
sql statement: alter database datafile 1 online
sql statement: alter database datafile 7 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 6 online
Starting recover at 16-OCT-13
using channel ORA_AUX_DISK_1
starting media recovery
archived log for thread 1 with sequence 702 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_702_807275402.dbf
archived log for thread 1 with sequence 703 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_703_807275402.dbf
archived log for thread 1 with sequence 704 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_704_807275402.dbf
archived log for thread 1 with sequence 705 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_705_807275402.dbf
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_702_807275402.dbf thread=1 sequence=702
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_703_807275402.dbf thread=1 sequence=703
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_704_807275402.dbf thread=1 sequence=704
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_705_807275402.dbf thread=1 sequence=705
media recovery complete, elapsed time: 00:00:01
Finished recover at 16-OCT-13
database opened
contents of Memory Script:
# make read only the tablespace that will be exported
sql clone 'alter tablespace TEST1 read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/tmp''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/tmp''";
executing Memory Script
sql statement: alter tablespace TEST1 read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/tmp''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/tmp''
Performing export of metadata...
   EXPDP> Starting "SYS"."TSPITR_EXP_CsFz":
   EXPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
   EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
   EXPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
   EXPDP> Master table "SYS"."TSPITR_EXP_CsFz" successfully loaded/unloaded
   EXPDP> ******************************************************************************
   EXPDP> Dump file set for SYS.TSPITR_EXP_CsFz is:
   EXPDP>   /tmp/tspitr_CsFz_17454.dmp
   EXPDP> ******************************************************************************
   EXPDP> Datafiles required for transportable tablespace TEST1:
   EXPDP>   /tmp/TRAINEE/datafile/o1_mf_test1_95wbkyck_.dbf
   EXPDP> Job "SYS"."TSPITR_EXP_CsFz" successfully completed at 14:56:02
Export completed
contents of Memory Script:
# shutdown clone before import
shutdown clone immediate
executing Memory Script
database closed
database dismounted
Oracle instance shut down
Performing import of metadata...
   IMPDP> Master table "SYS"."TSPITR_IMP_CsFz" successfully loaded/unloaded
   IMPDP> Starting "SYS"."TSPITR_IMP_CsFz":
   IMPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Removing automatic instance
Automatic instance removed
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_temp_95wblk08_.tmp deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_3_95wblj14_.log deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_2_95wblhn8_.log deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_1_95wblh8q_.log deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_sysaux_95wbkybz_.dbf deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_undotbs2_95wbkycy_.dbf deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_system_95wbkybb_.dbf deleted
auxiliary instance file /tmp/TRAINEE/controlfile/o1_mf_95wbkpvj_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/16/2013 14:56:16
RMAN-06963: Error received during import of metadata
RMAN-06961:    IMPDP> ORA-39123: Data Pump transportable tablespace job aborted
ORA-01565: error in identifying file '/oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3

Hi,
Cloud you please cheek below link:
ORACLE Cookies: TSPITR to recover a dropped tablespace
Thank you

Undo tablespace recovery from RMAN backup

Hi,
Lets's assume we have RMAN backup and archivelog backups, and now
my undo tablespace's disk crashed ,how can i recover?
Can i recover while database is up?
Thanks,
Kumar.

to recover UNDO tablespace from RMAN backup you must shutdown the database and start it in the MOUNT state to recover the missing files as follows
rman target /
RUN
STARTUP MOUNT;
ALLOCATE CHANNEL ch3 TYPE Disk;
RESTORE datafile 'c:\u01\prod3\undo01.dbf';
RECOVER datafile 'c:\u01\prod3\undo01.dbf';
ALTER DATABASE OPEN;
RELEASE CHANNEL ch3;
hope this will help you

How to backup read only tablespace in rman

Hi,
I am using oracle 10gR2 in solaris 10.
I am taking Rman full backup using catalog.
My target database have 5 datafiles, in that one datafile is in read only mode.
When I issue the backup command in rman. it takes only 4 datafiles. its not taking the readonly datafile.
I want to take backup of all 5 datafiles.
kindly help me..
Many Thanks

My target database have 5 datafiles, in that one datafile is in read only mode.I presume that you mean to say that 1 Tablespace consisting of 1 datafile is Read Only.
What does SHOW ALL in RMAN present ?
If you have BACKUP OPTIMIZATION set to ON, the Read Only Tablespace will not be backed up after the first backup.
You could still explicitly backup the tablespace with a BACKUP TABLESPACE tablespacename; , although a BACKUP DATABASE would exclude it.
Hemant K Chitale
http://hemantoracledba.blogspot.com
Edited by: Hemant K Chitale on May 3, 2010 12:02 AM

How to exclude tablespace UNDOTBS1 from backup in OEM

I use OEM to backup our database (11.2 on Redhat 2.6.18-92.el5 ). It take quite a bit time and disk space (32gb) to backup the UNDOTBS1 table space. I do not think that we need undo tablespace for a recovery. If this is correct how can I excludeit from the backup. OEM allow to exclude data tablespace from backup but not UNDOTBS1.
Thanks

To create a physical standby you need the entire database. Not just parts of it. The only thing at the standby system that will be different is the controlfile (it will be a standby controlfile) and the spfile. Everything else will be exactly the same. Locations of the files can differ of course if you set the appropriate parameters.
Please make sure you have read Chapter 3 "http://download.oracle.com/docs/cd/E11882_01/server.112/e10700/create_ps.htm#i63561" of the Data Guard Concepts and Administration manual.
You can use the RMAN qualifier FROM ACTIVE DATABASE to the DUPLICATE FOR STANDBY command to avoid the need for interim storage for the backup. That method streams the backup from the Primary directly into the standby server. Refer to Chapter 2 of our book "Oracle Data Guard 11g Handbook (http://www.amazon.com/Oracle-Guard-Handbook-Osborne-ORACLE/dp/0071621113)" for details.
Since you are using OEM, make sure you are using 10.2.0.4/5 Grid Control. The Data Guard standby creation wizard has a new option to use this RMAN option. It is the first selection on the type of backup page. (To get to the DG pages select your Primary database from the Database Targets page and then select the Availability tab, and then under Data Guard select the Add Standby Database link).
As for block change tracking, since we all thought you were just doing a backup and did not realize you were trying to create standby BCT can help make it faster. However it does not apply in this case.
Larry

RMAN Backup specially for tablespaces

Hi@everybody,
we have a Oracle 11gR2 (11.2.0.3.0) Server, based on RedHat 6, running in our company. For the Backups i'm using RMAN with a script. In that script this code specially creates the backup:
        run {
            allocate channel oem_backup_disk1 type disk;
            backup incremental level ${level} cumulative as COMPRESSED BACKUPSET tag '${tag}' database;
            backup as COMPRESSED BACKUPSET tag '${tag}' archivelog all not backed up;
            release channel oem_backup_disk1;
${level} is for 0 or 1, full backup or incremental backup. ${tag} is the name for the backup. This script is for the hole database. But now i want to change that script to tablespace level. We have some "test" tablespaces, where a backup is not needed. I just found that one:
backup tablespace TEST tag='BACKUP_TEST';
But now i'm not shure how i can implement that into my script.
Can you guys help me?
Thanks and best regards,
David

I've just to ask again to understand it right:
In RMAN - Console i just exclude the tablespaces that should not be backed up with:
CONFIGURE EXCLUDE FOR TABLESPACE Tbs1, tbs2, tbs5;
And then RMAN knows, when he is doing a backup of the database, he will exclude that tablespaces that i've told him? Thats awesome! And easier to handle!
EDIT: I've tested this on my Oracle Test server and it works! Thanks a lot for the answers!

Rman backup for tablespaces

Dear,
i want to use rman to backup the tablespaces. I have write a pram file as below.
owner=database
file=c:/backup/database.dmp
log=database.log
buffer=81920
How can i run this file from rman
ManyThanks

It appears that you have created a parfile for the export utility and NOT for RMAN. The basic command to backup a tablespace in RMAN is:
RMAN> BACKUP TABLESPACE USERS;If you are looking to actually export a tablespace, you can save the following to a file called user_parfile.txt
userid=system
file=d:\user_exp.dmp
log=d:\user_exp.log
tablespaces=users
buffer=81920and execute as:
exp parfile=d:\user_parfile.txt

Configure exclude for tablespace does not work.

I have to exclude a tablespace from my full database backups. I have Level-1 and Level-0 backup script.
run the following command as per documentation.
CONFIGURE EXCLUDE FOR TABLESPACE DATA_TEMP;
To reconfirm, if exclude is set.
run SHOW ALL;
it shows that exclude is set properly.
Now i have to restore on another machine and before running the restore i run
RESTORE DATABASE PREVIEW, just to confirm if backup health is ok.
it gives me error
RMAN-00571: =========================================================
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ================================================
RMAN-03002: failure of restore command at 09/28/2007 05:57:32
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 10 found to restore
The datafile 10 mentioned in the above error is the 'DATA_TEMP' tablespace which was excluded before taking the backup.
Restoring the database with RESTORE DATABASE command goes fine and restores the tablespace "DATA_TEMP".
My question is why RMAN have backuped up a tablespace which is in the exclusion list. i think rman reads its environment settings before starting a backup.
Have any one have experienced this before. the documentation says nothing about this.
Thanks.

sql> restore database preview;
The above command workd fine in 10.2.0.3.0.
But in 10.1.0.5.0 it does not works.

Backing up and restoring tablespaces with RMAN

We have some tables that we want to backup and other tables that we don't.
We are separating these tables by tablespaces and schema.
SchemaA uses tablespaceA
SchemaB uses tablespacesB
We are also backing up
sys
sysaux
undo
tablespaces.
Lets say we lose our tablespaces and do a restore. I am assuming that all my stored procedures can be restored no matter which schema I save them in. even if I save them in a schema that has a default tablespace that is not being backed up because the code in is in the System tablespace.
Is my assumption correct?

Here the key concept is Mean Time To Recover(MTTR), usually it is faster and easier to use an export backup file for this purpose, but this doesn't mean RMAN is bad :) RMAN was, is and will be the best practice for Oracle's B&R.
Still you may assist your RMAN backup with a daily norows export backup and also maybe a file system backup depending on your environment and application's need. Backup's backup do not harm :)

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.

Oracle 9i RMAN backup filling up all disk and failing at the very end

Hello to all and thank you in advance for any input from any of you.
I am new in oracle and the only one in my company with a little bit of oracle knowledge, which is not a whole lot.
I inherited a few servers (Linux and Windows based). We mostly run all our production environment on a Linux box hosting oracle 10g release 10.2.0.1 but we had a legacy application server that still runs on 9i release 9.2.0.1.0. This server is a windows 2003 box, the previous DBA or someone else with admin rights to this machine compressed the whole drive where oracle resides, when I started summarying the oracle assets, I saw this server with no backups scheduled and a compressed disk with very limited space after this compression, only 13 GB left, the database if uncompressed would definitively filled up all the disk. The machine is in used and cannot be taken down for more than a couple of hours. We tried adding another disk but the machine only accept it as a hot spare. The database is in archive mode, when I tried to run a RMAN backup, it start filling up the database drive until it's empty and it crashes the whole machine, it seems like the buffer is growing and growing until it fills up the whole drive. The only way to get the server up and running again is to reboot the machine since the server is more than 6 years old we are not please with this action because we are afraid the machine would go south in one of those reboots.
Has anyone heard of similar issues when running RMAN on a compressed drive? Can the compressed disk have any involvement in this kind of odd behaviour? I tried running the backup in debug mode and creating a log in a different disk (the one where the backup is going to) and still the same issue. Again any help is much appreciate,
Sincerely,
Alex

Sybrand,
Thank you for your fast response, I am going to use your previous post to answer one by one your question,
1 The Oracle binaries --- on a compressed drive > Yes
2 The Oracle database control files redo log files and datafiles on that same compressed drive? > Yes
3 The archived redo log ditto? > Yes
I know for a fact (as I have been using that in 9i) you can create a RMAN backup on a compressed drive, and you can have your archived redo go to a compressed drive. No problemo! > Excellent good news!!!
But I would never touch the data files. Please note backup sets are multiplexed files consisting of multiple datafiles, so RMAN would need to do some calculations to decompress several blocks at the same time and to calculate a new block and compress it.
Do you have enough space to:
a) (preferred) to make datafile copies instead of a backup >
Not in the drive that hosts the oracle instance but yes on an external usb drive (1TB) I attached to use as a backup repository, maybe this is why I am having these issues. I only have 13 GB left on that drive where the oracle instance resides (actually as I explained in a previous reply to Mark, the server only has 3 slots for disks, two of them as configured as RAID 1 and the other is a hot spare because the RAID configuration manager cannot can only added as hot-spare. The raided disk are partitioned in two, one small partition is for the OS and the other is for the oracle instance). When you said make a copy of the datafiles, I assumed you are talking about doing manual backups, and copying the database after using using "alter tablespace tablespace_name begin backup; then copy the file; alter tablespace tablespace_name end backup;
b) use filesperset=1 on the backup command line, so the multiplexing (and associated calculations) stop. I have not tried the option of fileperset yet but I can tryi it and see if that helps.
Can you post the last few lines of the RMAN log where RMAN bombs out? Note: the last few lines. Not all of it, or you must send some paracetamol in conjunction! >
When I ran the debug option, I stopped the backup at less than 20% because I didn't want to reboot the system in the middle of the production time, the backup consumed at least 3 GB during the time was running. The times I ran the RMAN backup I didn't used the debug option so I don't have a log long enough to send unless you want the last few lines of what I have.
Thanks again for your input,
Sincerely,
Alex

Rman backup 11g rel2

Hello Guys
I was testing rman backup on oracle 11g rel2 , logging time for backup using rman as in 2 ways 1) full database backup
2)full database backup /parallel feature say "section size 200M" in script
i was expecting due to new 11g feature option 2 should complete faster ,but its reverse without using this feature
its running more fast (completing by 4-5 minutes less time)
I also tried taking backup of 1 datafile or 1 tablespace using both the option and also placing backupsets
on different folders/mountpoints ,but result is same
if you had worked on this feature ,please give details what is benefit of using this feature,i can see disadvantage here
Thanks

804719 wrote:
so without section size this operation is not actually parallelYes, it's not parallel for datafile, but it parallel for the entire job.
You can analyze the backup log. It should contains the records about opening several channels simultaneously, for instance:
Starting backup at 26/04/12 23:14:19
channel tape1: starting full datafile backup set
channel tape1: specifying datafile(s) in backup set
input datafile file number=00049 name=/home/oracle/oradata/...
channel tape1: starting piece 1 at 26/04/12 23:14:21
channel tape2: starting full datafile backup set
channel tape2: specifying datafile(s) in backup set
input datafile file number=00050 name=/home/oracle/oradata/...
channel tape2: starting piece 1 at 26/04/12 23:14:22
channel tape3: starting full datafile backup set
channel tape3: specifying datafile(s) in backup set
All within 3 seconds, and working in parallel...

RMAN Backup Clone

Hi All,
Oracle 10gR2. Usual RMAN backups are taken to tapes using HP Data Protector.
Want to create a RMAN secondary backup (daily full backups) on the same SAN storage.
So that we can restore very fast.
What options do I have to take the backups.

Hi,
With backup as copy feature;
in a case of failure, you can benefit the following example cases:
RMAN> SWITCH DATABASE TO COPY;
RMAN> sql 'alter tablespace users offline';
RMAN> switch datafile 4 to copy;
RMAN> recover datafile 4;
RMAN> sql 'alter tablespace users online';
What i understood is you have a production database which you backup to tape with HP data protector now.
And i offer you forget direct backup to tape and, backup it to disk (FRA) first , then from FRA to tape.
But you mention about primary database in your second post, do ypu backup from standby or something else?

Restore a single tablespace from full backup erroring out

Hi,
I have backed up the full database using RMAN:
$ rman catalog rman/rman@catdb target /
RMAN> run {
backup as compressed backupset
format '<Full Path>/databkp/DATA_%d_%s_%p'
database
plus archivelog format '<Full Path>/arcbkp/ARC_%d_%s_%p';
Backup was successful.
Now dropped the tablespaces:
SQL> alter tablespace rtestusr offline;
SQL> drop tablespace RTESTUSR including contents and datafiles;
Now trying to restore the tablespace RTESTUSR
$ rman catalog rman/rman@catdb target /
RMAN> restore tablespace rtestusr;
Starting restore at 25-FEB-11
starting full resync of recovery catalog
full resync complete
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/25/2011 14:28:47
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20202: tablespace not found in the recovery catalog
RMAN-06019: could not translate tablespace name "RTESTUSR"
Also performed the Tablespace Point-in-time recovery:
RMAN> run {
2> set until time "to_date('2011-02-25:12:44:00','yyyy-mm-dd:hh24:mi:ss')";
3> restore tablespace RTESTUSR;
4> }
executing command: SET until clause
Starting restore at 25-FEB-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=46 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=45 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=44 devtype=DISK
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00006 to /dev2db/rmantst/db/oradata/rtest/rtestusr01.dbf
channel ORA_DISK_1: reading from backup piece /dev2db/rmantst/archrtst/databkp/DATA_RTEST_76_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/dev2db/rmantst/archrtst/databkp/DATA_RTEST_76_1 tag=TAG20110225T114341
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/25/2011 15:07:42
ORA-19654: must use backup control file to switch file incarnations
Please help.
Thanks in advance.
Regards,
Bikram

I think you misunderstand some concepts.
1) drop tablespace RTESTUSR including contents and datafiles;
is a valid command, it removes the named tablespace from the database. There's nothing wrong with the database (although it may be a logical (human) error). Restore/recovery is used to repair media failures. RMAN is right: 'RMAN-06019: could not translate tablespace name "RTESTUSR"', since there's no such tablespace in the actual database, the restore/recover process fails.
2) Unfortunately you hide your database version. Up to 10gR2 tablespace point-in-time recovery cannot be used to recover dropped tablespaces, in 11gR1 and higher it's possible.
And - TSPITR - requires a little bit more than 'set until ...'. Refer to the doumentation for your unknown database version.
Werner

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)

Exclude a tablespace in rman backup

Similar Messages

Maybe you are looking for