RMAN backup time increased

Hi All,
I need details about some diagnostic test regarding RMAN backup on my instance.
The following are the current configuration of details:
SQL> select release_name from fnd_product_groups;
RELEASE_NAME
11.5.8
SQL> select * from v$version;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
PL/SQL Release 9.2.0.8.0 - Production
CORE 9.2.0.8.0 Production
TNS for Solaris: Version 9.2.0.8.0 - Production
NLSRTL Version 9.2.0.8.0 - Production
===============================================
Database Size
1.5 TB
Earlier the RMAN backup used to take 20 -23 hours, now for the last 2 months, it has started taking 40 hours.
We want to identify the reason behind the increase in time.
Please let us know methods that we can use to diagnose the root cause.
Thanks
Peeks

Hi Talip,
Thanks for you suggestions.
I tried the three queries suggested by you, please find below the output:
SQL> select set_stamp from v$backup_async_io where to_date(open_time,'dd.mon.rr')='05.mar.12';
SET_STAMP
777154038
777154038
777154038
777154038
777154038
777154038
777154038
777154038
777154038
777154038
777167658
SET_STAMP
777167658
777167658
777167673
777167673
777167673
16 rows selected.The we checked the effective_bytes_per_second "mb/sec" column for the 777154038 and 777167658 Set_stamps.
SQL> select device_type "Device",
type,
open_time,close_time,
elapsed_time/100 "Ela",
effective_bytes_per_second/1024/1024 "mb/sec",
filename
from v$backup_async_io
where set_stamp = &a
order by close_time desc; 2    3    4    5    6    7    8    9
Enter value for a: 777154038
old   8: where set_stamp = &a
new   8: where set_stamp = 777154038
Device          TYPE      OPEN_TIME       CLOSE_TIME             Ela     mb/sec FILENAME
SBT_TAPE        OUTPUT    05-MAR-12       05-MAR-12            13498 3.03509712 bk_87606_1_777154038
SBT_TAPE        OUTPUT    05-MAR-12       05-MAR-12            13475 3.03425884 bk_87605_1_777154038
DISK            AGGREGATE 05-MAR-12       05-MAR-12            13476   3.041852
DISK            INPUT     05-MAR-12       05-MAR-12             2832 2.90395451 /u1141/oradata/PRD1/rbs03.dbf
DISK            AGGREGATE 05-MAR-12       05-MAR-12            13446 3.0486393
DISK            INPUT     05-MAR-12       05-MAR-12             2829 2.90703392 /u1141/oradata/PRD1/rbs01.dbf
DISK            INPUT     05-MAR-12       05-MAR-12             5332 3.07276821 /u1140/oradata/PRD1/ard01.dbf
DISK            INPUT     05-MAR-12       05-MAR-12             5314 3.08317661 /u1140/oradata/PRD1/applsysx01.dbf
DISK            INPUT     05-MAR-12       05-MAR-12             5309 3.08608055 /u1140/oradata/PRD1/gld01.dbf
DISK            INPUT     05-MAR-12       05-MAR-12             5300 3.09132099 /u1140/oradata/PRD1/applsysd01.dbf
10 rows selected.
SQL> /
Enter value for a: 777167658
old   8: where set_stamp = &a
new   8: where set_stamp = 777167658
Device          TYPE      OPEN_TIME       CLOSE_TIME             Ela     mb/sec FILENAME
SBT_TAPE        OUTPUT    05-MAR-12       06-MAR-12            13323 3.07180786 bk_87607_1_777167658
DISK            AGGREGATE 05-MAR-12       06-MAR-12            13289 3.08224869
DISK            INPUT     06-MAR-12       06-MAR-12             2652 3.08898926 /u1141/oradata/PRD1/rbs02.dbf
DISK            INPUT     06-MAR-12       06-MAR-12             5330 3.0739212 /u1140/oradata/PRD1/invd01.dbf
DISK            INPUT     05-MAR-12       06-MAR-12             5305 3.08840752 /u1140/oradata/PRD1/arx01.dbf
SQL>The above output looks fine, but when i checked the long wait uery, it showed high percentage usage for OUTPUT streams. The below is the output:
TYPE        IO_COUNT      READY SHORT_WAITS LONG_WAITS    LIO_PCT FILENAME
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/applsysd01.dbf
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/applsysx01.dbf
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/ard01.dbf
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/gld01.dbf
INPUT           8225       7711           0        514 6.24924012 /u1141/oradata/PRD1/rbs01.dbf
INPUT           8225       7711           0        514 6.24924012 /u1141/oradata/PRD1/rbs03.dbf
OUTPUT         10222       7662           0       2560 25.0440227 bk_87605_1_777154038
OUTPUT         10242       7678           0       2564 25.034173 bk_87606_1_777154038
AGGREGATE      40995      38433           0       2562 6.24954263
AGGREGATE      40995      38433           0       2562 6.24954263
10 rows selected.
TYPE        IO_COUNT      READY SHORT_WAITS LONG_WAITS    LIO_PCT FILENAME
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/arx01.dbf
INPUT          16385      15361           0       1024 6.24961855 /u1140/oradata/PRD1/invd01.dbf
INPUT           8193       7681           0        512 6.24923715 /u1141/oradata/PRD1/rbs02.dbf
OUTPUT         10232       7669           0       2563 25.0488663 bk_87607_1_777167658
AGGREGATE      40963      38403           0       2560 6.24954227So, as per the output please suggest possible solutions to decrease the backup time, if not possible any other option.
Is there any problem with the tape device or is it an oracle issue.
Thanks
Peeks

Similar Messages

REDUCE RMAN BACKUP TIME

Hi,
We have are 800GB database and we take daily backup through RMAN.
Backup policy is LEVEL 0 on week end and LEVEL1 AND LEVEL2 on other days.
When we take the backup our system utilization become high and which is effecting our 24X7 service.
How can I reduce the load on the database during backup.
Thanks in advance.

if you have a physical standby in place , or if you can create one, use that to backup. Using standby will completely off load your backup time & performance impact
other wise use RATE in channel
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE <piecesize> K FORMAT '/backups/DBSID/DBSID.bkup.%U' RATE 2000000;

Rman Backup time error

Today i saw this error in our production backup time .
Please let me know how to leave out from this.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/27/2011 01:13:47
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 05/27/2011 01:10:52
ORA-19566: exceeded limit of 0 corrupt blocks for file
N:\USERS01.DBF
Regs,
Brij

Also, be aware that rman: backup validate (check logical) command could not show the corrupted blocks if that block are newer used(or used before, but freed later for example). In this case, rman validate does not populate V$database_block_corruption but it also does not allows you to continue with your backup.
So the solution will be, as previous posters said, either set the limit for the sustained number of corrupted blocks or format/repair the corrupted block.
For checking the corrupted blocks you could also use db verify utility(dbv). This will definitely show you the details about corrupted blocks, even they are not used ever.

Rman backup time

Hi,
can any one please provide me the query to find how much time takes to take the backup of the database.
backup is by rman, that may be any thing like level 0 or 1 or 2
thanks

Hi,
can any one please provide me the query to find how much time takes to take the backup of the database.Pleaserun this and post the result.
alter session set nls_date_format = 'yyyy-MON-dd hh24:mi:ss';
select backup_type,
incremental_level,
round(sum(original_input_bytes)/1024/1024,2) "MB in",
round(sum(output_bytes)/1024/1024,2) "MB out",
status,
min(start_time),
max(completion_time),
round((sum(output_bytes)/1024/1024)/((max(completion_time)-min(start_time))*86400), 1) "MB/s"
from v$backup_set_details
group by backup_type, incremental_level, status, session_key, session_recid, session_stamp
order by 6
Regards,
Tycho

DPM 2010 System Drive and System State backup times increased dramatically

Using DPM 2010 to backup several computers, hypervisors, and the DPM server it self, a stand alone server all of a sudden no longer backs-up within a reasonable amount of time. This is just happening on the C drive and System State. The D drive and all other
servers and hypervisors are running smoothly. You can see below that something changed on December 11th. Backups for those two items when from about an hour to over 10 hours each. This is causing all other backups that have yet to run to be canceled because
we do not typically like the backups to run during business hours.
No changes to the server had been made. Updates were not applied to that server until December 18th. The server has been restarted. The agent version is the latest v3.0.7706.0. Ran the command "vssadmin list writers", show no errors. Any insight
would be appreciated. Thanks in advance.

I updated the exclusions based on the following article using the executables and path listed in TechNet article above but to no avail. Verified AV policy applied.
https://kc.mcafee.com/corporate/index?page=content&id=KB68701
Will have to figure out how to disable AV during backups and enable after completions.
Will probably write a PowerShell script for this.

How to speed up rman backup?

Hi,
we are taking backup using rman. my database size is increasing.so rman backup time is increasing. so i want to spped up rman bakup performance. how to speed up rman bakup?
Thnaks,

