The ignore directive is what you want.   I didn't test yet but Legato
confirmed one can have multiple directives;  if ignore is first, followed
by other directives, they all work.    It was reccommended that an "allow"
directive be specified for the nsr directory as its .nsr files are there
for a reason.

I have not tested the time/perfomance savings yet of ignoring.  I would
think it signifigant on savesets with many directories.  The thread last
month claimed a performance increase for windows clients.

I'm not that familar with windows directives. Is the ./ in your directive
really necessary?

Let us know if you find a measurable performance gain.

Robert Maiello
Thomson Medical Economics

On Fri, 9 May 2003 15:09:55 +1000, Peter D. Gray <pdg AT UOW.EDU DOT AU> wrote:

>I think I found what I need to do to stop
>.nsr files being used.
>My current directive looks like
>
>+ignore:        ./* ./.*
>+mtimeasm:      ./* ./.*
>+skip:          ./.snapshot
>
>Does snaybody think this will not:
>
>1) ignore .nsr files
>2) Use the modify time for determining if
>        a file needs to be backed up
>3) Ignore .snapshot directories (on my netapp).
>
>Regards,
>pdg
>
>--
>
>See mail headers for contact information.
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can
>also view and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=