locked
False Database Performance Alerts RRS feed

  • Question

  • I am getting the alerts below. I have checked all database and every indication is that they are healthy.

     

    A performance problem impacted a database copy's storage; client performance may be impacted. Alert Description Source: Database Copy Integrity: Suppression (E_1) - MB01 (Mailbox) - PA-EX1 At '2/22/2011 9:29:15 AM' the copy of database 'E1_8' on this server appears to be experiencing performance issues, possibly as a result of storage failure. Consult the event log on the server for other storage and "ExchangeStoreDb" events for more specific information about the failure. Recovery was not attempted.

    Has anyone else experienced this issue and can you relay the source of the problem and possible resolution?


    Regards, Rob
    Friday, February 25, 2011 5:14 PM

Answers

  • The alert can appear if index catalog has been corrupted

    Please try to reseed the index catalog for the problematic database from the source that hasn’t experienced this symptom

    Reseed the Search Catalog

    If the method above doesn’t work, please try to rebuild the index on the source, and then reseed again

    1.      Logon to the node that has the problematic database and index

    2.      Launch EMS, and then change to the following directory where the ResetSearchIndex.ps1 script is located

    <drive> :\Program Files\Microsoft\Exchange Server\Scripts

    3.      Suspend the replication from active node MBX1 to the target passive node MBX2

    Suspend-MailboxDatabaseCopy -Identity DB1\MBX2

    4.      Run the following script to remove the index directories that are associated with the specified mailbox database with the source MBX1

    ResetSearchIndex.ps1 -force MBX1

    5.      Verify that the rebuilding of the index has completed by adding the “MSExchange Search Indices\Full Crawl Mode Status” counter to Perfmon before doing the ResetSearchIndex. This counter will be 0 before running ResetSearchIndex and go to 1 during the full crawl and then back to 0 after ResetSearchIndex finishes

    Notes: Please monitor the event 109 and 110 in the application log

    6.      Follow the link above to reseed the index catalog

    7.      Resume the replication

    Resume-MailboxDatabaseCopy -Identity DB1\MBX2

    James Luo

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by RobBrown Wednesday, March 2, 2011 2:47 AM
    Monday, February 28, 2011 3:11 AM

All replies

  • The alert can appear if index catalog has been corrupted

    Please try to reseed the index catalog for the problematic database from the source that hasn’t experienced this symptom

    Reseed the Search Catalog

    If the method above doesn’t work, please try to rebuild the index on the source, and then reseed again

    1.      Logon to the node that has the problematic database and index

    2.      Launch EMS, and then change to the following directory where the ResetSearchIndex.ps1 script is located

    <drive> :\Program Files\Microsoft\Exchange Server\Scripts

    3.      Suspend the replication from active node MBX1 to the target passive node MBX2

    Suspend-MailboxDatabaseCopy -Identity DB1\MBX2

    4.      Run the following script to remove the index directories that are associated with the specified mailbox database with the source MBX1

    ResetSearchIndex.ps1 -force MBX1

    5.      Verify that the rebuilding of the index has completed by adding the “MSExchange Search Indices\Full Crawl Mode Status” counter to Perfmon before doing the ResetSearchIndex. This counter will be 0 before running ResetSearchIndex and go to 1 during the full crawl and then back to 0 after ResetSearchIndex finishes

    Notes: Please monitor the event 109 and 110 in the application log

    6.      Follow the link above to reseed the index catalog

    7.      Resume the replication

    Resume-MailboxDatabaseCopy -Identity DB1\MBX2

    James Luo

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by RobBrown Wednesday, March 2, 2011 2:47 AM
    Monday, February 28, 2011 3:11 AM
  • I'm having the same issue.  The migration to E2K10 at this particular site is in-progress, is co-existing with E2003, and DAGs are not configured yet.  Plan to hurry up and get the DAGs setup, but this does not appear to be a false alarm!

     

    Friday, September 2, 2011 5:58 PM