RMAN Backup - space exhausted

Hi, Im just playing around with RMAN backups,
Im using 11gr2 on OEL 5.5 with ASM configured,
I have a FRA diskgroup which the full backup seems to be attempted to be saved to,
When openeing RMAN and connecting to the target database, I have issued a 'backup database' command to do a full backup, however I have encountered the following error, could anyone make a suggestion of how I can solve this? Please see terminal session below:
RMAN> backup database;
Starting backup at 15-NOV-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=253 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=+DG1/orcl/datafile/system.256.734901431
input datafile file number=00002 name=+DG1/orcl/datafile/sysaux.257.734901433
input datafile file number=00003 name=+DG1/orcl/datafile/undotbs1.258.734901433
input datafile file number=00005 name=+DG1/orcl/datafile/example.265.734901913
input datafile file number=00006 name=+DG1/orcl/datafile/test1.267.734907043
input datafile file number=00007 name=+DG1/orcl/datafile/test2.268.734909449
input datafile file number=00004 name=+DG1/orcl/datafile/users.259.734901433
channel ORA_DISK_1: starting piece 1 at 15-NOV-10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/15/2010 22:59:11
ORA-19510: failed to set size of 121610 blocks for file "+FRA/orcl/backupset/2010_11_15/nnndf0_tag20101115t225424_0.279.735173667" (block size=8192)
ORA-17505: ksfdrsz:1 Failed to resize file to size 121610 blocks
ORA-15041: diskgroup "FRA" space exhausted
RMAN>

806595 wrote:
I have found a good tutorial for anyone who may have the same question...
http://www.oracledistilled.com/oracle-database/quick-rman-configuration-for-disk-based-backups/
Thanks anywayWell, in addition to Erik's blog, you should look at this one as well,
http://blogs.oracle.com/AlejandroVargas/
HTH
Aman....

Similar Messages

Min space rman backup

dear all,
i have 11g oracle database and my database size is 120gb .how much hard disk space i must keep to take backup of my database using rman .my backup strategy is on sunday i take level 0 incremental backup and on mon,tue.wed,thurs,fri and sat i m taking incremental level 1 differential backup.so how much minimum space i must keep on my hard disk for 1 week rman backup? your help appreciated.
thanks and regards,

941949 wrote:
dear all,
i have 11g oracle database and my database size is 120gb .how much hard disk space i must keep to take backup of my database using rman .my backup strategy is on sunday i take level 0 incremental backup and on mon,tue.wed,thurs,fri and sat i m taking incremental level 1 differential backup.so how much minimum space i must keep on my hard disk for 1 week rman backup? your help appreciated.
thanks and regards,
This is a question I'm having to answer as well. There are a lot of variables that determine how much space will be needed in any particular circumstance and the guidelines are only just that, guidelines. I read the links presented by Abufazal and while they are as good a starting point as any, you really have to read them with a critical eye and a firm understanding of your own backup and recovery requirements. Ultimately the only way to know how much space is going to be needed is to run the backups and see.

RMAN backup uses more space than actual DB size

Hi All,
Yesterday, we have configured the RMAN backup for an RAC db in HP-UX. The total DB size is 82GB
but the RMAN took around 250G space for backup and the backup failed. The oracle db is 10.2.0.1.
$ ls -artl
total 520626852
drwxr-xr-x 23 root root 8192 Feb 10 15:49 ..
drwxr-xr-x 2 root root 96 Feb 10 16:09 lost+found
-rw-rw-rw- 1 oracle dba 290 Feb 10 20:35 backup.log
-rw-rw---- 1 oracle dba 22768640000 Feb 10 21:30 bk_4_1_678488912
-rw-rw---- 1 oracle dba 37469036544 Feb 10 21:40 bk_3_1_678488912
-rw-rw---- 1 oracle dba 28807331840 Feb 10 21:52 bk_5_1_678490229
-rw-rw---- 1 oracle dba 22659448832 Feb 10 22:01 bk_6_1_678490845
-rw-rw---- 1 oracle dba 22775595008 Feb 10 22:14 bk_7_1_678491581
-rw-rw---- 1 oracle dba 19507593216 Feb 10 22:15 bk_8_1_678492076
-rw-rw---- 1 oracle dba 18644811776 Feb 10 22:29 bk_9_1_678492883
-rw-rw---- 1 oracle dba 19040927744 Feb 10 22:31 bk_10_1_678492958
-rw-rw---- 1 oracle dba 18791776256 Feb 10 22:44 bk_11_1_678493794
-rw-rw---- 1 oracle dba 15491096576 Feb 10 22:45 bk_12_1_678493889
-rw-rw---- 1 oracle dba 19860652032 Feb 10 23:00 bk_13_1_678494656
-rw-rw---- 1 oracle dba 20742381568 Feb 10 23:01 bk_14_1_678494701
drwxrwxrwx 3 oracle dba 1024 Feb 10 23:01 .
Why this is happening ? Any bug or i am missing out anything. Please help.
Regards,
Anand.

