Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2320
  • Last Modified:

Exchange Mailbox Database - ContentIndex State = Failed

Hey Guys,

Hope you can help with this one.

I am running Exchange 2010 with a DAG setup between 2 mailbox servers. The database on the passive server MBX02 had a state of "Failed and Suspended" after recreating the dag it went into a healthy state. And after a couple of hours the database automatically failed over to MBX02 making it the passive node and showed that the database which used to be Healthy on MBX01 was now in a Failed and Suspended state.

So I investigated a bit and cannot seem to get it in a healthy state again.

I tried a couple of EMS scripts in the hope of resolving the issue and these were the results:

Update-MailboxDatabaseCopy "Management 2.5GB\MBX01" -CatalogOnly
Update-MailboxDatabaseCopy "Management 2.5GB\MBX01" -CatalogOnly
Troubleshoot-CI.ps1 -Database "Management 2.5GB" -ActionDetectAndResolve
Troubleshoot-CI.ps1 -Database "Management 2.5GB" -ActionDetectAndResolve
Tried to force the database to suspend (Suspend-MailboxDatabaseCopy -Identity "Management 2.5GB\MBX01") and then resubmitted the Update-MailboxDatabaseCopy as mentioned above with the same result
Suspend-MailboxDatabaseCopy -Identity "Management 2.5GB\MBX01"
And I also ran the following and am very concerned that both databases (Active and Passive) has a failed ContentIndex State

Get-MailboxDatabaseCopyStatus -Identity "Management 2.5GB"
Get-MailboxDatabaseCopyStatus -Identity "Management 2.5GB"
Does anyone know how I can get the active copy in a Healthy ContentIndex State without moving every mailbox to a new database or doing a restore from backup?

As always your help would be greatly appreciated.

Thanks in advance :)
0
Hendrik Wiese
Asked:
Hendrik Wiese
  • 9
  • 7
1 Solution
 
jrhelgesonCommented:
Try running a MB DB repair:
New-MailboxRepairRequest -Database "Management 2.5GB" -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView
0
 
Hendrik WieseInformation Security ManagerAuthor Commented:
Hi there,

I ran the script above and the active database state has changed to crawling.

Results below:
New-MailboxRepairRequest -Database "Management 2.5GB" -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView
Get-MailboxDatabaseCopyStatus -Identity "Management 2.5GB"
Get-MailboxDatabaseCopyStatus -Identity "Management 2.5GB"
So I guess I need to wait for it to rebuild now?
0
 
jrhelgesonCommented:
Yes, lets see what the repair results return. Check the event logs for any informational/error messages relating to the repair and db copy and post them here.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Hendrik WieseInformation Security ManagerAuthor Commented:
I re-Updated Mailbox Database Copy and now have 2 healthy mailbox database copies. Thanks a lot jrhelgeson, much appreciated.

You have yourself a lovely day.

Cheers!!!
0
 
Hendrik WieseInformation Security ManagerAuthor Commented:
Both databases are in a failed ContentIndex State again. So any new suggestions would be great.
0
 
jrhelgesonCommented:
Well, that victory was short lived.

Run the following Exchange Powershell commands:
[PS] C:\>Get-MailboxDatabaseCopyStatus | fl name, contentindexstate

Name              : MB01\DB1
ContentIndexState : Failed

Name              : MB02\DB1
ContentIndexState : Healthy

Open in new window


Get the name of the database showing unhealthy/failed from the command above, (MB01\DB1) and use it in the following command:
[PS] C:\>Update-MailboxDatabaseCopy "MB01\DB1" -CatalogOnly

Open in new window

Then re-run the first command and it will show healthy.
[PS] C:\>Get-MailboxDatabaseCopyStatus | fl name, contentindexstate

Name              : MB01\DB1
ContentIndexState : Healthy

Name              : MB02\DB1
ContentIndexState : Healthy

Open in new window

0
 
Hendrik WieseInformation Security ManagerAuthor Commented:
Hi there,

Thanks again for your help, but I ran both scripts and the status is still in a "failed" state:

Update
Get
Any other suggestions?
0
 
jrhelgesonCommented:
I need the output from the following command:
Get-MailboxDatabaseCopyStatus | fl name, contentindexstate

The output above shows you ran the command on "Management 2.5GB\SVEXCHMBX-02", did you try running it on '-01'?

Update-MailboxDatabaseCopy "Management 2.5GB\SVEXCHMBX-02" -CatalogOnly

Update-MailboxDatabaseCopy "Management 2.5GB\SVEXCHMBX-01" -CatalogOnly
0
 
Hendrik WieseInformation Security ManagerAuthor Commented:
Hi,

As requested:

Get-MailboxDatabaseCopyStatus -identity "Management 2.5GB" | fl name, contentindexstate
Get-MailboxDatabaseCopyStatus -identity "Management 2.5GB" | fl name, contentindexstate
Update-MailboxDatabaseCopy "Management 2.5GB\SVEXCHMBX-02" -CatalogOnly
AND
Update-MailboxDatabaseCopy "Management 2.5GB\SVEXCHMBX-01" -CatalogOnly
Update-MailboxDatabaseCopy "Management 2.5GB\SVEXCHMBX-01" -CatalogOnly / SVEXCHMBX-02
I think the main problem here is the fact that both copies has a failed ContentIndex State

Thanks again for the help
0
 
Hendrik WieseInformation Security ManagerAuthor Commented:
0
 
jrhelgesonCommented:
Have you tried deleting the passive copy of the db, running the repairs on the single db instance, then re-creating the DAG?
0
 
Hendrik WieseInformation Security ManagerAuthor Commented:
Hi,

Yes I have tried all that.

Regards,
Hendrik Wiese
0
 
jrhelgesonCommented:
What about trying it without the -CatalogOnly command:

Update-MailboxDatabaseCopy "Management 2.5GB\SVEXCHMBX-02"
AND
Update-MailboxDatabaseCopy "Management 2.5GB\SVEXCHMBX-01"
0
 
Hendrik WieseInformation Security ManagerAuthor Commented:
Tried it an it fails with the following:

Update-MailboxDatabaseCopy
0
 
jrhelgesonCommented:
We should go back to what worked last. We should remove the copy from SVEXCHMBX-02 and clean all remnants off of that server.

Then run the mailbox repair on the copy that remains:
New-MailboxRepairRequest -Database "Management 2.5GB" -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

After the repair, run:
Update-MailboxDatabaseCopy "Management 2.5GB\SVEXCHMBX-01" -CatalogOnly

If we come back with no errors, then re-create the DAG.
If we still  run into problems, I'd just create a new mailbox database, and move the mailboxes from the old DB into the newly created one, then delete the old mailbox db.
0
 
Hendrik WieseInformation Security ManagerAuthor Commented:
I have tried everything above which did not resolve the issue. I logged a call with MS and we are busy trying to resolve the issue.

Thanks for all the help anyway.
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.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 9
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now