Is it “overkill” to deploy an Exchange Server database availability group for a relatively small number of mailbox users?
In this episode of the Exchange Server Pro Podcast my guest Brian Reid and I discuss ditching traditional backups for Native Data Protection in Exchange.
How to reseed a failed database copy in an Exchange Server 2016 database availability group.
Getting started with Exchange Server 2016 high availability by learning the fundamental concepts of database availability groups.
Can a database availability group have members that are running both Exchange Server 2013 and Exchange Server 2016?
How to use PowerShell scripts to configure and manage a balanced Exchange Server database availability group.
How to configure lagged database copies for Exchange Server 2013 DAGs, and use lagged copies for database recovery scenarios.
In Exchange Server the Get-MailboxDatabaseCopyStatus cmdlet may return the wrong activation preference value for a database copy.
On an Exchange 2013 server you may be presented with a warning message to restart the Information Store after adding a new mailbox database.
The Get-DAGHealth.ps1 PowerShell script has been updated to version 1.1 with bug fixes and Exchange 2013 compatibility.