Joshua Baker-LePain wrote:
> On Fri, 1 Feb 2002 at 12:57pm, Sacha Panasuik wrote
>
> > One slightly annoying problem is the nightly report that I receive from
> > one server (the main head office one) has, what appears to be,
> > impossible time information. For example, last nights:
> >
> > Estimate Time (hrs:min) 0:10
> >
> > Run Time (hrs:min) 6:26
> >
> > Dump Time (hrs:min) 19:14 13:46 5:28
> >
> > From this report it appears that it took 19 hours for the dump to occur
> > - perhaps I'm a little confused what run time vs. dump time is. That
> > amount of time seems very unrealistic because the backup starts at 12:15
> > AM and the report was emailed to me an 6:41 AM (i.e. less than 19 hours
> > apart by a long shot).
> >
> Amanda runs multiple dumpers in parallel whenever it can, and accounts
> for the time each dumper takes. So, while the 'amdump' command took 6:26
> to return (aka for *everything* to finish), there were actually 19:14
> worth of dumps done.
>
> Think of it like a SMP program. It may take 2 hours of wall clock time to
> finish, but it used ~4 hours of CPU time.
>
> --
> Joshua Baker-LePain
> Department of Biomedical Engineering
> Duke University
(Very large ding! goes off in head, sounds slightly echo-ey)
So I can actually use that number for some useful feedback on performance
tuning the number of dumpers, etc.
Ah yes, thanks.
--
Sacha Panasuik, MCSE
Senior Systems Administrator
TCENet Inc. - A Technology Company
"Reality is just a crutch for people who can't handle science fiction"
