ejabberd - Comments for "Migration from cluster to non cluster and version to version"

Please excuse the stupid question about the schema

dennypage — Thu, 26 Mar 2009 02:41:01 +0000

I'm editing the file by hand and it is working.

Thanks all.

Format for the dump file?

dennypage — Wed, 25 Mar 2009 19:58:29 +0000

I did try a few approaches at this, however I wasn't ever able to get the server to load the resulting file.

Part of the problem is that I was guessing about the format of the roster entries in the dump file. Is this documented anywhere?

Thanks,

Denny

You can try to dump to text file

mfoss — Wed, 25 Mar 2009 11:02:06 +0000

dennypage wrote:

So, the big problem that I have left is how to deal with the user data migration issue resulting from the renaming of the virtual host from "jabber.example.org" to "example.org"

So far, I haven't had much success editing the Mnesia database using a hex editor :-)

Has anyone else faced this issue? Any suggestions?

If you have a reasonable small database, instead of 'backup' the database to a binary file, you can 'dump' the database to a text file. After you edit the file, you can 'load' the text file in another ejabberd installation.

Remember that, if your users have contacts in other remote Jabber servers, such contacts will not be aware of the domain change.

Progress

dennypage — Thu, 19 Mar 2009 22:35:44 +0000

Looks like the convert.erl will end up dropping nodes that are not chosen for rename, so it looks like this part is easily solved.

So, the big problem that I have left is how to deal with the user data migration issue resulting from the renaming of the virtual host from "jabber.example.org" to "example.org"

So far, I haven't had much success editing the Mnesia database using a hex editor :-)

Has anyone else faced this issue? Any suggestions?

Thanks,

Denny