Re: Degraded dump in amanda 3.5.2
Am 18.01.23 um 14:09 schrieb Pablo Venini:
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"
Nothing stands out here.
includefile "advanced.conf"
includefile "/etc/amanda/template.d/dumptypes"
includefile "/etc/amanda/template.d/tapetypes"
What's in there? Maybe something crossfiring?
Maybe you also post the output of:
amadmin yourconf config
so we can see what is interpreted by amanda.
And try 3.5.1 maybe. I think noone knows about the bugs of 3.5.2 yet.
Re: Degraded dump in amanda 3.5.2
Am 18.01.23 um 14:12 schrieb Pablo Venini: 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 Why don't you just set up a small holding disk? I understand the intention to make it work without but I don't see the advantage of doing so. Amanda is designed to use a holding disk, it's just recommended and best practice ;-)
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.
Re: Degraded dump in amanda 3.5.2
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. Pablo El 5/1/2023 a las 08:06, Stefan G. Weichinger escribió: Am 30.12.22 um 15:34 schrieb Pablo Venini: Hi Nathan, no, (as far as I'm aware) I'm not using a holding disk as this is a vtape backup, the dumptype is as follows: You could fix that by defining and using a holding disk. Then a "degraded mode backup" should work. The question is "why does it go into degraded mode" ? I only quickly scan your config: * your tapetype defines a tape with 5 GB Would your DLEs each fit onto one vtape? I think you should use a larger vtape ... and make sure that the full backup of each DLE fits onto one vtape. A holding disk wouldn't hurt also: speed up things etc
Re: Degraded dump in amanda 3.5.2
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. Pablo El 7/1/2023 a las 15:24, Nathan Stratton Treadway escribió: On Fri, Dec 30, 2022 at 11:34:14 -0300, Pablo Venini wrote: amcheck doesn't report errors Hmmm. As Stefan said, the key question is why Amanda is going into degraded mode. Normally when I have that happen it's because the target tape wasn't available at the start of the amdump run, but that doesn't seem to be the situation in your case. But it seems like buried somewhere in your logs should be some futher explanation of why Amanda is switching to degraded mode (apparently mid-run) Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: Degraded dump in amanda 3.5.2
On Fri, Dec 30, 2022 at 11:34:14 -0300, Pablo Venini wrote: > amcheck doesn't report errors Hmmm. As Stefan said, the key question is why Amanda is going into degraded mode. Normally when I have that happen it's because the target tape wasn't available at the start of the amdump run, but that doesn't seem to be the situation in your case. But it seems like buried somewhere in your logs should be some futher explanation of why Amanda is switching to degraded mode (apparently mid-run) Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: Degraded dump in amanda 3.5.2
Hi, On 05-01-2023 12:06, Stefan G. Weichinger wrote: * your tapetype defines a tape with 5 GB Would your DLEs each fit onto one vtape? I think you should use a larger vtape ... and make sure that the full backup of each DLE fits onto one vtape. Please note the length of vtapes is only used for the planner, not for the actual flushing (or direct dumping if a holding disk is not used). Stefan is correct however: this length should still be enough (for the planner) for your largest DLE to fit in, given expected compression. It doesn't matter if the cumulative of all DLEs is a lot larger. Cheers, Kes
Re: Degraded dump in amanda 3.5.2
Am 30.12.22 um 15:34 schrieb Pablo Venini: Hi Nathan, no, (as far as I'm aware) I'm not using a holding disk as this is a vtape backup, the dumptype is as follows: You could fix that by defining and using a holding disk. Then a "degraded mode backup" should work. The question is "why does it go into degraded mode" ? I only quickly scan your config: * your tapetype defines a tape with 5 GB Would your DLEs each fit onto one vtape? I think you should use a larger vtape ... and make sure that the full backup of each DLE fits onto one vtape. A holding disk wouldn't hurt also: speed up things etc
Re: Degraded dump in amanda 3.5.2
Hi Nathan,
no, (as far as I'm aware) I'm not using a holding
disk as this is a vtape backup, the dumptype is as follows:
define dumptype sm-encrypt-compress {
gui-base
comment "SM dumptype with compression and encryption"
compress client fast
encrypt client
client_encrypt "/usr/sbin/amcryptsimple"
}
amcheck doesn't report errors
amcheck monitoreo10_diario
Amanda Tape Server Host Check
-
slot 1: volume 'monitoreo10_diario-1' is still active and cannot be
overwritten
slot 2: volume 'monitoreo10_diario-2'
Will write to volume 'monitoreo10_diario-2' in slot 2.
NOTE: skipping tape-writable test
NOTE: info dir
'/etc/amanda/monitoreo10_diario/curinfo/..zzz/_usr_libexec_amanda_application'
does not exist
it will be created on the next run
NOTE: index dir
'/etc/amanda/monitoreo10_diario/index/..zzz/_usr_libexec_amanda_application'
does not exist
it will be created on the next run
NOTE: info dir
'/etc/amanda/monitoreo10_diario/curinfo/..zzz/_var_lib_amanda'
does not exist
it will be created on the next run
NOTE: index dir
'/etc/amanda/monitoreo10_diario/index/..zzz/_var_lib_amanda'
does not exist
it will be created on the next run
NOTE: info dir
'/etc/amanda/monitoreo10_diario/curinfo/..zzz/_etc' does not
exist
it will be created on the next run
NOTE: index dir
'/etc/amanda/monitoreo10_diario/index/..zzz/_etc' does not exist
it will be created on the next run
Server check took 2.159 seconds
Amanda Backup Client Hosts Check
Client check: 1 host checked in 2.053 seconds. 0 problems found.
(brought to you by Amanda 3.5.2.git.6cec2349)
Pablo
El 29/12/2022 a las 19:33, Nathan Stratton Treadway escribió:
On Thu, Dec 29, 2022 at 17:17:56 -0300, Pablo Venini wrote:
Hi, I'm setting up a new backup server with amanda 3.5.2 on CentOS 7
with vtapes. I've setup the vtapes directories, created the job and
added the dlc, checked permissions, then run amcheck and it shows no
errors. However when I run amdump, only one of the dlc gets backed
up, the other ones give a "can't do degraded dump without holding
disk" error. The config is:
(I take it you are not attempting to configure any holding disk?)
What does "amcheck" report?
Nathan
Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: Degraded dump in amanda 3.5.2
On Thu, Dec 29, 2022 at 17:17:56 -0300, Pablo Venini wrote: > Hi, I'm setting up a new backup server with amanda 3.5.2 on CentOS 7 > with vtapes. I've setup the vtapes directories, created the job and > added the dlc, checked permissions, then run amcheck and it shows no > errors. However when I run amdump, only one of the dlc gets backed > up, the other ones give a "can't do degraded dump without holding > disk" error. The config is: (I take it you are not attempting to configure any holding disk?) What does "amcheck" report? Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Degraded dump in amanda 3.5.2
Hi, I'm setting up a new backup server with amanda 3.5.2 on CentOS 7
with vtapes. I've setup the vtapes directories, created the job and
added the dlc, checked permissions, then run amcheck and it shows no
errors. However when I run amdump, only one of the dlc gets backed up,
the other ones give a "can't do degraded dump without holding disk"
error. The config is:
amanda.conf
org "monitoreo10_diario" # your organization name for
reports
dumpuser "amandabackup" # the user to run dumps under
mailto "y@x" # 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 5000 mbytes
}
define policy monitoreo10_diario {
retention-tapes 8
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"
disklist
zzz.yyy.xx /etc sm-encrypt-compress
zzz.yyy.xx /usr/local/bin sm-encrypt-compress
zzz.yyy.xx /var/lib/amanda sm-encrypt-compress
zzz.yyy.xx /usr/libexec/amanda/application sm-encrypt-compress
logs
ANALYZING ESTIMATES...
pondering zzz.yyy.xx:/usr/libexec/amanda/application... next_level0
-19335 last_level -1 (due for level 0) (new disk, can't switch to
degraded mode)
curr level 0 nsize 300 csize 150 total size 249 total_lev0 150
balanced-lev0size 21
pondering zzz.yyy.xx:/var/lib/amanda... next_level0 -19335
last_level -1 (due for level 0) (new disk, can't switch to degraded mode)
curr level 0 nsize 390 csize 195 total size 477 total_lev0 345
balanced-lev0size 48
pondering zzz.yyy.xx:/usr/local/bin... next_level0 -19335 last_level
-1 (due for level 0) (new disk, can't switch to degraded mode)
curr level 0 nsize 10 csize 5 total size 515 total_lev0 350
balanced-lev0size 48
pondering zzz.yyy.xx:/etc... next_level0 -19335 last_level -1 (due
for level 0) (new disk, can't switch to degraded mode)
curr level 0 nsize 31490 csize 15745 total size 16293 total_lev0
16095 balanced-lev0size 2297
DUMP zzz.yyy.xx 9efefbfff3fffbf79f00 /etc
20221208211442 19336 0 1970:1:1:0:0:0 31490 15745 15 1024 "Skipping: new
disk can't be dumped in degraded mode"
DUMP zzz.yyy.xx 9efefbfff3fffbf79f00
/var/lib/amanda 20221208211442 19336 0 1970:1:1:0:0:0 390 195 0 1024
"Skipping: new disk can't be dumped in degraded mode"
DUMP zzz.yyy.xx 9efefbfff3fffbf79f00
/usr/libexec/amanda/application 20221208211442 19336 0 1970:1:1:0:0:0
300 150 0 1024 "Skipping: new disk can't be dumped in degraded mode"
DUMP zzz.yyy.xx 9efefbfff3fffbf79f00
/usr/local/bin 20221208211442 19336 0 1970:1:1:0:0:0 10 5 0 1024
"Skipping: new disk can't be dumped in degraded mode"
report
FAILURE DUMP SUMMARY:
zzz.yyy.xx /etc lev 0 FAILED [can't do degraded dump without
holding disk]
zzz.yyy.xx /var/lib/amanda lev 0 FAILED [can't do degraded dump
without holding disk]
zzz.yyy.xx /usr/libexec/amanda/application lev 0 FAILED [can't do
degraded dump without holding disk]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-GB
OUT-GB COMP% MMM:SS KB/s MMM:SS KB/s
---
-- -- -
zzz.yyy.xx /etc FAILED
zzz.yyy.xx /usr/libexec/amanda/application FAILED
zzz.yyy.xx /usr/local/bin
