Plan with care

mfoss — Wed, 25 Mar 2009 11:37:51 +0000

creiss wrote:

Using the internal db currently, and want to migrate to SQL (on the same host) now,

Notice: once you migrate from Mnesia to external, there isn't any way to go back to Mnesia.

The only good reasons I know for migrating from Mnesia storage to other external storage are: integration with previosly existing data; very tight integration with other systems that need continuous access to roster; very big server for which Mnesia is not recommended.

creiss wrote:

ideally by socket, not tcp.

I don't know what method is used by the Erlang's MySQL library used by ejabberd.

creiss wrote:

A "ejabberdctl ejabberd@alpha-labs.net backup ejabberd.db" gives me this:

This backups your Mnesia database, this is not intended for migration to SQL.

creiss wrote:

How would I go about porting data? I was thinking along the lines of dumping, changing to mysql, re-importing.

The migration from Mnesia to SQL involves:

Export some tables from Mnesia to SQL files:
- using manually ejd2odbc
- or using the command export2odbc included in mod_ctlextra. This module can be downloaded and compiled from ejabberd-modules SVN
If not yet done, install in ejabberd the files mysql*.beam.
Create the MySQL database and tables
Import the SQL files in the database
Configure ejabberd to use some ODBC modules instead of default ones

ok, I can export the database

creiss — Sun, 22 Mar 2009 18:46:01 +0000

ok,

I can export the database with dump/backup now, forgot "--node". And I was able to run a clean (no data) instance of ejabberd running MySQL. So it's working -- except the data.

I really desperatly need a pointer on how to export from amnesia and how to import into SQL..

Help!

-Chris

ejabberd - Comments for "2.x release: Going from internal to MySQL?"

Plan with care

ok, I can export the database