Re: amanda refuses to use tapes

2003-03-30 Thread Jean-Francois Malouin
Hello,

* Jon LaBadie ([EMAIL PROTECTED]) [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 01 (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 01 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 01:

20030217 01 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 wrongWhen, for 
instance, will tape 01 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 01 to 10.

 
  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:

Re: amanda refuses to use tapes

2003-03-30 Thread Jon LaBadie
On Sun, Mar 30, 2003 at 05:32:27PM -0500, Jean-Francois Malouin wrote:
 Hello,
 
 * Jon LaBadie ([EMAIL PROTECTED]) [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:
   
 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 01:
 
 20030217 01 reuse
 

Now that you mention it, did you look at the bottom of the list:

20030220 04 reuse
20030219 03 reuse
20030218 02 reuse
20030217 01 reuse
20030212 40 reuse

Tape 40 has not been used since much earlier than any other tape
in the tapelist.

Did you perhaps reset things between 2/12 and 2/17?
Amanda seems to want to use tape 40 or a new tape.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)


Re: amanda refuses to use tapes

2003-03-30 Thread Jean-Francois Malouin
Hi again,

* Jon LaBadie ([EMAIL PROTECTED]) [20030330 19:10] thus spake:
 On Sun, Mar 30, 2003 at 05:32:27PM -0500, Jean-Francois Malouin wrote:
  Hello,
  
  * Jon LaBadie ([EMAIL PROTECTED]) [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:

  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 01:
  
  20030217 01 reuse
  
 
 Now that you mention it, did you look at the bottom of the list:
 
   20030220 04 reuse
   20030219 03 reuse
   20030218 02 reuse
   20030217 01 reuse
   20030212 40 reuse
 
 Tape 40 has not been used since much earlier than any other tape
 in the tapelist.
 
 Did you perhaps reset things between 2/12 and 2/17?
 Amanda seems to want to use tape 40 or a new tape.

I did a number of things :)
First, while on holidays backups timed out for a period of 3 weeks and
my assistants could not find out why. Turned out that 'etimeout' was
too small. Right after that I realized that one critical filesystem
had only one full backup image left on tape (40) and, as things go
bad in cluster, that filesystem experienced corruption, or so it
seemed at the time. Turns out that one user with elevated privileges
messed up. So, while we digged for the error I reserved tape 00040
with 'amadmin stk_40-conf1 no-reuse 40'. After that, amanda always
complained about using it or a new tape *or* tapes 01 to 10.

regards,
jf

 
 -- 
 Jon H. LaBadie  [EMAIL PROTECTED]
  JG Computing
  4455 Province Line Road(609) 252-0159
  Princeton, NJ  08540-4322  (609) 683-7220 (fax)


Re: amanda refuses to use tapes

2003-03-30 Thread Jon LaBadie
On Sun, Mar 30, 2003 at 08:09:20PM -0500, Jean-Francois Malouin wrote:
 Hi again,
 
 * Jon LaBadie ([EMAIL PROTECTED]) [20030330 19:10] thus spake:
  On Sun, Mar 30, 2003 at 05:32:27PM -0500, Jean-Francois Malouin wrote:
   Hello,
   
   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 01:
   
   20030217 01 reuse
   
  
  Now that you mention it, did you look at the bottom of the list:
  
  20030220 04 reuse
  20030219 03 reuse
  20030218 02 reuse
  20030217 01 reuse
  20030212 40 reuse
  
  Tape 40 has not been used since much earlier than any other tape
  in the tapelist.
  
  Did you perhaps reset things between 2/12 and 2/17?
  Amanda seems to want to use tape 40 or a new tape.
 
 I did a number of things :)
 First, while on holidays backups timed out for a period of 3 weeks and
 my assistants could not find out why. Turned out that 'etimeout' was
 too small. Right after that I realized that one critical filesystem
 had only one full backup image left on tape (40) and, as things go
 bad in cluster, that filesystem experienced corruption, or so it
 seemed at the time. Turns out that one user with elevated privileges
 messed up. So, while we digged for the error I reserved tape 00040
 with 'amadmin stk_40-conf1 no-reuse 40'. After that, amanda always
 complained about using it or a new tape *or* tapes 01 to 10.


If I understand correctly, you labeled and had 40 tapes in circulation
and had a tapecycle of 40.  Then you removed one from circulation
reducing the number to 39.  Seems likely that is the reason amanda is
asking for a new tape, to get the number back up to 40.

Did you amlabel a new tape?  If so, that is the one it wants to use, though
I do not see it in your tapelist.

I see 40 shows in your tapelist as reuse, not no-reuse.
Did you try to amlabel it 40 again?
Remembering to use the -f option?
Or did you just hand edit the tapelist file?

But it seems to me that amanda wants to use tape 40 if it believes
40 is back in circulation, or a newly labeled (relabeled) tape if it 
thinks there are only 39 tapes in circulation.  But clearly not tapes
01 to 10.

jl
-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)