My general request whenever you post the question in forum please start your question something like this:
Oracle Version : <4 digit version> select * from v$version;
OS Information with complete version and/or patch whatsoever.
1. http://www.oracle-base.com/articles/10g/RMANEnhancements10g.php
2. Re: RMAN Backup Script
and read the reply of Adith
You can also use set
CONFIGURE BACKUP OPTIMIZATION ON
Additionally review
Restarting and Optimizing RMAN Backups
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmbackp007.htm#i1006318
Best Regards
Girish Sharma

RMAN backup to SAN takes 13 hours

Hi All,
I have configured my RMAN to run through Recovery Catalog, and take daily full backup (limitation of Standard Edition) to a shared location on Test Server (\\testdb), which takes around 35 minutes to complete successfully.
The same full database backup takes 13 hours to complete on shared location to SAN storage mounted on blade server (\\blade5). To investigate further I opened an SR with Oracle Support and ran a series of test to take backup of a single tablespace (using target controlfile) on following 3 locations:
1. Local Hard disk of Production Server
2. Shared location on Test Server
3. Shared location to SAN storage mounted on blade server
Following were the results of the test:
1. The backup tablespace size is 1.36 GB with one datafile.
2. The backup piece size in all 3 test cases is 1.1 GB each.
3. RMAN Backup Time at 3 location:
3a. Local Backup Duration (D:\backup): 04:55 minutes
3b. Shared Backup Duration (\\testdbl): 02:25 minutes
3c. Shared SAN Duration (\\blade5): 26:25 minutes
Based on the above finding Oracle Support concluded that Oracle RMAN is perfectly fine and It is at the SAN that the problem resides, whereas the IT Admins state the problem is at the RMAN side.
My query is, how do we determine that Oracle RMAN is underperforming due to issues with SAN or blade server or network?
Regard,
Z.K.

