Context Index State Crawling

Hello Experts,
One of the particular database was in Failed state so stopped the search services and deleted the CI CUID directory in an effort to rebuild the search catalog, but now just goes right back to crawling for more than 24 hours now.
The database size is 2 TB.
We also have passive but in FailedAndSuspended State.

Is this normal and how long will it take before turning to Healthy again? Any ideas would be appreciated.
LVL 3
cciedreamerAsked:
Who is Participating?
 
RoninConnect With a Mentor Commented:
I would say it's normal, CI is not a priority on the Exchange as much as I know, therefor it will be used when there will be enough resources.  However you should look into distributing your mailboxes across multiple databases.  2TB is the recommended maximum, you might potentially hitting the limit there.
https://technet.microsoft.com/en-us/library/ee832792(v=exchg.160).aspx
0
 
cciedreamerAuthor Commented:
Thanks Ronin,
I'll wait the crawling is finished and changes the status to healthy.
0
 
RoninCommented:
Just so you know, after upgrading CU7 to CU8 on a servers which run 5 databases each around 800GB it took over 2 weeks until all the indexes showed HEALTHY.

Again, I highly recommend review your database size allocation.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
cciedreamerAuthor Commented:
Its a good information to know that upgrading CU will put the databases into indexing
Thanks Ronin
0
 
cciedreamerAuthor Commented:
Hi,

The indexing is completed and active database CI state is changed to healthy.

However, the passive is in FailedAndSuspended state

I have tried the below but no luck

Get-MailboxDatabaseCopyStatus * | where {$_.ContentIndexState -eq “Failed”} | Update-MailboxDatabaseCopy -CatalogOnly

Appreciating any help.
0
 
RoninCommented:
On the passive node stop two Exchange services:
Stop-Service MsExchangeFastSearch
Stop-Service HostControllerService

Open in new window

Navigate to the location of the database for which indexing is failing.
Located the folder with GUID in it's name, either rename it or delete the folder.
Start the services.
0
 
cciedreamerAuthor Commented:
I already tried that as well but again same FailedAndSuspended.
0
 
RoninConnect With a Mentor Commented:
How long overall have you waited on it?
I'm inclined to suggest waiting couple of days perhaps.
Generally it should resolve by itself.
0
 
cciedreamerAuthor Commented:
Thank, its been now more than 12 hours.
I checked the registry values on both servers.

This CI GUID on Server 1 and Server 2
{b9fbc12f-dc89-408d-a13f-7ec1855c2d97}


But the data value is different no node 2. I tried copying from Server 1 to Server 2, it becomes healthy and again goes back to FailedAndSuspended.
0
 
cciedreamerAuthor Commented:
Hi Ronin,
You were right in your previous comment ( ID: 42377563)  I think I didn't has the patience.
All the databases are now healthy.
0
 
RoninCommented:
Is the issue resolved?
0
 
cciedreamerAuthor Commented:
Yes, all the databases ( active & passive copies) and CI are healthy.
But just a small concern the CI folder size on Server 1 and Server 2 for the database mentioned in this question is different Why is that so ?
0
 
RoninCommented:
Can't say, you might want to look up some information on how CI is performed and working in DAG.
0
 
cciedreamerAuthor Commented:
Thanks Ronin
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.