Application Development Software

We're migrating 250,000 mailboxes from iMS 5.2 on HP-UX to
JSMS 6.2 on Solaris 10. Our Sun consultant recommended that we copy
the user mailboxes and mboxlist db files to the new server, and
then run ims_db_upgrade. Because each user's uid is changing
to an immutable id, we also have to run mboxutil to rename the
migrated mailboxes. Mailboxes reside in a single partition on
both servers. We plan to split them into two partitions after
the migration.

My testing has uncovered that some user folders appear in
the mboxlist db files but are missing from the mailboxes. I've
addressed this by running ``reconstruct -m'' on 6.2
before renaming the mailboxes, but I'm concerned that some data
may be lost.

Second, an ``unreadable log'' error appears in the 6.2 default log when I
start ims the first time:

[08/Aug/2007:16:28:04 -0700] vmpm1 stored[5670]: Store Warning: stored: Sun Java(tm) System Messaging Server STORE 6.2-3.04 (built Jul 15 2005) starting up
[08/Aug/2007:16:28:04 -0700] vmpm1 stored[5670]: Store Critical: Mailbox database error: Ignoring log file: /mnt/mail_system/products/mail/data/store/mboxlist/log.0000000112: unreadable log version 2
[08/Aug/2007:16:28:06 -0700] vmpm1 imsched[5674]: General Notice: starting up

###
Migration steps:

On the 5.2 server:

1. stop-msg (as root)
2. Take snapshot of filesystem containing .../server5/msg-mymail/store
3. start-msg (as root)
4. Copy the ./mboxlist and ./partition/primary/=user directories
from the snapshot to temp locations on the 6.2 server using rsync.

On the 6.2 server:

1. stop-msg (as root)
2. Copy =user from temp location to /mnt/primary_store/=user
3. Copy mboxlist from temp location to /mnt/mail_system/products/mail/data/store
4. ims_db_upgrade (as root)
5. start-msg (as root)
6. reconstruct -m
7. Rename user mailboxes: mboxutil -r -f mboxutil_renames

###
Some questions:
1. Does copying from a snapshot taken from 5.2 while it's shut
down ensure that the mboxlist/*.db files are consistent with
the user mailboxes themselves?

2. What function do the mboxlist/log.* files have? If they're
used for journaling or caching database updates, can we
dispense with copying them or ignore the ``unreadable log''
errors as seen in the second log line above?

3. Do the inconsistencies we see on the 6.2 side when we run
reconstruct -m indicate trouble? E.g.: a user's folders appear
in the database but not in their store directory.

4. Is running ``reconstruct -m'' prior to renaming the
mailboxes a good idea? If we do this, would it be more
advantageous to copy and convert the .db files, or delete
then so reconstruct -m can rebuild them from scratch.

5. Is our migration procedure as described above missing anything
important?

##
Versions:
On the 5.2 server, ``imsimta version'' returns:

iPlanet Messaging Server 5.2 HotFix 2.12 (built May 22 2006)
libimta.so 5.2 HotFix 2.12 (built 15:13:17, May 22 2006)
HP-UX mailserv B.11.11 U 9000/800 1683737817 unlimited-user license

On the 6.2 server, it returns:

Sun Java(tm) System Messaging Server 6.2-3.04 (built Jul 15 2005)
libimta.so 6.2-3.04 (built 01:43:03, Jul 15 2005)
SunOS vmpm1 5.10 Generic_118833-36 sun4u sparc SUNW,Sun-Fire-V490

Please let me know if we can furnish any additional information.
Thanks.

David Pelinka