ebrian wrote:
When the backup is running to the SAN, you may want to see what RMAN may be waiting for from V$SESSION/V$SESSION_WAIT. In addition, you may want to enable tracing during the backup to the SAN and see if anything stands out from the trace file:
rman target / log rman.log trace rman.trc debug
As per your suggestion, I carried out the test again with tracing enabled.
1 Tablespace [with 1 datafile] size 1.36 GB used for RMAN backup.
Backup piece size: 1.1 GB
Please find below output of V$SESSION/V$SESSION_WAIT for all 3 cases:
*1. LOCAL DISK*
--v$session
SADDR     SID     SERIAL#     AUDSID     PADDR     USER#     USERNAME     COMMAND     OWNERID     TADDR     LOCKWAIT     STATUS     SERVER     SCHEMA#     SCHEMANAME     OSUSER     PROCESS     MACHINE     TERMINAL     PROGRAM     TYPE     SQL_ADDRESS     SQL_HASH_VALUE     PREV_SQL_ADDR     PREV_HASH_VALUE     MODULE     MODULE_HASH     ACTION     ACTION_HASH     CLIENT_INFO     FIXED_TABLE_SEQUENCE     ROW_WAIT_OBJ#     ROW_WAIT_FILE#     ROW_WAIT_BLOCK#     ROW_WAIT_ROW#     LOGON_TIME     LAST_CALL_ET     PDML_ENABLED     FAILOVER_TYPE     FAILOVER_METHOD     FAILED_OVER     RESOURCE_CONSUMER_GROUP     PDML_STATUS     PDDL_STATUS     PQ_STATUS     CURRENT_QUEUE_DURATION     CLIENT_IDENTIFIER
5428E7D8     30     14290     0     5425FD54     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     6200:5792     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     0D779F90     888448358     RMAN.EXE     0     0000001 FINISHED     2940145100          2466540     -1     0     0     0     3/9/2009 10:31:32 AM     6     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
542B01C8     87     3021     0     54263FBC     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     6200:5792     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     0AA8F068     1819975476     RMAN.EXE     0          0          2466515     -1     0     0     0     3/9/2009 10:31:51 AM     12     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
542C84B8     128     3620     0     542643A4     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     6200:5792     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     05B36878     1141676395     05B36878     1141676395     backup full datafile: ORA_DISK_1     3173805813     0000014 FINISHED     4058944949     rman channel=ORA_DISK_1     2466514     -1     0     0     0     3/9/2009 10:32:13 AM     12     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
--v$session_wait
SID     SEQ#     EVENT     P1TEXT     P1     P1RAW     P2TEXT     P2     P2RAW     P3TEXT     P3     P3RAW     WAIT_TIME     SECONDS_IN_WAIT     STATE
128     751     async disk IO     count     1     00000001     intr     32     00000020     timeout     2147483647     7FFFFFFF     -1     0     WAITED KNOWN TIME
30     655     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     264     WAITING
87     135     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     9     WAITING*2. TESTDB*
--v$session
SADDR     SID     SERIAL#     AUDSID     PADDR     USER#     USERNAME     COMMAND     OWNERID     TADDR     LOCKWAIT     STATUS     SERVER     SCHEMA#     SCHEMANAME     OSUSER     PROCESS     MACHINE     TERMINAL     PROGRAM     TYPE     SQL_ADDRESS     SQL_HASH_VALUE     PREV_SQL_ADDR     PREV_HASH_VALUE     MODULE     MODULE_HASH     ACTION     ACTION_HASH     CLIENT_INFO     FIXED_TABLE_SEQUENCE     ROW_WAIT_OBJ#     ROW_WAIT_FILE#     ROW_WAIT_BLOCK#     ROW_WAIT_ROW#     LOGON_TIME     LAST_CALL_ET     PDML_ENABLED     FAILOVER_TYPE     FAILOVER_METHOD     FAILED_OVER     RESOURCE_CONSUMER_GROUP     PDML_STATUS     PDDL_STATUS     PQ_STATUS     CURRENT_QUEUE_DURATION     CLIENT_IDENTIFIER
54290D98     34     11745     0     542643A4     0     SYS     0     2147483644               ACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5156:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     05B36878     1141676395     00     0     backup full datafile: ORA_DISK_1     3173805813     0000012 STARTED     2679454996     rman channel=ORA_DISK_1     2467508     -1     0     0     0     3/9/2009 10:50:26 AM     12     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
54294FA8     41     13232     0     54263FBC     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5156:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     0AA8F068     1819975476     RMAN.EXE     0          0          2467521     -1     0     0     0     3/9/2009 10:50:03 AM     3     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
5429D3C8     55     4581     0     5425FD54     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5156:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     58565384     2746682842     RMAN.EXE     0     0000001 FINISHED     2940145100          2467505     -1     0     0     0     3/9/2009 10:48:48 AM     15     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
--v$session_wait
SID     SEQ#     EVENT     P1TEXT     P1     P1RAW     P2TEXT     P2     P2RAW     P3TEXT     P3     P3RAW     WAIT_TIME     SECONDS_IN_WAIT     STATE
34     788     async disk IO     count     1     00000001     intr     32     00000020     timeout     2147483647     7FFFFFFF     -1     0     WAITED KNOWN TIME
41     95     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     3     WAITING
55     655     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     132     WAITING*3. SAN blade5*
--v$session
SADDR     SID     SERIAL#     AUDSID     PADDR     USER#     USERNAME     COMMAND     OWNERID     TADDR     LOCKWAIT     STATUS     SERVER     SCHEMA#     SCHEMANAME     OSUSER     PROCESS     MACHINE     TERMINAL     PROGRAM     TYPE     SQL_ADDRESS     SQL_HASH_VALUE     PREV_SQL_ADDR     PREV_HASH_VALUE     MODULE     MODULE_HASH     ACTION     ACTION_HASH     CLIENT_INFO     FIXED_TABLE_SEQUENCE     ROW_WAIT_OBJ#     ROW_WAIT_FILE#     ROW_WAIT_BLOCK#     ROW_WAIT_ROW#     LOGON_TIME     LAST_CALL_ET     PDML_ENABLED     FAILOVER_TYPE     FAILOVER_METHOD     FAILED_OVER     RESOURCE_CONSUMER_GROUP     PDML_STATUS     PDDL_STATUS     PQ_STATUS     CURRENT_QUEUE_DURATION     CLIENT_IDENTIFIER
54294FA8     41     13257     0     5425FD54     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5804:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     58565384     2746682842     RMAN.EXE     0     0000001 FINISHED     2940145100          2468381     -1     0     0     0     3/9/2009 10:55:08 AM     169     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
5429D3C8     55     4725     0     542643A4     0     SYS     0     2147483644               ACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5804:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     05B36878     1141676395     00     0     backup full datafile: ORA_DISK_1     3173805813     0000012 STARTED     2679454996     rman channel=ORA_DISK_1     2468384     -1     0     0     0     3/9/2009 10:56:16 AM     166     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
542C2FC8     119     14058     0     54263FBC     0     SYS     0     2147483644               INACTIVE     DEDICATED     0     SYS     ISCO\zafferk     5804:5620     ISCO\DBSERVER     DBSERVER     RMAN.EXE     USER     00     0     0AA8F068     1819975476     RMAN.EXE     0          0          2468834     -1     0     0     0     3/9/2009 10:55:52 AM     8     NO     NONE     NONE     NO     SYS_GROUP     DISABLED     ENABLED     ENABLED     0
--v$session_wait
SID     SEQ#     EVENT     P1TEXT     P1     P1RAW     P2TEXT     P2     P2RAW     P3TEXT     P3     P3RAW     WAIT_TIME     SECONDS_IN_WAIT     STATE
55     833     async disk IO     count     0     00     intr     32     00000020     timeout     2147483647     7FFFFFFF     -1     4     WAITED KNOWN TIME
41     656     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     1354     WAITING
119     495     SQL*Net message from client     driver id     1111838976     42455100     #bytes     1     00000001          0     00     0     10     WAITINGIf you'd like, I can post trace file output of backup to \\blade5.
Regards,
Z.K.

