Results 1 to 4 of 4

Thread: Amanda 3.3.1 on Debian Wheezy configuration issues

  1. #1

    Default Amanda 3.3.1 on Debian Wheezy configuration issues

    Hello Amanda community,

    First of all: This seems to be a very active community, which provides much information to me and helps me understanding Amanda. But, sadly, the knot in my brain is still remaining as I am an Amanda-greenhorn. So please excuse my lack of understading in the depths of how Amanda works. I was struggling around with searching each of this failure messages via google and especially this forums, but maybe due to my confusion of the functionality I can't figure out the suggestions to my needs.

    Please let me describe my Problem as follows:
    I installed Amanda 3.3.1 from Debian sources (apt-get install amanda-server amanda-client xinetd gnuplot) on a new clean debian wheezy VM.

    My config is the following:
    /etc/amanda/VMdaily/amanda.conf:
    Code:
    org "P4-Backup (wp5demo)"         # your organization name for reports
    mailto "backup@localhost"          # space separated list of operators at your site
    dumpuser "backup"       # the user to run dumps under
    
    logdir   "/etc/amanda/VMdaily/logs"           # log directory
    infofile "/etc/amanda/VMdaily/curinfo"        # database filename
    indexdir "/etc/amanda/VMdaily/index"          # index directory
    tapelist "/etc/amanda/VMdaily/tapelist"       # list of used tapes
    
    dumpcycle 7 days                        
    tapecycle 10 tapes                      
    tapetype DISK                           
    tpchanger "chg-disk"
    changerfile "/etc/amanda/VMdaily/changer" # needed by amlabel
    tapedev "file:/backup/amanda/VMdaily/slots"
    
    usetimestamps yes
    runtapes        10                      # Maximale Anzahl Tapes, die fuer ein Single-Backup zur Verfuegung stehen
    
    
    define tapetype DISK {
      comment "Backup to HD"
      length 5 gbytes                       # Laenge eines VTapes auf DISK
    }
    
    # comment holding disk section if needed
    #holdingdisk hd1 {
    #  directory "/dumps/"
    #}
    
    # to be used by any other dumptype
    define dumptype global {
      comment "Global definitions"
      index yes
      record yes
      auth "bsdtcp"
    }
    
    define dumptype daily {
      global
      comment "daily dumptype"
      compress client fast
      program "GNUTAR"
      strategy standard
      priority high
      exclude list "/etc/amanda/VMdaily/global-debian-exclude.list"
    }

    When executing amcheck I get the following response:
    Code:
    backup@backupsrv:/etc/amanda$ /usr/sbin/amcheck VMdaily
    Amanda Tape Server Host Check
    -----------------------------
    found in slot 10: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    slot 10: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    found in slot 1: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    slot 1: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    found in slot 2: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    slot 2: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    found in slot 3: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    slot 3: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    found in slot 4: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    slot 4: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    found in slot 5: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    slot 5: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    found in slot 6: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    slot 6: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    found in slot 7: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    slot 7: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    found in slot 8: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    slot 8: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    found in slot 9: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
    slot 9: Error checking directory /backup/amanda/VMdaily/slots/data/: No such file or directory
     all slots have been loaded
    Taper scan algorithm did not find an acceptable volume.
        (expecting a new volume)
    ERROR: No acceptable volumes found
    NOTE: host info dir /etc/amanda/VMdaily/curinfo/michael.mydomain.local does not exist
    NOTE: it will be created on the next run.
    NOTE: index dir /etc/amanda/VMdaily/index/michael.mydomain.local does not exist
    NOTE: it will be created on the next run.
    Server check took 4.772 seconds
    
    Amanda Backup Client Hosts Check
    --------------------------------
    Client check: 1 host checked in 2.028 seconds.  0 problems found.
    
    (brought to you by Amanda 3.3.1)
    The target host michael.mydomain.local aso is a debian machine in our network.


    When executing amdump i get the following error message:

    Code:
    ...header skipped....
    *** A TAPE ERROR OCCURRED: [No acceptable volumes found].
    No dumps are left in the holding disk.
    
    The next 10 tapes Amanda expects to use are: 10 new tapes.
    FAILURE DUMP SUMMARY:
      michael.mydomain.local /var/www/ lev 0  FAILED [Skipping: new disk can't be dumped in degraded mode]
    
    
    STATISTICS:
                              Total       Full      Incr.   Level:#
                            --------   --------   --------  --------
    Estimate Time (hrs:min)     0:00
    Run Time (hrs:min)          0:00
    Dump Time (hrs:min)         0:00       0:00       0:00
    Output Size (meg)            0.0        0.0        0.0
    Original Size (meg)          0.0        0.0        0.0
    Avg Compressed Size (%)      --         --         --
    DLEs Dumped                    0          0          0
    Avg Dump Rate (k/s)          --         --         --
    
    Tape Time (hrs:min)         0:00       0:00       0:00
    Tape Size (meg)              0.0        0.0        0.0
    Tape Used (%)                0.0        0.0        0.0
    DLEs Taped                     0          0          0
    Parts Taped                    0          0          0
    Avg Tp Write Rate (k/s)      --         --         --
    
    NOTES:
      planner: Adding new disk michael.mydomain.local:/var/www/.
      driver: Taper error: "No acceptable volumes found"
      taper: Slot 9 without label is not labelable
      taper: Slot 10 without label is not labelable
      taper: Slot 1 without label is not labelable
      taper: Slot 2 without label is not labelable
      taper: Slot 3 without label is not labelable
      taper: Slot 4 without label is not labelable
      taper: Slot 5 without label is not labelable
      taper: Slot 6 without label is not labelable
      taper: Slot 7 without label is not labelable
      taper: Slot 8 without label is not labelable
    
    
    DUMP SUMMARY:
                                           DUMPER STATS               TAPER STATS
    HOSTNAME     DISK        L ORIG-kB  OUT-kB  COMP%  MMM:SS   KB/s MMM:SS   KB/s
    Original Size (meg)          0.0        0.0        0.0
    Avg Compressed Size (%)      --         --         --
    DLEs Dumped                    0          0          0
    Avg Dump Rate (k/s)          --         --         --
    
    Tape Time (hrs:min)         0:00       0:00       0:00
    Tape Size (meg)              0.0        0.0        0.0
    Tape Used (%)                0.0        0.0        0.0
    DLEs Taped                     0          0          0
    Parts Taped                    0          0          0
    Avg Tp Write Rate (k/s)      --         --         --
    
    NOTES:
      planner: Adding new disk michael.mydomain.local:/var/www/.
      driver: Taper error: "No acceptable volumes found"
      taper: Slot 9 without label is not labelable
      taper: Slot 10 without label is not labelable
      taper: Slot 1 without label is not labelable
      taper: Slot 2 without label is not labelable
      taper: Slot 3 without label is not labelable
      taper: Slot 4 without label is not labelable
      taper: Slot 5 without label is not labelable
      taper: Slot 6 without label is not labelable
      taper: Slot 7 without label is not labelable
      taper: Slot 8 without label is not labelable
    
    
    DUMP SUMMARY:
                                           DUMPER STATS               TAPER STATS
    HOSTNAME     DISK        L ORIG-kB  OUT-kB  COMP%  MMM:SS   KB/s MMM:SS   KB/s
    -------------------------- ------------------------------------- -------------
    michael.mydom... /var/www/                                FAILED
    
    (brought to you by Amanda version 3.3.1)

    As far as I understood, the disk changer is looking for a new disk in each slot. I thought, by deploying disks during installation using the following commands this issue should be avoided:
    Code:
    mkdir -p /backup/amanda/vmDaily/slots
    for ((i=1; $i<=14; i++)); do mkdir /backup/amanda/vmDaily/slots/slot$i;done
    chown -R backup:backup /backup/amanda
    chmod 750 /backup/amanda
    The failure notices also say, that slots not labeled are not labelable, can I fix that issue by resetting and labeling this slots in any way?
    Or are there any other misconfigurations?

    Here's some additional information which might be useful for experts :
    Code:
    backup@backupsrv:/var/log/amanda/server/VMdaily$ tail amdump.20130923120221.debug
    Mon Sep 23 12:02:27 2013: thd-0xfe0e00: amdump: running amreport
    Mon Sep 23 12:02:27 2013: thd-0xfe0e00: amdump: /usr/sbin/amreport exited with code 20
    Mon Sep 23 12:02:27 2013: thd-0xfe0e00: amdump: ignoring failing exit code 20 from /usr/sbin/amreport
    Mon Sep 23 12:02:27 2013: thd-0xfe0e00: amdump: renaming trace log
    Mon Sep 23 12:02:27 2013: thd-0xfe0e00: amdump: trimming old trace logs
    Mon Sep 23 12:02:27 2013: thd-0xfe0e00: amdump: /usr/lib/amanda/amtrmlog exited with code 0
    Mon Sep 23 12:02:27 2013: thd-0xfe0e00: amdump: trimming old indexes
    Mon Sep 23 12:02:27 2013: thd-0xfe0e00: amdump: /usr/lib/amanda/amtrmidx exited with code 0
    Mon Sep 23 12:02:27 2013: thd-0xfe0e00: amdump: renaming amdump log and trimming old amdump logs (beyond tapecycle+2)
    Mon Sep 23 12:02:27 2013: thd-0xfe0e00: amdump: exiting with code 0
    Please let me know, if you need some more information.
    Any help or hint would be much appreciated!

    Best regards


    Note: the domain/host information are edited due to security issues.

  2. #2
    Join Date
    Oct 2005
    Posts
    1,559

    Default

    Did you label the vtapes (each slot) using amlabel?

  3. #3

    Default

    Quote Originally Posted by paddy View Post
    Did you label the vtapes (each slot) using amlabel?
    Hey, thank you for your quick reply!

    In between I fixed at least the label problem by deleting the vtapes (it was a fresh installation with no content yet), deploying new ones and labeling each one.
    I was able to run the first test backup with the following result:

    Code:
    ....These dumps were to tape VMdaily-02.
    The next 10 tapes Amanda expects to use are: 8 new tapes, VMdaily-01, VMdaily-02.
    The next 8 new tapes already labelled are: VMdaily-03, VMdaily-04, VMdaily-05, VMdaily-06, VMdaily-07, VMdaily-08,$
    
    
    STATISTICS:
                              Total       Full      Incr.   Level:#
                            --------   --------   --------  --------
    Estimate Time (hrs:min)     0:00
    Run Time (hrs:min)          0:05
    Dump Time (hrs:min)         0:04       0:04       0:00
    Output Size (meg)          322.0      322.0        0.0
    Original Size (meg)        773.0      773.0        0.0
    Avg Compressed Size (%)     41.6       41.6        0.0
    DLEs Dumped                    2          1          1  1:1
    Avg Dump Rate (k/s)       1294.4     1299.0        0.0
    
    Tape Time (hrs:min)         0:04       0:04       0:00
    Tape Size (meg)            322.0      322.0        0.0
    Tape Used (%)                6.3        6.3        0.0
    DLEs Taped                     2          1          1  1:1
    Parts Taped                    2          1          1  1:1
    Avg Tp Write Rate (k/s)   1323.5     1324.0        0.0
    
    USAGE BY TAPE:
      Label               Time         Size      %  DLEs Parts
      VMdaily-02          0:04      329678k    6.3     2     2
    
    NOTES:
      planner: Last full dump of michael.mydomain.local:/var/www/ on tape VMdaily-01 overwritten on this run.
      planner: Adding new disk michael.mydomain.local:/.
      taper: Slot 1 with label VMdaily-01 is not reusable
      taper: Slot 2 with label VMdaily-02 is usable
      taper: tape VMdaily-02 kb 329679 fm 2 [OK]
    So regarding the problem described above I think I found a solution
    Or are there any improvement suggestions for the configuration?

    My next step is testing a windows client backup.

    Is it advisable to setup a different configuration folder like VMdaily, winmachine1, linuxhost2 etc. and Vtape or set of Vtapes for each machine, when I want to backup many machines?

  4. #4

    Default amaddclient fails with wrong path

    After some weeks, where I was busy with other projects, I came back to work on my Amanda-backup installation.

    So far I was able to setup a configuration, which was able to backup linux-machines on a NFS share, so almost first half of my project seems to be fine.
    My next steps are windows-clients and mysql-zrm (which is hot option for me).

    Actually I'm getting trouble with the last step while setting up a windows-client backup: slots, config, labeling worked as far as I can say, but most confusing is the amaddclient command for me, as you can see in the following response:
    Code:
    backup@backupsrv:/etc/amanda$ ls
    clients  nastest  servers  template.d  VMdaily  wintest
    backup@backupsrv:/etc/amanda$ /usr/sbin/amaddclient --config clients/windows --client notebook1.mydomain.local --diskdev "C:/" --dumptype zwc-compress
    Logging to /var/log/amanda/amaddclient.20131024162509.debug
    /etc/amanda/clients/windows/disklist has 'notebook1.mydomain.local C:/ ...' entry, file not updated
    updating /var/lib/lib/amanda/.amandahosts on backupsrv.mydomain.local
    ERROR: Cannot open /var/lib/lib/amanda/.amandahosts : file or directory not found
    backup@backupsrv:/etc/amanda$
    Now the really confusing part is the path to "amandahosts" file. While it's stored in "/etc/amandahosts" and normally called from all of my other configs, in this case it calls " /var/lib/lib/amanda/.amandahosts"

    I tried to research in the amanda code files in order to check out, where the new path comes from, as this path has never been existing.
    Of course, normally there's no path like /var/lib/lib .... so I tried to set it up and trick it with a symlink to my real existing amandahosts file, but it didn't take affect.

    I'm sure, there is a misconfiguration on my site but after hours of researching and abusing google I cannot find the hint, that lets my penny drop.
    For a supposedly easy-to-install-and-handle backup solution I have been spending really much time and got just a depressing fraction working in this issue :-/
    But I don't want to give up, so I'm asking again

    So I'd be happy to get any Idea, what's wrong in my config.

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
  •