mark wragge wrote:
I have an unusual problem in that the archive bit is not being reset on any
files during full or incremental backups on my Linux Client using networker v
7.3.2. The puzzling thing is that the incremental backups are backing up the
correct amount of data. The total amount of data is 400gb and the nightly
incrementals are approx 80mb.
Why is the archive bit not being reset on the files?
Why are the incremental backups backing up the correct amount of data if they
are meant to use the archive bit to determine which files to back up?
How does a Linux client decide which files to backup during an incremental
backup?
Linux/Unix does not have an archive bit, so a Linux client cannot
reset it. On Unix clients the backups is performed based on comparing
the date of the last successful back at the relevant level and the 'last
modified date' in the files inode (also see my letter about the Linux
bug with the open (O_CREATE) system call which does not modify mtime,
just ctime).
How can you tell that the archive bit is not set ? ls -l will not
show such an attribute. Do you use SMB ?
Thanks
Send instant messages to your online friends http://uk.messenger.yahoo.com
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 with 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
--
-- Yaron.
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 with 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
| 