RMAN backup files are still exist since long time, how to delete?

Dear sir;
I'm using the below script to do daily backup, however there are many rman backup files are still exist and consumes HD size, how could I delete these files in daily bases? some files dated in FEB, MAR, APR,
============Daily RMAN script=========
rman target /<<!
backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
backup current controlfile format '/u15/rman/control_%U.rman';
delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
delete noprompt obsolete;
================================END
Thanks and best regards
Ali

Hi;
Our backup policy should have 7 days; however we have here some files from JAN, FEB,MAR, APR /2012 WHICH ARE BEYOND THE RETENTION DATE and these files should be deleted by executing " delete noprompt obsolete; ".
All files are exist in /u15/rman/
-rw-r----- 1 oracle oinstall 1151763968 Jan 21 01:36 arc_backup_7kn19h4a_1_1.rman
-rw-r----- 1 oracle oinstall 1136882176 Jan 21 01:36 arc_backup_7ln19h4q_1_1.rman
-rw-r----- 1 oracle oinstall 1135984640 Jan 21 01:36 arc_backup_7mn19h5a_1_1.rman
-rw-r----- 1 oracle oinstall 1126627328 Jan 21 01:37 arc_backup_7nn19h5q_1_1.rman
-rw-r----- 1 oracle oinstall 880606720 Mar 12 02:53 arc_backup_7nn5ldhp_1_1.rman
-rw-r----- 1 oracle oinstall 1093043712 Jan 21 01:37 arc_backup_7on19h6a_1_1.rman
-rw-r----- 1 oracle oinstall 9797632 Dec 15 01:04 control_04mu7tcp_1_1.rman
-rw-r----- 1 oracle oinstall 36896768 Mar 3 02:55 control_4cn4tm9k_1_1.rman
-rw-r----- 1 oracle oinstall 36896768 Mar 4 02:53 control_4on50ahm_1_1.rman
-rw-r----- 1 oracle oinstall 36896768 Mar 5 02:55 control_56n52v1j_1_1.rman
-rw-r----- 1 oracle oinstall 16252928 Jan 23 01:40 control_8tn1eq3t_1_1.rman
-rw-r----- 1 oracle oinstall 16252928 Jan 24 01:40 control_9cn1heg0_1_1.rman
-rw-r----- 1 oracle oinstall 202940416 Dec 15 01:04 full_backup_01mu7t50_1_1.rman
-rw-r----- 1 oracle oinstall 1097728 Dec 15 01:04 full_backup_02mu7tcc_1_1.rman
-rw-r----- 1 oracle oinstall 201285632 Dec 14 01:04 full_backup_0nmu58ou_1_1.rman
-rw-r----- 1 oracle oinstall 5957304320 Feb 29 02:46 full_backup_2ln4g9l1_1_1.rman
-rw-r----- 1 oracle oinstall 4128768 Feb 29 02:47 full_backup_2mn4gft8_1_1.rman
-rw-r----- 1 oracle oinstall 6027075584 Mar 1 02:49 full_backup_32n4o6ov_1_1.rman
-rw-r----- 1 oracle oinstall 4128768 Mar 1 02:49 full_backup_33n4od66_1_1.rman
-rw-r----- 1 oracle oinstall 6187171840 Mar 2 02:51 full_backup_3gn4qr50_1_1.rman
-rw-r----- 1 oracle oinstall 4145152 Mar 2 02:51 full_backup_3hn4r1kn_1_1.rman
-rw-r----- 1 oracle oinstall 6115786752 Mar 3 02:51 full_backup_40n4tfgu_1_1.rman
above is a short list of contents.
to do our daily backup we perform the following script (in daily)
==================
backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
backup current controlfile format '/u15/rman/control_%U.rman';
delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
delete noprompt obsolete;
==================
Thanks and best regards
Ali

