>> Hello Dan and Donna,
>>>> On May 25, 2018, at 1:31 PM, Donna Hofmeister < do...@allegro.com > wrote:
>>>> On Thu, May 24, 2018 at 9:26 AM, Donna Hofmeister < do...@allegro.com >
>>>> wrote:
>>>>> Second interesting question -- given my "Label Format" statement, I would
>>>>> expect
>>>>> my files to be named something like this: Vol-minerva.allegro.com
>>>>> -fd-File-20180517-2305-73-19. So why are my files named:
>>>>> MinervaBackup.2018-05-23_23.05.00_53?
>>>> To answer my own question....
>>>> I think the underlying issue was I had made several changes to the "label
>>>> format" statement while I've been testing Bacula...and had inadvertantly
>>>> created this situation.
>>>> To solve this, I wiped out my bacula storage environment and all seems to
>>>> be
>>>> working well.
>>>> So -- reasking my second question -- if you change the "label format"
>>>> statement,
>>>> is there additional steps after that? - donna
>>> Issue an update in bconsole.
>> I think the update is not necessary when changing the Volume Format since
>> prior
>> created volumes are already created and Bacula won't rename them.
> How will bacula-dir know about the changed label format without issuing the
> update command?
Hello Dan. I seek the principle that every Dir configuration change requires a
daemon restart or reload, when the new values would be applied.
Of course, I think the user can avoid that in this specific case, issuing an
update pool.
>> I also think Bacula could criticize erratic volume names when reloading.
>> E.g. a
>> misspelled variable ${Poll} is accepted, and the user will only find the
>> error
>> when a Job gets stalled unable to create new volumes.
> Sanity testing? Sounds good.
>> Finally, I think the Bacula configuration default Label Format should be
>> ${Pool}-${NumVols}. Vol- works, but it becomes ugly when you use multiple
>> Pools
>> such as Daily, Weekly etc. since Volume numeration matches the MediaID.
>> Having
>> the ${Pool} name on the Volume might also help to distinguish them in a
>> Bacula
>> disaster recovery scenario.
> I have never subscribed to the LOTS OF INFO IN THE VOLUME LABEL school of
> thought. I use Pool names:
> $ grep 'LabelFormat' *
> pools.conf: LabelFormat = "FullAuto-"
> pools.conf: LabelFormat = "DiffAuto-"
> pools.conf: LabelFormat = "IncrAuto-"
> pools.conf: LabelFormat = "IncrAutoNoNextPool-"
> pools.conf: LabelFormat = "FullAutoNoNextPool-"
> pools.conf: LabelFormat = "TwoHourly-"
> pools.conf: LabelFormat = "Daily-"
> pools.conf: LabelFormat = "Weekly-"
> pools.conf: LabelFormat = "Monthly-"
Regards,
--
Heitor Medrado de Faria | EB-1 Visa | LPIC-III | ITIL-F | EMC 05-001
• Check my Bacula Book at Amazon.com http://bacula.us/book
• Do you need Bacula training? http://bacula.us/video-classes/
• USA +1 (323) 300-5387 | Brazil +55 (61) 98268-4220 | http://bacula.us
------------------------------------------------------------------------------
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
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
