Dear users of Amanda,

This is my first SOS call so pls be "gentle" with me.

I've successfully compiled and got Amanda in place on RH Linux 6.2 but
have this problem. When I do a 'chg-scsi eject', this makes my HP 40x6e
autoloader go bongus. It will an error message 'semiloaded'.

anybody have sucessfully deployed a hp 40x6 on linux? I've attached my
amanda.conf and changer.conf files.

For your kind advice,
@p


org "DailySet1"        # your organization name for reports
mailto "[EMAIL PROTECTED]" # space separated list of operators at your site
dumpuser "amanda"    # the user to run dumps under

inparallel 4        # 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
netusage  100 mbps    # maximum net bandwidth for Amanda, in KB per sec

dumpcycle 5 days    # the number of days in the normal dump cycle
runspercycle 0          # the number of amdump runs in dumpcycle days
             # (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 6 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
### ### ###
# WARNING: don't use `inf' for tapecycle, it's broken!
### ### ###

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 300        # 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 1800        # number of idle seconds before a dump is aborted.

ctimeout 30        # maximum number of seconds that amcheck waits
             # for each client host

tapebufs 20

runtapes 1        # number of tapes to be used in a single run of amdump
tpchanger "chg-scsi"    # the tape-changer glue script
tapedev "0"    # the no-rewind tape device to be used
#rawtapedev "/dev/null"    # the raw device to be used (ftape only)
changerfile "/usr/local/etc/amanda/DailySet1/HPC5713A-scsi.conf"
#changerdev "/dev/sg2"


tapetype HP-DAT        # what kind of tape it is (see tapetypes below)
labelstr "^DailySet1[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.
# The advantages include: tape drive is more likely to operate in
streaming
# mode (which reduces tape and drive wear, reduces total dump time);
multiple
# dumps can be done in parallel (which can dramatically reduce total
dump time.
# The main disadvantage is that dumps on the holding disk need to be
flushed
# (with amflush) to tape after an operating system crash or a tape
failure.
# 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 than it
will be
# written directly to tape.  If more than one holding disk is
specified then
# they will all be used round-robin.

holdingdisk hd1 {
     comment "main holding disk"
     directory "/dumps/amanda"    # where the holding disk is
     use 290 Mb        # how much space can we use on it
             # a non-positive value means:
             #        use all space but that value
     chunksize 1Gb     # size of chunk if you want big dump to be
             # dumped on multiple files on holding disks
             #  N Kb/Mb/Gb split images in chunks of size N
             #          The maximum value should be
             #          (MAX_FILE_SIZE - 1Mb)
             #  0          same as INT_MAX bytes
     }

infofile "/usr/etc/amanda/DailySet1/curinfo"    # database DIRECTORY
logdir   "/usr/etc/amanda/DailySet1"        # log directory
indexdir "/usr/etc/amanda/DailySet1/index"    # index directory
#tapelist "/usr/adm/amanda/DailySet1/tapelist"    # list of used tapes
# tapelist is stored, by default, in the directory that contains
amanda.conf



define tapetype QIC-60 {
     comment "Archive Viper"
     length 60 mbytes
     filemark 100 kbytes        # don't know a better value
     speed 100 kbytes        # dito
}

define tapetype DEC-DLT2000 {
     comment "DEC Differential Digital Linear Tape 2000"
     length 15000 mbytes
     filemark 8 kbytes
     speed 1250 kbytes
}

# [EMAIL PROTECTED]
# in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
define tapetype DLT {
     comment "DLT tape drives"
     length 20000 mbytes        # 20 Gig tapes
     filemark 2000 kbytes    # I don't know what this means
     speed 1536 kbytes        # 1.5 Mb/s
}

define tapetype SURESTORE-1200E {
     comment "HP AutoLoader"
     length 3900 mbytes
     filemark 100 kbytes
     speed 500 kbytes
}

define tapetype EXB-8500 {
     comment "Exabyte EXB-8500 drive on decent machine"
     length 4200 mbytes
     filemark 48 kbytes
     speed 474 kbytes
}

define tapetype EXB-8200 {
     comment "Exabyte EXB-8200 drive on decent machine"
     length 2200 mbytes
     filemark 2130 kbytes
     speed 240 kbytes
}

define tapetype HP-DAT {
     comment "DAT tape drives"
     # data provided by Rob Browning <[EMAIL PROTECTED]>
length 19560
     filemark 1147 kbytes
     speed 2957 kbytes
}

