On Fri, Jun 28, 2019 at 13:00:25 +0100, Nuno Dias wrote:
> Yes, this will work if I use different labels not related with the
> name of the diskdevice, the only problem is more work when I run
> amstatus and amrecover to match the label with the disk/diredctory
(Deb, sorry... I seem to have missed your previous email when it came
through, but yes you showed what I was trying to get at, only with
more-helpful example names :) .)
Nuno,
I would be curious to hear from any other sites where this problem has
come up, but given that the current matching behavior seems to be more
than two decades old, I suspect that changing your "diskname" format is
going to be the easiest path forward to being able to select DLEs
properly from the amdump command line.
Note that you can certainly pick disknames that are "related" to the
diskdevice name, so it should be possible to find a convention that
works around the matching-problem without being too bad in the context
of amstatus/amrecover/the Amanda Mail Report.
For example, though I did it for competely unrelated reasons, in one
Amanda config I run (named "Nightly), I have set the diskname of each
DLE to be "ntly-" followed by the DLE path/"diskdevice path" (i.e.
"ntly-/", "ntly-/data", etc.). So in that case I can tell easily from
the diskname exactly what directory that DLE backs up... but yet none of
the strings used for disknames exactly matches any string used for a
diskdevice...
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
