DAG — Database Availability Group

A Database Availability Group (DAG) is a high-availability and data-recovery framework within Microsoft Exchange Server that groups up to 16 mailbox servers into a single unit. These servers use continuous replication to maintain copies of mailbox databases across different nodes. If a server, disk, or network component fails, the system automatically initiates a "switchover" or "failover," mounting the database on another healthy server in the group to ensure uninterrupted user access to email.

Technical and Architectural Context

The DAG is the fundamental building block for Exchange Server reliability. It leverages the Windows Failover Clustering (WFC) service, though much of the complexity is abstracted through the Exchange management interface. When a DAG is formed, it creates a quorum-based cluster that monitors the health of its members. Each server in the DAG can host a combination of active and passive database copies. Because data is replicated at the database level rather than the storage level, organizations can achieve site resilience by stretching a DAG across two geographically separate data centers.

Licensing Implications and Server Editions

While the DAG feature exists in both Standard and Enterprise editions of Exchange Server, licensing is the primary constraint on its scale:

• Exchange Server Standard: Limited to 5 mounted databases per server. In a DAG environment, this limit includes both active and passive copies. This makes the Standard edition suitable only for very small deployments or basic branch office redundancy.
• Exchange Server Enterprise: Scales to 100 mounted databases per server. This is the industry-standard choice for DAGs, as it allows for the high density of passive copies required for robust N+1 or N+2 redundancy strategies.
• Windows Server Requirements: Because a DAG relies on Windows Failover Clustering, the underlying operating system must be licensed appropriately. Historically, this required Windows Server Enterprise or Datacenter editions, though modern versions of Exchange allow DAGs on Windows Server Standard.

Common Misunderstandings

A frequent point of confusion is the relationship between DAGs and Client Access Licenses (CALs). A DAG is a server-side architectural feature; it does not change the requirement for every user or device to have an Exchange CAL. Furthermore, a DAG is not a backup replacement. While it provides high availability, it does not protect against accidental deletion or database corruption in the same way a point-in-time backup does. Finally, remember that Exchange Server licenses are separate from the hardware; while OEM licenses are pre-installed by manufacturers and tied to a specific machine, they are rarely used for complex DAG configurations which typically utilize Volume Licensing for better mobility and re-assignment rights.

What This Means When Buying

When reviewing a quote or Enterprise Agreement (EA), the term "Database Availability Group" itself won't appear as a line item. Instead, look for Exchange Server Enterprise licenses. If your architecture plan includes a DAG with more than five databases (active or passive) per node, the Enterprise edition is mandatory. Closely related terms to watch for include Active Manager (the internal DAG component that handles failovers) and Exchange Online Archiving, which is often purchased alongside on-premises DAG deployments to manage mailbox growth.

Need this in a quote?

Our team translates glossary concepts into concrete licenses, part numbers and price lists.