Hi, everyone,
I'm trying to setup a new backup server running Red Hat and Amanda
2.4.2p2. I'm using an Exabyte VXA-1 RakPaq, basically two LVD SCSI
VXA-1 tape drives which I have daisy chained together. vxaTool reports
that the first drive is /dev/sga and the second is /dev/sgb. I can
access
Hi, everyone,
Correction: that should read /dev/nst0, not /dev/st0
I changed the device to /dev/st0 and everything worked, including
amlabel. Apparently the problem is with vxaTool reporting the wrong
device and not amanda. I'll report the bug to Exabyte.
Thanks again,
Caity
Hi, everyone,
I changed the device to /dev/st0 and everything worked, including
amlabel. Apparently the problem is with vxaTool reporting the wrong
device and not amanda. I'll report the bug to Exabyte.
Thanks
Hi, everyone,
OK, I admit it. amanda is kicking my you-know-what.
amdump is failing because it's unable to write it's index files. Why?
From the errors it looks like a permissions problem, but the directory
is owned by amanda and right now I've got everything opened up to chmod
777. There
Hi, Frank, and everyone else.
My guess is that the permission problem is higher up. Try
su - amanda
and then try to cd down the directory structure. The index,
pip, and _users5 directories should be created automatically
during the backup run. As the amanda user, see if you can
create a
Hi, Gene,
The only thing that comes to mind quickly is probably related to the
question/statement you do have a user amanda, who is a member of
group disk, don't you?
Yes, of course. I think that was done automagically when I installed
the amanda rpms.
As I said in my response to Frank,
On Fri, 2002-09-20 at 15:07, Gene Heskett wrote:
I should have qualified that by saying the tarballs installer won't.
I have NDI whether the rpm does or not.
I did use the rpms, I did reinstall, and everything worked. I have no
clue what went wrong the first time. All I know I
Hi, Jon,
I've never installed and used amanda from a pre-built package.
I have on a Red Hat Linux system, but I also administer a lot of Solaris
and AIX boxes. I compiled amanda myself on Solaris, and an up-to-date
package that automated a lot of the steps I had to go through would be a
real
On Thu, 2002-10-10 at 17:56, Chris Noon wrote:
o A stronger community results when individuals respond to
individuals as opposed to responding to all members of the the list...
I don't doubt that you are right about that, but I do read threads that have
nothing to do with me. And I
On Tue, 2002-11-12 at 16:43, Galen Johnson wrote:
I've never heard of any but I can't think of any questions I've asked
that haven't been resolved with just this mailing list.
Hi, Galen, and everyone else,
In principle I agree. Try and sell that to a suit who doesn't
understand OSS. One of
On Tue, 2002-11-12 at 17:35, Frank Smith wrote:
Then again, I may be underestimating
the number of PHB's in the world.
Trust me, you are. Almost every suit I know of would want
professional support. (Software) Engineering is the lifeblood of this
company, and I work for Engineering, so I'm
On Wed, 2002-12-11 at 08:02, Ben Simpson wrote:
I have 2.4.3 version
If you need help let me know. I need to creat myself some install
instructions anyways.
Please post a link to the list. I'd like to try this approach (as
opposed to using Samba) myself.
Thanks,
Caity
Caitlyn M. Martin
Hi, Paul,
How feasible is it to
install Amanda and getting it working like, in one day? Any and all input
would greatly appreciated.
If you are only trying to backup a handful of servers initially it is
very feasible. One thing that sped up the process for me is that we
share /usr/local
13 matches
Mail list logo
