Client is 7.2.2 on Windows 2003.
Journaling is enabled for drive D
There is a system variable NSR_AVOID_ARCHIVE=YES
There is an CA eTrust AV on the client but is was disabled one night for test.
We've also tried updating the client to 7.2.2.Jumbo version.
Regardless of all our efforts, the customer complains that NetWorker still keeps resetting the archive bit on the files it backs up on this clien. Any suggestions what to do?
When you use journaling archive bit is not used by NW to perform incremental and differential backup so their state does not matter (at least for drive D).
Can you explain what do does customer mean under reseting - clearing off the bit from backups it does or not clearning them from files it does or maybe even setting them on those that should not be backed up?
If journaling is enabled then I see no reason why you should keep playing with archive bits which thanks to MS never really worked correctly anyway.
* Journaling is enabled in the "NetWorker Change Journal Manager" for the drive D (both check boxes) * Files on drive D have an attribute "Ready for archiving" checked * Backup of these files is ran * When checking the attributes, the "Ready for archiving" check box is cleared, and not checked anymore
If you use journaling then remove NSR_AVOID_ARCHIVE bit. I have no idea if Windows OS will reset archive bit when doing journaling backup, but I guess it should as you might skip journal approach and that would make next incremental using legacy approach good then. So, what you described looks fine to me.
ble1
6 Operator
•
14354 Posts
•
56186 Points
356
0
Posted July 20th, 2007 02:00
Can you explain what do does customer mean under reseting - clearing off the bit from backups it does or not clearning them from files it does or maybe even setting them on those that should not be backed up?
If journaling is enabled then I see no reason why you should keep playing with archive bits which thanks to MS never really worked correctly anyway.