On Dec 23, 2015, at 8:41 PM, Peter Keller wrote:
>
> Hello,
>
> I'm a new user who has just set up bacula on a couple of
> machines. During my initial tests, things were working fine, but
> when I went into production I started seeing these errors. These
> errors only appear to happen when a bac
On 12/26/2015 10:21 AM, Kern Sibbald wrote:
> Hello Peter,
>
> One more question: Is the client for which this Catalog error is
> occurring a Windows machine?
Nope, it is an x86_64 Linux Debian 8.0 box, technically a DomU on a Xen
Linux Debian Dom0 machine.
Thank you!
-pete
-
Hello Peter,
One more question: Is the client for which this Catalog error is
occurring a Windows machine?
If so, I believe that I have found the problem, if not, then I have to
look further.
Best regards,
Kern
On 12/25/2015 09:18 PM, Peter Keller wrote:
> Hello,
>
> On 12/25/2015 02:01 AM, Ke
Hello Peter,
On 12/25/2015 09:18 PM, Peter Keller wrote:
> Hello,
>
> On 12/25/2015 02:01 AM, Kern Sibbald wrote:
>> On 12/25/2015 08:11 AM, Kern Sibbald wrote:
>>> On 12/25/2015 01:33 AM, Peter Keller wrote:
> 23-Dec 18:47 DIR:xxx.yyy.zzz JobId 4: Error: Catalog error updating file
> dige
Hello Peter,
On Fri, Dec 25, 2015 at 9:18 PM, Peter Keller wrote:
> Hello,
>
> On 12/25/2015 02:01 AM, Kern Sibbald wrote:
> > On 12/25/2015 08:11 AM, Kern Sibbald wrote:
> >> On 12/25/2015 01:33 AM, Peter Keller wrote:
> 23-Dec 18:47 DIR:xxx.yyy.zzz JobId 4: Error: Catalog error updating
>
Hello,
On 12/25/2015 02:01 AM, Kern Sibbald wrote:
> On 12/25/2015 08:11 AM, Kern Sibbald wrote:
>> On 12/25/2015 01:33 AM, Peter Keller wrote:
23-Dec 18:47 DIR:xxx.yyy.zzz JobId 4: Error: Catalog error updating file
digest. bdb.h:101 Update failed: affected_rows=0 for UPDATE File SET
>>
On 12/25/2015 08:11 AM, Kern Sibbald wrote:
> On 12/25/2015 01:33 AM, Peter Keller wrote:
>> Hello,
>>
>>> 23-Dec 18:47 DIR:xxx.yyy.zzz JobId 4: Error: Catalog error updating file
>>> digest. bdb.h:101 Update failed: affected_rows=0 for UPDATE File SET
>>> MD5='oGhRwHZ+y+mWb+fv9ppFrA' WHERE FileId=
On 12/25/2015 01:33 AM, Peter Keller wrote:
> Hello,
>
>> 23-Dec 18:47 DIR:xxx.yyy.zzz JobId 4: Error: Catalog error updating file
>> digest. bdb.h:101 Update failed: affected_rows=0 for UPDATE File SET
>> MD5='oGhRwHZ+y+mWb+fv9ppFrA' WHERE FileId=6148914691236517205
> Also, I just noticed, 6148914
Hello,
Thanks for pointing out the misleading information in the manual. That
particular paragraph is very old (version 1.39.28 dates from *many*
years ago). I will update it to refer to "50GB or larger". I will also
correct the sentence about Bacula not being able to seek -- it in fact
does se
Hello,
> 23-Dec 18:47 DIR:xxx.yyy.zzz JobId 4: Error: Catalog error updating file
> digest. bdb.h:101 Update failed: affected_rows=0 for UPDATE File SET
> MD5='oGhRwHZ+y+mWb+fv9ppFrA' WHERE FileId=6148914691236517205
Also, I just noticed, 6148914691236517205 is 0x in Hex, which
is
On 12/24/2015 02:16 PM, Kern Sibbald wrote:
> Well, 4GB Volume size seems very small to me. I would start with
> something like 50GB and possibly make them bigger if there are more than
> a few thousand Volumes.
The manual is sometimes ambiguous about things like a good Volume size.
I chose 4GB b
Well, 4GB Volume size seems very small to me. I would start with
something like 50GB and possibly make them bigger if there are more than
a few thousand Volumes.
The error:
23-Dec 18:47 DIR:xxx.yyy.zzz JobId 4: Error: Catalog error updating file
digest. bdb.h:101 Update failed: affected_rows=0 f
Hello,
I'm a new user who has just set up bacula on a couple of
machines. During my initial tests, things were working fine, but
when I went into production I started seeing these errors. These
errors only appear to happen when a backup is big enough to cross
volume size boundaries. (I keep my vol
13 matches
Mail list logo
