Moving to a different arch

[Marco Colombo]

I'm planning to move one of our server from a Linux/SPARC box to an
Intel (well, AMD) based one. I'm also upgrading from 2.0.16 to 2.1.12.

I've copied both my configdirectory and partition-default to the new box.

When I start the daemon I get (I had to remove the db/__db.* files):

Mar 19 16:40:43 devel ctl_cyrusdb[4987]: recovering cyrus databases
Mar 19 16:40:43 devel ctl_cyrusdb[4987]: DBERROR db3: Ignoring log file: /home/from-backup/var/cyrus-imapd/db/log.0000000006: magic number 88090400, not 40988
Mar 19 16:40:43 devel ctl_cyrusdb[4987]: DBERROR db3: Invalid log file: log.0000000006: Invalid argument
Mar 19 16:40:43 devel ctl_cyrusdb[4987]: DBERROR db3: PANIC: Invalid argument
Mar 19 16:40:43 devel ctl_cyrusdb[4987]: DBERROR: critical database situation
Mar 19 16:40:43 devel master[4985]: process 4987 exited, status 75 

I have the strong feeling B-) that this is an endianess problem of
Berkeley db3 (see the magic). I guess I need to dump the database into
some text format on the sparc box and restore it on the intel one.
Now the questions:

1) is there a way to dump the db using cyrus utilities?
2) if I have to use db3 utils, can someone provide me with hints?
   (e.g., db_dump works on a file, which files should I dump? is it
   just the mailboxes.db file? - if so, I think ctl_mboxlist is
   all I need)
3) am I expected to run into other endianess problems? (cyrus.*
   files come into my mind).

I *think* I remember of being able to move across different archs
in the past (1.6.x), when the mailbox file was just a text file.
But maybe I'm wrong.

TIA,
.TM.
-- 
      ____/  ____/   /
     /      /       /			Marco Colombo
    ___/  ___  /   /		      Technical Manager
   /          /   /			 ESI s.r.l.
 _____/ _____/  _/		       Colombo at ESI.it