Results 1 to 3 of 3

Thread: server error in amcheck

  1. #1

    Default server error in amcheck

    When I run amcheck, the client checks out okay, but the server check shows the following:

    slot 1:read label `DailySet1_01', date `20080805202052'.
    Tape with label DailySet1_01 is still active and cannot be overwriten.
    slot 2:read label `DailySet1_02', date `20080825230455'.
    Tape with label DailySet1_02 is still active and cannot be overwriten.
    slot 2:read label `DailySet1_02', date `20080825230455'.
    Tape with label DailySet1_02 is still active and cannot be overwriten.

    and so on with the slot 2 message showing 16 times, probably because the tapecycle is 17. Here's the conf:

    --------------------------------
    org "DailySet1" # your organization name for reports
    mailto "amandabackup@myserver.com" # space separated list of operators at your site
    dumpcycle 7 # the number of days in the normal dump cycle
    runspercycle 7 # the number of amdump runs in dumpcycle days
    # (1 week * 7 amdump runs per week)
    tapecycle 17 tapes # the number of tapes in rotation
    # 1 week (dumpcycle) times 7 tapes per week
    # days) 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
    runtapes 1 # number of tapes to be used in a single run of amdump
    tapedev "null:" # (device comes from changer)
    device_property "S3_ACCESS_KEY" "access_key"
    device_property "S3_SECRET_KEY" "secret_key"
    tpchanger "chg-multi"
    changerfile "changer.conf"
    tapetype HARDDISK # what kind of tape it is (see tapetypes below)

    #label_new_tapes "daily-%%%%" # Enable auto labeling
    #labelstr "^daily-[0-9][0-9]*$" # label constraint regex: all tapes must match

    dtimeout 1800 # number of idle seconds before a dump is aborted.
    ctimeout 30 # maximum number of seconds that amcheck waits
    # for each client host
    etimeout 300 # number of seconds per filesystem for estimates.

    define dumptype global {
    comment "Global definitions"
    auth "bsdtcp"
    }

    define dumptype gui-base {
    global
    program "GNUTAR"
    comment "gui base dumptype dumped with tar"
    compress none
    index yes
    }

    define tapetype HARDDISK {
    comment "Virtual Tapes"
    length 348160 mbytes
    }


    includefile "./advanced.conf"
    includefile "/var/lib/amanda/template.d/dumptypes"
    includefile "/var/lib/amanda/template.d/tapetypes"
    ---------------------

    Here's the changerfile, changer.conf:
    ----------------------
    multieject 0
    gravity 0
    needeject 0
    ejectdelay 0
    statefile /var/amanda/changer-status
    firstslot 1
    lastslot 17

    slot 1 s3:access_key-backups/DailySet1/slot-01/
    slot 2 s3:access_key-backups/DailySet1/slot-02/
    slot 3 s3:access_key-backups/DailySet1/slot-03/
    slot 4 s3:access_key-backups/DailySet1/slot-04/
    slot 5 s3:access_key-backups/DailySet1/slot-05/
    slot 6 s3:access_key-backups/DailySet1/slot-06/
    slot 7 s3:access_key-backups/DailySet1/slot-07/
    slot 8 s3:access_key-backups/DailySet1/slot-08/
    slot 9 s3:access_key-backups/DailySet1/slot-09/
    slot 10 s3:access_key-backups/DailySet1/slot-10/
    slot 11 s3:access_key-backups/DailySet1/slot-11/
    slot 12 s3:access_key-backups/DailySet1/slot-12/
    slot 13 s3:access_key-backups/DailySet1/slot-13/
    slot 14 s3:access_key-backups/DailySet1/slot-14/
    slot 15 s3:access_key-backups/DailySet1/slot-15/
    slot 16 s3:access_key-backups/DailySet1/slot-16/
    slot 17 s3:access_key-backups/DailySet1/slot-17/
    ----------------------

    As you can see, I'm trying to store to s3. And the dates on the slots are correct: the first dump was 8/5 when I started having this problem and I've been trying to solve it since then! Running 2.6 on Debian Etch. Any help is greatly appreciated.

    Thanks.

  2. #2
    Join Date
    Mar 2007
    Location
    Chicago, IL
    Posts
    688

    Default

    The immediate problem of not incrementing slot numbers is a bug, and I *think* it's been fixed in HEAD, because I can't replicate it. I'll check more deeply.

    In the interim, you can select the slot that contains the correct tape with 'amtape'. If none of your slots are working, check the debug logs -- it may be due to a time synchronization issue. Amazon only allows your local clock to differ from theirs by 60 seconds.

  3. #3
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    Quote Originally Posted by amanda_elf View Post
    Here's the changerfile, changer.conf:
    ----------------------
    multieject 0
    gravity 0
    needeject 0
    ejectdelay 0
    statefile /var/amanda/changer-status
    firstslot 1
    lastslot 17
    Did your statefile (/var/amanda/changer-status) exist? amanda must be able to create/read and write to it.

Posting Permissions

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