Using Amanda amanda-2.5.2p1 with chg-zd-mtx with the
errors below.
Another question is I have two drives
/dev/rmt/0n
/dev/rmt/1n
How do I tell Amanda to use both drives?
Here is my error:
11:43:56 Using config file /etc/amanda/Full/changer.conf
11:43:56 Arg info:
$# = 1
$0 =
"/opt/amanda/client/libexec/chg-zd-mtx"
$1 =
"-info"
11:43:56 Running: mtxRunning: status
11:43:56 Exit code: 127
Stderr:
/opt/amanda/client/libexec/chg-zd-mtx: line 389: mtx:
command not found
11:43:56 Exit (2) -> <none> no slots available
chg-zd-mtx: pid 18883 finish time Fri Oct 12 11:43:56 2007
Error from e-mail:
taper: changer problem: no slots available
The tapes are labeled within Amanda and the backups work
fine with the chg-mtx script.
However mtx is working.
mtx -f /dev/scsi/changer/c3t3d1 status
Storage Changer /dev/scsi/changer/c3t3d1:2 Drives, 12
Slots ( 1 Import/Export )
Data Transfer Element 0:Full (Storage Element 1
Loaded):VolumeTag = EGV002
Data Transfer Element 1:Empty
Storage Element
1:Empty:VolumeTag=
Storage Element 2:Full
:VolumeTag=EGV003
Storage Element 3:Full
:VolumeTag=EGV004
Storage Element 4:Full
:VolumeTag=EGV005
Storage Element 5:Full
:VolumeTag=EGV006
Storage Element 6:Full
:VolumeTag=EGV007
Storage Element 7:Full :VolumeTag=EGV008
Storage Element 8:Full
:VolumeTag=EGV009
Storage Element 9:Full
:VolumeTag=EGV010
Storage Element 10:Full
:VolumeTag=EGV011
Storage Element 11:Full
:VolumeTag=EGV012
Storage Element 12
IMPORT/EXPORT:Empty:VolumeTag=
But not as Amanda user which I don’t know if it is
necessary:
mtx -f /dev/scsi/changer/c3t3d1 status
cannot open SCSI device '/dev/scsi/changer/c3t3d1' -
Permission denied
Here is the changer.conf file:
firstslot=1
lastslot=11
driveslot=0
autoclean=0
autocleancount=99
havereader=1
offline_before_unload=0
initial_poll_delay=0
Here is my conf file
# amanda.conf - Amanda configuration file for full dumps
org
"1sync.org" #
your organization name for reports
mailto "uadmin AT gs1us DOT org" # space separated
list of operators at your site
dumpuser "amanda" # the user to run dumps under
inparallel 8
# maximum dumpers that will run in parallel (max 63)
# this maximum can be increased at compile-time,
# modifying MAX_DUMPERS in server-src/driverio.h
dumporder "ttBTBTBTBTBTBTB" # specify the priority
order of each dumper
# s -> smallest size
# S -> biggest size
# t -> smallest time
# T -> biggest time
# b -> smallest bandwidth
# B -> biggest bandwidth
# try "BTBTBTBTBTBT" if you are not holding
# disk constrained
netusage 10000000 Kbps # maximum net bandwidth for
Amanda, in KB per sec
dumpcycle 2 weeks # the number of days in the normal dump
cycle
runspercycle
1 # the number of amdump
runs in dumpcycle days
# (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 1 tapes # the number of tapes in rotation
# 4 weeks (dumpcycle) times 5 tapes per week (just
# the weekdays) plus a few to handle errors that
# need amflush and so we do not overwrite the full
# backups performed at the beginning of the previous
# cycle
bumpsize 20 Mb # minimum savings (threshold) to
bump level 1 -> 2
bumpdays 1 # minimum
days at each level
bumpmult 4 # threshold =
bumpsize * bumpmult^(level-1)
etimeout 900 # number of seconds per
filesystem for estimates.
#etimeout -600 # total number of seconds for
estimates.
# a positive number will be multiplied by the number of
filesystems on
# each host; a negative number will be taken as an absolute
total time-out.
# The default is 5 minutes per filesystem.
dtimeout 18000 # number of idle seconds
before a dump is aborted.
ctimeout 30 # maximum number
of seconds that amcheck waits
# for each client host
tapebufs 20
# A positive integer telling taper how many 32k buffers to
allocate.
# WARNING! If this is set too high, taper will not be able
to allocate
# the memory and will die. The default is 20 (640k).
# Specify tape device and/or tape changer. If you
don't have a tape
# changer, and you don't want to use more than one tape per
run of
# amdump, just comment out the definition of tpchanger.
tpchanger "chg-zd-mtx" # the tape-changer glue
script
tapedev "/dev/rmt/1n" # the no-rewind tape
device to be used
changerfile "/etc/amanda/Full/changer.conf"
changerdev "/dev/scsi/changer/c3t3d1"
runtapes 1 #
number of tapes to be used in a single run of amdump
tapetype Ultrium3-SCSI # what kind of tape it is (see
tapetypes below)
labelstr "^EGV[0-9][0-9][0-9]*$" # label
constraint regex: all tapes must match
# Specify holding disks. These are used as a temporary
staging area for
# dumps before they are written to tape and are recommended
for most sites.
# If no holding disks are specified then all dumps will be
written directly
# to tape. If a dump is too big to fit on the holding
disk then it will be
# written directly to tape. If more than one holding
disk is specified then
# they will all be used based on activity and available
space.
holdingdisk hd1 {
comment "main holding disk"
directory
"/opt/data/amanda/Full" # where the holding disk is
use 45
Gb # how much space can we use
on it
}
# If amanda cannot find a tape on which to store backups, it
will run
# as many backups as it can to the holding disks. In
order to save
# space for unattended backups, by default, amanda will only
perform
# incremental backups in this case, i.e., it will reserve
100% of the
# holding disk space for the so-called degraded mode
backups.
# However, if you specify a different value for the
`reserve'
# parameter, amanda will not degrade backups if they will
fit in the
# non-reserved portion of the holding disk.
# reserve 30 # percent
# This means save at least 30% of the holding disk space for
degraded
# mode backups.
reserve 0
autoflush no
# if autoflush is set to yes, then amdump will schedule all
dump on
# holding disks to be flush to tape during the run.
# The format for a ColumnSpec is a ',' seperated list of triples.
# Each triple consists of
# + the name of the column (as in
ColumnNameStrings)
# + prefix before the column
# + the width of the column, if set to -1 it
will be recalculated
# to the maximum length of a line to
print.
#
# You need only specify those columns that should be changed
from
# the default. If nothing is specified in the configfile,
the
# above compiled in values will be in effect, resulting in
an
# output as it was all the time.
# The names of the columns are:
# HostName, Disk, Level, OrigKB, OutKB, Compress, DumpTime,
DumpRate,
# TapeTime and TapeRate.
#
ElB, 1999-02-24.
# columnspec "Disk=1:18,HostName=0:10,OutKB=1:7"
# (Note - the line below should be on one line)
columnspec "HostName=0:12,Disk=1:12,Level=1:1,OrigKB=1:7,OutKB=1:7,DumpTime=1:6,DumpRate=1:7,TapeTime=1:6,TapeRate
=1:7,Compress=1:0"
# Amanda needs a few Mb of diskspace for the log and debug
files,
# as well as a database. This stuff can grow large, so
the conf directory
# isn't usually appropriate. Some sites use
/usr/local/var and some /usr/adm.
# Create an amanda directory under there. You need a
separate infofile and
# logdir for each configuration, so create subdirectories
for each conf and
# put the files there. Specify the locations below.
# Note that, although the keyword below is infofile, it is
only so for
# historic reasons, since now it is supposed to be a
directory (unless
# you have selected some database format other than the
`text' default)
infofile "/var/log/debug/Full/curinfo" # database
DIRECTORY
logdir
"/var/log/debug/Full"
# log directory
indexdir "/var/log/debug/Full/index" # index
directory
Any help is greatly appreciated…
Anderson
