01-07-2009 01:35 AM
Hello all,
To 'clean up' exchangestores, we want to move all mailboxes from 1 store to another, delete the store, recreate it, then move the mailboxes back. As this is an action that probably will not complete in one day, I am wondering about the archving. I have found the documents regarding moving a mailbox, but those are targeted at moving a mailbox once. We will temporarily move a mailbox. When the action is finished, the mailbox will be moved back to it's original location.
We have 3 exchangeclusters. MBX archving servers do 1 server per cluster (Cluster1, Cluster11, Cluster111, where ev1 archives exch1, exch11 and exch111, ev2 archives exch2, exch12, exch112 etc) If I move the mailboxes from exch1 to exch11 and exch111, and later move them back to exch1, would i still get dubble entries in the ExchangeMailboxentry tabel? Should I set the SynchInMigrationMode key anyway? Or, would this pose no problems?
I think I need to set the registry key, but I am not sure. thanks.
Gertjan
Solved! Go to Solution.
01-08-2009 01:37 AM
Hi Gertjan
There is a bp article about mailbox moves.
I would stop the archiving tasks until you are finished with the exchange clean-up, if this is possible.
After you moved the mailboxes back, everything would be the same as before, so that should go very smooth.
01-07-2009 02:50 PM
01-07-2009 11:22 PM
Hi Paul,
We're talking average 1500 mbx's per store. Is it really necessary to follow the procedure as outlined? What are the risks if I don't? As far as I am aware, there seems to be no break in functionality, and apparently, there are no double entries in the table (believe it is ExchangeMailboxEntry in EVDirectory db? )
(no entries marked %MARKED% as far as I can see)
Thanks again
01-08-2009 01:37 AM
Hi Gertjan
There is a bp article about mailbox moves.
I would stop the archiving tasks until you are finished with the exchange clean-up, if this is possible.
After you moved the mailboxes back, everything would be the same as before, so that should go very smooth.