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

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?

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.

I don't believe it makes a difference, but you should experiment and see
what works best in your environment.

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?

I don't know if that still applies.  We're not currently doing that,
though we may resort to it again soon.

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