How to configure lagged database copies for Exchange Server 2013 DAGs, and use lagged copies for database recovery scenarios.
A demonstration of the underlying configuration for Exchange Server 2013 Autoreseed, and the Autoreseed workflow to recover from a disk failure.
A hotfix is available for Exchange 2013 CU6 database crashes/failovers in Exchange 2007 co-existence environments.
Version 1.09 of Test-ExchangeServerHealth.ps1 is now available, fixing a bug in the use of Test-ReplicationHealth for mixed Exchange 2010/2013 organizations.
Configuring the Exchange 2013 Mailbox servers during a migration from Exchange Server 2010.
While adding Exchange Server 2013 DAG members an error “Some or All Identity References Could Not Be Translated” occurs.
Ever wondered why your Exchange Server databases didn’t failover in order of activation preference?
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.
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.
How to use the Exchange 2013 management tools to reseed a failed database copy in a database availability group.