Results 1 to 2 of 2

Thread: Unable to recover backups

  1. #1

    Default Unable to recover backups

    I have amanda Version 2.6.0p2 installed on CentOS 5.2 (same thing as RHEL 5). Everything appears to be working. Can run amdump, tape drive shows activity and amadmin then shows that a backup was run to the tapedrive. When I try and restore files nothing gets restored. Again, tape drive becomes active, but no files are written. I'm using a single tape internal tape drive for testing.
    Here is my amanda.conf, and output of amchec (at bottom):
    org "DailySet1" # your organization name for reports
    mailto "amandabackup" # space separated list of operators at your site
    dumpcycle 1 day
    #dumpcycle 1 week # the number of days in the normal dump cycle
    #runspercycle 1
    #runspercycle 5 # the number of amdump runs in dumpcycle days
    # (1 week * 5 amdump runs per week -- just weekdays)
    tapecycle 2 tapes
    #tapecycle 10 tapes # the number of tapes in rotation
    # 1 week (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

    runtapes 1 # number of tapes to be used in a single run of amdump
    #tpchanger "chg-manual" # the tape-changer glue script
    tapedev "tape:/dev/nst0" # the no-rewind tape device to be used

    holdingdisk hd2 {
    directory "/var/lib/amanda/holdings/DailySet1"
    use 1000 Mb

    labelstr "^DailySet1-[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 {
    program "GNUTAR"
    comment "gui base dumptype dumped with tar"
    compress none
    index yes

    includefile "./advanced.conf"
    includefile "/etc/amanda/template.d/dumptypes"
    includefile "/etc/amanda/template.d/tapetypes"
    [[email protected] ~]# amcheck DailySet1
    Amanda Tape Server Host Check
    Holding disk /var/lib/amanda/holdings/DailySet1: 273300 MB disk space available, using 1000 MB as requested
    read label `DailySet1-100', date `20081014172832'.
    Tape with label DailySet1-100 is still active and cannot be overwriten.
    (expecting tape DailySet1-1 or a new tape)
    Server check took 0.082 seconds

    Amanda Backup Client Hosts Check
    ERROR: Unauthenticated user
    ERROR: Unauthenticated user
    Client check: 3 hosts checked in 1.762 seconds. 2 problems found.

    (brought to you by Amanda 2.6.0p2)
    Last edited by duckbag61; October 14th, 2008 at 02:05 PM.

  2. #2
    Join Date
    Aug 2008
    Sunnyvale, CA


    It appears from your amcheck that only one of the three clients is correctly configured for a back up. Nonetheless, the one appears to be ready for an amdump. After an amdump, what does the amreport (mailed to your amanda.conf's "mailto" email address) say? What does

    amadmin DailySet1 info

    give you?


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