AblSysadmin
asked on
Exchange 2010 Mailbox Server
Hi,
My one MBX server is running excessively high on CPU and the store.exe and msexchangerpl.exe is using up the most resources. I have done some reading and from what i can pickup is that i have to rebuild the indexes: http://technet.microsoft.com/en-us/library/aa995966%28EXCHG.80%29.aspx . Should i do this once a month? is this an automatic process that runs or must it be run manually. Also what best practice maintenance and scripts should be run on a regular basis.
Any reading that can be sent my way on this would be a huge help.
Thanks,
Walter
My one MBX server is running excessively high on CPU and the store.exe and msexchangerpl.exe is using up the most resources. I have done some reading and from what i can pickup is that i have to rebuild the indexes: http://technet.microsoft.com/en-us/library/aa995966%28EXCHG.80%29.aspx . Should i do this once a month? is this an automatic process that runs or must it be run manually. Also what best practice maintenance and scripts should be run on a regular basis.
Any reading that can be sent my way on this would be a huge help.
Thanks,
Walter
ASKER
Exchange 2010 SP 1 Rollup 5 Installed
ASKER
hi, updated to RU 6 last night
I would suggest running Exchange Best Practice Analyzer when the process hit 100% cpu utilization and see what it reports. Its a pretty good tool.
Regards,
Navdeep [v-2nas]
Regards,
Navdeep [v-2nas]
ASKER
Ran it and it is complaining about allot of things that do not apply to the server from which i run the check
Can you explain more ? Upload the report as well.
ASKER
Some of the errors have been addressed:
LDAP is now installed.
the temp/TMP folder has been moved long ago in environment variable and within the registry. dont know why this is getting picked up.
I ran this BPA from the MEX1 server which has just the mailbox server role installed.
I have a few perlog errors listed and a few in the event log. ID 106. save to ignore? please advise. also i have stopped the "microsoft Search(Exchange) and the Search Indexer service as this is causing issues on the cpu. the db is currently in a crawling state. i will start the services again for the server to finish the indexing.
ExBPA.A.201202140929391194.data.zip
LDAP is now installed.
the temp/TMP folder has been moved long ago in environment variable and within the registry. dont know why this is getting picked up.
I ran this BPA from the MEX1 server which has just the mailbox server role installed.
I have a few perlog errors listed and a few in the event log. ID 106. save to ignore? please advise. also i have stopped the "microsoft Search(Exchange) and the Search Indexer service as this is causing issues on the cpu. the db is currently in a crawling state. i will start the services again for the server to finish the indexing.
ExBPA.A.201202140929391194.data.zip
store.exe and msexchangerpl.exe consumes a lot of memory so its fine, are you facing some issues because of this?? or this is the only concern
Why is Exchange Store.exe so RAM hungry?
http://blogs.technet.com/b/exchange/archive/2004/08/02/206012.aspx
I understand that it applies to Exchange 20003, but things have not changed much since then as far as the memory utilization is concerned with store.exe
Why is Exchange Store.exe so RAM hungry?
http://blogs.technet.com/b/exchange/archive/2004/08/02/206012.aspx
I understand that it applies to Exchange 20003, but things have not changed much since then as far as the memory utilization is concerned with store.exe
Exchange 2010 does not need tasks like rebuilding indexes or manual defragmentation to be run on regular basis. The only important thing that needs to be done is backup.
For the most of other things is taken care automatically. But as always there is some possibility to go something wrong so it is important to monitor if everything is working fine.
Here are some things to regularly check:
http://www.windowsitpro.com/article/systems-administrator/regular-maintenance-tasks-for-exchange
http://blair-muller.blogspot.com/2011/07/administrative-and-maintenance-tasks.html
One of most useful tools is EXBPA. On my check list are also SMTP and agent logs, blacklist check....
About you current problem:
I had a similar cases when high CPU usage on store.exe and also some other exchange processes were caused by anti-virus program. In same cases I was able to "solve" the problem disabling VSAPI scanning and leaving only SMTP transport agent scan on.
Please make sure that you have also all needed exclusions selected on file level AV scanning:
http://technet.microsoft.com/en-us/library/bb332342.aspx
For the most of other things is taken care automatically. But as always there is some possibility to go something wrong so it is important to monitor if everything is working fine.
Here are some things to regularly check:
http://www.windowsitpro.com/article/systems-administrator/regular-maintenance-tasks-for-exchange
http://blair-muller.blogspot.com/2011/07/administrative-and-maintenance-tasks.html
One of most useful tools is EXBPA. On my check list are also SMTP and agent logs, blacklist check....
About you current problem:
I had a similar cases when high CPU usage on store.exe and also some other exchange processes were caused by anti-virus program. In same cases I was able to "solve" the problem disabling VSAPI scanning and leaving only SMTP transport agent scan on.
Please make sure that you have also all needed exclusions selected on file level AV scanning:
http://technet.microsoft.com/en-us/library/bb332342.aspx
ASKER
hi, Checked everything and all seems in order. I have stopped the service and will setup a auto stop and start job to stop the service before production hours(07h00) and start it again after (21h00). the servers seem more stable now. backups are done every night(full backups).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The problem you are referring is related to 2007 exchange as per given below article,
http://support.microsoft.com/kb/925252