Keith,
Did you check this?
It's for MySQL, but for PgSQL I think would be the same logic.
Fixing table 'bacula.batch' doesn't exist
Newer versions of Bacula create a temporary working table in order to do batch
inserts, which can greatly speed up inserting attributes into the catalog.
Unfortunately, if the MySQL connection gets dropped for any reason (such as a
timeout) the temporary table goes away. If you're seeing these problems, there
are two workarounds.
The simplest one is to turn off batch inserts. This will revert to the older,
somewhat slower behavior, but it should avoid this particular glitch.
The other option is to alter the MySQL timeouts to a sufficiently long value
that the connection never gets yanked out from under Bacula. For example,
adding these two lines to your my.cnf file in the [mysqld] block will set the
relevant timeouts to 8 days.
wait_timeout=691200
interactive_timeout=691200
Future versions of MySQL will automatically set the timeout values, which
should prevent the problem without requiring changing the global MySQL timeout
values.
Source: http://wiki.bacula.org/doku.php?id=faq
Regards,
=========================================================================
Heitor Medrado de Faria
Faltam poucos dias - Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 2021-8260 | 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: [email protected]
==========================================================================
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
