You should now see the Content Index State in a “healthy” status, which will allow you to fail your database over to other DAG members. Once these two services are stopped, you can delete or rename the index directory located with the database edb. Next, you will need to stop the “Microsoft Exchange Search” and “ Microsoft Exchange Search Host Controller” services. When the content index for a database has become corrupt, it will need to be rebuilt, or reseeded from another database copy in the DAG.
Add “Administrators” and “NetworkService” and give them each full control. In the comments of my blog post about repairing failed content indexes, Tipza asks: How do you monitor the status of this rebuild To answer the question, here’s an excerpt from the Exchange Server Troubleshooting Companion. Once created, ensure you have your ADUC Advanced Features view set, then open the security properties of the group.
get-mailboxdatabasecopystatus -server XYZAX123. Give it a minute and a new folder will be created and a new index will be built. Run Start-Service MSExchangeSearch if you are into Shell. Restart the Microsoft Exchange Search Indexer service. Delete this folder, which stores the corrupt index. Check the content index status for any failed database. Along with the database file, you will see a folder with CatalogData-random string as its name. get-mailboxdatabasecopystatus -server ABCAX123. Check the Database copy status on both the nodes. You will need to create an AD Group called “ContentSubmitters”. This post address an issue where the index status shows status failed with Exchange 2010 DAG. 1.Suspend the passive mailbox database copy 2.update the passive copy of the database from the active copy 3.Seed only catalog while updating.
The fix for this is simple, the Exchange 2013 setup /adprep command leaves out the creation of an AD group which is required for this index to function.
I had tried below: Update-MailboxDatabaseCopy -Identity DB1ServerName But it still failed. My second exchange database server has issue with Content Index Status - Failed. This won’t affect day to day operations, but it will prevent the database from failing over. Dear All, I have three exchange mailbox server running as DAG. With the Passive Copies of the two DB's on the same exchange server, why is one failing and the other not.When setting up a Exchange 2013 Database availability Group (DAG) for the first time, you may run into an issue where the database’s Content Index State is listed as “Failed”. 50Mbps MetroE connectivity or not, it'll still be slow. You can use the ResetSearchIndex.ps1 script to do this.' It is in fact the only copy and so I have to use this. They tell me this: 'If the mailbox database copy is the only copy, Exchange Search must create a new content index catalog.
I'm not backing up the active db over a WAN link. I have corrupted indexes in my Exchange 2013 server and I have having trouble figuring out how to reset them. This is not an option, as the passive database copy and the backup server are in the same data center, with the active copy being in the client main office.
Symantec Tech Support's initial fix was to email me this technote: which states the solution is to backup only the Active Database Copy. The Backup Exec Job fails with: V-79-57344-862 - The Backup Exec Agent for Microsoft Exchange was not used to create the last full backup of this database. The VSS errors state: The VSS Writer failed, but the operation can be retried (0x800423f3)
Recently, my Backup Exec 2012 SP1a install has been receiving failures from 1 of my 2 Exchange 2010 databases under DAG.