PDA

View Full Version : Amvault - invalid partnum



maker008
April 18th, 2011, 04:34 AM
I am trying to use amvault to copy the full dumps to archive disk every week.

I use following command:


amvault --src-timestamp 20110413-16 --fulls-only --dst-changer archivedisk1 --autolabel any --label-template WeeklyFull-%%% Daily2

Some dumps are copied correctly but for same servers there are strange errors:



FAILURE DUMP SUMMARY:
amvault: FATAL Invalid partnum (16) > totalparts (15)


I am using FreeBSD 8.2-RELEASE and Amanda 3.2.1

There is my amanda.conf (Daily2)



org "XXX" # your organization name for reports
mailto "admin@XXX.cz" # space separated list of operators at your site
dumpuser "amanda" # the user to run dumps under

inparallel 4 # maximum dumpers that will run in parallel (max 63)
# this maximum can be increased at compile-time,
# modifying MAX_DUMPERS in server-src/driverio.h
dumporder "TTTT" # specify the priority order of each dumper
# s -> smallest size
# S -> biggest size
# t -> smallest time
# T -> biggest time
# b -> smallest bandwitdh
# B -> biggest bandwitdh
# try "BTBTBTBTBTBT" if you are not holding
# disk constrained

taperalgo largestfit # The algorithm used to choose which dump image to send
# to the taper.
# Possible values:
# [first|firstfit|largest|largestfit|smallest|last]
# Default: first.
# first First in - first out.
# firstfit The first dump image that will fit
# on the current tape.
# largest The largest dump image.
# largestfit The largest dump image that will fit
# on the current tape.
# smallest The smallest dump image.
# last Last in - first out.

displayunit "m" # Possible values: "k|m|g|t"
# Default: k.
# The unit used to print many numbers.
# k=kilo, m=mega, g=giga, t=tera

netusage 9000 KBps # maximum net bandwidth for Amanda, in KB per sec

dumpcycle 4 days # the number of days in the normal dump cycle
runspercycle 3 # the number of amdump runs in dumpcycle days
# (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 37 tapes # the number of tapes in rotation
# 4 weeks (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

bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
bumppercent 20 # minimum savings (threshold) to bump level 1 -> 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)

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

flush-threshold-dumped 100
flush-threshold-scheduled 100

# 32k buffers to allocate. The default is 20 (640k).

usetimestamps yes

runtapes 7 # number of tapes to be used in a single run of amdump

tpchanger "chg-disk:/home/amanda/vtapes/Daily2/slots" # a virtual tape changer


define changer "archivedisk1" {
tpchanger "chg-disk:/mnt_backup/archivedisk1"
}

maxdumpsize -1 # Maximum number of bytes the planner will schedule
# for a run (default: runtapes * tape_length).

tapetype SPEC_SIZED_DISK


# -f flag for faster positioning of the tape.
# -l flag to check the label.
amrecover_changer "" # amrecover will use the changer if you restore
# from this device.
# It could be a string like 'changer' and
# amrecover will use your changer if you
# set your tape with 'settape changer'


holdingdisk hd1 {
comment "main holding disk"
directory "/home/amanda/amandahold/Daily2"
use -100 Mb
chunksize 0
}

autoflush yes #

logdir "/usr/local/etc/amanda/Daily2/"
infofile "/usr/local/etc/amanda/Daily2/curinfo"
indexdir "/usr/local/etc/amanda/Daily2/index"


define tapetype SPEC_SIZED_DISK {
filemark 4 KB
length 30 GB
part-size 3GB
}

define dumptype......



Thanks for any advice.

martineau
April 18th, 2011, 05:17 AM
post the log.<datestamps>.?

maker008
April 18th, 2011, 05:37 AM
The log file is attached.

martineau
April 18th, 2011, 07:54 AM
Soryr, post the log files for the source datestamp.

maker008
April 18th, 2011, 11:57 PM
Sorry, I don't understand which log do you wish. There is a log file from yesterday run, with the exactly same parameters as above.

Errors is always for the same servers (shrek.XXX.cz in this case).

According the amrecover history it seems that backup has only 16 parts.



200- Dump history for config "Daily2" host "shrek.XXX.cz" disk /
201- 2011-04-19-08-26-08 1 /home/amanda/amandahold/Daily2/20110419082608/shrek.in.idc.cz._.1:0
201- 2011-04-18-00-30-16 0 Daily2-18:6,7,8,9,10,11;Daily2-19:1,2,3,4,5,6,7,8,9,10;Daily2-20:1
201- 2011-04-16-00-30-16 1 Daily2-15:5
201- 2011-04-15-00-30-16 1 Daily2-12:18
201- 2011-04-14-00-30-16 1 Daily2-10:17
201- 2011-04-13-00-30-16 0 Daily2-30:9,10;Daily2-6:1,2,3,4,5,6,7,8,9,10;Daily2-7:1,2,3,4
201- 2011-04-11-00-30-16 1 Daily2-3:1
201- 2011-04-09-00-30-16 1 Daily2-37:2
201- 2011-04-08-00-30-15 0 Daily2-33:9,10,11,12,13,14,15,16,17;Daily2-34:1,2,3,4,5,6,7
201- 2011-04-07-00-30-16 1 Daily2-29:2
201- 2011-04-06-00-30-16 1 Daily2-26:2
201- 2011-04-05-00-30-15 1 Daily2-23:10
200 Dump history for config "Daily2" host "shrek.XXX.cz" disk /

martineau
April 19th, 2011, 03:28 AM
I want the log file of the source run that generated the log file that amvault do not parse correctly.
Post all log files dated between 20110413-16

maker008
April 20th, 2011, 12:27 AM
I post the log from 20110413 when the failure backup originate.

It seems that newer backup (after 20110414) are valuated OK.

martineau
April 20th, 2011, 05:36 AM
Post the amvault debug file.

maker008
April 27th, 2011, 12:25 AM
The error do not appear again and I am not able to reproduce it.
Thank you.