define tapetype DAT {
     comment "DAT tape drives"
     length 1000 mbytes        # these numbers are not accurate
     filemark 100 kbytes        # but you get the idea
     speed 100 kbytes
}

define tapetype MIMSY-MEGATAPE {
     comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
     length 2200 mbytes
     filemark 2130 kbytes
     speed 170 kbytes        # limited by the Emulex bus interface, ugh
}




define dumptype global {
     comment "Global definitions"
     # This is quite useful for setting global parameters, so you don't
have
     # to type them everywhere.  All dumptype definitions in this
sample file
     # do include these definitions, either directly or indirectly.
     # There's nothing special about the name `global'; if you create any
     # dumptype that does not contain the word `global' or the name of any
     # other dumptype that contains it, these definitions won't apply.
     # Note that these definitions may be overridden in other
     # dumptypes, if the redefinitions appear *after* the `global'
     # dumptype name.
     # You may want to use this for globally enabling or disabling
     # indexing, recording, etc.  Some examples:
     # index yes
     # record no
}

define dumptype always-full {
     global
     comment "Full dump of this filesystem always"
     compress none
     priority high
     dumpcycle 0
}

define dumptype root-tar {
     global
     program "GNUTAR"
     comment "root partitions dumped with tar"
     compress none
     index
     exclude list "/usr/local/lib/amanda/exclude.gtar"
     priority low
}

define dumptype user-tar {
     root-tar
     comment "user partitions dumped with tar"
     priority medium
}

define dumptype high-tar {
     root-tar
     comment "partitions dumped with tar"
     priority high
}

define dumptype comp-high-tar {
     root-tar
     comment "High priorty with max server compression"
     compress server best
}

define dumptype comp-high-tar-exclude {
     root-tar
     comment "High priorty with max server compression"
     compress server best
     exclude "*.class"
     exclude "core"
     exclude "*~"
}

define dumptype comp-root-tar {
     root-tar
     comment "Root partitions with compression"
     compress client fast
}

define dumptype comp-user-tar {
     user-tar
     compress client fast
}

define dumptype holding-disk {
     global
     comment "The master-host holding disk itself"
     holdingdisk no # do not use the holding disk
     priority medium
}

define dumptype comp-user {
     global
     comment "Non-root partitions on reasonably fast machines"
     compress client fast
     priority medium
}

define dumptype nocomp-user {
     comp-user
     comment "Non-root partitions on slow machines"
     compress none
}

define dumptype comp-root {
     global
     comment "Root partitions with compression"
     compress client fast
     priority low
}

define dumptype nocomp-root {
     comp-root
     comment "Root partitions without compression"
     compress none
}

define dumptype comp-high {
     global
     comment "very important partitions on fast machines"
     compress client best
     priority high
}

define dumptype nocomp-high {
     comp-high
     comment "very important partitions on slow machines"
     compress none
}

define dumptype nocomp-test {
     global
     comment "test dump without compression, no /etc/dumpdates recording"
     compress none
     record no
     priority medium
}

define dumptype comp-test {
     nocomp-test
     comment "test dump with compression, no /etc/dumpdates recording"
     compress client fast
}



define interface local {
     comment "a local disk"
     use 1000 kbps
}

define interface le0 {
     comment "100 Mbps ethernet"
     use 50 mbps
}

# You may include other amanda configuration files, so you can share
# dumptypes, tapetypes and interface definitions among several
# configurations.

#includefile "/usr/local/amanda.conf.main"

My Changer file:

number_configs 1
eject     1    # Tapedrives need an eject command
sleep     30    # Seconds to wait until the tape gets ready
cleanmax 100     # How many times could a cleaning tape get used
changerdev /dev/sg2
#
# Next comes the data for drive 0
#
config     0
drivenum 1
dev     /dev/nst0
scsitapedev /dev/sg2
startuse 0 # The slots associated with the drive 0
enduse     4    #
statfile     /usr/local/etc/amanda/DailySet1/tape0-slot  # The file
where the actual slot is stored
cleancart 5 # the slot where the cleaningcartridge for drive 0 is located
cleanfile /usr/local/etc/amanda/DailySet1/tape0-clean # The file where
the cleanings are recorded
usagecount /usr/local/etc/amanda/DailySet1/totaltime
tapestatus /usr/local/etc/amanda/DailySet1/tapestatus # here will some
status infos be stored
#labelfile /usr/local/etc/amanda/DailySet1/labelfile # Use this if you
have an barcode reader

Reply via email to