Backup Central

A couple of months ago, I added a server, centernet, to my Amanda backups. Since that time, about once a week or two, but not everyday, the backup runs for 16-20 hours, instead of its normal less than 8. It's running right now since last night at 8:00pm:
amanda < at > admin:~ > amstatus DailySet1
Using /var/log/amanda/DailySet1/amdump from Wed Jun 16 20:00:00 EDT 2004

admin://db/c$ 0 462720k finished (20:56:41)
admin://db/e$ 1 10k finished (20:16:16)
admin://db/f$ 1 2559660k finished (20:51:25)
admin://db/f$/inetsrv/webpub/images 1 30k finished (20:16:07)
admin:sda1 0 3410k finished (20:17:09)
admin:sda3 0 3683924k wait for dumping
admin:sdb1 0 24270k finished (20:17:05)
centernet:sda1 0 4846k finished (20:06:03)
centernet:sda2 0 715715k finished (2:15:47)
centernet:sda3 0 110883k finished (20:58:42)
centernet:sda5 0 1812031k dumping 1332992k ( 73.56%) (2:02:34)
centernet:sda6 1 73k finished (20:03:37)
centernet:sda7 0 564k finished (20:04:03)
centernet:sda9 0 30391k finished (20:18:59)
mailinglists:hda1 0 2198k finished (20:04:30)
mailinglists:hda2 0 399339k finished (23:03:41)
mailinglists:hda7 0 743827k finished (4:41:56)

SUMMARY part real estimated
size size
partition : 17
estimated : 17 11566387k
flush : 0 0k
failed : 0 0k ( 0.00%)
wait for dumping: 1 3683924k ( 31.85%)
dumping to tape : 0 0k ( 0.00%)
dumping : 1 1332992k 1812031k ( 73.56%) ( 11.52%)
dumped : 15 5057936k 6070432k ( 83.32%) ( 43.73%)
wait for writing: 0 0k 0k ( 0.00%) ( 0.00%)
wait to flush : 0 0k 0k (100.00%) ( 0.00%)
writing to tape : 0 0k 0k ( 0.00%) ( 0.00%)
failed to tape : 0 0k 0k ( 0.00%) ( 0.00%)
taped : 15 5057936k 6070432k ( 83.32%) ( 43.73%)
7 dumpers idle : no-hold
taper idle
network free kps: 26362
holding space : 34661948k ( 95.03%)
dumper0 busy : 8:13:03 ( 95.12%)
dumper1 busy : 6:24:10 ( 74.11%)
dumper2 busy : 2:52:40 ( 33.31%)
taper busy : 1:07:38 ( 13.05%)
0 dumpers busy : 0:00:00 ( 0.00%)
1 dumper busy : 0:13:42 ( 2.64%) no-hold: 0:13:42 (100.00%)
2 dumpers busy : 7:57:50 ( 92.18%) client-constrained: 5:31:58 ( 69.47%)
no-hold: 2:25:40 ( 30.49%)
start-wait: 0:00:11 ( 0.04%)
3 dumpers busy : 0:26:50 ( 5.18%) client-constrained: 0:26:47 ( 99.77%)
start-wait: 0:00:03 ( 0.23%)
amanda < at > admin:~ >

What can be determined from this status regarding the reasons for the backup of centernet:sda5 to be so slow? Actually, I guess it was either centernet:sda1 or centernet:sda3 which took over 20 hours (am I reading this correctly, or is it 20 minutes, or is this a time-of-day?).

ps on centernet doesn't show anything abnormal:
cn2:~# ps aux |grep amanda
amanda 27333 0.0 0.2 1680 636 ? S 02:01 0:00 /usr/local/libexec/sendbackup
amanda 27335 1.9 0.2 1596 600 ? S 02:01 11:08 /bin/gzip --fast
amanda 27336 0.0 0.1 1904 364 ? S 02:01 0:00 dump 0usf 1048576 - /dev/sda5
amanda 27337 0.0 0.2 1956 664 ? S 02:01 0:07 dump 0usf 1048576 - /dev/sda5
amanda 27338 0.0 0.1 1904 488 ? S 02:01 0:12 dump 0usf 1048576 - /dev/sda5
amanda 27339 0.0 0.1 1904 504 ? S 02:01 0:11 dump 0usf 1048576 - /dev/sda5
amanda 27340 0.0 0.1 1904 480 ? S 02:01 0:12 dump 0usf 1048576 - /dev/sda5
root 29630 0.0 0.1 1336 436 pts/1 S 11:43 0:00 grep amanda
cn2:~#

And the partitions on this host aren't outrageous:
cn2:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 7.3G 1.5G 5.5G 21% /
/dev/sda1 7.6M 5.6M 1.6M 78% /boot
/dev/sda3 4.6G 291M 4.0G 7% /usr
/dev/sda5 4.6G 2.0G 2.3G 46% /opt/analog/logdata
/dev/sda6 3.7G 794M 2.7G 23% /var/www/centernet/htdocs
/dev/sda7 3.7G 5.3M 3.4G 1% /var/lib/mysql
/dev/sda9 2.8G 572M 2.0G 22% /var/www/centernet/logs
cn2:~#

Here's the relevant parts of disklist and amanda.config:
amanda < at > admin:/etc/amanda/DailySet1 > grep centernet disklist
centernet sda1 comp-user # /boot
centernet sda2 comp-user # /
centernet sda3 comp-user # /usr
centernet sda5 comp-user # /opt/analog/logdata
centernet sda6 comp-user # /var/www/centernet/htdocs
centernet sda7 comp-user # /var/lib/mysql
centernet sda9 comp-user # /var/www/centernet/logs
amanda < at > admin:/etc/amanda/DailySet1 >

