Re: Degraded dump in amanda 3.5.2
Yes, I was also thinking about installing 3.5.1; I installed 3.5.2 from RPM so I thought it was ok (I was reinstalling an old server wich ran 3.3.9). I tried your suggestion and if I run amdump for each DLE, the dumps are ok El 18/1/2023 a las 06:23, Stefan G. Weichinger escribió: Am 18.01.23 um 01:47 schrieb Pablo Venini: Hi Stefan, sorry for the delay in answering. This is a backup of the amanda server itself (configs, etc.), there is less than 100MB of information. What worries me is that if I use a holding disk without correcting the problem the dumps will go there instead of going to the vtapes. Did you also test this config with amanda-3.5.1? 3.5.2 is rather untested, I think, as there are still no official packages available afaik. I would define a small holding disk and see if that helps ... just for debug purposes. A vtape-setup also benefits from a holding disk, no reason to not use that with virtual tapes. What if you only dump specific DLEs? amdump myconf /etc
Re: Degraded dump in amanda 3.5.2
This is the amanda.conf
org "monitoreo10_diario" # your organization name for reports
dumpuser "amandabackup" # the user to run dumps under
mailto "xxx...@y.zz" # space separated list of operators at
your site
dumpcycle 1week # the number of days in the normal dump cycle
tapecycle 8 # the number of tapes in rotation
runspercycle 7 # the number of amdump runs in dumpcycle days
define changer my_vtapes {
tpchanger "chg-disk:/backups/amanda/vtape/diarios/monitoreo10_diario/"
property "num-slot" "8"
property "auto-create-slot" "yes"
}
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 5 gbytes
}
define policy monitoreo10_diario {
retention-tapes 7
retention-days 0
retention-recover 0
retention-full 0
}
define storage monitoreo10_diario {
policy "monitoreo10_diario" # the policy
tapepool "monitoreo10_diario" # the tape-pool
tpchanger "my_vtapes" # the changer
runtapes 1 # number of tapes to be used in a single run of
amdump
tapetype "HARDDISK" # what kind of tape it is
labelstr "monitoreo10_diario" # label constraint regex: all
tapes must match
#autolabel
#meta-autolabel
taperscan "traditional"
#max-dle-volume 100
#taperalgo first
#taper-parallel-write 1
}
storage "monitoreo10_diario"
includefile "advanced.conf"
includefile "/etc/amanda/template.d/dumptypes"
includefile "/etc/amanda/template.d/tapetypes"
El 18/1/2023 a las 06:19, Stefan G. Weichinger escribió:
Am 18.01.23 um 01:43 schrieb Pablo Venini:
Hi Nathan, do you know if there is any setting to cause amanda to be
more verbose?
Another weird thing is that the report says:
NOTES:
planner: tapecycle (7) <= runspercycle (7)
However the config is like this:
tapecycle 8 # the number of tapes in rotation
runspercycle 7 # the number of amdump runs in dumpcycle days
the value reported for tapecycle is different than the one configured.
Maybe you show your amanda.conf for a start. This sounds wrong, yes.
Re: Degraded dump in amanda 3.5.2
Am 18.01.23 um 01:47 schrieb Pablo Venini: Hi Stefan, sorry for the delay in answering. This is a backup of the amanda server itself (configs, etc.), there is less than 100MB of information. What worries me is that if I use a holding disk without correcting the problem the dumps will go there instead of going to the vtapes. Did you also test this config with amanda-3.5.1? 3.5.2 is rather untested, I think, as there are still no official packages available afaik. I would define a small holding disk and see if that helps ... just for debug purposes. A vtape-setup also benefits from a holding disk, no reason to not use that with virtual tapes. What if you only dump specific DLEs? amdump myconf /etc
Re: Degraded dump in amanda 3.5.2
Am 18.01.23 um 01:43 schrieb Pablo Venini: Hi Nathan, do you know if there is any setting to cause amanda to be more verbose? Another weird thing is that the report says: NOTES: planner: tapecycle (7) <= runspercycle (7) However the config is like this: tapecycle 8 # the number of tapes in rotation runspercycle 7 # the number of amdump runs in dumpcycle days the value reported for tapecycle is different than the one configured. Maybe you show your amanda.conf for a start. This sounds wrong, yes.
