Hello,
* Jon LaBadie (jon AT jgcomp DOT com) [20030330 17:02] thus spake:
> On Sun, Mar 30, 2003 at 03:32:52PM -0500, Jean-Francois Malouin wrote:
> > Hi,
> >
> > I have amanda version 2.4.3b4-20020829 running on a SGI Origin2000
> > since last September and even I had a few problems (mainly I was
> > hitting known bugs with tar and exclude lists) the last one just
> > got me stumped and I can't clearly anymore even though I know the
> > answer must be staring at me right in the eyes...
> >
> > Essentially amanda is telling that she wants a new tape and she
> > refuses to backup to tape but the tapes in the library should be used
> > according to the amanda.conf dumpcycle, runspercycle and tapecycle
> > (see below). here's the output of amcheck:
> >
> > Amanda Tape Server Host Check
> > -----------------------------
> > Holding disk /holddisk/conf1: 35836836 KB disk space available, using
> > 35836836 KB
[...]
> > amcheck-server: slot 1: date 20030217 label 000001 (active tape)
[...]
> > ERROR: new tape not found in rack
> > (expecting a new tape)
> > NOTE: skipping tape-writable test
> > Server check took 950.340 seconds
> >
> > --
> > amanda.conf
> > --
> >
> > dumpcycle 2 weeks
> > runspercycle 14
> > tapecycle 40 tapes
>
> This should be the total number of tapes you want to have in
> circulation. Amanda will not reuse any tape until it has
> used this many different tapes. I'm guessing you have used
> the 10 in the changer but no others. Tape 000001 will not be
> used again until 30 more tapes are used.
did you looked at the dates on the 40 tapes for the stk_40-conf1
in the tapelist file? They should be reused. Look at tape 000001:
20030217 000001 reuse
Last time it was used was 17-feb-2003, more than 40 days ago!
Amanda shoud use it, no? I thought I understood what makes
a tape 'active' but obviuosly I got it wrong....When, for
instance, will tape 000001 status change from active with
the above conf variables?
BTW, Amanda is configured to use the first 10 slots of the changer
(but see below) and the contain tape 000001 to 000010.
>
> > runtapes 10
>
> This is the number of tapes amanda is allowed to use in a single
> huge amdump or amflush session. It will not use more tapes than
> it needs to hold the session, but it may use 10 in a single run.
yep, that's what I want!
I have over 800GB of disk space in that conf, all splitted in disklist
in chunks of 100GB or less so that each iamge can fit on one tape...
worst case that can happen is a full for all, in which case up to 8
or 9 tapes could be needed to fit them all.
>
> > tpchanger "chg-zd-mtx"
> > tapedev "/hw/tape/tps12d1nrnsv"
> > rawtapedev "/dev/null"
> > changerfile "/opt/amanda/amanda1/etc/amanda/stk_40-conf1/stk_40"
>
> Does this naming mean the library holds 40 tapes?
> And are all 40 labeled tapes in the library?
The library has 40 slots and 4 LTO tapedrives but only slots 1 to 10
and tape "0" are used for the conf 'stk_40-conf1'.
I have 4 amanda configurations (stk_40-conf[1234]), one drive
and 10 slots for each. Here's my conf details for conf1.
(the other confs used different tcp and udp portrange so I have
essentially duplicated 4 times the amanda setup with partionned
ports, drives and slots range)
amandad: version 2.4.3b4-20020829
amandad: build: VERSION="Amanda-2.4.3b4-20020829"
amandad: BUILT_DATE="Thu Aug 29 16:19:48 EDT 2002"
amandad: BUILT_MACH="IRIX64 feeble 6.5 10100655 IP27" CC="cc"
amandad: CONFIGURE_COMMAND="'./configure'
'--prefix=/opt/amanda/amanda1'
'--with-user=amanda'
'--with-group=sys'
'--with-testing=conf1'
'--with-tcpportrange=16384,16895'
'--with-udpportrange=739,802'
'--with-tape-device=/hw/tape/tps12d1nrnsv'
'--with-changer-device=/dev/changer'
'--with-gnutar=/usr/freeware/bin/tar'
'--with-tape-server=bullcalf'
'--with-index-server=bullcalf'
'--with-config=stk_40-conf1'"
amandad: paths: bindir="/opt/amanda/amanda1/bin"
amandad: sbindir="/opt/amanda/amanda1/sbin"
amandad: libexecdir="/opt/amanda/amanda1/libexec"
amandad: mandir="/opt/amanda/amanda1/man"
amandad: AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
amandad: CONFIG_DIR="/opt/amanda/amanda1/etc/amanda"
amandad: DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/"
amandad: DUMP="/sbin/dump" RESTORE="/sbin/restore"
amandad: XFSDUMP="/sbin/xfsdump" XFSRESTORE="/sbin/xfsrestore"
amandad: GNUTAR="/usr/freeware/bin/tar"
amandad: COMPRESS_PATH="/usr/sbin/gzip"
amandad: UNCOMPRESS_PATH="/usr/sbin/gzip" MAILER="/usr/sbin/Mail"
amandad: listed_incr_dir="/opt/amanda/amanda1/var/amanda/gnutar-lists"
amandad: defs: DEFAULT_SERVER="bullcalf" DEFAULT_CONFIG="stk_40-conf1"
amandad: DEFAULT_TAPE_SERVER="bullcalf"
amandad: DEFAULT_TAPE_DEVICE="/hw/tape/tps12d1nrnsv" HAVE_MMAP
amandad: HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad: AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
amandad: CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
amandad: COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
amandad: COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
>
> If so, perhaps your changer files says the last slot is #10
> and chg-zd-mtx is not looking at the others.
no. stk.conf shows (has specifies the variable 'changerfile' above):
firstslot=1
lastslot=10
cleanslot=-1
autoclean=0
autocleancount=99
havereader=1
offline_before_unload=1
driveslot=0
poll_drive_ready=30
max_drive_wait=120
Thanks for your time!
jf
> --
> Jon H. LaBadie jon AT jgcomp DOT com
> JG Computing
> 4455 Province Line Road (609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