amanda < at > admin:/etc/amanda/DailySet1 > egrep -v "(^( |\t)*#|^$)" amanda.conf
org "JHU/CCP" # your organization name for reports
mailto "isgalert < at > jhuccp.org" # space separated list of operators at your site
dumpuser "amanda" # the user to run dumps under
inparallel 8 # maximum dumpers that will run in parallel (max 63)
dumporder "tttttttt" # specify the priority order of each dumper
netusage 25000 Kbps # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 3 # the number of days in the normal dump cycle
runspercycle 3 # the number of amdump runs in dumpcycle days
tapecycle 25 tapes # the number of tapes in rotation
bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
etimeout 300 # number of seconds per filesystem for estimates.
dtimeout 1800 # number of idle seconds before a dump is aborted.
ctimeout 30 # maximum number of seconds that amcheck waits
tapebufs 20
tapedev "/dev/nst0" # the no-rewind tape device to be used
rawtapedev "/dev/null" # the raw device to be used (ftape only)
tapetype Python-DDS3 # what kind of tape it is (see tapetypes below)
labelstr "^DailySet1[0-9][0-9]*$" # label constraint regex: all tapes must match
holdingdisk hd1 {
comment "main holding disk"
directory "/var/amanda" # where the holding disk is
use -0Mb # how much space can we use on it. Use everything.
chunksize 1Gb # size of chunk if you want big dump to be
}
holdingdisk hd2 {
directory "/dumps2/amanda"
use -0 Mb
}
reserve 50 # percent
autoflush yes #
infofile "/var/log/amanda/DailySet1/curinfo" # database DIRECTORY
logdir "/var/log/amanda/DailySet1" # log directory
indexdir "/var/log/amanda/DailySet1/index" # index directory
define tapetype Python-DDS3 {
comment "Dell Python with DDS-3 tapes"
length 11570 mbytes
filemark 0 kbytes
speed 1078 kps
lbl-templ "/usr/local/etc/amanda/DailySet1/3holeJHUCCP.ps"
}
define dumptype global {
comment "Global definitions"
}
define dumptype comp-user {
global
comment "Non-root partitions on reasonably fast machines"
compress client fast
priority medium
}
define interface local {
comment "a local disk"
use 1000 kbps
}
define interface le0 {
comment "10 Mbps ethernet"
use 400 kbps
}
amanda < at > admin:/etc/amanda/DailySet1 >

Thanks for any suggestions on what's happening, and how to fix it. Please let me know if there's some other diagnostic I should run to further define this problem.

-Kevin Zembower


-----
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139

On Thu, Jun 17, 2004 at 12:02:29PM -0400, KEVIN ZEMBOWER wrote:
A couple of months ago, I added a server, centernet, to my
Amanda backups. Since that time, about once a week or two, but
not everyday, the backup runs for 16-20 hours, instead of its
normal less than 8. It's running right now since last night at
8:00pm:

[I've reordered the per-DLE lines, but made no other changes to them]


admin://db/c$ 0 462720k finished (20:56:41)
admin://db/e$ 1 10k finished (20:16:16)
admin://db/f$ 1 2559660k finished (20:51:25)
admin://db/f$/inetsrv/webpub/images 1 30k finished (20:16:07)
admin:sda1 0 3410k finished (20:17:09)
admin:sda3 0 3683924k wait for dumping
admin:sdb1 0 24270k finished (20:17:05)
mailinglists:hda1 0 2198k finished (20:04:30)
mailinglists:hda2 0 399339k finished (23:03:41)
mailinglists:hda7 0 743827k finished (4:41:56)

centernet:sda1 0 4846k finished (20:06:03)
centernet:sda2 0 715715k finished (2:15:47)
centernet:sda3 0 110883k finished (20:58:42)
centernet:sda5 0 1812031k dumping 1332992k ( 73.56%) (2:02:34)
centernet:sda6 1 73k finished (20:03:37)
centernet:sda7 0 564k finished (20:04:03)
centernet:sda9 0 30391k finished (20:18:59)


The times here are indeed times of day. I believe it's the time
that the DLE entered the state shown.

[...]

7 dumpers idle : no-hold
taper idle
network free kps: 26362
holding space : 34661948k ( 95.03%)
dumper0 busy : 8:13:03 ( 95.12%)
dumper1 busy : 6:24:10 ( 74.11%)
dumper2 busy : 2:52:40 ( 33.31%)
taper busy : 1:07:38 ( 13.05%)
0 dumpers busy : 0:00:00 ( 0.00%)
1 dumper busy : 0:13:42 ( 2.64%) no-hold: 0:13:42 (100.00%)
2 dumpers busy : 7:57:50 ( 92.18%) client-constrained: 5:31:58 ( 69.47%)
no-hold: 2:25:40 ( 30.49%)
start-wait: 0:00:11 ( 0.04%)
3 dumpers busy : 0:26:50 ( 5.18%) client-constrained: 0:26:47 ( 99.77%)
start-wait: 0:00:03 ( 0.23%)
[...]

Unfortunately, the amstatus output doesn't tell us how long each
DLE took to dump. We'll have to wait for the report email once
the run has finished, unless you want to start digging through
the "amdump" file -- and frankly, it's easier to wait and let
Amanda do the arithmetic But at this point, my guess would
be that it's centernet:sda2 and centernet:sda5 that are the
problems.

Interesting things here:
- Most of the DLEs finished before 21:00, i.e. within the first
hour. To the basic machinery seems to be working.

- Large DLEs tend to finish later -- but not always; consider
admin:://db/f$. Thus, size isn't the *only* factor. (E.g.
it's unlikely that large DLEs are being dumped direct to
tape; you would seem to have enough holding disk for a 2.5-GB
DLE, which is way more than centernet:sda5 needs.)

- All of the small DLEs on centernet finish quickly, so it
seems not to be the case that centernet's Amanda setup is
just hosed.

- The only non-centernet DLEs to finish later than 21:00 are
also large. But my first guess would be to put that down to
lack of holding-disk space; the two large centernet DLE's are
blocking the others. Thus, adding more holding disk would
help some, although, as mentioned above, I *don't* believe it
would address the underlying problem with centernet. E.g.
it would let admin:sda3 start dumping now, instead of waiting
for centernet:sda5 to finish.

- The run is currently in "no-hold" state, and has spent almost
three hours there; that's likely the amount of time (so far)
that more holding disk would save

dumpcycle 3 # the number of days in the normal dump cycle
runspercycle 3 # the number of amdump runs in dumpcycle days

I was going to guess that the problem happens when centernet:sda5
gets a level 0, but a three-day dumpcycle, together with your
observation that the problem happens "about once a week or two",
would seem to rule that out.

As for what's slowing down those large centernet DLEs, we don't
really know much yet. What's the CPU load like on centernet --
is it CPU-bound doing compression? Is any non-Amanda stuff
running that might be hogging resources?

How about the network between centernet and the Amanda server?
Try ftping a large file -- preferably while one of those DLEs is
still progressing slowly, so that if there's an intermittent
network problem, you'll have a better chance of catching it
red-handed.

Is there an overloaded firewall in between the two machines?

--

| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. erics < at > telepres.com
| | /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
- Patrick Lenneau

Eric and Frank, thank you very much for your detailed analysis of my problem.

I just noticed on the most recent amstatus I ran that centernet:sda5 completed, and admin:sda3 is now dumping to tape. I've pasted in the most recent amstatus to the end of this note. I guess the reason that it says just "dumping to tape" rather than centernet's "dumping 1332992k ( 73.56%) (2:02:34)" is that admin is the tapehost itself.

The holding disks on the tapehost are large, I thought:
amanda < at > admin:~ > df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 7.6G 5.2G 2.0G 72% /
/dev/sda1 22M 3.4M 17M 16% /boot
/dev/sdb1 8.3G 753M 7.1G 10% /var/amanda #This is hd1 (holding disk 1)
/dev/sdc1 33G 4.9G 26G 16% /dumps2 # and this is hd2
shmfs 1009M 0 1009M 0% /dev/shm
amanda < at > admin:~ >

They don't seem to be in use at this late stage of this backup:
amanda < at > admin:/dumps2/amanda > du -sxh . /var/amanda/
8.0k .
12k /var/amanda
amanda < at > admin:/dumps2/amanda >

Centernet is a low-volume web server, primarily. Even while running the backup, the load was less than 2. It's a 600MHz dual Pentium Dell PowerEdge 2450 with 256MB, 100MHz RAM. The tapehost, in contrast, right now has a load of almost 4:
amanda < at > admin:/dumps2/amanda > uptime
4:24pm up 1 day, 23:30, 1 user, load average: 3.77, 3.71, 3.57
amanda < at > admin:/dumps2/amanda >

There's no firewall between centernet and the tapehost, admin. Both are inside our firewall. The network is switched 100Mbps Ethernet.

Here's a ps list of the amanda jobs currently running on the tapehost:
amanda < at > admin:/dumps2/amanda > ps aux|grep amanda
amanda 4342 0.0 0.2 2220 1044 ? S Jun16 0:00 /bin/sh -c /usr/local/sbin/amdump DailySet1 && /usr/bin/mt -f /dev/nst0 offline
amanda 4346 0.0 0.2 2228 1104 ? S Jun16 0:00 /bin/sh /usr/local/sbin/amdump DailySet1
amanda 4381 0.0 0.2 2204 1080 ? S Jun16 0:02 /usr/local/libexec/driver DailySet1
amanda 4382 0.1 0.3 2780 1600 ? S Jun16 2:16 taper DailySet1
amanda 4383 0.4 0.2 2492 1216 ? S Jun16 5:12 dumper0 DailySet1
amanda 4384 0.0 0.2 2488 1208 ? S Jun16 1:07 dumper1 DailySet1
amanda 4385 0.0 0.2 2488 1208 ? S Jun16 0:28 dumper2 DailySet1
amanda 4386 0.0 0.1 2272 940 ? S Jun16 0:00 dumper3 DailySet1
amanda 4387 0.0 0.1 2272 940 ? S Jun16 0:00 dumper4 DailySet1
amanda 4388 0.1 0.2 2808 1536 ? D Jun16 1:50 taper DailySet1
amanda 4389 0.0 0.1 2272 940 ? S Jun16 0:00 dumper5 DailySet1
amanda 4390 0.0 0.1 2272 940 ? S Jun16 0:00 dumper6 DailySet1
amanda 4391 0.0 0.1 2272 940 ? S Jun16 0:00 dumper7 DailySet1
amanda 7185 0.0 0.1 2012 916 ? S 15:52 0:00 /usr/local/libexec/sendbackup
amanda 7187 57.4 0.1 1612 684 ? S 15:52 24:33 /usr/bin/gzip --fast
amanda 7188 0.1 0.2 2348 1512 ? S 15:52 0:03 dump 0usf 1048576 - /dev/sda3
amanda 7189 0.7 0.3 2440 1640 ? S 15:53 0:19 dump 0usf 1048576 - /dev/sda3
amanda 7190 1.0 0.2 2348 1504 ? S 15:53 0:27 dump 0usf 1048576 - /dev/sda3
amanda 7191 1.1 0.2 2348 1504 ? S 15:53 0:28 dump 0usf 1048576 - /dev/sda3
amanda 7192 1.0 0.2 2348 1504 ? S 15:53 0:27 dump 0usf 1048576 - /dev/sda3
amanda 7248 0.0 0.1 2064 924 pts/0 S 16:07 0:00 su - amanda
amanda 7249 0.0 0.2 2612 1508 pts/0 S 16:07 0:00 -bash
amanda 7335 0.0 0.2 2440 1504 pts/0 R 16:35 0:00 ps aux
amanda 7336 0.0 0.1 1540 576 pts/0 S 16:35 0:00 grep amanda
amanda < at > admin:/dumps2/amanda >

I'll send in the daily report as soon as I receive it. Normally, I would have interrupted amanda around 2:00pm by just killing all the amanda jobs on admin and running amcleanup. Then, I would put the next tape in and run amflush. This would complete before I needed to put the next tape in for the nightly run and go home. Tonight, I'll just let it run out. In addition, there's a thunderstorm rolling through Baltimore right now and all the lights are flickering. All the servers are on a UPS, but my workstation isn't.

The partitions on admin like "admin://db/c$" are actually Samba shares from an NT host.

Thanks, again, for all your suggestions. I won't make any changes right now, until you've had a chance to look at the daily report. I appreciate all your help.

It still hasn't ended and it's 5:03 and I'm hungry and tired, so I'm going home. I'll talk with you all again tomorrow.

-Kevin Zembower

amanda < at > admin:/dumps2/amanda > amstatus DailySet1
Using /var/log/amanda/DailySet1/amdump from Wed Jun 16 20:00:00 EDT 2004

admin://db/c$ 0 462720k finished (20:56:41)
admin://db/e$ 1 10k finished (20:16:16)
admin://db/f$ 1 2559660k finished (20:51:25)
admin://db/f$/inetsrv/webpub/images 1 30k finished (20:16:07)
admin:sda1 0 3410k finished (20:17:09)
admin:sda3 0 3683924k dumping to tape (15:52:43)
admin:sdb1 0 24270k finished (20:17:05)
centernet:sda1 0 4846k finished (20:06:03)
centernet:sda2 0 715715k finished (2:15:47)
centernet:sda3 0 110883k finished (20:58:42)
centernet:sda5 0 1818166k finished (15:52:41)
centernet:sda6 1 73k finished (20:03:37)
centernet:sda7 0 564k finished (20:04:03)
centernet:sda9 0 30391k finished (20:18:59)
mailinglists:hda1 0 2198k finished (20:04:30)
mailinglists:hda2 0 399339k finished (23:03:41)
mailinglists:hda7 0 743827k finished (4:41:56)

SUMMARY part real estimated
size size
partition : 17
estimated : 17 11566387k
flush : 0 0k
failed : 0 0k ( 0.00%)
wait for dumping: 0 0k ( 0.00%)
dumping to tape : 1 3683924k ( 31.85%)
dumping : 0 0k 0k ( 0.00%) ( 0.00%)
dumped : 17 10560026k 11566387k ( 91.30%) ( 91.30%)
wait for writing: 0 0k 0k ( 0.00%) ( 0.00%)
wait to flush : 0 0k 0k (100.00%) ( 0.00%)
writing to tape : 0 0k 0k ( 0.00%) ( 0.00%)
failed to tape : 0 0k 0k ( 0.00%) ( 0.00%)
taped : 16 6876102k 7882463k ( 87.23%) ( 59.45%)
7 dumpers idle : not-idle
taper writing, tapeq: 0
network free kps: 25498
holding space : 36474076k (100.00%)
dumper0 busy : 18:50:27 ( 95.06%)
dumper1 busy : 6:24:10 ( 32.31%)
dumper2 busy : 2:52:40 ( 14.52%)
taper busy : 1:40:59 ( 8.49%)
0 dumpers busy : 0:33:22 ( 2.81%) no-hold: 0:33:22 (100.00%)
1 dumper busy : 10:51:06 ( 54.75%) no-hold: 10:51:06 (100.00%)
2 dumpers busy : 7:57:50 ( 40.18%) client-constrained: 5:31:58 ( 69.47%)
no-hold: 2:25:40 ( 30.49%)
start-wait: 0:00:11 ( 0.04%)
3 dumpers busy : 0:26:50 ( 2.26%) client-constrained: 0:26:47 ( 99.77%)
start-wait: 0:00:03 ( 0.23%)
amanda < at > admin:/dumps2/amanda > date
Thu Jun 17 17:03:28 EDT 2004
amanda < at > admin:/dumps2/amanda >

Ohh, it ended just as I pressed 'send.' Here's the daily report:
These dumps were to tape DailySet104.
The next tape Amanda expects to use is: DailySet105.

FAILURE AND STRANGE DUMP SUMMARY:
admin //db/f$/inetsrv/webpub/images lev 1 STRANGE
admin //db/e$ lev 1 STRANGE
admin //db/f$ lev 1 STRANGE
admin //db/c$ lev 0 STRANGE


