SBS 2011 - Migrated from SBS 2003 - High CPU Use - microsoft.exchange.search.exsearch.exe

Hi All

On my Migrated SBS2011 Server
microsoft.exchange.search.exsearch.exe
Is consistently stuck @ 25 % CPU
What is this services and why would it be stuck @ 25%
LVL 2
it-proAsked:
Who is Participating?
 
Andrew OakeleyConsultantCommented:
If it does not come good you may like to considre rebuilding the indexes


1.Start the Exchange Management Shell.

2.Remove the index directories that are associated with specified mailbox databases:its in the same location as you storage group
Run this command from powershell
ResetSearchIndex.ps1 [-force]  <dbname> [<dbname>]
3.Remove the index directories that are associated with all mailbox databases:
ResetSearchIndex.ps1 [-force] -all

taken from
http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26203738.html
0
 
Andrew OakeleyConsultantCommented:
I have found this to be true on one of the two live migrations I have done. It seemed to settle down soon. I believe it is just indexing all the email you have just imported.

though this thread incicates if you have been playing around with databases and have one that is not mounted you may also see this behaviour http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/a0b9ddc5-80d7-4724-96f6-3797ee92b1e0/ 
0
 
it-proAuthor Commented:
I think ill give it a couple of days.. And then see.
We moved approx 24 GB of mailboxes on Sat, now its Monday Night.
I also notice the server is taking 96% of the available 12GB (Physical), is this what you are seeing at well with SBS 2011 ?
microsoft.exchange.search.exsearch.exe is only taking 10,704kb and not increasing which is good.
Store.exe is at 4.7 GB is that Normal ?
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
Andrew OakeleyConsultantCommented:
See attached for server with 75GB mailbox store and 15GB RAM Process
0
 
it-proAuthor Commented:
Does that RAM usage not seem a wee bit excess ?, is it because Exchange 2010 is based around RAM ?
0
 
Andrew OakeleyConsultantCommented:
Exchange will use as much RAM as it can. This is by design. It will be "nice" to other processes and give it back if it is needed. It just does not let any RAM sit idle if it can help it.

you can read a bit more about it here: http://eightwone.com/2010/03/25/limiting-exchange-2010-database-cache/

> I received a question from someone implementing Exchange 2010 who was surprised to see Exchange taking up all available memory. This is because in Exchange 2010 (2007 as well) memory allocation is dynamic, contrary to Exchange 2003 and earlier versions where, depending on the situation, you had to fiddle around with boot.ini switches like /3GB to make memory available to Exchange. Also, the maximum database cache size was limited in Exchange 2003 to around 1.2 GB due to virtual address space limitations (see MSKB 815372).

>The main reason Exchange 2007/2010 claims memory for its database cache is performance. The more memory is assigned to the database cache, the less I/O’s are generated because things can be dealt with in-memory and the database cache becomes more effective. When a certain amount of transactions has been reached, changes will be physically written to databases (so far they’ve been stored in-memory and written to transaction logs). This limit is called the log checkpoint depth target.
0
 
it-proAuthor Commented:
Thanks..

Will check back tomorrow regarding microsoft.exchange.search.exsearch.exe
Will give it time to settle down.
0
 
Cliff GaliherCommented:
Both the memory usage and the CPU usage is normal (just confirming what others have written.) the memory usage will stay high as this is how exchange 2010 optimizes performance. CPU usage will drop as exchange catalogs, indexes, and sorts the imported migration email. It takes some time to drop, as the process is intentionally throttled (or it'd be taking 100%) to leave resources for other process spikes.

-Cliff
0
 
Cliff GaliherCommented:
I would only do such a thing if the process appears to be running away. As this is a fresh migration, I doubt that is the case. Deleting and forcing a reindex will just restart the process, prolonging completion.

-Cliff
0
 
Andrew OakeleyConsultantCommented:
Agreed Cliff. Thanks for your insight.
0
 
TekyguyCommented:
And this is why we use ECC ram for servers...  Funny how in the past 'we' would complain that all the ram is not being used.  Now 'we' complain that most of the ram is bing used. :D
0
 
it-proAuthor Commented:
FYI just checked this Server and microsoft.exchange.search.exsearch.exe is still taking 25% CPU looks 5,640 k
Memory has dropped from first post
Any further ideas cannot believe it takes this long ?
0
 
Andrew OakeleyConsultantCommented:
I have never had it take that long... but will defer to Cliff before recomending anything else..... it might just be slow...

What is the hardware spec of the server?
0
 
it-proAuthor Commented:
Spoke to a another guy about this and he seems to think it can take days, to settle down.
I have also now started importing a large amount into the Personal Archives could not hold back it was the whole reason we upgraded to SBS 2011, so no doubt it is having to index all that data as well.
we have created a second store for the archive data as per SP1 feature.
It must be noted the 2010 Archive feature is very good, I am looking forward to being rid of .PST's at this site they are a real pain..
0
 
Andrew OakeleyConsultantCommented:
On a side note - Just remember that the online archive only works with Outlook from Pro Plus... will not work with OEM home and business or similar.....
0
 
it-proAuthor Commented:
I'm using Outlook 2010 Retail (Brought 5 copies) which is supported, I checked and Double checked as I know it's a gotcha thing, it's very stilly that only certain versions of outlook 2010 work with archiving.
Also Got 5 Exterprise Cals to make sure we are covered with MS.
0
 
it-proAuthor Commented:
2 weeks on and microsoft.exchange.search.exsearch.exe is still taking 25%
This does not seem to be causing an issue but I would like to confirm if anybody else is seeing this on there SBS 2011 sites.
Which service would this be related to, should I try restart or re-index ? or just leave it ?
0
 
Cliff GaliherCommented:
If your server has a quad core processor, thisnis wha I'd expect with a runaway process. Search is pegging a core thus the overall 25%. make a backup, then reset the indexes.

-Cliff
0
 
Andrew OakeleyConsultantCommented:

> Which service would this be related to
Microsoft Exchange Search Indexer

Though I thought we had already established that....

I would also suggest deleting and rebuilding the index. None of my SBS2011 servers have had this go on for this long...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.