this could be related to my other post in database crawling .

today i found a user whose mailbox reside in that database where the content index is still crawling after more than a week. in this user's Outlook, everything is in a state of updating folders views. very slow. thinking this might be the cause why my database is crawling, i issued a migration job to move this user's mailbox to a healthy database.

while waiting for the migration to finish, is there anything else i could do? should i make a PST of all his emails (without using cache mode)?

Reno,

I wouldn't make a PST if the mailbox is in the middle of a move request.   I assume that you are moving the user to a more healthy database.  What is different about this DB compared to others in your organization?  

If all of your other databases are healthy/fast/content index is up to date, and this one DB is giving you headaches, I would move all users from the problem database, delete the problem database, and create a new DB.  Move users back to the new DB and see if performance is better.

Jeff

Reno,

I wouldn't make a PST if the mailbox is in the middle of a move request.   I assume that you are moving the user to a more healthy database.  What is different about this DB compared to others in your organization?  

If all of your other databases are healthy/fast/content index is up to date, and this one DB is giving you headaches, I would move all users from the problem database, delete the problem database, and create a new DB.  Move users back to the new DB and see if performance is better.

Jeff

• Marked as answer by Reno Mardo 21 hours 44 minutes ago

hi,

finished moving the problem mailbox to a healthy database. all his problems went away.

yes i think i should do that, move all existing mailboxes to a new database since I've already allowed enough time for crawling.