STATISTICS:
Total Full Daily
-------- -------- --------
Estimate Time (hrs:min) 0:04
Run Time (hrs:min) 21:03
Dump Time (hrs:min) 29:18 28:55 0:23
Output Size (meg) 10446.5 7946.7 2499.8
Original Size (meg) 15747.4 13247.4 2500.0
Avg Compressed Size (%) 58.5 58.5 23.5 (level:#disks ...)
Filesystems Dumped 17 13 4 (1:4)
Avg Dump Rate (k/s) 101.4 78.2 1882.1

Tape Time (hrs:min) 2:52 2:27 0:25
Tape Size (meg) 10446.7 7946.9 2499.8
Tape Used (%) 90.3 68.7 21.6 (level:#disks ...)
Filesystems Taped 17 13 4 (1:4)
Avg Tp Write Rate (k/s) 1038.9 922.9 1730.4

USAGE BY TAPE:
Label Time Size % Nb
DailySet104 2:52 10446.7 90.3 17


FAILED AND STRANGE DUMP DETAILS:

/-- admin //db/f$/inetsrv/webpub/images lev 1 STRANGE
sendbackup: start [admin://db/f$/inetsrv/webpub/images level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4428 from pid 4428)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
| tar: dumped 5 files and directories
| Total bytes written: 22528
sendbackup: size 22
sendbackup: end
\--------

/-- admin //db/e$ lev 1 STRANGE
sendbackup: start [admin://db/e$ level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4462 from pid 4462)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
| tar: dumped 9 files and directories
| Total bytes written: 1536
sendbackup: size 2
sendbackup: end
\--------

/-- admin //db/f$ lev 1 STRANGE
sendbackup: start [admin://db/f$ level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4482 from pid 4482)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
| tar: dumped 215 files and directories
| Total bytes written: 2620979200
sendbackup: size 2559550
sendbackup: end
\--------

/-- admin //db/c$ lev 0 STRANGE
sendbackup: start [admin://db/c$ level 0]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4486 from pid 4486)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\system (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\software (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\default (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\software.LOG (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\default.LOG (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SECURITY (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SECURITY.LOG (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SYSTEM.ALT (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SAM (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SAM.LOG (\WINNT\system32\config\)
? ERRDOS - ERRnoaccess opening remote file \pagefile.sys (\)
| tar: dumped 5941 files and directories
| Total bytes written: 470870016
sendbackup: size 459834
sendbackup: end
\--------


NOTES:
planner: Last full dump of admin://db/f$ on tape DailySet105 overwritten in 1 run.
planner: admin //db/f$ 20040616 0 [dump larger than tape, 12838742 KB, full dump delayed]
planner: Full dump of centernet:sda2 promoted from 2 days ahead.
planner: Full dump of mailinglists:hda2 promoted from 1 day ahead.
planner: Full dump of admin:sdb1 promoted from 2 days ahead.
planner: Full dump of mailinglists:hda7 promoted from 1 day ahead.
planner: Full dump of centernet:sda9 promoted from 2 days ahead.
planner: Full dump of admin://db/c$ promoted from 1 day ahead.
planner: Full dump of mailinglists:hda1 promoted from 2 days ahead.
planner: Full dump of centernet:sda3 promoted from 2 days ahead.
planner: Full dump of admin:sda1 promoted from 2 days ahead.
planner: Full dump of centernet:sda7 promoted from 2 days ahead.
planner: Full dump of centernet:sda1 promoted from 2 days ahead.
taper: tape DailySet104 kb 10697984 fm 17 [OK]


DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-------------------------- --------------------------------- ------------
admin //db/c$ 0 462720 462720 -- 4:191788.1 5:141475.5
admin //db/e$ 1 10 32 -- 0:09 1.1 0:002839.9
admin //db/f$ 1 25596602559680 -- 9:544312.1 24:391730.4
admin -pub/images 1 30 32 -- 12:34 0.0 0:002822.6
admin sda1 0 3410 3424 -- 0:013081.9 0:031014.4
admin sda3 0 54646573821088 69.9 70:36 902.1 70:37 901.9
admin sdb1 0 24270 24288 -- 0:055047.4 0:38 640.4
centernet sda1 0 5670 4864 85.8 1:54 42.5 0:05 887.7
centernet sda2 0 1482550 715744 48.3 306:39 38.9 13:14 901.6
centernet sda3 0 317710 110912 34.9 37:28 49.3 2:00 920.9
centernet sda5 0 20678301818176 87.9 796:47 38.0 33:21 908.7
centernet sda6 1 310 96 31.0 0:04 20.2 0:003080.0
centernet sda7 0 6090 576 9.5 0:15 37.9 0:003035.6
centernet sda9 0 580430 30400 5.2 12:29 40.6 0:33 910.4
mailinglists hda1 0 2861 2208 77.2 0:54 40.8 0:02 984.9
mailinglists hda2 0 983941 399360 40.6 171:46 38.7 7:27 892.9
mailinglists hda7 0 2163157 743840 34.4 332:00 37.3 13:42 905.2

(brought to you by Amanda version 2.4.4)

I'll take a closer look at this tomorrow. You all have a good evening.

-Kevin

--On Thursday, June 17, 2004 17:08:46 -0400 KEVIN ZEMBOWER <KZEMBOWE < at > jhuccp.org> wrote:

Ohh, it ended just as I pressed 'send.' Here's the daily report:
These dumps were to tape DailySet104.
The next tape Amanda expects to use is: DailySet105.

FAILURE AND STRANGE DUMP SUMMARY:
admin //db/f$/inetsrv/webpub/images lev 1 STRANGE
admin //db/e$ lev 1 STRANGE
admin //db/f$ lev 1 STRANGE
admin //db/c$ lev 0 STRANGE


STATISTICS:
Total Full Daily
-------- -------- --------
Estimate Time (hrs:min) 0:04
Run Time (hrs:min) 21:03
Dump Time (hrs:min) 29:18 28:55 0:23
Output Size (meg) 10446.5 7946.7 2499.8
Original Size (meg) 15747.4 13247.4 2500.0
Avg Compressed Size (%) 58.5 58.5 23.5 (level:#disks ...)
Filesystems Dumped 17 13 4 (1:4)
Avg Dump Rate (k/s) 101.4 78.2 1882.1

Tape Time (hrs:min) 2:52 2:27 0:25
Tape Size (meg) 10446.7 7946.9 2499.8
Tape Used (%) 90.3 68.7 21.6 (level:#disks ...)
Filesystems Taped 17 13 4 (1:4)
Avg Tp Write Rate (k/s) 1038.9 922.9 1730.4

USAGE BY TAPE:
Label Time Size % Nb
DailySet104 2:52 10446.7 90.3 17


FAILED AND STRANGE DUMP DETAILS:

/-- admin //db/f$/inetsrv/webpub/images lev 1 STRANGE
sendbackup: start [admin://db/f$/inetsrv/webpub/images level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4428 from pid 4428)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
| tar: dumped 5 files and directories
| Total bytes written: 22528
sendbackup: size 22
sendbackup: end
\--------

/-- admin //db/e$ lev 1 STRANGE
sendbackup: start [admin://db/e$ level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4462 from pid 4462)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
| tar: dumped 9 files and directories
| Total bytes written: 1536
sendbackup: size 2
sendbackup: end
\--------

/-- admin //db/f$ lev 1 STRANGE
sendbackup: start [admin://db/f$ level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4482 from pid 4482)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
| tar: dumped 215 files and directories
| Total bytes written: 2620979200
sendbackup: size 2559550
sendbackup: end
\--------

/-- admin //db/c$ lev 0 STRANGE
sendbackup: start [admin://db/c$ level 0]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4486 from pid 4486)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\system (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\software (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\default (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\software.LOG (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\default.LOG (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SECURITY (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SECURITY.LOG (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SYSTEM.ALT (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SAM (\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SAM.LOG (\WINNT\system32\config\)
? ERRDOS - ERRnoaccess opening remote file \pagefile.sys (\)
| tar: dumped 5941 files and directories
| Total bytes written: 470870016
sendbackup: size 459834
sendbackup: end
\--------


NOTES:
planner: Last full dump of admin://db/f$ on tape DailySet105 overwritten in 1 run.

This is a big problem. After your next run you will no longer be able to do a
full restore of this filesystem. This is caused by the line below.

planner: admin //db/f$ 20040616 0 [dump larger than tape, 12838742 KB, full dump delayed]

Amanda knows its time to do a full, but is unable to because the dump
won't fit on a single tape. You either need to split this disklist entry
into 2 (or more) subdirectories or experiment with the tape spanning code
still in development (or get bigger tapes).

planner: Full dump of centernet:sda2 promoted from 2 days ahead.
planner: Full dump of mailinglists:hda2 promoted from 1 day ahead.
planner: Full dump of admin:sdb1 promoted from 2 days ahead.
planner: Full dump of mailinglists:hda7 promoted from 1 day ahead.
planner: Full dump of centernet:sda9 promoted from 2 days ahead.
planner: Full dump of admin://db/c$ promoted from 1 day ahead.
planner: Full dump of mailinglists:hda1 promoted from 2 days ahead.
planner: Full dump of centernet:sda3 promoted from 2 days ahead.
planner: Full dump of admin:sda1 promoted from 2 days ahead.
planner: Full dump of centernet:sda7 promoted from 2 days ahead.
planner: Full dump of centernet:sda1 promoted from 2 days ahead.
taper: tape DailySet104 kb 10697984 fm 17 [OK]


DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-------------------------- --------------------------------- ------------
admin //db/c$ 0 462720 462720 -- 4:191788.1 5:141475.5
admin //db/e$ 1 10 32 -- 0:09 1.1 0:002839.9
admin //db/f$ 1 25596602559680 -- 9:544312.1 24:391730.4
admin -pub/images 1 30 32 -- 12:34 0.0 0:002822.6
admin sda1 0 3410 3424 -- 0:013081.9 0:031014.4
admin sda3 0 54646573821088 69.9 70:36 902.1 70:37 901.9
admin sdb1 0 24270 24288 -- 0:055047.4 0:38 640.4

All the rates on admin look good.

centernet sda1 0 5670 4864 85.8 1:54 42.5 0:05 887.7
centernet sda2 0 1482550 715744 48.3 306:39 38.9 13:14 901.6
centernet sda3 0 317710 110912 34.9 37:28 49.3 2:00 920.9
centernet sda5 0 20678301818176 87.9 796:47 38.0 33:21 908.7
centernet sda6 1 310 96 31.0 0:04 20.2 0:003080.0
centernet sda7 0 6090 576 9.5 0:15 37.9 0:003035.6
centernet sda9 0 580430 30400 5.2 12:29 40.6 0:33 910.4
mailinglists hda1 0 2861 2208 77.2 0:54 40.8 0:02 984.9
mailinglists hda2 0 983941 399360 40.6 171:46 38.7 7:27 892.9
mailinglists hda7 0 2163157 743840 34.4 332:00 37.3 13:42 905.2

The dumper rates on these others are pretty poor. Do you have a duplex
mis-match on your server, client or switch? If you ftp a fair-sized file
both ways between admin and centernet, what transfer rates do you get?
I get a little over twice that rate on the clients I backup over a 4.5 megabit
VPN WAN link, and even my slowest local client (an ancient MIPS-based box) can
dump at around 100KB/s. Most of my clients dump (client compress tar, actually)
in the 1000-3000KB/s range.

You might want to set columnspec in your config so the numbers don't all
run together.

Frank


(brought to you by Amanda version 2.4.4)

I'll take a closer look at this tomorrow. You all have a good evening.

-Kevin



--
Frank Smith fsmith < at > hoovers.com
Sr. Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501

Frank, thanks, again, for your analysis.

When you mentioned the connection speed, I remembered that I had to ask our network administrators to change the speed and auto-negotiation properties on the Cisco switch that the old centernet host was plugged into to fix the speed at 100baseTx-FD and turn off auto-negoiation. I've forgotten to do that for the new centernet host. On the admin host, it was okay:

admin:~ # mii-diag
Using the default interface 'eth0'.
Basic registers of MII PHY #1: 2100 780d 02a8 0154 05e1 0000 0000 0000.
Basic mode control register 0x2100: Auto-negotiation disabled, with
Speed fixed at 100 mbps, full-duplex.
You have link beat, and everything is working OK.
Link partner information is not exchanged when in fixed speed mode.
End of basic transceiver information.

admin:~ #
admin:~ # ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:90:27:B6:FB:E7
inet addr:172.16.2.7 Bcast:172.16.255.255 Mask:255.255.0.0
inet6 addr: fe80::290:27ff:feb6:fbe7/10 Scope:Link
inet6 addr: fe80::90:27b6:fbe7/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22539412 errors:0 dropped:0 overruns:0 frame:0
TX packets:16228564 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:768887232 (733.2 Mb) TX bytes:1301570470 (1241.2 Mb)
Interrupt:21 Base address:0x8000

admin:~ # uptime
11:00am up 2 days, 18:06, 1 user, load average: 2.01, 1.97, 1.59
admin:~ # date
Fri Jun 18 11:00:23 EDT 2004
admin:~ #

Even thought the admin host has only been up 2 days, there are zero collisions and carrier errors. When I tested the file transfer speed between centernet and admin, before making any changes, I also noticed that auto-negoiation was on, and that it was not set to full duplex:

cn2:~# mii-diag
Using the default interface 'eth0'.
Basic registers of MII PHY #1: 3000 782d 02a8 0154 05e1 4081 0003 0000.
The autonegotiated capability is 0080.
The autonegotiated media type is 100baseTx.
Basic mode control register 0x3000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
Your link partner advertised 4081: 100baseTx.
End of basic transceiver informaion.

cn2:~#

kevinz < at > cn2:~/dblogs$ ncftpput -u kevinz -p xxxxxx admin ~/ 20040610.popline..wpd
20040610.popline.wpd: 988.09 MB 36.13 kB/s
ncftpput 20040610.popline.wpd: data transfer aborted by local user.
kevinz < at > cn2:~/dblogs$

After fixing the speed to 100baseTx-FD and turning auto-negoiation off, the speed improved 300 times:

cn2:~# mii-diag -F 100baseTx-FD
Using the default interface 'eth0'.
Setting the speed to "fixed", Control register 2100.
Basic registers of MII PHY #1: 2100 780d 02a8 0154 05e1 4081 0001 0000.
The autonegotiated capability is 0080.
The autonegotiated media type is 100baseTx.
Basic mode control register 0x2100: Auto-negotiation disabled, with
Speed fixed at 100 mbps, full-duplex.
You have link beat, and everything is working OK.
Your link partner advertised 4081: 100baseTx.
End of basic transceiver informaion.

cn2:~#

cn2:~# mii-diag
Using the default interface 'eth0'.
Basic registers of MII PHY #1: 2100 780d 02a8 0154 05e1 4081 0001 0000.
The autonegotiated capability is 0080.
The autonegotiated media type is 100baseTx.
Basic mode control register 0x2100: Auto-negotiation disabled, with
Speed fixed at 100 mbps, full-duplex.
You have link beat, and everything is working OK.
Your link partner advertised 4081: 100baseTx.
End of basic transceiver informaion.

kevinz < at > cn2:~/dblogs$ ncftpput -u kevinz -p xxxxxx admin ~/ 20040610.popline..wpd
20040610.popline.wpd: 988.09 MB 11.04 MB/s
ncftpput 20040610.popline.wpd: data transfer aborted by local user.
kevinz < at > cn2:~/dblogs$

I should have also noticed the large number of collision and carrier errors on centernet:

cn2:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:B0:D0:49:55:20
inet addr:172.16.2.4 Bcast:172.16.255.255 Mask:255.255.0.0
IPX/Ethernet 802.3 addr:00000958:00B0D0495520
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:43966452 errors:0 dropped:0 overruns:0 frame:0
TX packets:50236123 errors:0 dropped:0 overruns:25 carrier:10736563
collisions:11145079 txqueuelen:100
RX bytes:1206617378 (1.1 GiB) TX bytes:4000069366 (3.7 GiB)
Interrupt:16 Base address:0x5000

cn2:~# uptime
11:00:06 up 45 days, 13 min, 1 user, load average: 0.00, 0.04, 0.13
cn2:~# date
Fri Jun 18 11:00:07 EDT 2004
cn2:~#

I compared this with the OLD centernet host, which I still have up and has been up much longer than either admin or the new centernet:
OLD centernet:
centernet:~ # ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:A0:C9:E4:5B:D5
inet addr:172.16.2.6 Bcast:172.16.255.255 Mask:255.255.0.0
inet6 addr: fe80::a0:c9e4:5bd5/10 Scope:Link
inet6 addr: fe80::2a0:c9ff:fee4:5bd5/10 Scope:Link
IPX/Ethernet 802.3 addr:00000958:00A0C9E45BD5
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:244996240 errors:0 dropped:0 overruns:0 frame:0
TX packets:178882777 errors:0 dropped:0 overruns:0 carrier:2
collisions:2 txqueuelen:100
Interrupt:14 Base address:0x2000

centernet:~ # uptime
11:06am up 228 days, 5 min, 1 user, load average: 0.99, 0.97, 0.91
centernet:~ # date
Fri Jun 18 11:06:55 EDT 2004
centernet:~ #

So, based on all this, I think the main problem was the transfer speed. I've taken these steps to correct that, although I wish I could remember what I need to do to set the NIC to this speed and no auto-negoiation on boot-up. I'm also going to increase the interface le0 speed in amanda.conf from 400 to 4000kbps, as the backup runs at night when the network is lightly loaded. I don't know why the 33G of holding disk space doesn't seem like enough or isn't getting used. I'll reverse the order of holding disk hd1, which is only 8G, with hd2, 33G, so maybe it'll use the larger one first.

Thanks, again, for all your help. I'll address the problem you spotted with the last full dump of admin://db/f$ being overwritten in another message to the list, as I'm confused about this, too.

-Kevin

KEVIN ZEMBOWER wrote:

I don't know why the 33G of
holding disk space doesn't seem like enough or isn't getting used.
I'll reverse the order of holding disk hd1, which is only 8G, with
hd2, 33G, so maybe it'll use the larger one first.

Any other parameters in the config for holding disk that could
affect the use of it?



--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens < at > xplanation.com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************

Paul, thanks for your thoughts. I don't think so. The whole amanda.conf concerning the holding disks is:
holdingdisk hd1 {
comment "main holding disk"
directory "/var/amanda" # where the holding disk is
use -0Mb # how much space can we use on it. Use everything.
chunksize 1Gb # size of chunk if you want big dump to be

}
holdingdisk hd2 {
directory "/dumps2/amanda"
use -0 Mb
}
reserve 50 # percent

amanda < at > admin:/etc/amanda/DailySet1 > amcheck DailySet1
Amanda Tape Server Host Check
-----------------------------
Holding disk /dumps2/amanda: 28166344 KB disk space available, using 28166344 KB
Holding disk /var/amanda: 8307732 KB disk space available, using 8307732 KB
NOTE: skipping tape-writable test
Tape DailySet106 label ok
Server check took 10.613 seconds

Amanda Backup Client Hosts Check
--------------------------------
Client check: 3 hosts checked in 1.359 seconds, 0 problems found

(brought to you by Amanda 2.4.4)
amanda < at > admin:/etc/amanda/DailySet1 > df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 7.6G 5.2G 2.0G 72% /
/dev/sda1 22M 3.4M 17M 16% /boot
/dev/sdb1 8.3G 8.0k 7.9G 1% /var/amanda
/dev/sdc1 33G 4.9G 26G 16% /dumps2
shmfs 1010M 0 1010M 0% /dev/shm
amanda < at > admin:/etc/amanda/DailySet1 >

Can you think of something I'm overlooking?

Thanks, again.

-Kevin

Paul Bijnens <paul.bijnens < at > xplanation.com> 06/18/04 12:43PM >>>
KEVIN ZEMBOWER wrote:

I don't know why the 33G of
holding disk space doesn't seem like enough or isn't getting used.
I'll reverse the order of holding disk hd1, which is only 8G, with
hd2, 33G, so maybe it'll use the larger one first.

Any other parameters in the config for holding disk that could
affect the use of it?



--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens < at > xplanation.com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************

Boy is it hard to send a reply that makes sense when there
is a mixture of unedited top and bottom postings :(


On Fri, Jun 18, 2004 at 01:12:35PM -0400, KEVIN ZEMBOWER wrote:

Paul Bijnens <paul.bijnens < at > xplanation.com> 06/18/04 12:43PM >>>
KEVIN ZEMBOWER wrote:

I don't know why the 33G of
holding disk space doesn't seem like enough or isn't getting used.
I'll reverse the order of holding disk hd1, which is only 8G, with
hd2, 33G, so maybe it'll use the larger one first.

Any other parameters in the config for holding disk that could
affect the use of it?

Paul, thanks for your thoughts. I don't think so. The whole amanda.conf concerning the holding disks is:
holdingdisk hd1 {
comment "main holding disk"
directory "/var/amanda" # where the holding disk is
use -0Mb # how much space can we use on it. Use everything.
chunksize 1Gb # size of chunk if you want big dump to be

}
holdingdisk hd2 {
directory "/dumps2/amanda"
use -0 Mb
}
reserve 50 # percent

...

Can you think of something I'm overlooking?


Just a wierd, unlikely, possibility.

The amanda man page says for the "use" parameter

- a positive number means use only that amount
- a zero means use all available
- a negative number means use all EXCEPT that amount

You use parameter fits none of these exactly in that you have
a negative zero. Is it possible the zero is being interpreted
as "all" and the negative as "except"?


--
Jon H. LaBadie jon < at > jgcomp.com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)

Jon, I apologize. My email reader, GroupWise, doesn't quote lines, so I'd have to manually break each line and insert ">". That gets me into trouble with the other half of the world who want their email readers to adjust line length to the width that they prefer.

You know, I've never looked at the amanda man page for the 'use' value. I just went by the comments in the amanda.conf file, which state, "a non-positive value means: use all space but that value." So I couldn't use 0 (zero) because that would say "use only zero KB" according to these comments. I used '-0' meaning 'use everything BUT 0 KB'. Thanks for pointing this out. I'll change it right away, and see if that makes a difference.

Thanks, again, for your suggestions.

-Kevin

jon < at > jgcomp.com 06/18/04 01:45PM >>>
Boy is it hard to send a reply that makes sense when there
is a mixture of unedited top and bottom postings :(


On Fri, Jun 18, 2004 at 01:12:35PM -0400, KEVIN ZEMBOWER wrote:

KEVIN ZEMBOWER wrote:

Paul, thanks for your thoughts. I don't think so. The whole amanda.conf concerning the holding disks is:
holdingdisk hd1 {
comment "main holding disk"
directory "/var/amanda" # where the holding disk is
use -0Mb # how much space can we use on it. Use everything..
chunksize 1Gb # size of chunk if you want big dump to be

}
holdingdisk hd2 {
directory "/dumps2/amanda"
use -0 Mb
}
reserve 50 # percent

....

Can you think of something I'm overlooking?


Just a wierd, unlikely, possibility.

The amanda man page says for the "use" parameter

- a positive number means use only that amount
- a zero means use all available
- a negative number means use all EXCEPT that amount

You use parameter fits none of these exactly in that you have
a negative zero. Is it possible the zero is being interpreted
as "all" and the negative as "except"?


--
Jon H. LaBadie jon < at > jgcomp.com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)

KEVIN ZEMBOWER wrote:

The amanda man page says for the "use" parameter

- a positive number means use only that amount
- a zero means use all available
- a negative number means use all EXCEPT that amount

You use parameter fits none of these exactly in that you have
a negative zero. Is it possible the zero is being interpreted
as "all" and the negative as "except"?


You could leave it out too, and use the default ( = all space).