We have run multiple tests on the system.  Writing the backup to
/dev/null results in over 100 MB/s throughput, but running the same jobs
over the network maxes out at 60 MB/s regardless of number of streams or
tape drives or disk on the back end (we generally write to virtual tape,
which has a throughput of over 150 MB/s).  We do see a maximum
throughput of 40 MB/s per stream--I believe this is just the overhead
from bpbkar.  The disks we are reading from are capable of pushing data
much faster than that (backend disks are on a clarion cx600).  Even
running three backup streams from the same disk results in over 100 MB/s
throughput.  

Matthew Dobbertien
Sr. Systems Analyst
Chicago Tribune
mdobbertien AT tribune DOT com
312-222-2203 (Work)
312-656-3019 (Cell)

-----Original Message-----
From: blaine_robison AT netzero DOT com [mailto:blaine_robison AT netzero DOT 
com] 
Sent: Monday, January 31, 2005 9:09 AM
To: Dwayne.Brzozowski AT mail.va DOT gov
Cc: Dobbertien, Matthew; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] backing up LARGE oracle databases (looking for
s ugge stions)


Hey,
thanks Dwayne, 

Matt how do you know the GigE connection is the choke point?


Blaine Robison
Solaris Certified System Administrator
Solaris Certified Network Administrator 
Sun Certified Backup and Recovery Engineer
Veritas Certified Professional Data Recovery