On Tue, Nov 12, 2019 at 11:20:49 +0100, Stefan G. Weichinger wrote:
> Am 11.11.19 um 22:10 schrieb Debra S Baddorf:
> > My dumptype definition includes
>
> > strategy noinc #don???t even calculate partial sizes
> > skip-incr yes # belt and suspenders
> > record no # daily incrementals are based on the daily level-0s.
> > # If I let this record, I think that messes the daily
> > incrementals.
>
> That "record no" ... hm, really?
> I mean, afaik there are NO incrementals done here anyway, right?
When you are running multiple configs together over time which have the
same DLEs, you do need to be very careful of the GNU tar incremental
snapshot files (assuming that you are using either GNUTAR or amgtar,
obviously).
The danger in your particular case is that the "weekly" run will update
the level 0 snapshot file for each DLE, and then the any "daily" runs
that do level 1 dumps the following week will only include files changed
after that "weekly" level 0 -- so if you were to try to recover using
only the "daily" dumps, there could be some files that are missing....
You can check for this sort of clash by looking at the dates of the
files in the gnutar-listdir/gnutar-list-dir directory, which defaults to
/var/lib/amanda/gnutar-lists/ in the Debian/Ubuntu Amanda package. If
you check there early in the week and you see a mix of dates from the
previous week ("daily" config runs) and over the weekend (the "weekly"
runs), then you are affected.
I haven't ever tried "record no", but skimming the source code it
appears that this works by preventing amanda from renaming the working
incremental snapshot file, "<DLE>_<LEVEL>.new" back to "<DLE>_<LEVEL>".
So I guess as long as the only files dated over the weekend are ".new"
files, you are okay; those files are just "orphans" will be ignored by
later runs.
(If you don't want to use "record no" for one of the configs and are
using amgtar, it's easy to avoid the conflicting-snapshot-files problem
by setting separate directories for each config in the amanda.conf
amgtar application defintion, e.g. add the config name at the end of the
path, so for config "TestBackup" I have:
define application-tool app_amgtar {
comment "amgtar"
plugin "amgtar"
property "GNUTAR-LISTDIR" "/var/lib/amanda/gnutar-lists/TestBackup/"
property "CHECK-DEVICE" "NO"
}
You do have to manually create that directory for each config as part of
getting a new client machine set up in the disklist, though. [amcheck
will warn you, if I remember correctly.]
For GNUTAR, you have to configure this in per-config amanda-client.conf
files on each client, so it's more of a pain.)
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - 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
