amanda problems

[Sandra Panesso]

Hi everybody:


I start to use the tape cleaner but I have had some problems. When i run amcheck all the time I got the error
amcheck-server: slot 5: rewinding tape: No medium found
amcheck-server: fatal slot 6: mtx: Cleaning Cartridge Installed and Ejected
ERROR: label miro_daily-5 or new tape not found in rack
(expecting tape miro_daily-5 or a new tape)
the tape miro_daily-5 is there on the first slot (1).

so I have to use mtx -f /dev/sga load slot 1 after that I run amcheck again and I don't have problem. I don't think so that it is normal because before when i didn't use the cleaner tape I never got any error like that. This my changer configuration

number_configs 1
eject 0 # Tapedrives need an eject command
sleep 90 # Seconds to wait until the tape gets ready
changerdev /dev/sga
#
# Next comes the data for drive 0
#
config 0
drivenum 0
dev /dev/nst0
scsitapedev /dev/sga
startuse 1 # The slots associated with the drive 0
enduse 5 #
statfile /usr/local/etc/amanda/miro_daily/tape0-slot # The file where th
e actual slot is stored
cleancart 6 # the slot where the cleaningcartridge for drive 0 is lo
cated
cleanfile /usr/local/etc/amanda/miro_daily/cleanfile # The file where the
cleanings are recorded
usagecount /usr/local/etc/amanda/miro_daily/totaltime
tapestatus /usr/local/etc/amanda/miro_daily/changer-status # here will some
status infos be stored
#labelfile /usr/local/etc/amanda/DailySet1/labelfile # Use this if you have
an barcode reader


I have another question that maybe is related or maybe not.

I 'm using as dumcycle 4 weeks and tapecycle 25 tapes. To run amadump I have in my cron 6 days so I don't know if it is ok. I ask you is because since few days ago I have seen that when I have to run amflush for my weekend backups I get an error "whiteley.t /Local lev 0 FAILED [out of tape]"
NOTES:
taper: tape miro_daily-3 kb 12765152 fm 1 writing file: No space left on device
taper: retrying whiteley.tomandandy.com:/Local.0 on new tape: [writing file: No space left on device]
taper: tape miro_daily-4 kb 12767232 fm 1 writing file: No space left on device
amflush: /amanda_holding-2/20010609/whiteley.tomandandy.com._Local.0: taper error, leaving file on disk
amflush: Could not rmdir /amanda_holding-2/20010609. Check for cruft.


so I have been reading on amanda pages and this mailing list and I think that maybe is not correct my configuration so I would like to be sure . This my amanda.conf



# amanda.conf - sample Amanda configuration file. This started off life as
# the actual config file in use at CS.UMD.EDU.
#
# If your configuration is called, say, "csd", then this file normally goes
# in /usr/local/etc/amanda/csd/amanda.conf.
#

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

inparallel 7 #mimum dumpers that will run in parallel
netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec

dumpcycle 4 weeks # the number of days in the normal dump cycle
runspercycle 20 # the number of amdump runs in dumpcycle days
# (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 25 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 3600 # 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.

# changers, read docs/TAPE.CHANGERS.

# At most one changerfile entry must be defined; select the most
# appropriate one for your configuration. If you select man-changer,
# keep the first one; if you decide not to use a tape changer, you may
# comment them all out.

runtapes 4 # number of tapes to be used in a single run of amdump
# we have two to enable writing to holding disk for morn
ing amflushes.
tpchanger "chg-zd-mtx" # the tape-changer glue script
# Even though tapedev is ignored since we use
# tpchanger, we keep this in case we need to revert
# to no changing.
tapedev "/dev/nst0" # the no-rewind tape device to be used
rawtapedev "/dev/null" # the raw device to be used (ftape only)
#changerstatus "/usr/local/etc/amanda/miro_daily/changer-status"
changerfile "/usr/local/etc/amanda/miro_daily/changer.conf"
changerdev "/dev/sga"

#tapetype DDS2 # what kind of tape it is (see tapetypes below)
tapetype DDS3
labelstr "^miro_daily-[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.

holdingdisk hd1 {
comment "main holding disk"
directory "/amanda_holding-2" # where the holding disk is
use -10 Mb # how much space can we use on it
# a negative value mean:
# use all space except that value
chunksize 2000 Mb # size of chunk if you want big dump to be
# dumped on multiple files on holding disks
# N Kb/Mb/Gb split disks in chunks of size N
# 0 split disks in INT_MAX/1024 Kb chunks
# -1 same as -INT_MAX/1024 (see below)
# -N Kb/Mb/Gb dont split, dump larger
# filesystems directly to tape
# (example: -2 Gb)
# chunksize 2 Gb
}


# 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 0 # percent

# This means use none of the holding disk space for degraded
# mode backups.

reserve 0 # percent

# This means use none of the holding disk space for degraded
# mode backups.

# 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 "/usr/local/etc/amanda/miro_daily/curinfo" # database DIRECTORY
logdir "/var/log/amanda/miro_daily" # log directory
indexdir "/usr/local/etc/amanda/miro_daily/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


# tapetypes

define tapetype DDS3 {
comment "DDS3 HP Surestore DAT 24"
length 12288 mbytes
filemark 0 kbytes
speed 1024 kbytes

# dumpuser "operator" # the user to run dumps under
# printer "mypostscript" # printer to print paper label on

# here is an example of my definition for an EXB-8500


I'm sorry if I am sending a lot staff but right now I have 8 machines running whit amanda and I want to add three more but first I have to fix all this problems..If anybody can help me I would really really appreciated.

thanks for read my message
Sandra