Re: Disagreements between amplot, amstatus
2006-05-30 17:00:57
Ross Vandegrift wrote:
Hello everyone,
I'm working on getting one of my Amanda servers to finish dumping a
little bit faster. Right now, all but one of my hosts are taking
around four hours to finish.
Anyhow, I noticed that amstatus says this after the run:
0 dumpers busy : 0:33:39 ( 3.64%) not-idle: 0:33:39 (100.00%)
1 dumper busy : 9:38:18 ( 62.47%) not-idle: 9:37:29 ( 99.86%)
no-bandwidth: 0:00:49 ( 0.14%)
2 dumpers busy : 0:28:11 ( 3.05%) not-idle: 0:27:57 ( 99.18%)
no-bandwidth: 0:00:13 ( 0.82%)
3 dumpers busy : 0:26:59 ( 2.92%) no-bandwidth: 0:22:59 ( 85.20%)
not-idle: 0:03:59 ( 14.80%)
4 dumpers busy : 2:13:20 ( 14.40%) no-bandwidth: 1:56:04 ( 87.06%)
not-idle: 0:17:15 ( 12.94%)
5 dumpers busy : 1:12:40 ( 7.85%) no-bandwidth: 1:12:40 (100.00%)
6 dumpers busy : 0:32:23 ( 3.50%) no-bandwidth: 0:32:23 (100.00%)
7 dumpers busy : 0:03:03 ( 0.33%) no-bandwidth: 0:03:03 (100.00%)
8 dumpers busy : 0:00:27 ( 0.05%) no-bandwidth: 0:00:27 (100.00%)
9 dumpers busy : 0:00:48 ( 0.09%) no-bandwidth: 0:00:48 (100.00%)
10 dumpers busy : 0:00:09 ( 0.02%) no-bandwidth: 0:00:09 (100.00%)
Looks like I have too many dumpers for my bandwidth, no? FWIW,
netusage is set to 80 Mbps.
But amplot's Bandwidth Allocated graph shows the line mostly pegged at 0% the
entire time. From glancing through the amplot scripts, I'm guessing
this should be labeled "Bandwidth Free"?
If you run amstatus again what is the value you have in the field below:
network free kps: ?
also what is your inparallel and maxdumps set to in amanda.conf?
|
|
|