Looking for something else?
Database availability groups replaced Exchange Server 2007’s high-availability model, which was based on local continuous replication (LCR), standby continuous replication (SCR), single copy clustering (SCC) and cluster continuous replication (CCR).
Exchange administrators can choose to use DAGs in different geographic locations and in many different architectural designs and configurations, making it considerably more flexible than previous high-availability setups.
NTFAQGuy explains how high availability features have evolved from Exchange Server 2003 through Exchange Server 2010 and at 4 minutes in, explains how Exchange database availability groups work.
Continue Reading About database availability group (DAG)
'database availability group (DAG)' is part of the:
View All Definitions