We are using the belwo scripts,
rman target sys/system nocatalog msglog /backup/backup.log
RUN {
ALLOCATE CHANNEL ch00 TYPE DISK;
ALLOCATE CHANNEL ch01 TYPE DISK;
BACKUP
INCREMENTAL LEVEL=0
SKIP INACCESSIBLE
TAG hot_db_bk_level0
FILESPERSET 5
FORMAT '/backup/bk_%s_%p_%t'
DATABASE;
sql 'alter system archive log current';
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00 TYPE DISK;
ALLOCATE CHANNEL ch01 TYPE DISK;
BACKUP
filesperset 20
FORMAT '/backup/al_%s_%p_%t'
ARCHIVELOG from time 'sysdate - 1' ;]
#For backing up the archive of the second server.
ALLOCATE CHANNEL ch02 TYPE DISK connect 'sys/system@qicdbr2';
BACKUP
filesperset 20
FORMAT 'al2_%s_%p_%t'
ARCHIVELOG from time sysdate - 1 ;
RELEASE CHANNEL ch02;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00 TYPE DISK;
BACKUP
FORMAT '/backup/cntrl_%s_%p_%t'
CURRENT CONTROLFILE;
RELEASE CHANNEL ch00;
RMAN> LIST BACKUPSET SUMMARY;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
1 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
2 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
3 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
4 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
5 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
6 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
7 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
8 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
9 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
10 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
11 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
12 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
RMAN> show all;
using target database control file instead of recovery catalog
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 OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/orahome/OraRAC/dbs/snapcf_QICDB1
.f'; # default

Error , ORA-19809 & ORA-19804 While restoring RMAN backup .

Hi Experts,
I am restoring production RMAN backup to UAT . Using below steps
1)rman target=/
2)RMAN> startup nomount;
3) RMAN> restore controlfile from '/orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl';
Starting restore at 05-AUG-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=3 device type=DISK
channel ORA_DISK_1: copied control file copy
output file name=+DATA_ACME/acme/controlfile/current.256.724845209
output file name=+DATA_ACME/acme/controlfile/current.257.724845209
Finished restore at 05-AUG-10
4) RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
5) RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME1/current/%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
new RMAN configuration parameters are successfully stored
6) RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
7) RMAN> CATALOG START WITH '/orabkdump/Rman_Bak/ACME';
searching for all files that match the pattern /orabkdump/Rman_Bak/ACME
List of Files Unknown to the Database
=====================================
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
List of Files Which Where Not Cataloged
=======================================
File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
RMAN-07517: Reason: The file header is corrupted
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
RMAN-07517: Reason: The file header is corrupted
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
RMAN-07517: Reason: The file header is corrupted
8) RMAN> run {
2> set until sequence 1789 thread 2;
3> restore database;
4> recover database;
5> sql 'alter database open resetlogs';
6> }
executing command: SET until clause
Starting restore at 06-AUG-10
using channel ORA_DISK_1
Finished restore at 06-AUG-10
Starting recover at 06-AUG-10
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=2803
channel ORA_DISK_1: restoring archived log
archived log thread=2 sequence=6051
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=2804
channel ORA_DISK_1: reading from backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/06/2010 23:10:38
ORA-19870: error while restoring backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 49283072 bytes disk space from 5218762752 limit
** My UAT database should be in noarchival mode . Generally such errors have been observed during backup , but have no clue why they occurred during recovery .Please advice .
Thanks
Edited by: user11981514 on Aug 6, 2010 9:46 AM

Hi,
Since the error ORA-19809 indicates the lack of space in flash recovery area during the media recovery, I suggested increasing the value of the parameter DB_RECOVERY_FILE_DEST_SIZE.
Yes, during the media recovery the RMAN will restore the archived log to the default destination (only if the required archived logs are not already on the disks).You can confirm the restore location of the archived log in RMAN restore log/destination specified by parameters log_archive_dest_1/db_recovery_file_dest.
Regards,
Vaibhav

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 slow

