> I decide that the data in the directory becomes important and want to back
> it up, so I remove the .nsr file. During the night an incremental backup
> runs but doesn't backup anything because none of the files have changed.
> When I look at what nwrecover has for that directory, the directory is empty.
> 
> When I touch a file in the directory (change the ctime), that one file is
> backupped during the next incremental.
> 
> Shouldn't the client check for each directory if a .nsr file previously
> existed and if it did, backup all the files and not just the new ones? With
> the current behaviour it will take until the next full backup before the
> files are backupped (which might still be a few weeks).

Correct.

Remember the client is not told what files have or have not been backed
up.  All it has is a timestamp.  So the client cannot make backup
decisions except based on the timestamp passed in, directives, local
.nsr files, and file timestamps.

On a windows host, the archive flag could cover this case, but it has
other drawbacks.

> Is this the behaviour I should expect or is it a bug in the client software?
> If this is the expected behaviour, is there a configuration option I can set
> to change the behaviour? Is this behaviour version dependant? Will upgrading
> the server software "solve" this?

I would expect that you need to explicitly back up any data when you
release restrictions in .nsr or directives unless you are willing to
wait for the next full to occur.

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

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