It was during the Exchange training (you would have taken it too) about server migration. It's in that area of the course and won't fit in this small space. I think that section is what you need to go back and review.
A client recently had a failure with their mail database. The database was repaired using the ESEutil and isinteg utilities to get the database back into a clean state. (exchange 2007 SP1)
However after the above processes there have been a number of quirks that have appeared, for instance:
some users could not open up mail in another users shared mailbox
some users had all mail from different mailbox folders deleted that were from a date prior to the database going down
One user could not see any new mail in cached mode in outlook.
Generally a lot of niggly issues. My thought is that the database still has a number of small corruptions and I would like to create a new mailbox database and move the users mail across to this new database.
Office tech info:
Client using outlook 2003 sp3 and outlook 2010. Total mail database size = 15 GB.
What would be the best method of achieving a fresh database and moving old mail across?
I have considered moving the mailbox database and log files to another location and then getting exchange to create a new database. I would then look to create a recovery storage group and put the old database files and logs in the appropriate folder and move mail form the old database to the new one.
The other method I have looked at is to export all mail to PST's and then reimport it into a fresh database.
I have not used the recovery storage group before so your opinions and advice to achieve my goal would be much appreciated.