There are some limitations with trunking the GigE connections, since these are 
sun clusters (everything I have read says that sun trunking is not supported on 
a sun cluster).  We are going to do some testing using multiple interfaces and 
multiple policies.  Right now I would be satisfied to saturate a GigE 
connection on the backup server.  But in the end, 120 MB/s still isn't very 
fast.  That's about 7 GB/M or 400 GB/Hour.  O.k., that's pretty fast, but when 
you are talking about 2 to 4 TB of data, that's still 5-8 hours of backup.  If 
this is to be done daily on a system that requires 24/7 availability, how do 
you make the timeframe reasonable?

Matthew Dobbertien
Sr. Systems Analyst
Chicago Tribune

-----Original Message-----
From: David Magda [mailto:dmagda AT ee.ryerson DOT ca] 
Sent: Thursday, January 27, 2005 6:30 PM
To: Dobbertien, Matthew
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] backing up LARGE oracle databases (looking for 
suggestions)


On Jan 27, 2005, at 17:59, Dobbertien, Matthew wrote:

> Right now, the chokepoint is the GigE connections.  I'd like to be 
> able to use snapshots to backup the data directly to tape, but there 
> doesn't seem to be a good way to manage the snaphshot process using 
> Netbackup with Clariion arrays.

Have you thought about trunking multiple interfaces? Sun sells quad 
GigE cards (uses the ce driver).

Both the source and destination of the bitstream would have to support 
the bandwidth in question of course.