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.

Similar Messages

Rman backup to disk 2 Minutes; Backup to tape hours

Solaris 10
Oracle 10gR2
MML Netbackup 6.0
I have the following scenario
Rman backup to disk < 2 Minutes; Backup to tape takes hours
and occassionaly fails with a media manager layer error.
Any suggestions to speed up the backup to tape?

A backup of under 2 minutes . . . not very big.
A backup to tape of hours?
I don't think that is your problem . . . I think you need to check and see if your tapes are valid. If Oracle fails at the end of a backup to tape, it sounds like the tapes are 'bad'.
If the tapes are good: Then look at why it is so slow - I would 'guess' network backup.
Can you backup to disk and then send them to tape?
Solaris 10
Oracle 10gR2
MML Netbackup 6.0
I have the following scenario
Rman backup to disk < 2 Minutes; Backup to tape takes
hours
and occassionaly fails with a media manager layer
error.
Any suggestions to speed up the backup to tape?

RMAN Backup Speed

Hi All,
Our Database size is 1.3 TB and we take RMAN backup but it takes around 48 Hours to do backup in oracle 9i and in oracle 10g offers block compression can this help to reduce the backup time.
Regards
Balu

Please have a look to links mentionned in this thread:
Re: RMAN BACKUP PERFORMANCE.

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

Time Machine Problem - New Internal Hard Drive, Now Backup Takes Hours

