In regard to: [Networker] Backup saveset speed: Enumerating directories vs...:

On our main SAN, we enumerate the folders to be backed up, rather than
just specifying ALL (or in our case, "H:"). We do this for speed reasons -
it's a lot faster to do this, rather than specifying a saveset of ALL. I'm
told that ALL backs up folders in sequence, while enumerating them (in
conjunction with parallelism) makes them back up in parallel, rather than
sequence.

Methods for safely doing this have been discussed several times on the
list before.  The two common suggestions are

1) use a script on your backup server that periodically probes the client
to find what mountpoints/volumes are present, and have the script update
the saveset attribute for that client to add any new volumes that have
appeared.

2) use two client definitions -- on definition uses the ALL saveset *but*
it uses a directive you create for just that client that skips the volume
you want to parallelize.  Then create a second client definition that just
lists e.g. H:\foo, H:\bar, H:\baz in the saveset.

See my post in the archives on April 5 2004 for more details on method #2,
or the thread in early April 2003 from Howard Martin, Itzik Meirson, and
Andrew McGeorge.  Andrew's post does a great job explaining how to do it.

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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