Re: [Bacula-users] Intervention needed for backup

2018-05-26 Thread Heitor Faria 
>> 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

Re: [Bacula-users] Intervention needed for backup

2018-05-26 Thread Dan Langille 
> On May 26, 2018, at 5:39 PM, Heitor Faria  wrote:
> 
> Hello Dan and Donna,
> On May 25, 2018, at 1:31 PM, Donna Hofmeister  > wrote:
> 
> 
> On Thu, May 24, 2018 at 9:26 AM, Donna Hofmeister  > 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?

> 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-"

-- 
Dan Langille - BSDCan / PGCon
d...@langille.org


--
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

Re: [Bacula-users] Intervention needed for backup

2018-05-26 Thread Heitor Faria 
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. 
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. 
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. 

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

Re: [Bacula-users] Intervention needed for backup

2018-05-26 Thread Dan Langille 
> On May 25, 2018, at 1:31 PM, Donna Hofmeister  wrote:
> 
> 
> On Thu, May 24, 2018 at 9:26 AM, Donna Hofmeister  > 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.

The change will affect only future Volumes. Existing Volumes are never affected.

-- 
Dan Langille - BSDCan / PGCon
d...@langille.org



--
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

Re: [Bacula-users] Bacula 7+mysql

2018-05-26 Thread Dan Langille 
> On May 23, 2018, at 1:02 PM, Chris Wilkinson  wrote:
> 
> This will seem a dumb question to the experienced Bacula user. I would prefer 
> to use mysql rather than the default sqlite. During installation (Debian 
> Stretch repo, Bacula v7.4.4) I said no to configuring sqlite expecting to be 
> offered the opportunity to configure mysql instead. That didn't happen. I 
> have created an empty bacula database with the appropriate user/permissions 
> but can't figure out how to make Bacula populate it or connect.

That sounds like a Debian packaging problem.

> 
> At present the director fails to start of course.
> 
> An extract from journalctl -xe follows indicating it is looking for sqlite.
> 
> -- Unit bacula-director.service has begun starting up.
> May 23 17:40:41 HOMESERVER bacula-dir[16139]: bacula-dir: dird.c:969-0 Could 
> not open Catalog "MyCatalog", databasMay 23 17:40:41 HOMESERVER 
> bacula-dir[16139]: bacula-dir: dird.c:974-0 sqlite.c:199 Database 
> /var/lib/bacula/XXX_DMay 23 17:40:41 HOMESERVER bacula-dir[16139]: 23-May 
> 17:40 bacula-dir ERROR TERMINATION
> May 23 17:40:41 HOMESERVER bacula-dir[16139]: Please correct configuration 
> file: /etc/bacula/bacula-dir.conf
> May 23 17:40:41 HOMESERVER systemd[1]: bacula-director.service: Control 
> process exited, code=exited status=1
> May 23 17:40:41 HOMESERVER systemd[1]: Failed to start Bacula Director Daemon 
> service.
> -- Subject: Unit bacula-director.service has failed
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support 
> --
> -- Unit bacula-director.service has failed.
> --
> -- The result is failed.
> May 23 17:40:41 HOMESERVER systemd[1]: bacula-director.service: Unit entered 
> failed state.
> May 23 17:40:41 HOMESERVER systemd[1]: bacula-director.service: Failed with 
> result 'exit-code'.
> May 23 17:47:01 HOMESERVER minissdpd[716]: 4 new devices added
> lines 2591-2644/2644 (END)
> 
> 
> This seems to indicate that bacula-dir is wrong but I haven't found an 
> example of what it should be.
> 
> Any help with that would be great.

Does this help? 
http://www.bacula.org/7.4.x-manuals/en/main/Installing_Configuring_MySQ.html 

Bacula will not create the required tables etc. You must do that.

-- 
Dan Langille - BSDCan / PGCon
d...@langille.org


--
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

Re: [Bacula-users] Bacula 7+mysql

2018-05-26 Thread Chris Wilkinson 
I gave up trying to fix this so compiled Bacula 9 from source 
(http://bacula.us/compilation/ ). That did all 
the right things so good to go now. Just got to work through the script bugs.

-Chris-



> On 26 May 2018, at 9:40 pm, Dan Langille  wrote:
> 
>> On May 23, 2018, at 1:02 PM, Chris Wilkinson > > wrote:
>> 
>> This will seem a dumb question to the experienced Bacula user. I would 
>> prefer to use mysql rather than the default sqlite. During installation 
>> (Debian Stretch repo, Bacula v7.4.4) I said no to configuring sqlite 
>> expecting to be offered the opportunity to configure mysql instead. That 
>> didn't happen. I have created an empty bacula database with the appropriate 
>> user/permissions but can't figure out how to make Bacula populate it or 
>> connect.
> 
> That sounds like a Debian packaging problem.
> 
>> 
>> At present the director fails to start of course.
>> 
>> An extract from journalctl -xe follows indicating it is looking for sqlite.
>> 
>> -- Unit bacula-director.service has begun starting up.
>> May 23 17:40:41 HOMESERVER bacula-dir[16139]: bacula-dir: dird.c:969-0 Could 
>> not open Catalog "MyCatalog", databasMay 23 17:40:41 HOMESERVER 
>> bacula-dir[16139]: bacula-dir: dird.c:974-0 sqlite.c:199 Database 
>> /var/lib/bacula/XXX_DMay 23 17:40:41 HOMESERVER bacula-dir[16139]: 23-May 
>> 17:40 bacula-dir ERROR TERMINATION
>> May 23 17:40:41 HOMESERVER bacula-dir[16139]: Please correct configuration 
>> file: /etc/bacula/bacula-dir.conf
>> May 23 17:40:41 HOMESERVER systemd[1]: bacula-director.service: Control 
>> process exited, code=exited status=1
>> May 23 17:40:41 HOMESERVER systemd[1]: Failed to start Bacula Director 
>> Daemon service.
>> -- Subject: Unit bacula-director.service has failed
>> -- Defined-By: systemd
>> -- Support: https://www.debian.org/support 
>> --
>> -- Unit bacula-director.service has failed.
>> --
>> -- The result is failed.
>> May 23 17:40:41 HOMESERVER systemd[1]: bacula-director.service: Unit entered 
>> failed state.
>> May 23 17:40:41 HOMESERVER systemd[1]: bacula-director.service: Failed with 
>> result 'exit-code'.
>> May 23 17:47:01 HOMESERVER minissdpd[716]: 4 new devices added
>> lines 2591-2644/2644 (END)
>> 
>> 
>> This seems to indicate that bacula-dir is wrong but I haven't found an 
>> example of what it should be.
>> 
>> Any help with that would be great.
> 
> Does this help? 
> http://www.bacula.org/7.4.x-manuals/en/main/Installing_Configuring_MySQ.html 
> 
> Bacula will not create the required tables etc. You must do that.
> 
> -- 
> Dan Langille - BSDCan / PGCon
> d...@langille.org 
--
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