The question has come up a couple times in my blog on high availability and redundancy of Database Availability Groups (DAGs) specific to “What happens to the Client Access Server (CAS) and Hub ...

Exchange Server 2010 incorporates a number of high-availability features that system admins will find useful, including a new database availability groups (DAG) feature. Mailbox databases and the data ...

One of the improvements made in Exchange 2010 is the redundancy built-in to the routing of messages through the Exchange environment. Microsoft built-in a technology they call “Shadow Redundancy” ...

Exchange 2007 and 2010 both offer multiple server roles. Some are new and have no connection to pre-2007 Exchange, such as the Edge Transport server role and the Unified Messaging server role. Others ...

Question: Our organization has Exchange 2007 deployed. We have a high availability solution consisting of 4 Exchange 2007 servers -- two servers that have the Hub Transport and Client Access server ...

With the release of Exchange 2007 and then 2010, Microsoft moved admins to a role-based model for deployment, with changes both to roles and services that admins should understand. Exchange 2013 takes ...

I've been working on putting an Exchange 2007 infrastructure together.<BR><BR>I've got two edge transport servers, one server running the hub transport and client access roles, and two boxes clustered ...

Mailbox databases and the data they contain are critical to any Exchange organization. To ensure high availability for mailbox databases, Exchange Server 2007 provided a variety of replication and ...