Migrating Mailboxes from ims5.2 to 6.2

Question

Hello again,
Our test/migration 6.2 system is at the following:
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)
Testing an in-place migration. Have done a small test using imsbackup/imsrestore
with just a few users on a different box. Went through the upgrade scripts, restored
the users, and that worked okay.
My testing now is different. We cloned one of our 300G mail partitions from the
current 5.2 production system. It contains close to 5000 accts and is about 95G of actual
data. I attached and mounted the clone on our test system and can see the 5.2 mail data.
Went through the upgrade scripts (mta, configutil, mboxlistdb). I had previously copied
the 5.2 mbox/config information to the 6.2 system and used as input.
The scripts ran with no problems. The problem I am having is that once I start up 'stored'
so I can check the database, the *.db files aren't what they used to be - looks like the
originals moved to a directory called 'removed'. Now, it's like a brand new db.
The upgrade changes introduced several partitions, of which only two would actually be
there (the primary & the one 300G clone). I am wondering if stored didn't like something
about the physical store and re-initialized.
At this point, I went ahead and ran 'reconstruct -m', which ran really fast for the 95G
of actual data that was there, so that's encouraging. The mailbox db looks good.
Would like to know why the db info would disappear. Is there a startup log that
may provide insight to this? Would like to know what I did wrong.
Thanks for your input.
Keith

Answer 1

kmrnm10 wrote:
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)You should be patching up to the latest 6.2 (118207-63) prior to attempting the migration - there were a few bugs fixed with the UpgradeMsg5toMsg6.pl migration script with the later patch.
Also you may want to consider going straight to 6.3 (once again make sure you use the latest patch-level).
http://www.sun.com/bigadmin/hubs/comms/files/ms52-ms6-upgrade.html
The scripts ran with no problems. The problem I am having is that once I start up 'stored'
so I can check the database, the *.db files aren't what they used to be - looks like the
originals moved to a directory called 'removed'. Now, it's like a brand new db.Did you copy the entire store mailbox directory or just the *.db files?
The upgrade changes introduced several partitions, of which only two would actually be
there (the primary & the one 300G clone). Not quite sure what you mean by this. What were the actual changes?
I am wondering if stored didn't like something
about the physical store and re-initialized.Entirely possible. Review the default log file (/opt/SUNWmsgsr/log/default).
At this point, I went ahead and ran 'reconstruct -m', which ran really fast for the 95G
of actual data that was there, so that's encouraging. The mailbox db looks good.Worst case scenario you can use this method. Although this method won't give you the same results as the on-disk copies of the data (store.* files) aren't necessarily 100% up-to-date so users may notice some read/deleted email comes back.
Would like to know why the db info would disappear. Is there a startup log that
may provide insight to this? Would like to know what I did wrong.default log file as mentioned previously.
Regards,
Shane.