Hi,
I have a Production Database (10204) running on HP Unix (B.11.11).
Daily morning 6AM, a full RMAN backup runs. The db size is only around 225GB. But it takes 4.5 hours to complete.
The syntax which I use is given below.
RMAN> run {
     allocate channel ch1 type "sbt_tape";
     allocate channel ch2 type "sbt_tape";
     allocate channel ch3 type "sbt_tape";
send
'NB_ORA_CLIENT=jjcprd04-back.backup.ncsus.jnj.com,NB_ORA_POLICY=JJCPRD04-RMAN';
     backup
     format 'bk_%s_%p_%t'
     (database include current controlfile);
     sql 'alter system archive log current';
     backup
     format 'arch_%d_%s_%p_%t'
     (archivelog all delete input );
Is there a way to increase the speed of this backup? Currently the backup is way too slow as it takes 4.5 hours to copy 225GB of data!
Thanks!

I'll start by stating that backups directly to tape are generally quite slow.
I'd still recommend moving to disk backups though... and just archiving it to a tape...Hi Jony,
You can of course backup to disk. Thats a common solution. But you have to deal with space more than everything. In addition to that backing up to disk does not free you from moving/copying your data - depending on your backup strategy - to a long-term storage.
So you have two different and not conjunct backup operations: the rman backup itself and the job which backups the rman area to another media.
In recovery cases you might end up with RMAN requesting older backupsets which are not on disk anymore. This will most probably lead to recovery failures and manual intervention which is not desirable in recovery scenarios.
Another point is the control of the data flow. Backing up via a MML (i.e. "to tape") does not necessarily mean "to tape". Instead it means "to the backup software" which is responsible for managing the backup data. Common scenarios involve backing up the full backups via SAN directly to tape and backing up the archivelogs or incremental backups over LAN which will be stored by the backup software on a hard disk and later copied and/or moved on to tape. The data flow (to SAN / to disk / whereever) is solely controlled by the backup software.
The advantage here is one continuous backup and restore job. The backup software deals with "where is my saveset located" and requests automatically the needed tapes or disks in recovery scenarios. This makes recoveries far more flexible and comfortable.
Regarding the throughput i have set up a rather large OLTP database ( 12 TB currently) which is backed up with EMC Networker. Full backups are written via SAN directly to tape. The average speed with four LTO-3 drives is approx. 550 MB/s (the tape drives compress the data in hardware; the database itself is text-only and seems rather good compressable). I guess thats not too bad.
you can also compress the BACKUPSETS (this generates a little more CPU but less network IO)He said he is on HP-UX. These kind of CPUs tend to be not that fast. Using compression is an option worth testing but there is another point to test when doing compressed backups: The RESTORE TIME.
Ronny Egner
My Blog: http://blog.ronnyegner-consulting.de

Need to Configure RMAN backup in 8.1.7.4.1

I have been asked to design a backup and recovery strategy for our production and test databases
I got 2003 Enterprise server with 3 disks of each 300gb.
There are 10 databases running in versions 8,9,10 with 5 production and 5 UAT database.
The sum of the Db will be around 70Gb
I got 200Gb free space in 2 disks
how can i design a BACKUP startegy here. I have palnned to use RMAN backups.
Any useful links and proper guiding from you people expected.
Right Now there is only export backup in Night.
I have informed them we are running the Db in risk,.They have asked me to comeup with a plan.
Any help please
Message was edited by:
Maran.E

Maran,
>
Is it possible to backup 8.1.7.4.1 by 10g database.
i can create a recovery catalog in 10g and wil i be able to backup a 8 and 9 Db
>
I have test 10g catalog with 9i. No idea with the 8i.
I guess, 8i(817) is more comportable with 10g and it should work.
Have a try with your test database and also cross check the metrix with different version in the Metalink.
Jaffar
Good news Maran,
I just come across of the following note which explains the RMAN compatibility between 8 - 10g versions.
RMAN Compatibility Oracle8i 8.1.7.4 - Oracle10g 10.1.0.4
Doc ID: Note:307022.1
In case, if you dont have access to metalink, the punch line from the note is :
SUMMARY
=======
Is best practice to use 'rule of thumb'. Always used the target database RMAN executable and the latest release of Oracle for your recovery catalog.
If you are going to use a lower version RMAN executable to backup higher version databases remember you are restricted to only the features available
in the database your using. But the executable you are using must be able to handle the feature or configuration you are using. Case and point the
RMAN-06466 error above where in 9.0.1 there is no concept of "AS BACKUPSET".
Because configure commands were executed some options in the controlfile were not understood when parsed by the lower version RMAN.
Message was edited by:
Syed Jaffar

How to ensure the rman backup is successful?

Hi,
we have scheduled rman backup jobs.
1. But how do we ensure all the rman backups are successful?
2. if the rman writes directly to tape, how do we ensure all tape backups are successful?
thanks
andrew

But what is incremental merge, couldn't find in the 10g manual?check it out on http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmquick.htm#BRADV89354
do you use image backup in real production environment?Of course. We have a standard to to use image copies that way.
what do you suggest to do with rman normal way of backup or go for image backup?Depends on your specific situation. Like anything else, I prefer to provide some rationale on the recommendation.
Image Copies with Incremental Merge
Pros:
(1) one one full backup taken ever; no need to take another full backup
(2) the restore time is the same, regardless of the day of the week the db failed
(3) every day the incremental merge's success means the backup was good - an automatic validation
(4) it allows you to quickly switch to copy, rather than restore
Cons:
(1) Space requirement is more (since it's a bit to bit copy)
(2) can't do a point in time recovery from the disk alone
(3) can't go to the tape directly; must be a disk based backup.
Backupsets with Incremental Backup
Pros:
(1) space requirement is lower (since only never-used blocks are not copied)
(2) point in time recovery is possible
(3) direct backup to tape possible (no need for disk backup)
Cons:
(1) restore time varies depending on the day of the week the db failed
(2) you have to take a full backup regularly, perhaps once a week
(3) no validation unless you use validate backupset (takes resources)
So, as you can see, there are pros and cons to each approach. You have to decide for yourself which one weighs more (or less) to come to a conclusion.
Hope this helps.
Arup Nanda

Delete RMAN backup

Oracle 11.2.0.1
Windows
I takes RMAN backup at D:\RMAN_BAKCUP of our test database. Now there is space problem, I have to allocate some space to other folder. I shall take cold backup of database by shutdown. How do I start to delete RMAN backup from above location. It is incremental backup. What precautions should be there while deleting RMAN backup with archive logs.
Can I delete all archive logs too after consistent backup by shutting down the database ?
I am facing space problem, thats why I though that I shall take cold backup of db and now no need of rman backup as well as archive logs. Am I correct ?
Thanks.

user12050217 wrote:
Oracle 11.2.0.1
Windows
I takes RMAN backup at D:\RMAN_BAKCUP of our test database. Now there is space problem, I have to allocate some space to other folder. I shall take cold backup of database by shutdown. How do I start to delete RMAN backup from above location. It is incremental backup. What precautions should be there while deleting RMAN backup with archive logs.
Can I delete all archive logs too after consistent backup by shutting down the database ?
I am facing space problem, thats why I though that I shall take cold backup of db and now no need of rman backup as well as archive logs. Am I correct ?
Thanks.Given what else I've read in this thread (test database, no need for point in time recovery, etc.) A 'cold' backup may be appropriate, but I'd still use rman to do it. I have a similar situation right now with one of my test databases. I took an rman cold backup (database is open MOUNT) with KEEP UNTIL 'SYSDATE + 60'. Once, sometimes twice, a day the developer asks for a restore to the backup. Piece of cake with rman, especially with a little script all ready to go. Would be a bit more difficult with a 'user managed' backup.

Need best practices PROCESS to schedule RMAN Backups.

Hi All,
I would like a suggestion on the following for RMAN Backups:
Details:
Database: - 11gR2, Size 3TB on ASM - DW database.
Like suggestions on:
1) What kind of backups to schedule - Incremental along with Block backups?
2) Size required to allocate for the Backup Space - Can it be ASM or Disk Space?
3) Anything else - please suggest.
Thank you.

