>>>>> On Thu, 25 Aug 2022 14:25:30 +0200, Uwe Schuerkamp said: > > 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).
Do you have non-ASCII characters in your volume, job or client names? If not, then I don't see why the warning would cause them to look quite funny (whatever that means). __Martin _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
