Nope, that's expected behaviour.
You said "don't back anything up", so it didn't.
Then you say backup everything that has changed since the date that the last
backup ran (definition of an incremental backup for NetWorker). Nothing has
changed since the last backup, so nothing is backed up.
If you change the time on the file, it has changed, so it is backed up.
Everything is exactly as expected.
Note the definition of an incremental backup.
Siobhán Ellis
EMC Certified NetWorker Specialist
IDATA Integrity Pty Ltd
Sydney, Australia
On 16/10/06 7:34 PM, "Rik Theys" <rik.theys AT ESAT.KULEUVEN DOT BE> wrote:
> Hi,
>
> I've noticed a strange (?) behaviour of the Legato/EMC networker (client)
> and am not sure if the behaviour is what I should expect or if it's a bug in
> the client.
>
> The backup client runs Legato Networker Client for Linux (x86 or x86_64
> version) version 7.1/7.3. The server runs version 6.0.3 on an Alpha.
>
> I create a directory on the client with data (say unpack the linux source
> code) and create a .nsr file in that directory that specifies that nothing
> (except the .nsr file) should be backupped in that directory. When the
> backup client is instructed to make an incremental (or full) backup, the
> backup client backups the .nsr file and nothing else in that directory (so
> far so good).
>
> 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).
>
> 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?
>
> Thanks in advance,
>
> Rik
>
> 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
>
Siobhán
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
|
