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 for UPDATE File SET
MD5='oGhRwHZ+y+mWb+fv9ppFrA' WHERE FileId=6148914691236517205

Is not something that is "fatal", because having the MD5 in the catalog
is not critical, but it indicates a real problem.  The FileId is clearly
wrong, and possibly indicates a bad build or some strange bug due to an
unusual configuration.  I would be interested to know if you know how to
reproduce it.

Best regards,
Kern

On 12/24/2015 02:41 AM, 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 backup is big enough to cross
> volume size boundaries. (I keep my volumes at 4GB in size and I do
> disk backups only with Full/Differential/Incremental pools).
>
> I poked the list a little with the search engine about this error
> but was unsuccessful at finding something similar.
>
> 23-Dec 18:46 SD-0:xxx.yyy.zzz JobId 4: End of medium on Volume
> "FullBackup-0005" Bytes=3,999,937,436 Blocks=62,003 at 23-Dec-2015 18:46.
> 23-Dec 18:46 DIR:xxx.yyy.zzz JobId 4: Created new Volume="FullBackup-0006",
> Pool="FullBackup", MediaType="Disk-0" in catalog.
> 23-Dec 18:46 SD-0:xxx.yyy.zzz JobId 4: Labeled new Volume "FullBackup-0006" on
> file device "Device-Disk-0" (/backups/bacula-archive/disk-0).
> 23-Dec 18:46 SD-0:xxx.yyy.zzz JobId 4: Wrote label to prelabeled Volume
> "FullBackup-0006" on file device "Device-Disk-0" 
> (/backups/bacula-archive/disk-0)
> 23-Dec 18:46 SD-0:xxx.yyy.zzz JobId 4: New volume "FullBackup-0006" mounted on
> device "Device-Disk-0" (/backups/bacula-archive/disk-0) at 23-Dec-2015 18:46.
> 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
> 23-Dec 18:50 SD-0:xxx.yyy.zzz JobId 4: End of medium on Volume
> "FullBackup-0006" Bytes=3,999,937,664 Blocks=62,003 at 23-Dec-2015 18:50.
> 23-Dec 18:50 DIR:xxx.yyy.zzz JobId 4: Created new Volume="FullBackup-0007",
> Pool="FullBackup", MediaType="Disk-0" in catalog.
> 23-Dec 18:50 SD-0:xxx.yyy.zzz JobId 4: Labeled new Volume "FullBackup-0007" on
> file device "Device-Disk-0" (/backups/bacula-archive/disk-0).
> 23-Dec 18:50 SD-0:xxx.yyy.zzz JobId 4: Wrote label to prelabeled Volume
> "FullBackup-0007" on file device "Device-Disk-0" 
> (/backups/bacula-archive/disk-0)
> 23-Dec 18:50 SD-0:xxx.yyy.zzz JobId 4: New volume "FullBackup-0007" mounted on
> device "Device-Disk-0" (/backups/bacula-archive/disk-0) at 23-Dec-2015 18:50.
> 23-Dec 18:50 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='Hh8yl5gZPABvG9+8Ow50gQ' WHERE FileId=6148914691236517205
>
> The above produced an "OK -- with warnings" result of the backup and I was 
> able
> to restore things out of it.
>
> Something which might be relevant is that when I read this portion
> of the manual:
>
> "However, one additional point is that in the case that no match
> was found, Bacula will use the options found in the last Options
> resource. As a consequence, if you want a particular set of ``default''
> options, you should put them in an Options resource after any other
> Options. "
>
> I fixed all of my file sets to have a last Options block in which I put the
> signature=MD5 and compression=GZIP1 specification because otherwise there
> were cases where compression didn't happen and such if they were first.
>
> Does anyone know what this is or how I can fix it?
>
> Thank you!
>
> -pete
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>


------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to