Friday, March 5, 2010

DAG Database Copy stays in Index crawling state, Server Seed Error Content Index is Crawling

when you try to move the active copy of the database from an Exhcange 2010 mailbox server to another server in the DAG you receive : Server Seed Error Content Index is Crawling
you might recieve this error also:
A server-side seed operation has failed. Error: An error occurred while performing the seed operation, which may indica te a problem with the source disk. Error: Failed to open a log truncation context to source <>. Hresult: 0xc 7ff1004. Error: Error returned from an ESE function call (-1305).
the database copy state is healthy in the GIU, how ever when you do Get-MailboxDatabaseCopyStatus you will get that copy status is crawling, to receive this error follow these steps:
Change to the following directory where the ResetSearchIndex.ps1 script is located:

:\Program Files\Microsoft\Exchange Server\Scripts

2. Suspend the mailboxdatabasecopy process from the active to the target passive node.

Suspend-MailboxDatabaseCopy -Identity DB1\MBX1

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

ResetSearchIndex.ps1 -force sourcemailbox

4. Verify that the rebuilding of the index has completed:

a. Before doing the ResetSearchIndex - add this counter to a live Perfmon: MSExchange Search Indices\Full Crawl Mode Status
b. This counter will be 0 before running ResetSearchIndex and go to 1 during the full crawl and then back to 0 after ResetSearchIndex finishes
c. You will receive MSExchange Search Indexer Event ID 109 when the full crawl begins.
d. You will receive MSExchange Search Indexer Event ID 110 when the full crawl ends.

5. Reseed the Search Catalog: Exchange 2010 Help
6. Reseed the content index catalog from a specific source source node is the active
node MBX2 and the passive node is MBX1:

Update-MailboxDatabaseCopy -Identity DB1\MBX1 -SourceServer MBX2 –CatalogOnly

7. Resume the mailboxdatabasecopy from the active node MBX2 to the passive node MBX1:

Resume-MailboxDatabaseCopy -Identity DB1\MBX1

1 comment:

SATU said...

Did that, successfuly
Update-MailboxDatabaseCopy -CatalogOnly
but passove db still Crawling status. any other suggestions?