so many considerations here! There's memory, cpu, network etc. but from a 
purely Networker point of view I would just say - parallelism.

Here's a simple ex. a Solaris filesystem /db contains 200 x 2GB database files. 
If this were backed up as one "saveset" performance would be poor. In this 
situation I would try to create say 10 even sized savesets (20 files each) - 
/db/1, /db/2, /db/3 etc.  You could for example achieve this using symlinks 
etc. When this client is backed up Networker will run these savesets in 
parallel (there are parallelism settings for server, jukeboxes etc that need 
tuning)

There is a point of diminishing return for this, I have found 10-12 parallel 
savesets works well on 4 cpu Solaris machine with no other significant 
processing. 

The gist of this is to keep your cpu and network busy and your tape drives 
streaming.

+----------------------------------------------------------------------
|This was sent by dbarton AT fsma.com DOT au via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER