basically, I think I have amanda up and running. Now when amdump starts, it fails to get to the device I want to backup(which is on the local machine also). I do have both a client and server running on this same machine. And just for test purposes, I'm running amanda as root.
here is the report I get...
*These dumps were to tape DailySet101. *
*The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY: beaker /backups lev 0 FAILED [disk /backups offline on beaker?]
STATISTICS:
Total Full Daily
-------- -------- --------
Estimate Time (hrs:min) 0:00
Run Time (hrs:min) 0:01
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: planner: Adding new disk beaker:/backups. driver: WARNING: got empty schedule from planner taper: tape DailySet101 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
-------------------------- --------------------------------- ------------
beaker /backups 0 FAILED ---------------------------------------
(brought to you by Amanda version 2.4.3)
*Any ideas what I might be doign wrong when I'm trying to access the directory I want to backup? The /backups directory consists of two seperatte directories which are both stored on their own partitions(sdb1 and sdb2).
Anyone have any ideas?
Paul
