Hi,
On Tue, Jun 19, 2001 at 03:10:50PM -0500, John R. Jackson wrote:
If anyone has this jukebox and has amanda working with it, can you tell me
what your config is as far as the jukebox control??? All I really need is
the scsi driver to interface between amanda and the jukebox to tell the
Since a few weeks I have serious problems backing
up a remote system (Cobalt server) with my Sun Solaris 2.6 machine.I backup
different machines and different directories on each machine.all machines
(including the cobalt) backup well, except for two directory branches on the
Cobalt (the
Try amcheck configuration_name without parameter. If there will be no
error, it's o.k.
amcheck -m only sends mail if you have any errors.
Luke Miller schrieb:
I have 2.4.2p2 running under Solaris 7/Sparc. I am finding that I am not
getting mail from amanda. I have tried compiling amanda to
All,
I am new to amanda, read the faq, read the archives etc but cannot find
solutions to my problems which are mostly related to permission problems.
I have configured amanda with as suggested in the INSTALL file:
./configure --with-user=bin and --with-group=disk
I ran make and make install
On Wed, 20 Jun 2001 at 10:01pm, Jobst Schmalenbach wrote
I have configured amanda with as suggested in the INSTALL file:
./configure --with-user=bin and --with-group=disk
NOTE: skipping tape-writable test
Tape DailySet1-01 label ok
Why does it skip the writetest?
That's normal.
Well, I've made a little progress with my problem of getting
Amanda to work with my Seagate STT2A. For those who were
following, Amlabel would go through the motions of labeling a new
tape on this IDE ATAPI drive (using /dev/nht0) then error out and
insist that /dev/nht0 was not a
The information below should do the trick. Annoyingly, I've just
discovered the Debian packages for stable are, in fact, 2.4.1. Grrr!
My apologies if this is wasting your time.
That's pretty old, but if I had to guess, I'd say the following change
(from 1998 :-) is probably what fixed the
John R. Jackson wrote:
using an IBM SCSI tape drive with DDS4 cartridges. I have confirmed
that the tape drive is working when I use it manually (ie: I can read
and write to /dev/sa0).
Is this the device name you gave Amanda? Are you sure it's the no-rewind
name (I would expect an 'n' in
... Other tools
such as BRU and Tar seem perfectly happy with the non-rewinding
feature of this device but amlabel remained unconvinced.
Those other tools don't rewind the tape between doing things. That's
historically (reportedly) been the problem -- the driver doesn't rewind
when asked to.
I am new to amanda ...
Welcome!
read the faq, read the archives etc ...
Good for you! :-)
but cannot find
solutions to my problems which are mostly related to permission problems.
As Joshua Baker-LePain wrote, it looks like most of your problems are
related to not putting bin in group
By it you mean the kernel. Amanda doesn't output these errors. So if
you want more information, you'll have to go to the kernel driver folks.
In general, that's a SCSI Request Sense output buffer. I don't have
the documentation for your particular device, but a sense key of 5 is an
How would one obtain the CDB? The kernel message that I
included in my message was all that was printed
You're asking the wrong people. You have to talk to the kernel folks.
It's their message, they're the ones that built the CDB (request) and
issued it.
Aaron Smith
John R. Jackson,
Hi all,
I would like to set up Amanda to do archive tapes once a month and would
like to store them offsite. So what I did according to:
http://amanda.sourceforge.net/fom-serve/cache/28.html
http://amanda.sourceforge.net/fom-serve/cache/30.html
I created a (week-) daily and a monthly
Does any of the guru know the following error? ...
? invalid mid from server!
This has come up a few times and the general answer has been go ask
the SAMBA people. It has nothing to do with Amanda (other than Amanda
got bit by it). I don't think anyone has ever posted back with a SAMBA
No, I gave amanda the name nsa0.
Good.
FATAL taper shmget: (983160 tapebufs) Cannot allocate memory
...
I just noticed the Cannot allocate memory message. Could that be the
problem? ...
Absolutely. Didn't this show up bright and bold in the failures section
of the Amanda E-mail?
If so,
... I've done that, but amrecover wants a portnumber 1024... You can
off course hack the sources ;-)
As far as I know, only the 2.5 (development) code branch has this problem
with amrecover. Have you seen it with 2.4.2p2?
Arjan
John R. Jackson, Technical Software Specialist, [EMAIL
Ok. I did some poking around in the various kernel
sites and came across the solution. For the benefit of anyone
else who runs into similar problems with the Seagate STT2A,
after adding in support for ide-scsi emulation you have to put an
append= line into lilo with hdX=ide-scsi
For security: My NoRewinding device ist /dev/nst0.
Shall i take this device for my changer?
It should be the tape device name. Whether it is also your changer
device name depends on your hardware.
When i take
amrecover -d /dev/nst0 or
amrecover -d /dev/st0
and i become the same error ...
cobalt01.s /home lev 0 FAILED [data timeout]
...
sendbackup: info BACKUP=/bin/gtar
This tells me two things. First, that at this time you were using GNU
tar to do the backup, and second that the Amanda server side waited half
an hour and didn't get any data from the client (which triggered the
Thanks a lot!
thats perfectly fine for me. I planed to run the archives on a separate day
anyhow.
Alberto
-Original Message-
From: John R. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 20, 2001 14:33
To: Alberto Gobbi
Cc: '[EMAIL PROTECTED]'
Subject: Re: long term achieving
My question is about using gnu tar. since tar will be called with the
--listed-incremental option and the filename does not include the
configuration I am wondering if there would be an interference of the
monthly full backups with the daily incremental.
You're right, that looks like a
JObst,
A couple of answers:
1) it seems that for reason amanda did install itself with owner root
instead of bin.
What you chown for amcheck should be done for other pieces of software
too.
Better try a make install again?
2) I beleive you have a tcp-wrapper installed, you should allow
st0: Error with sense data: [valid=0] Info fld=0x0, Current st09:00: sns = 70
5
ASC=20 ASCQ= 0
Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00
0x20 0x00 0x00 0x00 0x00 0x00
Is a system message, it is due to /dev/st0 and the emulation EDI/SCSI,
not due to Amanda.
I
On Jun 20, 2001, John R. Jackson [EMAIL PROTECTED] wrote:
One possible workaround (some would say hack :-) if the runs might
happen at the same time would be to add a trailing /. to all the disk
names in your disklist. For instance, if your daily run backs up /home
have the archive run do
24 matches
Mail list logo
