> For the sake of example, let's say that I break it into 5 sub-trees:
> D:\A, D:\B, D:\C, D:\D, and D:\E.  So, I set up my client with the
> following save sets:

This will also make the job faster, as it will backup multiple streams at 
once. Or so it has always appeared to me.

<SNIP>

> So, to protect my own job, I create a second client definition on the
> server that has D:\ as its only save set, and I create a server side
> directive that I assign to this client definition which says:

I do this all the time, except that I use SKIP:, not NULL:, since the 
files are already picked up by the other job.

> << D:\A >>
>    +null: .

<SNIP>
 
> I add this second client definition into my Safety Net group.

I call mine "Catch All", so it catches anything that the enumerated job 
misses.

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