Cannot Activate Database Copy: Content Index Catalog Files in Failed State

exchange-2010-cannot-activate-database

When activating a database copy in an Exchange Server 2010 Database Availability Group it may fail with an error message that catalog index files are in a failed state.

Why Bother Running DAG Server Maintenance Mode Scripts?

exchange-2010-logo-212

Answering a reader question on whether the DAG server maintenance scripts are really necessary when performing maintenance or installing updates on database availability group members.

Exchange Server 2013: Using Test-ReplicationHealth to Test Database Availability Group Members

powershell-logo

How to use the Test-ReplicationHealth PowerShell cmdlet to test the database replication health for Exchange 2013 Database Availability Group members.

How to Reseed a Failed Database Copy in Exchange Server 2013

exchange-2013-reseed-from-active

How to use the Exchange 2013 management tools to reseed a failed database copy in a database availability group.

How to Remove a DAG Member in Exchange Server 2013

exchange-2013-remove-dag-member-02

The step by step process for how to remove an Exchange 2013 Mailbox server from a Database Availability Group.

MSExchangeRepl Error: “The process cannot access the file because it is being used by another process.”

exchange-2010-logo-212

An Exchange database may failover when the Exchange replication service is unable to access a transaction log file that is in use by another process.

We are an Authorized DigiCert™ SSL Partner.