Is it “overkill” to deploy an Exchange Server database availability group for a relatively small number of mailbox users?
Podcast Episode 24: Native Data Protection with Brian Reid
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.
Reseeding a Failed Database Copy in an Exchange Server 2016 Database Availability Group
How to reseed a failed database copy in an Exchange Server 2016 database availability group.
Introduction to Exchange Server 2016 Database Availability Groups
Getting started with Exchange Server 2016 high availability by learning the fundamental concepts of database availability groups.
Can Exchange 2013 and Exchange 2016 Servers Be Added to the Same Database Availability Group?
Can a database availability group have members that are running both Exchange Server 2013 and Exchange Server 2016?
PowerShell Scripts for Balancing Database Availability Groups
How to use PowerShell scripts to configure and manage a balanced Exchange Server database availability group.
Exchange Server 2013 Lagged Database Copies In Action
How to configure lagged database copies for Exchange Server 2013 DAGs, and use lagged copies for database recovery scenarios.
Get-MailboxDatabaseCopyStatus Displays Incorrect Activation Preference Value
In Exchange Server the Get-MailboxDatabaseCopyStatus cmdlet may return the wrong activation preference value for a database copy.
Warning: Please Restart the Microsoft Exchange Information Store Service After Adding New Mailbox Databases
On an Exchange 2013 server you may be presented with a warning message to restart the Information Store after adding a new mailbox database.
V1.1 of Get-DAGHealth.ps1 is Available
The Get-DAGHealth.ps1 PowerShell script has been updated to version 1.1 with bug fixes and Exchange 2013 compatibility.