Re: problems with backup to one specific box
-BEGIN PGP SIGNED MESSAGE-
> "John" == John R Jackson <[EMAIL PROTECTED]> writes:
>> I setup a new config for just that system. I ran it with tcpdump watching.
>> I never saw an attempt to connect to backup.
>> ...
>> *** A TAPE ERROR OCCURRED: [label DailySet120 doesn't match labelstr "^LOX[0-9
>> ][0-9]*$"].
>> ...
>> loxwd0a lev 0 FAILED [can't switch to incremental dump]
>> ...
>> planner: Adding new disk lox:wd0a.
John> When Amanda "sees" a client/disk it has never done before, it has to do
John> a level 0 (full) dump to get things started. However, a tape error,
John> such as the label string mismatch, tells Amanda it should drop into
Okay, fair enough.
John> "degraded mode" in which it will only do incrementals of anything that
John> has not yet been processed. But it cannot do that in your case since
John> the disk is new, so it gave up.
John> Short answer -- fix the tape problem so Amanda has a tape to write to.
John> Longer answer -- you can change the "reserve" parameter to a value less
John> than the default of 100% to allow Amanda to go ahead and do level 0
John> dumps into the holding disk (assuming they will fit) even when a tape
John> error happens.
That will help me diagnose the problem on the limited config. (with just
the one host).
It doesn't address the fundamental problem.
Why is there a write file problem, I'm not sure. I think my tape size
estimate is slightly off, so i fall off the end of the tape. However, many
things did go to disk. I will toggle reserve to see if that helps.
(My hold disk is 15Gb in size. My tapes are HP DAT DDS-II drive, so there
is no problem running)
[note, slightly edited to remove host names that I do now want public]
These dumps were to tape DailySet120.
*** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: DailySet109.
FAILURE AND STRANGE DUMP SUMMARY:
marajade wd0h lev 0 FAILED [disk wd0h offline on marajade?]
loxwd1g lev 0 FAILED [Request to lox timed out.]
loxwd1f lev 0 FAILED [Request to lox timed out.]
loxwd1e lev 0 FAILED [Request to lox timed out.]
loxwd0g lev 0 FAILED [Request to lox timed out.]
loxwd0f lev 0 FAILED [Request to lox timed out.]
loxwd0e lev 0 FAILED [Request to lox timed out.]
loxwd0a lev 0 FAILED [Request to lox timed out.]
cassidyhdc3 lev 5 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)1:10
Run Time (hrs:min) 6:55
Dump Time (hrs:min)7:43 6:36 1:07
Output Size (meg)2355.4 988.7 1366.8
Original Size (meg) 4504.7 2681.6 1823.2
Avg Compressed Size (%)52.3 36.9 75.0 (level:#disks ...)
Filesystems Dumped 19 4 15 (1:9 2:1 3:4 5:1)
Avg Dump Rate (k/s)86.7 42.6 346.8
Tape Time (hrs:min)0:43 0:24 0:19
Tape Size (meg) 1035.6 539.3 496.2
Tape Used (%) 26.9 14.0 12.9 (level:#disks ...)
Filesystems Taped17 3 14 (1:9 2:1 3:4)
Avg Tp Write Rate (k/s) 407.8 379.3 444.0
NOTES:
planner: Adding new disk marajade:wd0h.
planner: Incremental of istari:sd0e bumped to level 3.
planner: Dump larger than tape: full dump of cassidy:hdc3 delayed.
planner: Full dump of istari:sd0e promoted from 21 days ahead.
planner: Full dump of marajade:wd0a promoted from 21 days ahead.
planner: Full dump of istari:sd3g promoted from 21 days ahead.
planner: Full dump of istari:sd2e promoted from 21 days ahead.
taper: tape DailySet120 kb 1664544 fm 18 writing file: Input/output error
driver: going into degraded mode because of tape error.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
- -- -
cassidy hda11 32010 2848 8.9 1:33 30.7 0:12 232.3
cassidy hda33 238140 170720 71.7 8:02 353.9 6:15 455.7
cassidy hdc11 330 32 9.7 1:26 0.4 0:001194.8
cassidy hdc23 226490 78464 34.6 5:41 229.8 2:59 438.8
cassidy hdc35 1062490 891904 83.9 28:34 520.4 N/A N/A
cassidy hdc43 186390 183424 98.4 5:34 548.6 6:50 447.8
istari sd0a1 399 96 24.1 0:26 3.7 0:00 759.8
istari sd0e0 188251 28192 15.0 46:51 10.0 1:16 373.4
istari sd0f1 121 32 26.4 0:46 0.7 0:00 454.2
istari sd1a2 420
Re: problems with backup to one specific box
> I setup a new config for just that system. I ran it with tcpdump watching. >I never saw an attempt to connect to backup. >... >*** A TAPE ERROR OCCURRED: [label DailySet120 doesn't match labelstr "^LOX[0-9 >][0-9]*$"]. >... > loxwd0a lev 0 FAILED [can't switch to incremental dump] >... > planner: Adding new disk lox:wd0a. When Amanda "sees" a client/disk it has never done before, it has to do a level 0 (full) dump to get things started. However, a tape error, such as the label string mismatch, tells Amanda it should drop into "degraded mode" in which it will only do incrementals of anything that has not yet been processed. But it cannot do that in your case since the disk is new, so it gave up. Short answer -- fix the tape problem so Amanda has a tape to write to. Longer answer -- you can change the "reserve" parameter to a value less than the default of 100% to allow Amanda to go ahead and do level 0 dumps into the holding disk (assuming they will fit) even when a tape error happens. >Michael Richardson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
problems with backup to one specific box
-BEGIN PGP SIGNED MESSAGE-
I run a small-ish network. There is a 4-port firewall that seperates boxes
of various security levels which have different policies.
My backup server lives on the most secure network.
With one machine (a RH 7.2 server) I went through rebuilding with
port-ranges set and I adjusted the firewall. That backup is working fine.
Another network has two boxes (lox and nox). Both run NetBSD/i386 (1.5.2)
with amanda-client installed from pkgsrc. This was built on the backup server
and the pkg distributed. My notebook (a PIII-650) runs the identical code
without problem.
Until two weeks ago, lox was a P75 with 6Gb of disk, and nox is a K2-350
with 4Gb of disk. (Old systems).
I never got a good backup of lox, while nox has never failed.
No partition is larger than the raw size of the tape device.
As it was overdue, lox was upgraded to a PII-233 with slightly more disk
space. More importantly, it got a brand new /etc dir. (The previous one dated
to 1993...).
I got a single good backup from lox the following night. (a level 0)
I setup a new config for just that system. I ran it with tcpdump watching.
I never saw an attempt to connect to backup.
Some nights I've gotten "can't switch to incremental dumps".
With the seperate config with just that host, I always get a failure.
Even with just one disk listed in disklist.
I thought that was a FAQ, but it isn't.
From: System Operator <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: LOX AMANDA MAIL REPORT FOR January 23, 2002
*** A TAPE ERROR OCCURRED: [label DailySet120 doesn't match labelstr
"^LOX[0-9][0-9]*$"].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
loxwd0a lev 0 FAILED [can't switch to incremental dump]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk lox:wd0a.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
- -- -
lox wd0a0 FAILED ---
(brought to you by Amanda version 2.4.2p2)
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON|net architect[
] [EMAIL PROTECTED] http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy"); [
-BEGIN PGP SIGNATURE-
Version: 2.6.3ia
Charset: latin1
Comment: Finger me for keys
iQCVAwUBPE9aO4qHRg3pndX9AQFzAQP/VK+agfRfYLpp1q2kNGPGzhx0nrKJNe92
JeO0avk3mPfeFfYMajh2vl6C6ttEv0yE226c7fPfiegitnrp0WUarFihykTiHrlj
cP3tlUbKJhTHT5IYmTeGD5GH1weLvHWW8652BtB9C9jEZ7D5BE34rWh+0SJ3Cx9k
hdyjwvQGfQU=
=t7BV
-END PGP SIGNATURE-
