On Wed, Nov 27, 2002 at 10:54:42AM +0100, Helas, Stephan wrote: > Christoph Scheeder wrote: > > Hi > > this is very strange, > > i have a few servers under linux using ext3 and gnutar with amanda > > doing fine level1 and 2's. > > I guess you may have a process on your server touching all your files > > once a day, making tar thinking they where changed and for that > > taking them into your level one backups. > > Any chance for that posibility? > > Christoph > > > > Helas, Stephan schrieb: > >> Hello, > >> > >> I backup several unix and Linux Server without having trouble. but > >> one redhat 7.3 server don't work that way. i got some strange > >> problem by backup this linux server with ext3. i use normal > >> configuration, but my incremental backup are as big as the full > >> backup. for example i post some info: > >> > >> 0 20021126 Tag05 4 3451500 3451500 1295 > >> 1 20021127 Tag06 9 3451510 3451510 1143 > >> ------------ snap ------------------------------------ > >> > >> as you can see, the filesize between level 0 and level 1 don't > >> differ. > >> > >> now my question. is it a effect ob using ext3? can't ext3 handle the > >> archive bit in the way that amanda use it? do i have to go back > >> using ext2? > > One example for Files: > > [root@gt1webdev2 software]# ls -l > insgesamt 66104 > -rw-r--r-- 1 root root 706573 Okt 8 10:38 ant-1.5.1-3jpp.noarch.rpm > -rwxr--r-- 1 webuser nobody 602566 Nov 15 08:04 >ant-optional-full-1.5.1-3jpp.noarch.rpm > -rwxr--r-- 1 webuser nobody 25146816 Nov 16 15:42 >j2sdk-1_3_1_04-linux-i586-rpm.bin > -rwxr--r-- 1 root root 25150518 Nov 16 15:04 >j2sdk-1_3_1_06-linux-i586.rpm.bin > -rw-r--r-- 1 root root 2807094 Okt 11 2001 jakarta-ant-1.4.1-bin.zip > -rw-r--r-- 1 root root 468566 Okt 11 2001 >jakarta-ant-1.4.1-optional.jar > > [root@gt1webdev2 software]# find . -mtime -7
Does amanda use the data modification time or the inode change time to determine if a file requires backing up? I suspect the latter so that if the permmisions or owner/group of a file changes (affecting inode change time but not data mod time) then the file still needs to be backed up. Check again with "ls -lc" and "find . -ctime" I forget whether you are using tar or a dump, but the tar option to retain file access time causes inode change time to be set to current time. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
