On Dec 23, 2015, at 8:41 PM, Peter Keller <pkel...@sift.net> 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).
FWIW, I use 5GB Volumes, mostly because many of my backups are small. My thinking: if your average backup is 5GB, then that's a decent size for a volume. This means some of my bigger backups use 30 or 40 volumes, but that's no big deal to me. I have about 3000 volumes on disk for about 11TB on a FreeBSD 10.2 system using ZFS for the filesystem. I also use snapshots on a regular basis, just in case sometime accidentally wipes out files on disk. Backups are copied to tape on a regular basis. > 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 That is a very big number. 6,148,914,691,236,517,205 What database system are you using? I wonder what happened in order for this to occur. ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
