thanks Jay, makes great sense.
so the tpchanger envirornment is attemping to call the C program in the libexec
directory
NOW my only problem IS: tpchanger should call the C program (chg-scsi) in my
case...
where does the CONFIG (chg-scsi.conf) get called from, or it doesnt need to be?
so this error(s)
Amanda Tape Server Host Check
-----------------------------
(1)amcheck-server: could not get changer info: could not read result from
"/usr/local/etc/amanda/DailyBackup/chg-scsi.conf"
or now:
(2)amcheck-server: could not get changer info: check your config and use a
config file for chg-scsi
..amanda.conf snippet:
..snip..
notes: IF THIS line (A) is commented/# out, I get errror 1
(otherwise I get error B
(A) tpchanger "chg-scsi"
# the tape-changer glue script
(B) tpchanger "/usr/local/etc/amanda/DailyBackup/chg-scsi.conf"
tapedev "/dev/rmt/0n" # the no-rewind tape device to be used
changerfile "/usr/local/etc/amanda/DailyBackup/chg-scsi.conf"
changerdev "/dev/scsi/changer/c1t0d0"
-----Original Message-----
From: Jay Lessert [mailto:jayl AT accelerant DOT net]
Sent: Tuesday, July 15, 2003 3:52 PM
To: Bruntel, Mitchell L, SOLCM
Cc: amanda-users AT amanda DOT org
Subject: Re: Pre-emptive sanity check Question
On Tue, Jul 15, 2003 at 01:58:20PM -0500, Bruntel, Mitchell L, SOLCM wrote:
> OK. Jay makes sense here:
> 1) Jay says: I have choices: chg-scsi or chg-zd-mtx.
> but I have a third config file in the distribution called
> chg-scsi-solaris.conf
The files: example/chg-scsi-{hpux,linux,solaris}.conf are just example
chg-scsi config files with OS-specific "typical" device names inserted;
they do not represent different tpchanger executables. You'll not find
libexec/chg-scsi-solaris, right?
> The X80 has 80 slots for tapes. (elements) Tape Drive 1 is element
> 451, 2 is 452, 3 is 453,
I'm sure there is an excellent and highly amusing reason for that. :-)
and the cleaning cartridge lives in slot 0
> and element 401-405 are the only way to put tapes in/out of unit!
You're apparently intended to initially populate the library through
the little five-tape import/export hole, and then seldom/never touch
the tapes again. Unless you were planning on rotating tapes off-site,
that's actually a perfectly good way to go, I guess.
Amanda won't do anything with the import/export slots, you'll deal with
that outside amanda somewhere.
With mtx, you would fill the import/export slots, then have a script
do something like:
mtx transfer 401 1
mtx transfer 402 2
mtx transfer 403 3
mtx transfer 404 4
mtx transfer 405 5
> so it should be 'startuse 1', 'enduse 80'
If you're planning on using that many tapes, yes. Only specify as many
slots as you're actually intending to use in this amanda config.
> Now can someone explain the following:
> a) what is the relationship of mtx to chg-scsi
None.
chg-scsi: is a C program that controls a SCSI tape library and directly
implements the amanda changer interface described in
docs/TAPE.CHANGERS. Part of the amanda source distribution.
mtx: A C program that controls a SCSI tape library and does NOT
directly implement the amanda changer interface. It is very useful
to use by hand, however ('mtx load 3 452' would load the tape in
slot 3 to tape drive 452), and a wrapper script can convert it to
amanda. Source from http://mtx.badtux.net/.
There is another, older mtx, which I have never seen in the wild.
chg-zd-mtx: A sh script wrapper around mtx which converts it to the
amanda changer interface.
> b) what is the relationship of chg-scsi.conf and the files in the
> /usr/local/libexec directory (/usr/local/libexec/chg-scsi)
libexec/chg-scsi is a C program that expects to find a configuration
file somewhere. chg-scsi.conf might be that file.
--
Jay Lessert jay_lessert AT accelerant DOT net
Accelerant Networks Inc. (voice)1.503.439.3461
Beaverton OR, USA (fax)1.503.466.9472
|
