If you are using PostgreSQL, heads up. If not, ignore this. This email is based on a recent IRC conversation. Investigations are incomplete, but it's urgent enough to warrant a HEADS UP.
NOTE: It is documented that PostgreSQL should be used with SQL_ASCII: http://www.bacula.org/en/rel-manual/Installi_Configur_PostgreS.html Check your database: $ psql -l | grep bacula bacula | bacula | SQL_ASCII If you see UTF-8, not SQL_ASCII, read on, otherwise, ignore. If you are using UTF-8 encoding for your database, and you have non-UTF-8 filenames, I suspect that Bacula is silenting failing to properly include all the files in the Catalog. I suspect this may be a BATCH mode issue. Bacula should be raising an error, but it is not. The type of error raised by PostgreSQL is: postgres[15132]: [2-1] ERROR: invalid byte sequence for encoding "UTF8": 0xab See also: http://bugs.bacula.org/view.php?id=1017 More will follow as I find it out. Short term solution, untested: take down bacula-dir alter database bacula rename to baculaold; pg_dump baculaold > bacula.sql createdb -E SQL_ASCII -O bacula psql bacula < bacula.sql start bacula-dir -- Dan Langille -- http://www.langille.org/ ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
