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
<https://www.linkedin.com/company/allegro-consultants-inc->
Like us on Facebook <http://www.facebook.com/allegroconsultantsinc>
------------------------------------------------------------------------------
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

Reply via email to