Hi, I'm running a Bacula director and a File client on a Samba server, and I'm doing full and incremental backups to another machine running a Storage daemon (just writing the Volumes to disk). Both
Author: "John Drescher" <drescherjm AT gmail DOT com>
Date: Tue, 9 Sep 2008 14:59:55 -0400
Not sure of this since I do not use bat at work. It always times out on operations. I assume 46 clients, 12400 jobs, and 4.7 million files are too much for it to handle. I assume that a lot of these
John Drescher wrote: On Tue, Sep 9, 2008 at 2:44 PM, Alan Garrison <alang AT cronosys DOT com> wrote: Skimming a pg_dump of the bacula database shows nowhere near 162,000 file records. The job comple
Hi, Might also be related to PostgreSQL's handling of non-ASCII text data, the character set of the columns in question, and so on. Dan knows more about this :-) Without actually verification I belie
09.09.2008 21:07, Alan Garrison wrote: John Drescher wrote: On Tue, Sep 9, 2008 at 2:44 PM, Alan Garrison <alang AT cronosys DOT com> <mailto:alang AT cronosys DOT com> wrote: Skimming a pg_dump of t
Author: Ralf Gross <Ralf-Lists AT ralfgross DOT de>
Date: Tue, 9 Sep 2008 22:56:04 +0200
Alan Garrison schrieb: And that results in a fail of the whole batch insert and therefor all information of the job is silently lost. It's more or less a known problem. http://article.gmane.org/gmane
Ralf Gross wrote: Alan Garrison schrieb: Well the bacula database is set up for UTF8 instead of SQL_ASCII. Poking around the postgres log I see at the time when a job started: 2008-09-09 09:52:58 EDT