Jason Joines wrote:
> Mark Nienberg wrote:
>> Jason Joines wrote:
>>
>>> Anyone seen this before? Is it just a time synchronization issue
>>> causing the error?
>> Actually, it looks like your autolabel mechanism is not incrementing
>> properly. I
>> think bacula is trying to operate multi
Mark Nienberg wrote:
> Jason Joines wrote:
>
>> Anyone seen this before? Is it just a time synchronization issue
>> causing the error?
>
> Actually, it looks like your autolabel mechanism is not incrementing
> properly. I
> think bacula is trying to operate multiple times on the same vol
Jason Joines wrote:
> Anyone seen this before? Is it just a time synchronization issue
> causing the error?
Actually, it looks like your autolabel mechanism is not incrementing properly.
I
think bacula is trying to operate multiple times on the same volume name.
Mark
-
Jason Joines wrote:
>
> Anyone seen this before? Is it just a time synchronization issue
> causing the error?
I doubt it has anything to do with the time. Let's see the pool definition for
the
default pool in your bacula-dir.conf file.
Mark
---
This is from the Director and Storage daemons running under Bacula
2.2.5 on Linux and a 2.2.6 file daemon running on windows 2003. It
looks like it automatically created the volume and labeled it ok but has
a problem using it after after the error message about the time being
different.
