[jadmin] Migrating jabberd2 to ejabberd

[jeff Garner]

Depending on what database you are storing you information into, I am
sure that you can move the data from inside the database and then move
it into the new database for ejabberd.  I have done this for a jabberd2
to wildfire migration.  Basically it is merging table data into one
large table then pulling the matched data out into a new database
structure.  Not for the faint of heart, but a decent DBA should be able
to do it for you in a day.

On Thu, 2006-05-18 at 14:05 +1000, Trejkaz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi all.
> 
> I know that it's possible to migrate from jabberd2 to ejabberd by  
> migrating to jabberd14 first.  However, if we do this, then users'  
> privacy lists aren't preserved.  It looks like offline messages are  
> thrown out during the migration to jabberd14 as well.
> 
> Does anyone know of a way to perform a direct migration, so as not to  
> lose data?
> 
> TX
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (Darwin)
> 
> iD8DBQFEa/J0uMe8iwN+6nMRAkqSAJ9GFKjPIDEAg3SK5F/d4fk5zd191gCglvOU
> bDPyTZJ32xFJxvmRBAAd4r0=
> =0t7i
> -----END PGP SIGNATURE-----
> _______________________________________________
> jadmin mailing list
> jadmin at jabber.org
> http://mail.jabber.org/mailman/listinfo/jadmin
> FAQ: http://www.jabber.org/about/jadminfaq.shtml
> _______________________________________________
> 
> _____________________________________________________________________________
> Scanned by Sanmina-SCI eShield _____________________________________________________________________________
-- 
Jeff Garner
Network Administrator
Sanmina-SCI Corporation
Allen, Texas
469.675.2441 <office>
972.768.5913 <cell>
jeff.garner at sanmina-sci.com
        


_____________________________________________________________________________
Scanned by Sanmina-SCI eShield  _____________________________________________________________________________