Amanda seems to start up and run fine, it then starts writing to tape...
a VXA-2 to be exact, about 80G uncompressed. The data is only about 37G.
Here's the log:
[EMAIL PROTECTED] logs]# cat log
DISK planner beaker sdb1
DISK planner beaker sdb2
START planner date 20031031
INFO planner Adding
I'm able to get amanda running just ifne without compression running.
Now I want to go ahead and enable it.
I tried using high-tar just to see what would happen, and the system
times out after 30 minutes. I see the data is still compressing on the
client. Is there any way to make amanda sit
The amanda server and client are both running on the same machine.
Any ideas what's going on?
Original Message
Subject:DailySet1 AMANDA MAIL REPORT FOR October 29, 2003
Date: Wed, 29 Oct 2003 11:34:55 -0500 (EST)
From: [EMAIL PROTECTED] (Amanda user)
To: [EMAIL
Hey guys, I think I've finally gotten close to finishing up this
configuration... now I'm running amcheck... any ideas what's wrong?
bash-2.05b$ /usr/sbin/amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk /var/amanda/dumps: 284572 KB disk space available,
Hey guys, I've spent the last few days searching for answers on the web
with no luck
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
