> 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.

If I understand correctly, I make 2 client definitions:

1. NT_SAN1
Saveset: ALL
with a directive to skip a specifically named set of directories

2. NT_SAN1
Saveset: only the directories listed as being skipped above

And I schedule both to run every night. So if a new directory is added, it 
gets caught by the client definition #1 ... since it does not match the 
SKIP directive. Meanwhile, client definition #2 is backing up 6 
directories at a time.

Yes? 

Does the order matter - for instance, should I schedule #2 first, and then 
#1 an hour later?
And the fact that the schedule is "Level 1 weekdays, FULL on Fri" should 
not affect anything.

Do you happen to know if this consideration - 


There are some unpleasant consequences however at this time...
At recovery time, not all backed up directories are displayed even
though the indexes are ok.

still applies to 7.4 SP2? 

Thanks so much for the clues!

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