Re: Problem with initial install of amanda on SCO openserver
taper: tape DailySet101 kb 1408 fm 1 writing filemark: I/O error ... Now, I know that there is enough room on the tape for what I am backing up. (40G tape, /home on the cvs server = 188M, /home on the cclcsup server = 3.1G) Amanda is just telling you what the OS told it -- there was an I/O error while trying to write to the tape. That could be hardware (tape or drive), the drive may need cleaning, cabling problems or any number of other things. But you need to get that fixed before you'll be able to do reliable backups (with Amanda or anything else). I'd probably do a bunch of big dd bs=32k I/O tests to the drive (and *scratch* tapes :-). driver: dumper0 pid 2129 is messed up, ignoring it. driver: dumper0 exited with signal 6 This is odd. It implies the dumper died with an I/O trap (which is different than the above error -- don't get confused) or it call abort() on itself. Are there core files in /tmp/amanda (or wherever)? Is there anything else of interest about dumper0 in amdump.NN? Also, what is the recommended solution for replacing a tape in a tape run? i.e. if the tape gets damaged? Presumably you would need to get a new tape, label it the same as the old tape and just add it to the run, right? Yup. If the old tape has valid data on it, you might run amrmtape to clean out that information. Or just keep it around until the tapes cycle and get reused. -Josh John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problem with initial install of amanda on SCO openserver
Thanks for the help, I more-or-less got things working.
The problem was a combination of the etimeout value, and
some oddities that occurred when I replaced MMDF with Sendmail.
However, I now have a new problem. The check seems to run fine:
--start check--
[root]/home/users su amanda -c /usr/local/sbin/amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /usr/local/amanda/dumps: 58975840 KB disk space available, that's plenty
ERROR: cannot overwrite active tape DailySet101
(expecting a new tape)
NOTE: skipping tape-writable test
Server check took 4.827 seconds
Amanda Backup Client Hosts Check
Client check: 2 hosts checked in 1.696 seconds, 0 problems found
(brought to you by Amanda 2.4.3)
---end check---
However, the actual run seems to have problems:
---start run---
These dumps were to tape DailySet101.
*** A TAPE ERROR OCCURRED: [[writing filemark: I/O 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: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
cclcsup/home lev 0 FAILED [out of tape]
cclcsup/home lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:13
Run Time (hrs:min) 0:45
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 1.30.01.3
Original Size (meg) 1.30.01.3
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped1 0 1 (1:1)
Avg Dump Rate (k/s) 371.9-- 371.9
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 1.40.01.4
Tape Used (%) 0.00.00.0 (level:#disks ...)
Filesystems Taped 1 0 1 (1:1)
Avg Tp Write Rate (k/s) 146.6-- 146.6
NOTES:
planner: Last full dump of cclcsup:/home on tape overwritten in 1 run.
taper: tape DailySet101 kb 1408 fm 1 writing filemark: I/O error
driver: dumper0 pid 2129 is messed up, ignoring it.
driver: dumper0 exited with signal 6
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
cclcsup /home 0 FAILED ---
cvsserver/home 11370 1408 --0:04 371.8 0:10 146.6
(brought to you by Amanda version 2.4.3)
---end run---
Now, I know that there is enough room on the tape for what I am backing up.
(40G tape, /home on the cvs server = 188M, /home on the cclcsup server = 3.1G)
Any suggestions?
Also, what is the recommended solution for replacing a tape in a tape run?
i.e. if the tape gets damaged? Presumably you would need to get a new tape,
label it the same as the old tape and just add it to the run, right?
Thanks,
-Josh
[EMAIL PROTECTED]
Re: Problem with initial install of amanda on SCO openserver
On Tuesday 31 December 2002 18:04, Josh More wrote:
Thanks for the help, I more-or-less got things working.
The problem was a combination of the etimeout value, and
some oddities that occurred when I replaced MMDF with Sendmail.
However, I now have a new problem. The check seems to run fine:
--start check--
[root]/home/users su amanda -c /usr/local/sbin/amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /usr/local/amanda/dumps: 58975840 KB disk space
available, that's plenty ERROR: cannot overwrite active tape
DailySet101
(expecting a new tape)
This is a showstopper Josh. Either you need to label more tapes for
amanda's use or whatever as amanda thinks there is already a backup
on that tape, and will refuse to overwrite it until tapecycle
tapes have been used since the last time this tape was written to.
Amanda will not normally append to an existing backup because of the
uncertainties of where on the tape it is unless it has total
control of the drive in one contiguous run.
NOTE: skipping tape-writable test
Server check took 4.827 seconds
Amanda Backup Client Hosts Check
Client check: 2 hosts checked in 1.696 seconds, 0 problems found
(brought to you by Amanda 2.4.3)
---end check---
However, the actual run seems to have problems:
---start run---
These dumps were to tape DailySet101.
*** A TAPE ERROR OCCURRED: [[writing filemark: I/O 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: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
cclcsup/home lev 0 FAILED [out of tape]
cclcsup/home lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:13
Run Time (hrs:min) 0:45
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 1.30.01.3
Original Size (meg) 1.30.01.3
Avg Compressed Size (%) -- -- --
(level:#disks ...) Filesystems Dumped1 0
1 (1:1) Avg Dump Rate (k/s) 371.9--
371.9
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 1.40.01.4
Tape Used (%) 0.00.00.0
(level:#disks ...) Filesystems Taped 1 0
1 (1:1) Avg Tp Write Rate (k/s) 146.6--
146.6
NOTES:
planner: Last full dump of cclcsup:/home on tape overwritten in
1 run. taper: tape DailySet101 kb 1408 fm 1 writing filemark: I/O
error driver: dumper0 pid 2129 is messed up, ignoring it.
driver: dumper0 exited with signal 6
DUMP SUMMARY:
DUMPER STATSTAPER
STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS
KB/s MMM:SS KB/s --
- cclcsup /home
0 FAILED --- cvsserver
/home 11370 1408 --0:04 371.8 0:10 146.6
(brought to you by Amanda version 2.4.3)
---end run---
Now, I know that there is enough room on the tape for what I am
backing up. (40G tape, /home on the cvs server = 188M, /home on
the cclcsup server = 3.1G)
Any suggestions?
Also, what is the recommended solution for replacing a tape in a
tape run? i.e. if the tape gets damaged? Presumably you would
need to get a new tape, label it the same as the old tape and
just add it to the run, right?
One could, with a lot of hand editing, do that. However amanda
needs to know that the tape is fubar so amanda can remove the
indices and such associated with that tape, see the manpages
please. Once that is done, then you can label a new one to replace
it, but amanda will then use it when she asks for it, which may not
be in the proper numerical order for humans to use. Amanda doesn't
care as long as the tape she is supposed to use is available when
she needs it.
Thanks,
-Josh
[EMAIL PROTECTED]
[This E-mail scanned for viruses by Declude Virus]
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.21% setiathome rank, not too shabby for a WV hillbilly
Problem with initial install of amanda on SCO openserver
I have installed amanda on SCO Openserver 5.0.6, and everything has
passed the checks. However, when I issue the command:
su amanda -c /usr/local/sbin/amdump Daily
I get the report at the bottom of this email.
I have checked the net and the faq-o-matic, and can't
seem to figure out what is causing this. The only note that
I saw related to symlinks, but there are none in /home.
Please help me by telling me where to look, or ask for
information I have not provided. I'm new at this, so I
don't even know what information is needed.
-Josh
[EMAIL PROTECTED]
--Start Report
These dumps were to tape DailySet101.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
backupmast /home RESULTS MISSING
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 backupmaster:/home.
driver: WARNING: got empty schedule from planner
taper: tape DailySet101 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
backupmaster /home MISSING --
(brought to you by Amanda version 2.4.3)
--End Report--
Re: Problem with initial install of amanda on SCO openserver
On Mon, 30 Dec 2002, Josh More wrote: FAILURE AND STRANGE DUMP SUMMARY: backupmast /home RESULTS MISSING Firstly, before running amdump did you run amcheck? If yes, what do you see in /tmp/amanda? -Mitch
