Hi folks,
I'm trying (for educational purposes) to migrate an existing bacula
catalog to use with a postgres backend (mariadb10 / postgresql12,
Ubuntu 20.04).
I've imported the bacula catalog using pgloader and this config:
LOAD DATABASE
FROM mysql://bacula:XXXXXXXXXXXXX@localhost/bacula
INTO postgresql://bacula:XXXXXXXXX@localhost/bacula
WITH include drop, create tables, no truncate,
create indexes, reset sequences, foreign keys;
The import works fine, however when connecting to bacula 13.0.1 (compiled
from source for postgres use) I get the following message in bconsole:
25-Aug 14:08 zif-dir JobId 0: Warning: Encoding error for database
"bacula". Wanted SQL_ASCII, got UTF8
Most web searches are ancient so I'm wondering if the ASCII bit is
still a valid requirement? In bconsole, the volume, job and client
names all look quite funny when doing a stat dir and the volume isn't
found when I run a backup job (probably due to this encoding issue).
I've also checked the configure script for any options related to the
encoding, but could not find anything, also I've used the provided
create_postgres_database script to (hopefully) initialize the catalog
db in postgres with the correct encoding.
Is there anything I'm doing wrong? Please excuse my ignorance, as I'm
only now getting my feet wet with postgres especially w/r to the
mariadb import...
Thanks in advance & all the best,
Uwe
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
