On Thu, Aug 25, 2022 at 06:57:46PM +0100, Martin Simmons wrote: > 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
Hi folks, thanks for your answers. No, I don't have any non-ascii chars in my client, job or volume names. By "looking funny" I mean that for instance the disk volume name "zif-full-0001" turns into \xverlongrowofrandomcharacters. Of course I could start with an empty catalog but it'd be nice to transfer the existing history to the postgres db which I guess would (or should, even) be possible somehow. In another experiment I migrated a mariadb django backend to postgresql on the same machine without any issues, it's just bacula that's acting up in this case. All the best, Uwe -- Uwe Schürkamp // email: <uwe.schuerk...@bertelsmann.de> _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
