Results 1 to 4 of 4

Thread: No acceptable volumes found - can't do degraded dump without holding disk

  1. #1
    Join Date
    Feb 2016
    Posts
    3

    Default No acceptable volumes found - can't do degraded dump without holding disk

    Could someone give me an idea where to look to resolve this? Backups have been doing fine for one complete cycle but now they're failing, citing "no acceptable volumes" and referencing "degraded mode". There appear to be plenty of unused virtual tapes left but they're not being used.

    I'm not sure exactly what "degraded mode" is but it looks like it has something to do with a holding disk. I did not configure a holding disk for either of the two jobs I've setup. I cannot see the advantage of reserving a large amount of disk space to hold files that are going into virtual tape files on the same disk. It was running fine without one until these errors started popping up.

    Installed from RPM downloaded from this site: amanda-backup-server-3.3.7-1.rhel6.x86_64
    Server and client platforms: RHEL 6.7

    I recently noticed while adding another Amanda backup client that Amanda backups stopped working. I encountered the following errors when doing "amcheck" after adding the new client. Two of the clients (no route to host) are offline.

    Code:
    -bash-4.1$ amcheck DailySet1
    Amanda Tape Server Host Check
    -----------------------------
    slot 1: volume 'DailySet1-1' is still active and cannot be overwritten
    slot 2: volume 'DailySet1-2' is still active and cannot be overwritten
    slot 3: volume 'DailySet1-3' is still active and cannot be overwritten
    slot 4: volume 'DailySet1-4' is still active and cannot be overwritten
    slot 5: volume 'DailySet1-5' is still active and cannot be overwritten
    slot 6: volume 'DailySet1-6' is still active and cannot be overwritten
    slot 7: volume 'DailySet1-7' is still active and cannot be overwritten
    slot 8: volume 'DailySet1-8' is still active and cannot be overwritten
    slot 9: volume 'DailySet1-9' is still active and cannot be overwritten
    slot 10: volume 'DailySet1-10' is still active and cannot be overwritten
    slot 11: volume 'DailySet1-11' is still active and cannot be overwritten
    slot 12: volume 'DailySet1-12' is still active and cannot be overwritten
    slot 13: contains an empty volume
    slot 14: contains an empty volume
    slot 15: contains an empty volume
    slot 16: contains an empty volume
    slot 17: contains an empty volume
    slot 18: contains an empty volume
    slot 19: contains an empty volume
    slot 20: contains an empty volume
    slot 21: contains an empty volume
     volume ''
    Taper scan algorithm did not find an acceptable volume.
        (expecting a new volume)
    ERROR: No acceptable volumes found
    NOTE: host info dir /etc/amanda/DailySet1/curinfo/av8b96 does not exist
    NOTE: it will be created on the next run.
    NOTE: index dir /etc/amanda/DailySet1/index/av8b96 does not exist
    NOTE: it will be created on the next run.
    NOTE: host info dir /etc/amanda/DailySet1/curinfo/av8b100 does not exist
    NOTE: it will be created on the next run.
    NOTE: index dir /etc/amanda/DailySet1/index/av8b100 does not exist
    NOTE: it will be created on the next run.
    Server check took 0.224 seconds
    
    Amanda Backup Client Hosts Check
    --------------------------------
    WARNING: av8b99: selfcheck request failed: No route to host
    WARNING: av8b96: selfcheck request failed: No route to host
    Client check: 4 hosts checked in 22.039 seconds.  3 problems found.
    
    (brought to you by Amanda 3.3.7)
    -bash-4.1$
    Here is the disklist:

    Code:
    # host  partition      partition                                dumptype
    # name  name           device
    
    av8b93  root           /dev/mapper/vg_cymhost-lv_root           comp-high
    av8b93  boot           /dev/sda1                                comp-high
    av8b93  home           /dev/mapper/vg_cymhost-lv_home           comp-high
    av8b93  tmp            /dev/mapper/vg_cymhost-lv_tmp            comp-high
    av8b93  var            /dev/mapper/vg_cymhost-lv_var            comp-high
    av8b93  var_log        /dev/mapper/vg_cymhost-lv_var_log        comp-high
    av8b93  var_log_audit  /dev/mapper/vg_cymhost-lv_var_log_audit  comp-high
    
    av8b99  root           /dev/mapper/vg_cymhost-lv_root           comp-high
    av8b99  boot           /dev/sda1                                comp-high
    av8b99  home           /dev/mapper/vg_cymhost-lv_home           comp-high
    av8b99  tmp            /dev/mapper/vg_cymhost-lv_tmp            comp-high
    av8b99  var            /dev/mapper/vg_cymhost-lv_var            comp-high
    av8b99  var_log        /dev/mapper/vg_cymhost-lv_var_log        comp-high
    av8b99  var_log_audit  /dev/mapper/vg_cymhost-lv_var_log_audit  comp-high
    
    av8b96  root           /dev/mapper/vg_cymhost-lv_root           comp-high
    av8b96  boot           /dev/sda1                                comp-high
    av8b96  home           /dev/mapper/vg_cymhost-lv_home           comp-high
    av8b96  tmp            /dev/mapper/vg_cymhost-lv_tmp            comp-high
    av8b96  var            /dev/mapper/vg_cymhost-lv_var            comp-high
    av8b96  var_log        /dev/mapper/vg_cymhost-lv_var_log        comp-high
    av8b96  var_log_audit  /dev/mapper/vg_cymhost-lv_var_log_audit  comp-high
    
    av8b100  root          /dev/mapper/vg_cymhost-lv_root           comp-high
    av8b100  boot          /dev/sda1                                comp-high
    av8b100  home          /dev/mapper/vg_cymhost-lv_home           comp-high
    av8b100  tmp           /dev/mapper/vg_cymhost-lv_tmp            comp-high
    av8b100  var           /dev/mapper/vg_cymhost-lv_var            comp-high
    av8b100  var_log       /dev/mapper/vg_cymhost-lv_var_log        comp-high
    av8b100  var_log_audit /dev/mapper/vg_cymhost-lv_var_log_audit  comp-high
    DailySet1 configuration:

    /etc/amanda/DailySet1/amanda.conf
    Code:
    org "DailySet1"		# your organization name for reports
    dumpuser "amandabackup"	# the user to run dumps under
    mailto "root@localhost"	# space separated list of operators at your site
    dumpcycle 28		# the number of days in the normal dump cycle
    runspercycle 20		# the number of amdump runs in dumpcycle days
    tapecycle 21	# the number of tapes in rotation
    runtapes 1		# number of tapes to be used in a single run of amdump
    
    define changer my_vtapes {
        tpchanger "chg-disk:/data/amanda/vtape/DailySet1"
        property "num-slot" "21"
        property "auto-create-slot" "yes"
    }
    tpchanger "my_vtapes"
    
    tapetype HARDDISK	# what kind of tape it is
    labelstr "DailySet1"	# label constraint regex: all tapes must match
    dtimeout 1800	# number of idle seconds before a dump is aborted
    ctimeout 30	# max number of secconds amcheck waits for each client
    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 30000 mbytes
    }
    includefile "advanced.conf"
    includefile "/etc/amanda/template.d/dumptypes"
    includefile "/etc/amanda/template.d/tapetypes"
    Please let me know if you need more information to analyze this issue.

    Thank you in advance for any help.

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

    Default

    Degraded mode is when amanda do not find a tape it can write to (because of your config).

    Read 'man amanda.conf' to understand the parameter you set
    You have tapecyle set to 21 but you have only 12 vtapes labeled, I'm happy to see amanda give the expected result.

    You should label the slot 13 to 21 or allow amanda to do it (set autolabel)

  3. #3
    Join Date
    Feb 2016
    Posts
    3

    Default

    Thank you for the pointer martineau.

    I did read the man page for amanda.conf for several hours while attempting to setup everything but it was not apparent that I needed to explicitly enable autolabel anywhere.

    I found the autolabel line in /etc/amanda/DailySet1/advanced.conf commented out. I've uncommented it as suggested in the comments. Will this cause Amanda to relabel the virtual tapes the next time it runs or will I need to do something else?

    autolabel "DailySet1-%%%" empty

    If I were to manually label the vtapes would commands like this be appropriate in my case?

    amlabel DailySet1 'DailySet1-13' slot 13

    When I first installed Amanda I originally configured this job with a 12 tape set but reconfigured to to have 21. Somehow they were automatically labeled for the original configuration but did not autolabel after the reconfiguration.

    The reconfiguration used this command:

    amserverconfig DailySet1 --template harddisk --tapedev /data/amanda/vtape/DailySet1 \
    --mailto backup@localhost --dumpcycle 28 --runspercycle 20 --tapecycle 21 --runtapes 1

    I could find no "autolabel" parameter for this command. So I'm guessing that the person using it is expected to know that amanda.conf changes are required in addition to this.

    Gratefully,

    Cal Webster

  4. #4
    Join Date
    Feb 2016
    Posts
    3

    Default

    I went ahead and manually labelled the remaining vtapes with the following commands:

    Code:
    amlabel DailySet1 "DailySet1-13" slot 13
    amlabel DailySet1 "DailySet1-14" slot 14
    amlabel DailySet1 "DailySet1-15" slot 15
    amlabel DailySet1 "DailySet1-16" slot 16
    amlabel DailySet1 "DailySet1-17" slot 17
    amlabel DailySet1 "DailySet1-18" slot 18
    amlabel DailySet1 "DailySet1-19" slot 19
    amlabel DailySet1 "DailySet1-20" slot 20
    amlabel DailySet1 "DailySet1-21" slot 21
    Each of these had indications similar to the following:
    Code:
    -bash-4.1$ amlabel DailySet1 "DailySet1-13" slot 13
    Reading label...
    Found an empty tape.
    Writing label 'DailySet1-13'...
    Checking label...
    Success!
    -bash-4.1$
    Each also creates a tape header file in the "slot??" directory:
    Code:
    -bash-4.1$ ls /data/amanda/vtape/DailySet1/slot13/
    00000.DailySet1-13
    -bash-4.1$ file /data/amanda/vtape/DailySet1/slot13/00000.DailySet1-13
    /data/amanda/vtape/DailySet1/slot13/00000.DailySet1-13: AMANDA  tape header file, Unused TAPE DailySet1-13\012\014\012 DATE X TAPE DailySet1-13\012\014\012
    -bash-4.1$
    amcheck now seems to go through without any issues. Only warnings were for off-line hosts this time.

    Code:
    -bash-4.1$ amcheck DailySet1
    Amanda Tape Server Host Check
    -----------------------------
    slot 13: volume 'DailySet1-13'
    Will write to volume 'DailySet1-13' in slot 13.
    NOTE: skipping tape-writable test
    NOTE: host info dir /etc/amanda/DailySet1/curinfo/av8b96 does not exist
    NOTE: it will be created on the next run.
    NOTE: index dir /etc/amanda/DailySet1/index/av8b96 does not exist
    NOTE: it will be created on the next run.
    NOTE: host info dir /etc/amanda/DailySet1/curinfo/av8b100 does not exist
    NOTE: it will be created on the next run.
    NOTE: index dir /etc/amanda/DailySet1/index/av8b100 does not exist
    NOTE: it will be created on the next run.
    NOTE: host info dir /etc/amanda/DailySet1/curinfo/av8b97 does not exist
    NOTE: it will be created on the next run.
    NOTE: index dir /etc/amanda/DailySet1/index/av8b97 does not exist
    NOTE: it will be created on the next run.
    Server check took 0.144 seconds
    
    
    Amanda Backup Client Hosts Check
    --------------------------------
    WARNING: av8b99: selfcheck request failed: No route to host
    WARNING: av8b96: selfcheck request failed: No route to host
    Client check: 5 hosts checked in 207.058 seconds.  3 problems found.
    
    (brought to you by Amanda 3.3.7)
    -bash-4.1$
    I'm fairly confident the backups will go through now.

    Thank you for the help.

    Cal

Posting Permissions

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