Content Index State on Exch 2013 DBS, shows failed state

I have an exch 2013 dbs that when I select it and look to the right the Content Index State is reporting failed state.
Is this something I need to be concerned about and if so, how do I fix this issue and will fixing this affect the users?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Exchange will still work.  What you will find is that multi-mailbox searches, searches through OWA, and Outlook clients in ONLINE mode will not retrieve full search results when doing mail searches.

Additionally, Exchange wont fail the DAG to a copy with a corrupt index by default.  You could manually FORCE it to mount if needed using the -ignoreclientexperience flag on the mount, but that would be extreme.

Typically, you can rebuild the "CI" (Content Index" with a command such as:

Update-MailboxDatabaseCopy -Identity DB1\MBX1  -CatalogOnly

Where DB1 is the name of the database and MBX1 is the name of the server.

If that doesn't work, try:

        Stop the “Microsoft Exchange Search service” as
        well as the “Microsoft Exchange Host Controller.”
        Delete the Existing CI catalog folder or move it
        to a new location.
        Start the “Microsoft Exchange Search service” as
        well as the “Microsoft Exchange Host Controller” services.

This should trigger it to be rebuilt or replicated from a healthy copy.

In extreme cases, I've found that I had to delete the replica (not the whole database, but just the standby replica with the bad CI) and re-seed from the active copy, but usually I can get the rebuild to work.

Be careful - In my recommendations, I'm assuming you have a DAG, and that we're working only on inactive standby copies.  note that if you dismount a database it will be client impacting!!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
vmichAuthor Commented:
Yes I did do the above steps you mentioned after I posted this and it is rebuilding it as we speak.. It has the status of crawling which it will until it completes..
vmichAuthor Commented:
correct file
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.