Thanks!

chikoo — Tue, 15 Nov 2005 17:55:59 +0000

That sounds reasonable, thanks!

AFAIR, this procedure was

sander — Tue, 15 Nov 2005 17:22:00 +0000

AFAIR, this procedure was used on the jabber.ru server a long time ago (maybe 2 years). Try to talk to ermine or alexey as they will know more of it. You can do this via the mailing list or via the chatroom.

--
sander

What about this procedure?

mfoss — Tue, 15 Nov 2005 16:53:49 +0000

I've not tried the full procedure, but it sounds as if it can work:

On newhost, install ejabberd from scratch (same version of erlang and ejabberd as on oldhost).
Interconnect the two Erlang nodes. This deals mostly with cookies. Interconnecting Erlang Nodes
Setup both ejabberds as required to build a cluster. This deals mostly with setting Mnesia. ejabberd Guide.
Now you will have two ejabberd servers, both serving the same domain, but each one on a different host (and a different IP address, of course). Only of them has the correct DNS name. Both ejabberd nodes share the database, and changes are replicated instantly.
If you want to play: how to connect to the Jabber server that does not match DNS-name with Host-name? Most Jabber clients allow you to specify the machine to connect to, additionally to the Jabber server.
Modify the DNS so jabber.server.com points to the newhost, instead of the oldhost.
When the clients try to connect, they will connect directly to the newhost, instead of oldhost. The clients that are already connected to oldhost will not be disconnected, or moved magically.
You can wait one or two days, waiting for clients to connect to the newhost. Once there are only a few clients on oldhost, you can send them a massive message indicating that the server will be restarted. Stop oldhost forever.

ejabberd - Comments for "Migrating ejabberd from one ISP to another"

Thanks!

AFAIR, this procedure was

What about this procedure?