Need some help!
Background.
Almost 4 year old 24" aluminum iMac; 4 gb ram; 500 gb hard drive; OS 10.6.8.
About 2 months after Alpple Care expired, the internal hard drive failed (New Year's Eve of all times!). Everything else working great.
Had a Mac technician I know install a new 750 gb drive for me. I cloned back from SuperDuper, and was ready to go. The SuperDuper external is 1.5 TB, partitioned - one half TM, the other half SuperDuper.
All apps, internet, mail - fine.
I hooked up my existing Time Macinne (probably not a good idea), and the next backup failed.
Did some research, and since I have plenty of archived backup anyway, decided that the best thing to do would be to erase the TM external, and start fresh.
Did that, and as expected, first backup took a couple hours.
The Problem.
Now, every incremental backup takes 4 to 5 hours, even if no data has changed.
"Indexing" lasts for 45 minues; "Backing Up" reads 600,000 plus files, which also goes on for 30 or 40 minutes (approx.), and wants to Calculate changes etc forever; then the actual backup starts out at 10 kb, and in 20 minutes is at 30 kb and then after about an hour I start getting into gbs and the blue bar progresses pretty fast after that. Then "Finishing Up" takes approximately 2 - 3 hours.
Not right. :~(
What I've Done to Toubleshoot.
First, I re-erased the TM external.
Then reset PRAM and did an SMC reset on the iMac.
Then backed up to TM again. The same problem persisted.
So next, I repeated that process (other than backing up), and I also deleted from the Root Library/Preferences com.apple.timemachine.plist, and from Home/Library/Preferences deleted com.apple.finder.plist. Then rebboted the iMac. Then I did a Disk Utility verify of the empty external - all was/is fine. Then I ran DiskWarrior on the iMac and all was fine; repaired permissions on the iMac from DiscWarrior as well. Then, I did another TM backup to the external, which took a couple hours since it was backing up to an empty drive.
Next 3 incremental backups still take 4 to 5 hours, even if nothing has changed on theiMac.
The Request.
Please if anyone can give me some easy to understand step by step options I might try to get TM working correctly again, it will be most appreciated.
If I've left out any details that might assist, please also let me know.
The problem computer is at home and I'm at work, so if any logs are needed, I can post those later today (but in that event, please tell me exactly which log to post and how to isolate it from System Profiler or Console (as there are many logs to choose from and I want to provide the proper info if someone needs to see a log to assist)).
Thanks in advance!

Pondini,
Did every step in D2 (green box) - except did not reinstall Combo Updater which I did late last night.
After that, did a TM backup - started at 6:15.
All apps were off.
Sequence of events and facts:
At start, 434.03 0f 500.1 GB available on the external TM
Last backup shown - 7:58 AM; Oldest Back Up - Yesterday at 9:56 (that's the 1st backup after I reinitialized the external for the 2nd or 3rd time trying to get this thing figured out)
Upon starting and doing the backup -
Preparing 250,000 (approx.) items (too quick to get the final number) - Parenthetically, this AM it was over 600,000; probably has to do with turning off Spotlight per your D2 instructions
Next message -
Backing Up 6.96 GB
Hung at 2 kb to 90 kb for 20 minutes before progressing
Ultimately, at 1.78 GB the progress bar started moving rapidly (as it should) - so this isn't a cable connection issue - the Backup phase took 22 minutes, but from 1.78 GB to 6.96 GB took only a few seconds; I have seen this precise same sequence repeatedly the past 2 days
Next - Backing Up (the candy cane blue and white progress bar) - Preparing 140,000 items - took 12 minutes
Now shows 426.95 GB available on the external
Next - Backing Up (no count of items shown) - started at 7:05 and went until 7:45 (40 minutes)
Next - Finishing Backup (blue/white candy cane progress bar; no count of items shown) - started at 7:45 - went until sometime after 8:15 (can't give a precise time because I need to sit down and eat :~) )
Backup completed (between bites of chicken) at 8:23.
Over 2 hours - something isn't right.
Also, TM Prefs tells me that the Latest Backup was at 7:44 - odd.
Anyway - to take a step further, here's the TM Buddy widget info you might need:
Successful Backup: 02:06:32.
There is no log entry or data showing.
Just as I sent this, a new backup started, and it appears to be going through the same routine, from Preparing ....
Gotta eat.
Please post any further instructions and I'll do what I can tonight.
Thanks!
What is the problem? How do I speed this mother up?
Thanks!

Is RMAN only way to take backup and delete Archive Logs?

On primary db:
===============
OS: Windows 2003 server 32-bit
Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
On Physical standby db:
===============
OS: Windows 2003 server 32-bit
Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
Data Guard just configured. Archive Logs are properly being shipped to standby db. Is RMAN only way to take backup and delete Archive Logs from both primary and standby db? What other command can be used?
Thanks

No, but anything else is way more work. Without using RMAN you would have to find another way to keep track of applied logs.
RMAN make this very simple :
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;Using another method would be like using the handle of your screwdriver as a hammer.
See "RMAN Recipes for Oracle Database 11g" ISBN 978-1-5959-851-1
Best Regards
mseberg

Configure backup agent to take the RMAN backup

Hi,
We have a Sun Storagetek SL48 tape library with us. we want to take the backup to tape using Rman.
In order to take the RMAN backup, we need a backup agent needs to be installed on the database server.
1. My doubt is If we have Sun Storagetek SL48 tape library, what backup agent needs to be installed on the server?
2. If we know agent name, Could you please share the document to install the agent?
Thanks for your help.
R.Sundaravel

These softwares support the SL48 and they have an agent for RMAN : Symantec NetBackup, Legato Networker.
For Symantec, please check this URL : http://www.symantec.com/business/support/index?page=content&id=HOWTO44847#v15496705
For Legato, this one : https://store.emc.com/Product-Family/DATA-DOMAIN-PRODUCTS/EMC-NetWorker/p/EMC-NetWorker

Is it necessary to take RMAN backup for ASM

Hi all
I also know we need RMAN to take backup for ASM . But i also seen its possible to take backup by using dd command itself on ASM . Why we need RMAN rather than this method . What is the specific reason we using RMAN,

its possible to take backup by using dd command itself on ASM Very bad idea.
1. You'll run into the classic "fractured block" issue when attempting a recover or reading a block after the restore
2. RMAN can be used to
a relocate individual datafiles,
b duplicate / clone database,
c restore to an alternate server,
d copy / move from ASM to filesystem
e verify for corruption
f generate reports on backups taken
None of which dd of ASM will do reliably (depending on the skills of the DBA/SA).
Hemant K Chitale
Edited by: Hemant K Chitale on Feb 19, 2013 9:56 AM
Added the words : "reliably (depending on the skills of the DBA/SA)"

Who takes RMAN backup?

Hi all,
I have an oracle 9.2.0.7 database instance on SLES9 sp3 64bit. And RMAN backup is taken every day by one who is I dont know although I changed sys and system passwords. It seems that the backup is taken on local machine, doesn't it? I looked at v$session_longops view then I saw backup is taken SYS user. Anyone doesn't have RECOVERY_CATALOG_OWNER role. I looked at crontab of oracle and root users, then I looked at dba_jobs. But I dont see anything about rman backup anywhere. I wonder who takes RMAN backup on my system?
Regards
İlke ALTINPULLUK

hi,
I sent one of my audit files. Then I looked at baandb machine's crontab but I didnt find anything. Then I looked at dba_jobs on baandb. I didnt find anything.
my audit files like follow:
Audit file /opt/oracle/oracle/product/9iR2/rdbms/audit/ora_27666.aud
Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
ORACLE_HOME = /opt/oracle/oracle/product/9iR2
System name:    Linux
Node name:      baandb
Release:        2.6.5-7.244-smp
Version:        #1 SMP Mon Dec 12 18:32:25 UTC 2005
Machine:        x86_64
Instance name: gcam
Redo thread mounted by this instance: 1
Oracle process number: 22
Unix process pid: 27666, image: oracle@baandb (TNS V1-V3)
Thu Jan 13 01:05:50 2011
ACTION : 'CONNECT'
DATABASE USER: '/'
PRIVILEGE : SYSDBA
CLIENT USER: oracle
CLIENT TERMINAL:
STATUS: 0
Dear EJR; I didnt understand what you mean?
Edited by: ilke_altinpulluk on 20.Oca.2011 03:51

Why does it take hours to sync and backup a 12GB data?

Does anyone know why it takes hours and hours to just sync and backup my 16GB iPhone 3GS before it installs the iOS5? This is getting rediculous! Why do Apple force us to use iTunes?

Shouldn't take that long although waiting a long time in between syncs can create longer backup times... ie more data, apps, etc... to back up etc... Make sure both iPad and iTunes are most current versions. Make sure you are using the iPad sync cord that came with the device and not another from a iPhone or iPod. Cables can screw up the deal.
Start there first and let us know how it goes.

Is it possible to take RMAN Backup

Can anyone tell me whether we can take Rman Backup in Oracle 10g Express Editon.
Thanks in advance.

hi,
Thanks for the reply.
I tried to take a rman backup and got this error:
Starting backup at 14-APR-08
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/14/2008 17:19:13
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06171: not connected to target database
When tried to connect to target database this is what i got.
RMAN> connect target /;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-01031: insufficient privileges
Please help. Thanks in advance.

Like to take rman backup files into some other machine

Dear all
I like to take Rman backup into some other machine rather than its default storage location $oracle_home/dbs in to some other machine..
While i ran database backup in rman it stores the file sets into default location $ORACLE_HOME/dbs ... I relocated in to some other drivers in same machine also.. I got work ... But due to space issue i would like to take backup into some other machine so its possible ? how to configure it...
Regards
Gopinath

GopiKrishna wrote:
Dear all
I like to take Rman backup into some other machine rather than its default storage location $oracle_home/dbs in to some other machine..
While i ran database backup in rman it stores the file sets into default location $ORACLE_HOME/dbs ... I relocated in to some other drivers in same machine also.. I got work ... But due to space issue i would like to take backup into some other machine so its possible ? how to configure it...
Regards
GopinathYou need to mount the second machine and take backup to that mount point
Kamran Agayev A.
Oracle ACE
My Oracle Video Tutorials - http://kamranagayev.com/oracle-video-tutorials/
My ebook - http://kamranagayev.com/2011/10/19/step-by-step-oracle-installation-all-in-one-e-book/

HT203177 I have not backed up my computer using Time Machine since before I updated to Mavericks. It has been "preparing backup" for a half hour at least and shows no indication of how long this may take. Is something wrong?

I have not backed up my computer using Time Machine since before I updated to Mavericks. It has been "preparing backup" for a half hour at least and shows no indication of how long this may take. Is something wrong?

No. TM has to look through your entire drive contents and copy them all. This will take some time.
Once the first backup is made, then subsequent backup will be much quicker, depending on how much data has changed since the last one.

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

10.1.0.2.0 RMAN backup- What would cause RMAN to hang?

Oracle gurus- Fellow in trouble, need your guidance.
I have a serious issue that has no direct error to examine or fix.
I have a replicated offline server that has a scripted RMAN backup to run nightly, but the backup times flux from what should be only 1 hour 30 minutes. Every other day it takes up to 10 hours to complete a backup that normally takes 1 hr 30 minutes. There is no difference in data loads- the server is offline and the data has not changed to any effect. I use database control instead of grid control, and I turn off emctl every night before the rman backup- I thought maybe emctl was hogging resources. There is nothing else running on the server except replication inserting a couple of rows of data on three tables every other minute.
Where would I look to see where the problem exists when no errors are generated?
Does RMAN wait to backup files if they are being accessed?
Here is my backup script (the OS is Linux AS3) I run an AT job nightly.
at -f /path/path/rman_backup 0600 tomorrow
rman target/
run {
backup database plus archivelog;
delete noprompt obsolete;
sql 'alter system archive log current';
exit;
The Administrators are running a Legato Jukebox backup? a tape backup that backs up my DB files nightly. They run the Legato backup 3 hours after my RMAN backup- the problem is that my RMAN backup may be running during the Legato backup- so I assume that contention occurs and both backups fight for the DB files. This is not an issue when RMAN plays nice and finishes in the normal 1 hour 30 minutes, but when it exceeds 3 hours- we have serious issues, both RMAN and Legato backups take 10 hours.
Please help, I am really puzzled. This is causing me major headaches, how can I assure that RMAN has a consistent backup time to completion. Is there anyway to script it to use more resources to ensure it finishes quickly?

Have you monitored CPU and I/O during this process? Are there any other processes running during this time? You mentioned the server is offline, but you also mentioned replication is taking place ?
You could query V$BACKUP_ASYNC_IO and look at EFFECTIVE_BYTES_PER_SECOND, WAITS and IO_COUNT.
During the backup, you can run the following query to monitor RMAN:
SELECT sid, serial#, context, sofar, totalwork,
     round(sofar/totalwork*100,2) "% Complete"
     FROM v$session_longops
     WHERE opname LIKE 'RMAN%'
     AND opname NOT LIKE '%aggregate%'
     AND totalwork != 0
     AND sofar <> totalwork;If the % Complete doesn't seem to be increasing, you should run the following select to determine what waits exist:
SELECT sid, seconds_in_wait AS sec_wait, event FROM v$session_wait
     WHERE wait_time = 0
     ORDER BY sid;

RMAN backup to SAN takes 13 hours

Similar Messages

Maybe you are looking for