Last May(2000), I installed amanda-2.4.1p1 on a Redhat 6.2 Intel box with an
internal EXB-8500 drive at /dev/st0. When I did the install back then, I
simply reformatted the amanda.conf, created the disklist and setup the
crontab. Everything worked.
Of course, typical with some "magically works" installs, it STOPPED working
last March (this is an OLD contract of mine). Currently what the box is
experiencing is:
These dumps were to tape Daily09.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
<server FQDN here> /dev/ida/c0d0p5 lev 0 FAILED [Request to <server FQDN
here> timed out
<server FQDN here> /dev/ida/c0d0p8 lev 0 FAILED [Request to <server FQDN
here> timed out.]
<server FQDN here> /dev/ida/c0d0p7 lev 0 FAILED [Request to <server FQDN
here> timed out.]
<server FQDN here> /dev/ida/c0d0p9 lev 0 FAILED [Request to <server FQDN
here> timed out.]
<server FQDN here> /dev/ida/c0d0p6 lev 0 FAILED [Request to <server FQDN
here> timed out.]
<server FQDN here> /dev/ida/c0d0p10 lev 0 FAILED [Request to <server FQDN
here> timed out.]
<server FQDN here> /dev/ida/c0d0p1 lev 0 FAILED [Request to <server FQDN
here> timed out.]
STATISTICS:
Total Full Daily
-------- -------- --------
Estimate Time (hrs:min) 1:10
Run Time (hrs:min) 1:10
Dump Time (hrs:min) 0:00 0:00 0:00
Output Size (meg) 0.0 0.0 0.0
Original Size (meg) 0.0 0.0 0.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped 0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min) 0:00 0:00 0:00
Tape Size (meg) 0.0 0.0 0.0
Tape Used (%) 0.0 0.0 0.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
driver: WARNING: got empty schedule from planner
taper: tape Daily09 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-------------------------- --------------------------------- ------------
<server FQDN here> -ida/c0d0p1 0
FAILED ---------------------------------------
<server FQDN here> -da/c0d0p10 0
FAILED ---------------------------------------
<server FQDN here> -ida/c0d0p5 0
FAILED ---------------------------------------
<server FQDN here> -ida/c0d0p6 0
FAILED ---------------------------------------
<server FQDN here> -ida/c0d0p7 0
FAILED ---------------------------------------
<server FQDN here> -ida/c0d0p8 0
FAILED ---------------------------------------
<server FQDN here> -ida/c0d0p9 0
FAILED ---------------------------------------
(brought to you by Amanda version 2.4.2p2)
It was also experiencing the same issue under amanda-2.4.1p1 as well. Since I
didnt know a whole lot about amanda, I simply reinstalled with the newer
version hoping for another "magical install". The install went okay, however I
still get the above report emailed to me at the end of the crontab process.
While the process is running, I see gtar running, which I am told it should.
So it appears that the compression of the filesystem is doing what it is
suppose to do before moving it too tape (am I saying this right?).
Anyways, what I am going to ask is this:
If I have a server that will EVENTUALLY need to backup remote boxes (hence the
amanda). However current it ONLY needs to back up itself. What is the
"proper" way I should be setting this up? DO I have to do a regular install
and THEN a client install? Any help would be appreciated.
Thanks
Kevin