Can RMAN backup and export datapump executed at the same time?

Hello,
I have several databases that I backup using RMAN and export datapump everynight starting at 6PM and end at Midnight. The backup maintenance window doesn't give me enough time for each database to run at different time. I am using crontab to schedule my backups. Since I have so many databases that need to be backed up between 6PM - Midnight, some of the export and RMAN backup scripts will execute almost at the same time. My question is can my export data pump and RMAN backup scripts run at the same time?
Thank you in advance.
John

Needs must. If you don't run expdp parallel then it doesn't use that much. If it was really killing the system then look into setting up a Resource plan that knocks that user down but this is a big step.
I woud better look into using Rman
system incrementals, and block change tracking, to minimize your RMAN time.
Regards
If your shop needs to do both simultaneously then go for it.
Chris.
PS : One of my shops has maybe 20-30 rmans and pumps all kicking off some simultaneous, some not, from 0000 to 0130. No complaints from users and no problems either. Go for it.
Edited by: Chris Slattery on Nov 25, 2012 11:19 PM

RMAN backup to write on tape and disk in the same time

Hi all,
I want to take backup using RMAN and to have the backup file in a tape and a disk, i know i can allocate channel for tape, or disk. My question is can i use the both disk and tape in an rman backup one time. I mean i want to have rman writing backup file in a local disk and a tape in the same time to have redoundant backup at a tape and local disk.
If some scripts is there, it will be welcome.
Thanks
Raitsarevo

See Duplexing backup sets.

RMAN BACKUPS TAKING A LONG TIME IN 11.1.0.6

Its almost 4 days since the RMAN Full Backup is running and it has completed almost 91% and is stuck at this point since last 2 days, so now we killed the RMAN backup Process and started the RMAN Full Backup on Disk. We need to take the RMAN Backups on Tapes.
When we take the RMAN Full Backup to Tape manually with the same script attached, the Backup runs successfully withing Hours. While if the RMAN Full Backup is running through Cronjobs , then it takes days and it gets hung.
Initially it happened with Full backup , now Incremental Backup is also not working.
Log File of Current RMAN Incremental Backup Running and in Hung state
Recovery Manager: Release 11.1.0.6.0 - Production on Mon Nov 5 20:00:02 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: ZSBO (DBID=4052190355)
RMAN>
2>
3>
4> run{
5> allocate channel t1 type 'SBT_TAPE'
6> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
7> allocate channel t2 type 'SBT_TAPE'
8> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
9> allocate channel t3 type 'SBT_TAPE'
10> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
11> allocate channel t4 type 'SBT_TAPE'
12> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
13> backup
14> incremental level 2
15> format 'Incremental_zsbo_%U_%t'
16> (database);
17> sql "alter system archive log current";
18> backup
19> format 'arch_zsbo_%d_%s_%p_%t'
20> (archivelog from time 'sysdate-1' all delete input);
21> release channel t1;
22> release channel t2;
23> release channel t3;
24> release channel t4;
25> }
26>
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: SID=2086 device type=SBT_TAPE
channel t1: NMO v4.5.0.0
allocated channel: t2
channel t2: SID=2075 device type=SBT_TAPE
channel t2: NMO v4.5.0.0
allocated channel: t3
channel t3: SID=2069 device type=SBT_TAPE
channel t3: NMO v4.5.0.0
allocated channel: t4
channel t4: SID=2061 device type=SBT_TAPE
channel t4: NMO v4.5.0.0
Starting backup at 05-NOV-12
channel t1: starting incremental level 2 datafile backup set
channel t1: specifying datafile(s) in backup set
input datafile file number=00096 name=/data13/oradata/zsbo/A0186LA2591_00_CURR_12.dbf
input datafile file number=00058 name=/data17/oradata/zsbo/A0436IL2022_00_PREV_01.DBF
input datafile file number=00014 name=/data7/oradata/zsbo/A1225NY2502_00_TEMP_01.dbf
input datafile file number=00087 name=/data7/oradata/zsbo/A1086IL2502_00_PREV_01.dbf
input datafile file number=00045 name=/data7/oradata/zsbo/A1143BO2515_00_CURR_IDX_01.dbf
input datafile file number=00130 name=/data7/oradata/zsbo/A0171LA2034_01_DEMO_IDX_01.dbf
input datafile file number=00080 name=/data7/oradata/zsbo/A0436IL2022_00_CURR_IDX_02.DBF
input datafile file number=00119 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_05.dbf
input datafile file number=00136 name=/data5/oradata/zsbo/A1225NY2502_00_TEMP_11.dbf
channel t1: starting piece 1 at 05-NOV-12
channel t2: starting incremental level 2 datafile backup set
channel t2: specifying datafile(s) in backup set
input datafile file number=00095 name=/data12/oradata/zsbo/A0186LA2591_00_CURR_11.dbf
input datafile file number=00075 name=/data17/oradata/zsbo/A0186LA2591_00_CURR_IDX_02.dbf
input datafile file number=00094 name=/data6/oradata/zsbo/A0186LA2591_00_CURR_10.dbf
input datafile file number=00151 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_06.dbf
input datafile file number=00148 name=/data8/oradata/zsbo/A1143BO2515_00_PREV_02.dbf
channel t2: starting piece 1 at 05-NOV-12
channel t3: starting incremental level 2 datafile backup set
channel t3: specifying datafile(s) in backup set
input datafile file number=00127 name=/data8/oradata/zsbo/A1143BO2515_00_PREV_01.dbf
input datafile file number=00018 name=/data15/oradata/zsbo/A1225NY2502_00_TEMP_05.dbf
input datafile file number=00062 name=/data15/oradata/zsbo/A0436IL2022_00_TEMP_02.dbf
input datafile file number=00081 name=/data15/oradata/zsbo/A1110CH2505_00_PREV_01.dbf
input datafile file number=00137 name=/data7/oradata/zsbo/A1225NY2502_00_TEMP_12.dbf
input datafile file number=00065 name=/data18/oradata/zsbo/A1086IL2003_00_CURR_01.dbf
input datafile file number=00103 name=/data2/oradata/zsbo/A0186LA2591_00_PREV_05.dbf
channel t3: starting piece 1 at 05-NOV-12
channel t4: starting incremental level 2 datafile backup set
channel t4: specifying datafile(s) in backup set
input datafile file number=00059 name=/data6/oradata/zsbo/A0436IL2022_00_PREV_02.DBF
input datafile file number=00068 name=/data5/oradata/zsbo/A0186LA2591_00_CURR_01.dbf
input datafile file number=00071 name=/data9/oradata/zsbo/A0186LA2591_00_CURR_04.dbf
input datafile file number=00078 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_01.dbf
channel t4: starting piece 1 at 05-NOV-12 ----> No Progress since last 10 hours
Any help will be appreciated.
Regards,
Mohit
Edited by: 969777 on Nov 6, 2012 4:29 AM

