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] Intervention needed for backup

2018-05-25 Thread Donna Hofmeister 
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

-- 
Donna Hofmeister
Allegro Consultants, Inc.
408-252-2330
Visit us on Linkedin

Like us on Facebook 
--
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

[Bacula-users] Intervention needed for backup

2018-05-24 Thread Donna Hofmeister 
Here's an example of the email I'm getting from Bacula (7.4.7):

24-May 06:05 bacula.allegro.com-sd JobId 104: Job
MinervaBackup.2018-05-23_23.05.00_53 is waiting. Cannot find any appendable
volumes.
Please use the "label" command to create a new Volume for:
Storage:  "FileChgr1-Dev1" (/santa/bacula/backup)
Pool: File
Media type:   File1

I went into bconsole and labeled a file named
-- MinervaBackup.2018-05-23_23.05.00_53. Bacula seems happy with this name
but I was immediately flooded with the following messages (this is just an
example):

bacula.allegro.com-dir JobId 104: Purging oldest volume
"MinervaBackup.2018-05-22_23.05.00_14"
bacula.allegro.com-dir JobId 104: 0 File on Volume
"MinervaBackup.2018-05-22_23.05.00_14" purged from catalog.
bacula.allegro.com-dir JobId 104: Purging oldest volume
"MinervaBackup.2018-05-22_23.05.00_14"
bacula.allegro.com-dir JobId 104: 0 File on Volume
"MinervaBackup.2018-05-22_23.05.00_14" purged from catalog.
bacula.allegro.com-dir JobId 104: Purging oldest volume
"MinervaBackup.2018-05-22_23.05.00_14"
bacula.allegro.com-dir JobId 104: 0 File on Volume
"MinervaBackup.2018-05-22_23.05.00_14" purged from catalog.
bacula.allegro.com-dir JobId 104: Purging oldest volume
"MinervaBackup.2018-05-22_23.05.00_14"
bacula.allegro.com-dir JobId 104: 0 File on Volume
"MinervaBackup.2018-05-22_23.05.00_14" purged from catalog.

I guess "purged from catalog" doesn't include actually purge the "_14" file
because it's still there:

 ll /santa/bacula/backup/M*
-rw-r- 1 root root 244 May 23 08:03
/santa/bacula/backup/MinervaBackup.2018-05-22_23.05.00_14
-rw-r- 1 root root 244 May 24 08:06
/santa/bacula/backup/MinervaBackup.2018-05-23_23.05.00_53

And fwiw...clearly the "_53" file is there but it's not being written to.
For giggles, I tried to make/label a "_54" file but that errored.

So I have this backup (which is the first of six) just sitting. If I cancel
this job, the next job in line will continue to sit too...

So what's wrong?

Here's my (only real) Pool definition:

Pool
{
  Name = File
  Pool Type= Backup
  Recycle  = yes  # Bacula can automatically recycle
Volumes
  AutoPrune= yes  # Prune expired volumes
  Volume Retention = 30 days  # 30 days
  Maximum Volume Bytes = 1G   # Limit Volume size to something
reasonable
  Maximum Volumes  = 30   # Limit number of Volumes in Pool
  Maximum Volume Jobs  = 1# Force a Volume switch after 1 job
  Volume Use Duration  = 14h  # Force volume switch
  Label Format =
"Vol-${Client}-${Pool}-${Year}${Month:p/2/0/r}${Day:p/2/0/r}-${Hour:p/2/0/r}${Minute:p/2/0/r}-${JobId}-${NumVols}"
  Purge oldest Volume  = yes
}

I do, of course, have a scratch pool:

Pool
{
  Name  = Scratch
  Pool Type = Backup
}

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?

sigh- donna

-- 
Donna Hofmeister
Allegro Consultants, Inc.
408-252-2330
Visit us on Linkedin

Like us on Facebook 
--
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