On 29.6.2015 16.47, tballin wrote:

Hi

I try to migrate from am mysql db to postgres. I am failing to import
thy mysql dump into the postrgres :
(according to these instructions:
http://www.bacula.org/7.0.x-manuals/en/main/Installing_Configuring_Post.html#SECTION004150000000000000000
bacula 7.1 / CentOS )
lots of
psql:/tmp/bacula-backup2pg.sql:46485014: invalid command
\'].sublime-snippet');
psql:/tmp/bacula-backup2pg.sql:46485018: invalid command
\'].sublime-snippet');
psql:/tmp/bacula-backup2pg.sql:46485025: invalid command
\'].sublime-snippet');
psql:/tmp/bacula-backup2pg.sql:46485027: invalid command
\'].sublime-snippet');
psql:/tmp/bacula-backup2pg.sql:46485042: invalid command
\'].sublime-snippet');
psql:/tmp/bacula-backup2pg.sql:46485194: invalid command
\'-Marker.sublime-snippet');
psql:/tmp/bacula-backup2pg.sql:62088431: out of memory

The point is - I do not need really the big file table (33M+ rows) since
we will start the migration - or better finish the migration with a new
full backup and could keep the old mysql until no longer needed.

But I would like to keep as much information as possible. e.g. the
volume labels/pools. Is there a easy way to just do that?

If any one had a good Idea or documentation how to do that I would
depreciate any help.

Timo

I think it is not possible to run the dump (created by mysqldump) as is.

There are several database conversion tools available for this. That 
said, I have never yet done this... it is in my mind to do, but have not 
yet had the time.