Hi,
We have upgraded our database from 10.2.0.3 to 11.1.0.6.
The Script runs fine when we take command line backup on disk which we took 6 days backup, but when we schedule the same on cronjob RMAN Full Backup completes till 91% and it hangs forever. Everything was running fine with Incremental backup which we took 2 days before and it ran successfully but the above log is of Incremental Backup which is still in Hang state from the last 10 Hours , but still showing no Errors.
Please let me know if anything you want to confirm.
Thanks for ur prompt response,
Mohit

Increased Shared Pool size longer hot backup time?

Hello,
I have hot backup that usually took 2 hours to complete. Then we had to increase Shared pool size from 280Mb to 380Mb due to some performance issue.
One week after increase of size the hot backup is taking 4 hours to complete. Since there was no other changes to the system I am suspecting size increase
of Shared Pool from 280Mb to 380Mb might be is reason for such drastic increase of backup time.
I would like to get your comments on my suspicion to the problem.
thank you

Paul.S wrote:
One week after increase of size the hot backup is taking 4 hours to complete. Since there was no other changes to the system I am suspecting size increase of Shared Pool from 280Mb to 380Mb might be is reason for such drastic increase of backup time.Hmm... at first glance it does not seem that this is the problem.. but perhaps it contributes to it.
When a SQL hits the SQL engine, the 1st thing the SQL engine does is determine if there is an existing parsed and ready-to-use copy of that SQL. If there is, that existing SQL is re-used - thus the name SQL Shared Pool. The resulting soft parse of the SQL is a lot faster (or should be) than a hard parse . A hard parse is where there is no re-usable copy, and the SQL needs to be parsed, validated and execution plan determined, etc.
Kind of like re-using an existing compiled program (with different input data) versus compiling that program before using it. (and that is what source SQL is - a program that needs to be compiled).
Okay, now what happens if there 100's of 1000's of SQLs in your shared pool? The scan that the SQL engine does to determine if there is a re-usable cursor, becomes pretty slow. A soft parse quickly becomes very expensive.
The problem is typically clients that create SQLs that are not sharable (where the input data is hardcoded into the program, instead of input variables to the program). In other words, SQLs that do not use bind variables.
Each and every hardcoded SQL that hits the SQL engine, is now a brand new SQL. And requires storage in the SQL Shared Pool. Shared Pool footprint grows and you start getting errors like insufficient shared pool memory.. and increase the shared pool which means even more space to store even more unique non-sharable SQLs and making soft and hard parses even more expensive.
Like moving the wall a few metres further and then running even faster into it. !http://www.pprune.org/forums/images/smilies2/eusa_wall.gif!
Now if the backup fires off a load of SQLs against the SQL engine, the fast soft/hard parses can now be a lot slower than previously, thanks to a larger shared pool that now caters for more junk than before.
Unsure if this is the problem that you are experiencing.. but assuming that your suspicion is correct, it offers an explanation as to why there can be a degradation in performance.

