Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

RMAN backup to SAN takes 13 hours

zaffer khan cisaMar 7 2009 — edited Mar 10 2009
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.
This post has been answered by tychos on Mar 10 2009
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Apr 7 2009
Added on Mar 7 2009
16 comments
2,956 views