Results 1 to 2 of 2

Thread: new tape not found in rack

  1. #1
    Join Date
    Oct 2009
    Location
    Russellville, MO
    Posts
    3

    Default new tape not found in rack

    I am a very new newbie to Linux, so bear with me if I ask stupid questions. I am trying to get Amanda set up. I followed "The 15 minute Amanda Configuration Guide" instructions. (It only took me three days.<sigh>) It is doing a tape changer routine to virtual tapes on the hard drive of a 1Tb machine. I got it to run and send me e-mails, but it was giving me empty backups. I changed some stuff and now I am getting the following for amcheck:

    [amandabackup@jcback ~]$ amcheck DailySet1
    Amanda Tape Server Host Check
    -----------------------------
    WARNING: holding disk /u01/backup/tmp: only 1162277080 KB free (4263510016 KB requested)
    amcheck-server: slot 22: not an amanda tape
    amcheck-server: slot 23: not an amanda tape
    amcheck-server: slot 24: not an amanda tape
    amcheck-server: slot 25: not an amanda tape
    amcheck-server: slot 1: date 20091001 label DailySet1-01 (active tape)
    amcheck-server: slot 2: date 20091001 label DailySet1-02 (active tape)
    amcheck-server: slot 3: date 20091001 label DailySet1-03 (active tape)
    amcheck-server: slot 4: date 20091001 label DailySet1-04 (active tape)
    amcheck-server: slot 5: date 20091001 label DailySet1-05 (active tape)
    amcheck-server: slot 6: date 20091002 label DailySet1-06 (active tape)
    amcheck-server: slot 7: date 20091002 label DailySet1-07 (active tape)
    amcheck-server: slot 8: date 20091002 label DailySet1-08 (active tape)
    amcheck-server: slot 9: date 20091002 label DailySet1-09 (active tape)
    amcheck-server: slot 10: not an amanda tape
    amcheck-server: slot 11: not an amanda tape
    amcheck-server: slot 12: not an amanda tape
    amcheck-server: slot 13: not an amanda tape
    amcheck-server: slot 14: not an amanda tape
    amcheck-server: slot 15: not an amanda tape
    amcheck-server: slot 16: not an amanda tape
    amcheck-server: slot 17: not an amanda tape
    amcheck-server: slot 18: not an amanda tape
    amcheck-server: slot 19: not an amanda tape
    amcheck-server: slot 20: not an amanda tape
    amcheck-server: slot 21: not an amanda tape
    ERROR: new tape not found in rack
    (expecting a new tape)
    NOTE: skipping tape-writable test
    NOTE: info dir /etc/amanda/DailySet1/curinfo/jcback.ciberjc.local/_u01_backup_YEFiles: does not exist
    NOTE: index dir /etc/amanda/DailySet1/index/jcback.ciberjc.local/_u01_backup_YEFiles: does not exist
    Server check took 0.528 seconds

    Amanda Backup Client Hosts Check
    --------------------------------
    Client check: 1 host checked in 10.022 seconds, 0 problems found

    (brought to you by Amanda 2.4.4p3)

    Here is my amanda.conf file:


    org "Ciber Jefferson City MO" #Ciber-Jefferson City, MO
    mailto "nmcdowell@ciber.com" # space separated list of operators at your site
    dumpuser "amandabackup" # the user to run dumps under

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

    dumpcycle 7 days # the number of days in the normal dump cycle
    runspercycle 5 # the number of amdump runs in dumpcycle days
    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 400 # number of seconds per filesystem for estimates.

    runtapes 1 # number of tapes to be used in a single run of amdump
    tpchanger "chg-disk" # the tape-changer glue script
    tapedev "file:/space/vtapes/DailySet1/slots" # the no-rewind tape device to be used
    #tapetype HARDDISK
    #rawtapedev "/dev/null" # the raw device to be used (ftape only)
    #changerfile "/var/lib/amanda/DailySet1/changer"
    #changerfile "/var/lib/amanda/DailySet1/changer-status"
    changerfile "/etc/amanda/DailySet1/changer"
    #changerdev "/dev/null"
    tapetype HARDDISK # 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 "/u01/backup/tmp" # where the holding disk is
    use -30 Gb # how much space can we use on it
    # a negative value mean:
    # use all space except that value
    # chunksize 2 Gb # 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
    # -N Kb/Mb/Gb dont split, dump larger
    # filesystems directly to tape
    # (example: -2 Gb)
    }
    define tapetype HARDDISK{
    length 100000 mbytes
    }
    #holdingdisk hd2 {
    # directory "/dumps2/amanda"
    # use 1000 Mb
    # }
    #holdingdisk hd3 {
    # directory "/mnt/disk4"
    # use 1000 Mb
    # }


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


    # tapetypes



    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
    }

    define tapetype HP-notUltrium{
    comment "HP Ultrium 400GB"
    length 400000 mbytes
    filemark 100 kbytes
    speed 120 mbytes
    }
    # [email]goluboff@butch.Colorado.EDU[/email]
    # 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 <rlb@cs.utexas.edu>
    length 1930 mbytes
    filemark 111 kbytes
    speed 468 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 tapetype HP-ULTRIUM{
    comment "HP Ultrium data cartridge 400GB"
    length 196608mbytes
    filemark 0 kbytes
    speed 27626 kps
    }
    # dumptypes

    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
    #auth "bsd"
    exclude list "/u01/backup/tmp"
    }
    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-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
    }

    # network interfaces

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

    define interface eth0 {
    comment "1 Gbps ethernet"
    use 120 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"



    I don't know what else you need to see. Just let me know and I will post.

  2. #2
    Join Date
    Sep 2007
    Location
    Massachusetts
    Posts
    58

    Default

    Did you resolve this?

    It looks like you have a tape cycle of 25, and you have only labeled the first 9 tapes. So, at present, it thinks it cannot run a backup, because it cannot recycle any of the available labeled tapes. You can get around this problem by labeling the remaining unlabeled tapes (vtapes).

    Then you will have to show what happens after that. Without seeing the errors, I'm not sure why you were getting empty backups before.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •