11-29-2012 06:08 AM
Hi all- To be more specific, I'm curious about how the archiving bit works in this scenario. If you cancel a diff, it doesn't appear that the partial backup is usable for restore purposes. I was also under the assumption NBU would clear the archive bit as files are processed. Putting thse two together, it would seem like files processed before a backup is cancelled have their archive bit incorrectly non-set - is that how it works or am I missing something, because that's certainly not desirable.
All this is based on the assumption NBU uses the archive bit.
Thank you!
Scott
11-29-2012 06:19 AM
Archive bit is cleared after successful backup.
The 'Wait time before clearing archive bit' in Windows Client properties is 300 (5 min).
Extract from Admin Guide I:
11-29-2012 06:37 AM
Thank you for the very quick reply, Marianne! That gives rise to one more question though - is it possible for a file to be archived, then modified (while the backup is still running), then the post-backup archive-bit clearing job incorrectly clears the flag since the file was modified after it was archived by NBU?
11-29-2012 09:47 AM
Hi Scott
I have in all honesty never tested your theory in real life.
It should be easy enough for you to copy some files to temp folder, create test policy and perform tests as per your post? I am quite curious to know the result...
You also have the option to de-select 'Incrementals based on archive bit'.
This will perform Incr backups based on file datestamp.
As per the manual: