Centralized Backup Server With Amanda On CentOS

Discussion in 'HOWTO-Related Questions' started by nandan.m.1, Apr 27, 2009.

  1. nandan.m.1

    nandan.m.1 New Member

    I am a newbie on Linux. I have visited this link http://www.howtoforge.com/centralized-backup-server-with-amanda-on-centos but did not know where to do the changes if I want to use my hardisk as the back up device.

    I am getting the error messages like after I used the following command (Reference to Step 11. Label the virtual tapes: in the above mentioned link.)

    -bash-3.2$ for ((i=1; $i<=15; i++)); do /usr/sbin/amlabel intra intra-$i slot $i; done

    "/etc/amanda/intra/amanda.conf", line 22: a quoted string expected
    "/etc/amanda/intra/amanda.conf", line 22: end of line expected
    "/etc/amanda/intra/amanda.conf", line 23: tape type parameter expected
    "/etc/amanda/intra/amanda.conf", line 23: end of line expected
    "/etc/amanda/intra/amanda.conf", line 24: tape type parameter expected
    "/etc/amanda/intra/amanda.conf", line 24: end of line expected
    "/etc/amanda/intra/amanda.conf", line 25: tape type parameter expected
    "/etc/amanda/intra/amanda.conf", line 25: end of line expected
    "/etc/amanda/intra/amanda.conf", line 26: tape type parameter expected

    Could someone help me fix it?

    My /etc/amanda/intra/amanda.conf file reads is as it is as mentioned in the above link.

    The below mentioned is my /etc/amanda/intra/amanda.conf file.

    org "Configuration name"
    mailto "email"
    netusage 600 Kbps

    dumpcycle 2 weeks
    runspercycle 10
    tapecycle 15 tapes

    #tpchanger "chg-manual"
    tpchanger "chg-disk"

    changerfile "/etc/amanda/intra/changer"

    #tapedev "null:"
    tapedev "file:/backup/intra/slots"

    #tapetype HP-DAT
    #labelstr "^DailySet1-[0-9][0-9]*$"

    tapetype HARDDISK
    define tapetype HARDDISK {
    comment “Backup to Virtual Tape”
    length 3072 mbytes # each tape is 3 Gigs
    }

    # amrecover_changer "null:"
    amrecover_changer "changer"


    #infofile "/etc/amanda/DailySet1/curinfo" # database DIRECTORY
    #logdir "/etc/amanda/ DailySet1" # log directory
    #indexdir "/etc/amanda/ DailySet1/index" # index directory
    infofile "/var/log/amanda/intra/curinfo" # database DIRECTORY
    logdir "/var/log/amanda/intra" # log directory
    indexdir "/var/log/amanda/intra/index" # index directory
     
  2. falko

    falko Super Moderator

    Please use real quotation marks in line 22. Your line looks like this...
    Code:
    comment [COLOR="Red"]“[/COLOR]Backup to Virtual Tape[COLOR="Red"]”[/COLOR]
    ... but it must look as follows:
    Code:
    comment [COLOR="Red"]"[/COLOR]Backup to Virtual Tape[COLOR="Red"]"[/COLOR]
     
  3. nandan.m.1

    nandan.m.1 New Member

    Thanks Falko

    I fixed that. But now I am stuck with a new error as mentioned below:

    "/etc/amanda/intra/disklist", line 1: disk dumptype expected
    "/etc/amanda/intra/disklist", line 2: disk dumptype expected
    Amanda Tape Server Host Check
    -----------------------------
    ERROR: logdir /var/log/amanda/intra: No such file or directory, you must create a directory.
    slot 1: read label `intra-1', date `X'

    NOTE: skipping tape-writable test
    Tape intra-1 label ok
    NOTE: info dir /var/log/amanda/intra/curinfo: does not exist
    NOTE: it will be created on the next run.
    Server check took 0.112 seconds

    Amanda Backup Client Hosts Check
    --------------------------------
    Client check: 0 hosts checked in 0.000 seconds, 0 problems found

    (brought to you by Amanda 2.5.0p2)

    when I used the following command /usr/sbin/amcheck intra on the backup server.

    I checked the the /etc/amanda/intra/disklist file and it read as follows:

    alpha /home/test comp-user-tar
    Beta /home/test1 comp-user-tar

    both my alpha and Beta are on Centos 5.2.

    I tried including

    define dumptype example {
    global
    comment "example dumptype"
    compress client fast
    program "GNUTAR"
    strategy standard
    priority high
    }

    in /etc/amanda/intra/amanda.conf and then tried the same command /usr/sbin/amcheck intra for which I received and error stating as mentioned below:

    "/etc/amanda/intra/amanda.conf", line 27: dump type parameter expected
    amcheck: errors processing config file "/etc/amanda/intra/amanda.conf"

    Please Help!
     
  4. tebokkel

    tebokkel New Member

    Then I'ld recommend not starting off with using Amanda.

    Have a look at Bacula or sbackup or whatever. Really. Amanda is a beast (at least it was in '03 when I was trying to get it to work cross platform over some 5, 6 platforms) - there ain't such a thing as a universal 'tar').

    Paul
     
  5. nandan.m.1

    nandan.m.1 New Member

    Ok. This was where I went wrong instead of editing the amanda.conf file I had copied and pasted whatever was mentioned in the link @ http://www.howtoforge.com/centralize...anda-on-centos.

    I just reverted back to the original file and then edited the same and it resolved the issue.

    Here is another one! Error 3:
    Amanda Tape Server Host Check
    -----------------------------
    Holding disk /dumps/amanda: 59359123 KB disk space available, using 59256456 KB
    ERROR: logdir /var/log/amanda/intra: No such file or directory, you must create a directory.
    slot 1: read label `intra-1', date `X'

    NOTE: skipping tape-writable test
    Tape intra-1 label ok
    NOTE: info dir /var/log/amanda/intra/curinfo: does not exist
    NOTE: it will be created on the next run.
    NOTE: index dir /var/log/amanda/intra/index: does not exist
    NOTE: it will be created on the next run.
    Server check took 0.420 seconds

    Amanda Backup Client Hosts Check
    --------------------------------
    WARNING: alpha: selfcheck request failed: timeout waiting for ACK
    Client check: 1 host checked in 30.164 seconds, 1 problem found

    (brought to you by Amanda 2.5.0p2)

    I tried referring to this link for the client side error @ http://wiki.zmanda.com/index.php/Amc...request_failed
    but for some reason I am not able to access it.

    But I checked for the amanda process on both my client and server ans it was running.

    I used the following command netstat -a | grep amanda

    and I also checked the /var/lib/amanda/.amandahosts file on client(alpha) and it had only one line which is as mentioned below:

    gamma amanda

    The server(gamma) however had two lines in /var/lib/amanda/.amandahosts file as mentioned below:

    alpha amanda
    gamma amanda

    I am not sure why it is failing again? Please help!
     
  6. choogendyk

    choogendyk New Member

    You seriously need to update your information. That was 6 years ago, which is a long time time in the life of open source products. Amanda has gone through a tremendous amount of development and major version changes during that period of time. Zmanda has come into being and provided commercial support. Amanda is now one of a handful of open source products certified as secure by the Department of Homeland Security.

    There are frequent complaints from beginners on the Bacula list about the steep learning curve, and those complaints are acknowledged by the veterans on the list. So you aren't offering an easier path by telling someone to start over there rather than helping fix their configuration issues here.

    It's inappropriate to get into arguments about preferred products rather than helping the questioner. I promise not to interfere if someone asks for help with their Bacula setup when they are having trouble.

    Meanwhile, since this thread is cross posted on linuxquestions.org, I think I'll continue posting help there. Nandan.m.1 can post here with resolutions in case people are interested.
     
  7. nandan.m.1

    nandan.m.1 New Member

    New error message

    All I did to do to get rid of my old error message(mentioned below) was to add an entry on the client system in /etc/hosts file - gamma 192.168.1.1

    Amanda Backup Client Hosts Check
    --------------------------------
    WARNING: alpha: selfcheck request failed: timeout waiting for ACK
    Client check: 1 host checked in 30.012 seconds, 1 problem found

    Now I am getting a new error message:

    ERROR: alpha: [can not read/write /etc/amandates: Permission denied]

    I checked the file permissions for /etc/amandates and it is as mentioned below.

    -rw-r--r-- 1 amanda disk 0 Jan 7 2007 /etc/amandates

    Any quick thoughts or suggestion on this?
     

Share This Page