For that size, you might do weekly L0 and daily L1 (differential) backups. Try to do L1 (cumulative) backups if possible.
Getting the total sizes of Segments (from DBA_SEGMENTS) will give you an approximation for the minimum size. (Tables/Indexes that have been dropped and are no longer in DBA_SEGMENTS wouldn't appear but the underlying blocks for them if unused by other Tables/Indexes would still be backed up as they'd have been formatted).
You could run the Backup as a COMPRESSED BACKUPSET to reduce the size.
Whether you want ASM or FileSystem depends on your comfort level. If you run backups to ASM, you can only use RMAN to backup from ASM to Tape. However, backups on FileSystem can be copied to tape using any other method (tape backup utility). Also consider if you want to replicate/copy the backups to other servers and what methods you'd have available.
Hemant K Chitale

RMAN backup destination

Hi
Is there any way to mention the RMAN backup destination for datafiles and archivelog files with their exact name?
e.g
backup as backupset
format 'c:\backup\'
filesperset 1
database plus archivelog all;
Backup will be stored in c:\backup with the actual name of the files.
Destination has to be other than the FRA.
Regards

Does this mean if I use non FRA then 'delete force
noprompt obsolete;' will not delete the obsole
backups from non FRA destinations?
-- but I have checked it is deleting even from the
non FRA location also.
no i didnt mean to say that i mean to say if you dont use FRA for backup strategy then you are also not using OMF (Oracle managed files) cause one of the parameter db_recovery_file_dest_size define location of RMAN backups which enable also the OMF and its advantegous to use OMF cause it reduce wasted disk space consumed by obsolete files by deleting itself when FRA pressure goes to 85%.
You can mock up this situtaion by enabling FRA which in turn enable OMF and start taking backup iteratively when oracle see the space goes to 85% then OMF will remove the earliest obsolete files,you can check it in yours oracle alert log files where you will find
Deleted oracle managed files '<filename>'
I hope yours confusion is cleared now.
Khurram

RMAN backup archivelog all delete input

Hello DBAs,
what does this command will do?
RMAN> backup archivelog all delete input;
DN

I have set cron job for RMAN> backup archivelog all delete input; and its work.
But I got following message in my log file.
Please give ur feed back.
Recovery Manager: Release 10.1.0.4.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
RMAN>
connected to target database: SIDNAME (DBID=XXXXXXXX)
using target database controlfile instead of recovery catalog
RMAN>
Starting backup at 10-FEB-06
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=269 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=268 devtype=DISK
channel ORA_DISK_1: starting compressed archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=5701 recid=2412 stamp=581958928
input archive log thread=1 sequence=5702 recid=2413 stamp=581961105
input archive log thread=1 sequence=5703 recid=2414 stamp=581964532
input archive log thread=1 sequence=5704 recid=2415 stamp=582025325
input archive log thread=1 sequence=5705 recid=2416 stamp=582029976
input archive log thread=1 sequence=5706 recid=2417 stamp=582031922
channel ORA_DISK_1: starting piece 1 at 10-FEB-06
channel ORA_DISK_2: starting compressed archive log backupset
channel ORA_DISK_2: specifying archive log(s) in backup set
input archive log thread=1 sequence=5707 recid=2418 stamp=582037207
input archive log thread=1 sequence=5708 recid=2419 stamp=582038471
input archive log thread=1 sequence=5709 recid=2420 stamp=582043538
input archive log thread=1 sequence=5710 recid=2421 stamp=582048518
input archive log thread=1 sequence=5711 recid=2422 stamp=582055205
channel ORA_DISK_2: starting piece 1 at 10-FEB-06
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/10/2006 18:00:
12
ORA-19502: write error on file "/u02/backup/backup_6ehb2t97_1_1", blockno 6145 (
blocksize=512)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
channel ORA_DISK_1 disabled, job failed on it will be run on another channel
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/10/2006 18:00:
12
ORA-19502: write error on file "/u02/backup/6fhb2t97_1_1", blockno 6145
(blocksize=512)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
channel ORA_DISK_2 disabled, job failed on it will be run on another channel
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/10/2006 18:00:
12
ORA-19502: write error on file "/u02/backup/backup_6ehb2t97_1_1", blockno 6145 (
blocksize=512)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
RMAN>
Recovery Manager complete.
DN

Delete all AVAILABLE valid RMAN backup by RMAN command

Hi
We are taking RMAN full backup on disk every day. But right now we don’t have enough space on RMAN backup mount point. So we want to delete all AVAILABLE valid RMAN backup by RMAN command.
Please guide to delete all AVAILABLE valid RMAN backup by RMAN command.
-Thanks
Edited by: Fazlul Kabir Mahfuz on May 13, 2013 11:06 AM

You can do it by manually delete the backups and archivelogs from OS location. Then use below commands
RMAN>crosscheck backup;
It will give status as EXPIRED for backups which are valid but not available at OS level.
RMAN>delete expired backup;
Delete all the backups whose status are EXPIRED from database level.
Similarly for archivelogs
RMAN>crosscheck archivelog all;
RMAN>delete expired archivelog all;

Compressing rman backup

Hi all,
My database is growing up adn becomes very big, i have a problem of the backup because when i take full backup it gives error of disk space. I want to reduce the size of my backup and i know the existance of compressing rman backup.
My question is how to set rman compressed backup and is compress option working for incremental backup or not. I want this because i'm taking full backup once a week ansd incremental backup every monday till saturday.
Thanks for the help
Ratsarevo.

Hi,
Thanks all for your replies, No i'm reassured for my backup type.
Here is my backup configuration:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/data1/rman_backup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/data1/rman_backup/%d_%T_%U';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/data2/rman_backup/%d_%T_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/data1/rman_backup/snapcf_abdb.f';
Is it good for compressed backup ?
Thanks

RMAN Backup - space exhausted

Similar Messages

Maybe you are looking for