Stephen Joyce wrote:
One other thing to be aware of is that giving the -time option to vos dump makes it look at the files' modification timestamps to determine what to back up. It's very possible to create a file with an old timestamp (using tar, touch, etc) so that it won't be caught by anything except a full backup. Mv'ing a file between volumes is an easy way to accidentally cause this. Just something to be aware of.
The vos dump process does not look at unix time stamps to determine if a file needs to be backed up. This is a nice feature of AFS. Any modification to the volume updates the volume time stamp, and if you keep track of these correctly, you'll get the new data even if the unix times would not predict that. I cp -p /usr/bin/filesize to my afs volume. As you can see it is all of the unix times are from 2000: # stat filesize File: `filesize' Size: 68 Blocks: 2 IO Block: 4096 regular file Device: dh/13d Inode: 80281630 Links: 1 Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2000-09-04 11:24:42.000000000 -0400 Modify: 2000-09-04 11:24:42.000000000 -0400 Change: 2000-09-04 11:24:42.000000000 -0400 I then took an incremental backup of the volume and checked our file lookup database and the file is there: FILE 68 Mon Sep 4 11:24:42 2000 afs|user.kwebb|/filesize If vos dump did not give us these older files consistently, our synthetic backup process would detect it. Kris -- Mr. Kristen J. Webb Teradactyl LLC. PHONE: 1-505-242-1091 EMAIL: [EMAIL PROTECTED] VISIT: http://www.teradactyl.com Home of the True incremental Backup System
smime.p7s
Description: S/MIME Cryptographic Signature
