> >>>If you're still willing to bet your data on such a drive, you
> >>> can configure Amanda to put all backups on the holding disk and
> >>> then flush them to the tape. By flushing you won't get any
> >>> writing time gaps and the backup will succeed.
> >>
> >>I have to ask, how does one go about doing this?
> >
> >The easiest solution is to allow Amanda to write level 0 dumps to
> > the holding disk and don't put a tape in the drive. :-) That's
> > what I did.
> 
> I was hopeing for a bit more exotic solution, like a ./configure 
> option or an argument that could be passed to amdump 6 days, and a 
> amflush done on the 7th, or something alone those lines.
> 
> That of course should work, but requires some intelligent human to 
> do, as opposed to something that cron could do.  Like here where if 
> it wasn't for amchecks nudging, I'd forget to change tapes at least 
> once a week.  I've never been able to get cron to reach out to the 
> drive and load 4 new tapes in it when they are due :)

This seems like it would work.

Set: tapedev "/dev/notnowdarling" (in amanda.conf)

rm -f /dev/notnowdarling
amdump Daily
ln -s /dev/nst0 /dev/notnowdarling
amflush Daily
amverify Daily