Hello,
2018-07-16 18:08 GMT+02:00 Donna Hofmeister <[email protected]>:
>
> On Sun, Jul 15, 2018 at 10:26 AM, Radosław Korzeniewski <
> [email protected]> wrote:
>
>>
>> Could you explain why do you need a such bizarre volume label format?
>>
>
> it's a management decision on my part. i have other systems that use
> different backup methods, that write their backups into a file that
> contains the system's name. so, at a glance, i can say "oh, that's foo
> server's backup".
>
and i can also say the backup was made on this particular date.
>
> when it's all "fleshed out", it may look something like
> this: Vol-templeton.allegro.com-fd-File-20180705-2305-244-247
>
> "templeton" is the server's name. the backup was made on 5 Jul 2018
> (american's like yyyymmdd ;-) at 23:05.
>
> for bacula, for this particular server, the naming rule is working.
>
> i've got several other servers where the name *always* begins with
> "Vol-bacula...." (bacula is the name of my bacula server). the actual
> client name never gets used :-(
>
>
It will work this way only when: you never recycle your volumes and proper
define your pools and devices. Otherwise you'll be surprised.
All the information you want is stored in catalog database, so it is not
required to duplicate it in volume names as Bacula does not use volume
names for that.
best regards
--
Radosław Korzeniewski
[email protected]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
