> On Wed, 04 May 2011 13:38:37 +1000, Philip Yarra said:
>
> On 03/05/11 00:00, John Drescher wrote:
> > 2011/5/2 Philip Yarra:
> >> My bacula now seems to be firmly wedged, with all jobs trying to use the
> >> same volume (and my config very definitely says to use each volume only
> >> once).
On 03/05/11 00:00, John Drescher wrote:
> 2011/5/2 Philip Yarra:
>> My bacula now seems to be firmly wedged, with all jobs trying to use the
>> same volume (and my config very definitely says to use each volume only
>> once).
>>
>> Scheduled Jobs:
>> Level Type Pri Scheduled
2011/5/2 Philip Yarra :
> My bacula now seems to be firmly wedged, with all jobs trying to use the
> same volume (and my config very definitely says to use each volume only
> once).
>
> Scheduled Jobs:
> Level Type Pri Scheduled Name Volume
> ===
My bacula now seems to be firmly wedged, with all jobs trying to use the
same volume (and my config very definitely says to use each volume only
once).
Scheduled Jobs:
Level Type Pri Scheduled Name Volume
=
An update: after leaving it to run last night, it appears that
incremental jobs are trying to use volume Incr-0017, which is already
used (and not appendable). So why is bacula trying to re-use volumes it
is not allowed to, and how can I stop it from doing so?
I've pasted the debug output from
On 4/27/11 12:05 AM, Philip Yarra wrote:
> Hi, I'm having some troubles with bacula failing to perform automatic
> backups. The issue seems to be that the storage daemon is not
> automatically labelling a new volume. The setup looks like this:
>
> Director lives on an Intel server running Ubuntu
