Re: dumps too big, but cannot incremental dump new disk
2002-08-20 19:01:05
On Tue, 20 Aug 2002 at 3:39pm, Marvin Davenport wrote
> I am trying to perform a forced full backup on all
> disks in disklist to tapetype HARD-DISK
>
>
> define tapetype HARD-DISK {
> length 40000 mbytes
> }
>
> there is 70GB available on the disk but I get this
> error on most of the files in the disklist
>
> FAILURE AND STRANGE DUMP SUMMARY:
> s2a.dotcom /home lev 0 FAILED [dumps too big, but
> cannot incremental
> dump new disk]
What version of amanda, and what is your tapedev?
Most likely, this is what is going on:
Amanda wants to dump to your tapedev, but can't (b/c it doesn't exist, or
some such), and so goes into "degraded mode".
In degraded mode, amanda by default reserves 100% of the disk for degraded
mode dumps, which are incrementals only.
These are all new disks, so amanda can't do incrementals, and so FAILs all
the disks.
Your options are:
1) Crank reserve down to 0, which should alleviate this problem, or
2) Use 2.4.3b3 ("b" is for beta), and its "file:" driver for tapedev, the
details of which are in the included amanda(8) man page.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
|
|
|