Networker is not resetting the Archive Bit

[MHartsock]

I have recently realized that Networker is not resetting the Archive Bit after running a Full backup on my NetWare servers. The backup servers are all NT 4, SP6, running Networker 5.5.1 and 6.0.1. The NetWare servers are 4.11 and 5.1, running the Networker 4.15 client. Doesn't matter what the backup server is or what the client is, Networker refuses to reset the archive bit! I have an open case with Legato's tech support but I had to explain the tech that a full backup is supposed to reset that bit.. so.. I'm hoping I'll find more help in here.

I did an experiment and learned that the archive bit is getting reset on my NT and 2000 servers. For the NetWare servers, I made a small change to an autoexec.ncf file (a file that doesn't change unless I change it), verified that it enabled the archive bit, ran a full backup on that directory, but the archive bit was still enabled after the backup completed. I ran a full backup on the entire server, and the bit is still set.

Any ideas?

 

[Guest_imported]

did you set this variable ?

> > Summary of documentation
> > ------------------------
> >
> > 1) NSR_AVOID_ARCHIVE=no *or* not present
> >
> > This is the new default behavior of scheduled backups on NT by
> > using the Archive file attribute as another factor in determining
> > if a file needs to be backed up incrementally in addition to the
> > Last Written, Creation time of a file. The Archive file attribute
> > is turned off based on the criteria listed below after a schedule
> > backup.
> >
> > A) full scheduled backups
> >
> > archive-bit(Attribute file attribute) turned off if on
> >
> > B) Last Written time *or* Creation time >= last scheduled backup time
> >
> > file is backed up, archive-bit turned off if on
> >
> > C) Last Written time *and* Creation time < last scheduled backup time
> >
> > a) archive-bit is on
> >
> > file is backed up, archive-bit will not get turned off until
> > the file is &quot;captured&quot; by a later future scheduled backup
> > (typically case A above, but possibly case B)
> >
> > b) archive-bit is off
> >
> > file is not backed up
> >
> > 2) NSR_AVOID_ARCHIVE=yes (any value other than case insensitive &quot;no&quot
> >
> > This is the older behavior of scheduled backup without using the
>archive
> > bit, except for older filesystem which used archive-bit as in (1).
> >
> > A) full scheduled backups
> >
> > B) Last Written time *or* Creation time >= last scheduled backup time
> >
> > file is backed up
> >
> > C) Last Written time *and* Creation time < last scheduled backup time
> >
> > file is not backed up
> >
> > By specifying NSR_AVOID_ARCHIVE environment variable, one can turn
> > off the new default archive-bit backup behavior. After changing this
> > enviornment variable, the NetWorker/NT client must be rebooted to get
> > the proper effect.

 

[MHartsock]

Where would I find such a variable?

 

[Guest_imported]

on your client :

in a dos-box type set|more

look for nsr variables

bye

 

[MHartsock]

Where did you find this documentation? It looks like this would apply to an NT client, and my problem is related to a NetWare client. The archive bit is reset on NT and 2000 servers after a full backup, but the bit is not getting reset on my NetWare servers after a full.

I added that environment variable to the backup server (NT 4) but it still did not reset the archive bit on a NetWare server after running a full.

 

[MHartsock]

I talked to a Legato technician and he said that Legato does not reference the Archive bit on NetWare servers. Instead, it uses and algorhythm to reference time stamps on the files to determine if they need backed up or not. Whatever works I guess..

But anyway, I just wanted to pass on the info to finalize this thread.