On Wed, 18 Apr 2001, John R. Jackson wrote:
> >3hrs, and 46min???
>
> Right. Note that you did estimates of 11 separate disks, and the default
> etimeout is 5 minutes per disk, which is 55 minutes, hence the timeout
> errors. You need to crank that way up, or it might indicate there is
> a problem with that client (bad disk, etc) that needs to be investiaged.
Okay, I cranked her up to 900 secs and last night's appeared to have gone
though ...
> >In the file for last night was a bunch of:
> >
> > DUMP: Unknown intermediate format in /etc/dumpdates, line 1
> >
> >I looked at /etc/dumpdates and the "error" was obvious in there ...
>
> I'm not clear. Are you saying the error was obvious and you fixed it,
> or that the file contained a bunch of "sendsize: running" lines (which
> would be very bad)?
Sorry, it had a 'bad' line at the top of the file ... looked like a
control character and a time stamp ... removed that ...
> >how many times should it be doing the estimations?
>
> Planner will ask for a level 0 estimate of everything in your
> disklist, and then it will ask for the same level it ran last time and
> then it may also ask for the next level.
Ah, okay ... sounds painful *but* understanding how amanda tries to
balance its backups, understandable ...
Thanks ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
