> On Nov 19, 2018, at 4:11 PM, Nathan Stratton Treadway <[email protected]>
> wrote:
>
> Keep in mind that the label is the identifier Amanda uses to communicate
> with you about what it's doing and/or looking for. So you do care a
> little bit what the labels are, since you'll see them in reports,
> command output, etc.
>
> A common convention (i.e. Amanda doesn't require this, but it seems to
> work well at many sites) is to have your volume labels be all-caps
> versions of the config name, or something related to that, followed by a
> zero-padded two-or-three digit number. For example, I have a
> configuration called TestBackup, and in that configuration I have
> labelstr "^TESTBACKUP-[0-9][0-9]$"
> , and because I have 21 vtapes my volume labels I used are
> TESTBACKUP-01, TESTBACKUP-02, .... TESTBACKUP-09, TESTBACKUP-10,
> TESTBACKUP-11, ... TESTBACKUP-21.
Huh. I never thought of that, so I’m not following that “convention”. :D
I run amanda on two dis-connected servers, with separate clients.
So my labels show the group, the tape type (we’re on the 4th or 5th type of
tapes)
[when I read the tapelist, I can tell which type of tape is meant, and whether
I still
have physical hardware to read that any more….]
and then the config, followed by some numbers.
The barcode label (Yeah, I’m using real tapes, so not all of this nonsense
applies to you)
is a far shortened version of that, with enough to tell one group’s tape from
the other.
I also keep the number ranges separate, as another clue.
ad5-daily-1nn
ad5-arch-2xxx
apc4-daily-nn
apc4-arch-5nn
So — use whatever you like, but yeah, put the config name in there!
Deb Baddorf
Fermilab
