Jon LaBadie wrote: > On Fri, Sep 06, 2002 at 11:44:35AM +0200, Walter Willmertinger wrote: > > > > >Is there any option to switch amdump only to dump to the (large > > >enough) holding disk? > > >We have the problem that our tape drive (Onstream ADR-50) has a > > I think everyone who has an Onstream does. > > > >frimware problem, as recognized by some people in this group, so > > >that the normal way which amdump uses to write to teh tape, produces > > >hardware errors, when reading the tape. > > >The firmware has problems with the large breaks between writing > > >different tape blocks, which is an usual feature of amanda. > > > > > >So I thought of > > >1. using amdump to produce the holding disk > > >2. after amdump has completely finished writing to the holding disk, > > >to use amflush to save the whole thing on tape. This should work, > > >because in this case the tape is written in one large amount without > > >any break. > > Just leave the tape out, it will automatically collect on the holding disk. > > This assumes you have the reserve parameter (reserve for incrementals) set > to a sufficiently low percentage. The default is 100 I think, meaning > reserve the entire holding disk for incrementals. > >
Hi Jon, You forgot to mention to run amflush <config> in the morning after sticking the tape in. This setup has been running succesfull here for 2 months now. And I also run amverify after each tape is written. Just to make sure.... In the meantine, I received an OnStream ADR^2 120 SCSI drive for testing purposes. This one works like a charm with Amanda. I use the ADR 50 for the daily backups and the ADR^2 120 for the weekly firebackup (offsite storage) Regards, Edwin Hakkennes [EMAIL PROTECTED]