How to estimate recovery time from rman backup

how to estimate recovery time from rman backup?
The database is of size 800GB.
the approximate time to backup is 8- 10 hours.

"Recovery time" is : RESTORE DATABASE time + RECOVER DATABASE time.
RESTORE can be done
a. in parallel with multiple channels if your backup was created as multiple backupsets
b. using incremental backups
c. whether the backups are on
i. disk
ii. tape
Alternatively, if you have a Recovery Area with an Incrementally Update backup of the database, you can SWITCH DATABASE almost immediately
RECOVER depends on
a. how many archivelogs (in terms of size, not necessarily number) need to be applied
-- this depends on
i. transaction volume
ii. the "freshness" of the backups (how recent the backups are)
b. whether required archivelogs are available on disk (which can be the case if the database backup itself is a very recent backup and archivelogs since then haven't been deleted {whether they have been backed up or not}) OR whether they need to be restored from
i. disk backup
ii. tape backup

REDUCE THE BACKUP TIME/RMAN

I am taking full backup every week end. But its taking a long time to complete as size of database is very big. Is ther any way to do backup fastly as parrallal processing . We are using RMAN. Kindly tell me some way.

user9231434 wrote:
I am taking full backup every week end. But its taking a long time to complete as size of database is very big. Is ther any way to do backup fastly as parrallal processing . We are using RMAN. Kindly tell me some way.SEveral methods in the rman guide (see tahiti.oracle.com) and also in "Oracle Database RMAN Backup & Recovery" by Hart and Freeman (Oracle Press). Depending on your needs, a couple of things come to mind immediately, and they are not mutually exclusive:
1 - take a full (incremental 0) backup only once a week, with incremental (incremental 1) backups the other 6 days.
2 - backup only a subset of your tablespaces each day - different subset each day.
3 - implement change tracking, so rman only backs up blocks that have actually been modified
Also be aware
- you don't mention down time ... are you taking a cold backup? Are you aware that rman can do a hot backup, so you don't have to stop the database? Performance impact is usually pretty minimal.
- you must be in archivelog mode for any of the above.

Rman backup to Tape taking a long time

Hi,
I am trying to backup 10 TB database to tape using RMAN. It is taking 2 days to complete. Can some one have any suggestions to improve the backup time.
Here is the configuration parameters
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 8 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE 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 '/oinstall/10201_0_64/dbs/snapcf_FR2.f'; # default
Here is the backup Script.
run
allocate channel t1 type 'sbt_tape' parms'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t2 type 'sbt_tape' parms'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t3 type 'sbt_tape' parms'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t4 type 'sbt_tape' parms'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t5 type 'sbt_tape' parms'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t6 type 'sbt_tape' parms'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t7 type 'sbt_tape' parms'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t8 type 'sbt_tape' parms'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
backup filesperset 15 as compressed backupset format '%d_Full_u%U_s%s_p%p_t%t' database plus archivelog delete input;
backup current controlfile format '%d_CF_u%U_s%s_p%p_t%t';
crosscheck copy of controlfile;
crosscheck backup;
crosscheck archivelog all;
release channel t1;
release channel t2;
release channel t3;
release channel t4;
release channel t5;
release channel t6;
release channel t7;
release channel t8;
Please Help !!!!!

Hi,
Yeah.. we had TSM set up with TDPO installed. Four tape drives has been dedicated for this server. hence i am running it with four channels.
We are backing up directly to tapeThis is backup system info.
The storage would be like :
- SAN (?)
- SSD (?)
- Exadata cells (?)
- local disk (?)
- RAID (?)
- Volume manager (?)
- amount of spindles (?)
- etc
Regards,
Tycho

RMAN backup time increased

Similar Messages

Maybe you are looking for