Bacula-users

[Bacula-users] Bacula 5.2.6 fails to select next volume when max duration time is reached

2012-04-01 07:51:52
Subject: [Bacula-users] Bacula 5.2.6 fails to select next volume when max duration time is reached
From: Uwe Schuerkamp <uwe.schuerkamp AT nionex DOT net>
To: Bacula Users Mailing List <bacula-users AT lists.sourceforge DOT net>
Date: Sun, 1 Apr 2012 13:48:19 +0200
Hi folks,

after the recent changes in my pool setup outlined on this list, we
now seem to have a problem with Bacula 5.2.6 failing to select the
next volume after the max use duration (1 day in our case) has been
reached. Backup jobs are scheduled correctly, but they seem to be
stuck waiting of the file storage. 

Here's what's recorded in the log file: 

01-Apr 09:31 deniol186-dir JobId 17140: Start Backup JobId 17140,
Job=den.2012-04-01_06.00.00_59
01-Apr 09:31 deniol186-dir JobId 17140: Purging oldest volume
"full-0076"
01-Apr 09:31 deniol186-dir JobId 17140: 0 File on Volume "full-0076"
purged from catalog.
01-Apr 09:31 deniol186-dir JobId 17140: Purging oldest volume
"full-0076"
01-Apr 09:31 deniol186-dir JobId 17140: 0 File on Volume "full-0076"
purged from catalog.

Please note that volume #76 has not been written yet, I've assigned a
maximum of 14 volumes to the "full" pool, only seven or so actually
exist. 

these messages continue to show up in the log right until now: 

01-Apr 13:37 deniol186-dir JobId 17140: Purging oldest volume
"full-0076"
01-Apr 13:37 deniol186-dir JobId 17140: 0 File on Volume "full-0076"
purged from catalog.
01-Apr 13:37 deniol186-dir JobId 17140: Purging oldest volume
"full-0076"

... and so on, but bacula never starts the next backup job. 

"stat dir" in bconsole shows the following situation: 

den.2012-04-01_06.00.00_59 is waiting on Storage "FileStorage_full"

Any idea what could be wrong here? If I shut down bacula manually
(like I had to yesterday when this deadlock first occured), everything
works fine again until the next volume from the "full" pool is
selected.

Here's the relevant pool definition: 

Pool {
  Name = Online_full
  Storage = FileStorage_full
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes                   
  Volume Retention = 60 days        
  Purge Oldest Volume = yes
  Recycle  Oldest Volume = yes
  Maximum Volumes = 14
  Volume Use Duration = 1 day
  Label Format ="full-"
  Next Pool = Offline
}

Here's the "list media" output (sorry for the long lines): 

+---------+------------+-----------+---------+-------------------+----------+--------------+---------+------+-----------+-----------+---------------------+
| MediaId | VolumeName | VolStatus | Enabled | VolBytes          |
VolFiles | VolRetention | Recycle | Slot | InChanger | MediaType |
LastWritten         |
+---------+------------+-----------+---------+-------------------+----------+--------------+---------+------+-----------+-----------+---------------------+
|      62 | full-0062  | Used      |       1 |   474,008,138,133 |
110 |    5,184,000 |       1 |    0 |         0 | File      |
2012-03-21 09:50:29 |
|      63 | full-0063  | Used      |       1 |   234,047,013,204 |
54 |    5,184,000 |       1 |    0 |         0 | File      |
2012-03-23 01:06:00 |
|      64 | full-0064  | Used      |       1 | 2,931,052,582,969 |
682 |    5,184,000 |       1 |    0 |         0 | File      |
2012-03-25 00:35:20 |
|      65 | full-0065  | Used      |       1 |   651,341,068,848 |
151 |    5,184,000 |       1 |    0 |         0 | File      |
2012-03-25 21:37:30 |
|      66 | full-0066  | Used      |       1 | 1,144,819,463,200 |
266 |    5,184,000 |       1 |    0 |         0 | File      |
2012-03-27 23:52:43 |
|      67 | full-0067  | Used      |       1 |    95,371,103,450 |
22 |    5,184,000 |       1 |    0 |         0 | File      |
2012-03-28 04:13:22 |
|      68 | full-0068  | Used      |       1 |   751,492,764,411 |
174 |    5,184,000 |       1 |    0 |         0 | File      |
2012-03-31 09:23:21 |
|      70 | full-0070  | Used      |       1 |   919,941,359,159 |
214 |    5,184,000 |       1 |    0 |         0 | File      |
2012-04-01 13:41:51 |
|      71 | full-0071  | Append    |       1 |                 0 |
0 |    5,184,000 |       1 |    0 |         0 | File      | 0000-00-00
00:00:00 |
|      72 | full-0072  | Append    |       1 |                 0 |
0 |    5,184,000 |       1 |    0 |         0 | File      | 0000-00-00
00:00:00 |
|      73 | full-0073  | Append    |       1 |                 0 |
0 |    5,184,000 |       1 |    0 |         0 | File      | 0000-00-00
00:00:00 |
|      74 | full-0074  | Append    |       1 |                 0 |
0 |    5,184,000 |       1 |    0 |         0 | File      | 0000-00-00
00:00:00 |
|      75 | full-0075  | Append    |       1 |                 0 |
0 |    5,184,000 |       1 |    0 |         0 | File      | 0000-00-00
00:00:00 |
|      76 | full-0076  | Append    |       1 |                 0 |
0 |    5,184,000 |       1 |    0 |         0 | File      | 0000-00-00
00:00:00 |
+---------+------------+-----------+---------+-------------------+----------+---

Note that many volumes are in state "append", so for me it seems there
isn't actually a reason to go about purging an empty volume that
bacula hasn't written to previously. 

Thanks in advance for any ideas on how to resolve this situation
(bacula has been working perfectly before I put all my online volumes
into a single directory as suggested here on the list). 

All the best, 

Uwe 

-- 
NIONEX --- Ein Unternehmen der Bertelsmann AG



------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Bacula-users] Bacula 5.2.6 fails to select next volume when max duration time is reached, Uwe Schuerkamp <=