On Monday 14 January 2008, Gene Heskett wrote: >On Sunday 13 January 2008, Dustin J. Mitchell wrote: >>On Jan 13, 2008 9:00 PM, Gene Heskett <[EMAIL PROTECTED]> wrote: >>> Is there anything in that config driver that I should change for 2.6.0b1? >> >>Not that I know of. The changes to note are in the NEWS and >>ReleaseNotes -- in particular, some new build dependencies, lib and >>libexec files moved to lib/amanda and libexec/amanda, and >>/etc/amandates moved to /var/amanda/amandates unless you supply >>--with-amandates=/etc/amandates. >> >>Thanks so much for testing this. Has anyone else had a chance to take >>it out for a ride? >> >>Dustin > >Well, this ride ended in a 100% disaster. /tmp/amanda and /tmp/amanda-dbg > were used and duly populated with debug files from yesterdays amcheck and > amlabel activities, but was unable to make the /tmp/amanda/Daily dir for > the rest of it. There isn't anything left in the /dumps holding disk, and > the virtual tape it was going to use is empty except for the label file. > >The /tmp/amanda and /tmp/amanda-dbg dirs do not contain *any* files dated to >the start time of the run, only leftovers I had pulled with amrecover, and >the amcheck & amlabel runs to set up the new drive that were made last night >as I was getting it setup. > >I've made that missing /tmp/amanda/Daily dir, and touched the gene.log file >there and restarted it. It seems to be doing its thing ok now as its >generating files in the /tmp/amanda dirs and 1Gb chunk.tmp files are showing >up in /dumps, so I'm going back to bed & when I wake up again, I'll fire off >my catchup script since it all failed for round one, and about 22 Gb failed >for round two according to amstatus. catchup will run about 6 backups in a >row & should begin to establish some order. > >Who would have thought that one missing subdir containing one, constantly > over written log file in /tmp/amanda/Daily/gene.log would have screwed > things up so bad. My script obviously needs to handle that and didn't. > >Humm, although it says the first 7.6Gb dle has been taped, the chunk files > are still in /dumps, I thought they were cleaned out once they were written > to tape? Has this behavior changed? > >>From amstatus: >coyote:/usr/movies 0 7672400m finished (2:42:12), PARTIAL > >What is this 'PARTIAL'? > >More news later.
PS, from the amverify run I do after the backup run: ------------------- Volume Dailys-30, Date 20080114023115 ** Error detected (FILE: date 20080114023115 host coyote disk /usr/movies lev 0 comp N program /bin/tar) could not open conf file "/usr/local/etc/amanda/amanda-client.conf": No such file or directory Restoring from tape Dailys-30 starting with file 1. amrestore: 1: restoring FILE: date 20080114023115 host coyote disk /usr/movies lev 0 comp N program /bin/tar /bin/tar: Unexpected EOF in archive /bin/tar: Error is not recoverable: exiting now End-of-Tape detected. -------------------------- Which explains what the PARTIAL above might mean, but in all my history with amanda, I don't recall ever needing or having a /usr/local/etc/amanda/amanda-client.conf file. What is this and what does it do? Currently that dir contains the Daily/config files. Another datum point: From an ls -lR of /amandatapes/Dailys: -------------------------- /amandatapes/Dailys/slot30: total 177769 -rw------- 1 amanda amanda 32768 2008-01-14 02:41 00000.Dailys-30 -rw------- 1 amanda amanda 181284864 2008-01-14 02:42 00001.coyote._usr_movies.0 -rw-rw-r-- 1 amanda amanda 0 2008-01-14 03:21 configuration.tar -rw-rw-r-- 1 amanda amanda 0 2008-01-14 03:21 indices.tar ----------------------------- Only 181 megabytes out of 7.4Gb written? This was looked at AFTER a flush session, but the file time is from the end of the backup session, not the flush. And the flush did NOT advance the vtape to #1 as it should have. So the failure also caused the tapelist and the rest of the tally files in /usr/local/etc/amanda/Daily to not be updated.. Houston, we may have a problem here. :-) -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Information Processing: What you call data processing when people are so disgusted with it they won't let it be discussed in their presence.