Hi folks, On Tue, Aug 30, 2022 at 03:53:47PM +0100, Martin Simmons wrote:
> Bacula will probably not work if pgloader created the schema. I think you > should do that part with Bacula's make_postgresql_tables script and configure > pgloader to keep that schema (i.e. the opposite of most of the "WITH" clauses > that you mentioned originally. > I've now used the bacula provided scripts to create the database, tables and grants and have reloaded the catalog using this gploader file: LOAD DATABASE FROM mysql://bacula:vampyre2020k@localhost/bacula INTO postgresql://bacula:vampyre2020k@localhost/bacula ; I didn't see any errors during the import and postgres-bacula (hehe :-)) starts up fine. When I issue a "stat dir" in bconsole I'm seeing the mangled volume names again though: cheduled Jobs: Level Type Pri Scheduled Job Name Volume =================================================================================== Incremental Backup 10 01-Sep-22 10:45 zif \x7a69662d696e63722d30303139 ==== The funny thing is that while the "job" name above looks fine, they're mangled too when I do a "list jobs", same goes for the pool, media and other objects that can be inspected using the "list" command. Bacula no longer complains about the non-ASCII database scheme so it seems like the script-created database survived the import by pgload intact. I'll also have a look at Wanderlei's scripts to see if they work fine. I managed to import the db using the "INSERT" filtering outlined above and omitting the JobStatus table, but then bacula was unable to find any appendable volumes when trying to run a test job. 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
