Re: Times from amreport

2002-07-21 Thread Frank Smith



--On Sunday, July 21, 2002 12:30:05 -0400 Jon LaBadie [EMAIL PROTECTED] wrote:

 On Sun, Jul 21, 2002 at 12:28:52PM +0200, Ulrik Sandberg wrote:
 On Sun, 21 Jul 2002, Frank Smith wrote:
 
 For example, cron started one config at 9:30PM, sent the report
  email at 11:23PM, and reported the following:
  
  Estimate Time (hrs:min)0:06
  Run Time (hrs:min) 1:57
  Dump Time (hrs:min)4:12   1:57   2:14
  Tape Time (hrs:min)0:33   0:20   0:12
  

 
 You get away with 6 minutes of Estimates, but mine takes an hour and a
 half. So it may be a relevant question for me. :-)
 
 Yeah Frank, how do you get such quick estimates?
 Even my unix boxes take 30 min.
 The pc's an extra 2 hrs.
 

I didn't realize it was supposed to take longer ;-), I just grabbed my
latest report.  That particular config's disklist has 83 entries from
25 hosts. Most are small, the largest single entry is about 11GB. The
used filesytem sizes total about 65GB, daily writes to tape are 7-10GB. 
  All entries use tar, almost all use client compressed tar.  Original
daily size is 13-16GB).  OS's are Linux and Solaris, and some of the
larger directories are NFS mounted on the backup server (they are on
an NFS server appliance).  I don't do any Samba shares.

Frank

--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501



Re: Times from amreport

2002-07-21 Thread Frank Smith



--On Sunday, July 21, 2002 12:28:52 +0200 Ulrik Sandberg [EMAIL PROTECTED] wrote:

 On Sun, 21 Jul 2002, Frank Smith wrote:
 
For example, cron started one config at 9:30PM, sent the report
 email at 11:23PM, and reported the following:
 
 Estimate Time (hrs:min)0:06
 Run Time (hrs:min) 1:57
 Dump Time (hrs:min)4:12   1:57   2:14
 Tape Time (hrs:min)0:33   0:20   0:12
 
 This would lead me to believe that run time is wall clock time
 that Amanda ran, and dump time is the total time dumpers were
 running (i.e., 4 dumpers running in parallel for 1 hour would
 be 4 hours of dump time).
 
 Run Time is Total Wall Clock Time, Estimates included. Thanks.
 
 Since estimates, dumpers, and tapers can all run in parallel I don't
 think you can add up any of the times and get anything meaningful.
 
 Please define all run in parallel. My feeling is that no Dump will
 start until all Estimates are finished. If that's correct, then there
 could no parallelism (multiple sendsize, but zero Dumpers) during the
 Estimate phase, right?
 
 You get away with 6 minutes of Estimates, but mine takes an hour and a
 half. So it may be a relevant question for me. :-)
 
 --
 Ulrik Sandberg
 

Sorry, my best answers don't usually happen at 3am. The estimates have 
to finish first so the proper scheduling can be done, then the dumpers
and tapers can run in parallel. 

Frank   

--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501



Times from amreport

2002-07-19 Thread Ulrik Sandberg

I'm a little confused about the times reported by Amanda. Perhaps
someone could explain?

Estimate Time (hrs:min)1:25
Run Time (hrs:min) 4:02
Dump Time (hrs:min)3:07   2:38   0:30
Tape Time (hrs:min)0:43   0:42   0:02

Does this mean:

a) Total run time (estimate, dump and tape): 4:02

b) Total run time (estimate, dump and tape): 5:27 (4:02 + 1:25)

--
Ulrik Sandberg






Re: Times from amreport

2002-07-19 Thread Mitch Collinsworth


On Fri, 19 Jul 2002, Ulrik Sandberg wrote:

 Estimate Time (hrs:min)1:25
 Run Time (hrs:min) 4:02
 Dump Time (hrs:min)3:07   2:38   0:30
 Tape Time (hrs:min)0:43   0:42   0:02

 Does this mean:

 a) Total run time (estimate, dump and tape): 4:02

 b) Total run time (estimate, dump and tape): 5:27 (4:02 + 1:25)

Total run time is 4:02, as stated.  The numbers don't add up because
there is parallelism to be had from dumping simultaneous dumps to
holding disk, plus there can be another dump simultaneously being
spooled to from holding disk to tape.

-Mitch