If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

amrecover generating HUGE debug logs

The backup is generating an amindex where each entry (one entry per file restored) is 440K bytes. This backup is 84,000 directories with 6.9 million files. At this rate the debug file alone will be over 3 terabytes. At the current rate it will take the amindex step 100 days to finish. (about 4GB a day).

There was an old bug report in the 5.x version where the answer was upgrade to the latest as this is fixed there. The original backup was done with 2.5.x updated to 2.6.1 because of the reported fix. Unfortunately, it did not fix the issue.

Is there a flag to turn the debugging off? There is no way for me to restore this backup with the amrecover under the current implementation.
disklist layout
vlstst00 / exclude-mnt
vlstst00 /mnt/yeast user-span-LTO3
vlstst00 /mnt/work user-span-LTO3
vlstst00 /mnt/backup user-span-backup
vlstst00 /mnt/tickets/cpe user-span-LTO3
vlstst00 /mnt/tickets/test user-span-LTO3

amanda.conf layout
org "supportTics" # your organization name for reports
mailto "myemail" # space separated list of operators at your site
dumpuser "amandabackup" # the user to run dumps under
usetimestamps yes
inparallel 4 # maximum dumpers that will run in parallel (max 63)
dumporder "sssS" # specify the priority order of each dumper
taperalgo first # The algorithm used to choose which dump image to send
displayunit "m" # Possible values: "k|m|g|t"
netusage 8000 Kbps # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 1 weeks # the number of days in the normal dump cycle
runspercycle 7 # the number of amdump runs in dumpcycle days
tapecycle 24 tapes # the number of tapes in rotation
bumpsize 1000 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 300 # number of seconds per filesystem for estimates.
dtimeout 1800 # number of idle seconds before a dump is aborted.
ctimeout 30 # maximum number of seconds that amcheck waits
device_output_buffer_size 1280k
runtapes 8 # number of tapes to be used in a single run of amdump
tpchanger "chg-zd-mtx" # the tape-changer glue script
tapedev "/dev/nst0" # the no-rewind tape device to be used
changerfile "/etc/amanda/backup/changer.conf"
changerdev "/dev/sg2"
maxdumpsize -1 # Maximum number of bytes the planner will schedule
tapetype LTO3 # what kind of tape it is (see tapetypes below)
labelstr "^VLS[0-9][0-9][0-9]L3*$" # label constraint regex: all tapes must match
amrecover_do_fsf yes # amrecover will call amrestore with the
amrecover_check_label yes # amrecover will call amrestore with the
amrecover_changer "chg-zd-mtx" # amrecover will use the changer if you restore
holdingdisk hd1 {
comment "main holding disk"
directory "/mnt/amandaTmp/amtemp" # where the holding disk is added one directory down for fix
use -100 Mb # how much space can we use on it
chunksize 10Gb # size of chunk if you want big dump to be
}
autoflush yes #
define tapetype LTO3 {
comment "just produced by tapetype prog (hardware compression off)"
length 387072 mbytes
filemark 0 kbytes
speed 46228 kps
}