Premium Content

Access "When disaster strikes in Exchange Server 2010"

Serdar Yegulalp, Contributor Published: 12 Oct 2012

A large part of an Exchange Server administrator's job involves preparing for and recovering from disaster -- setting up a backup strategy or configuring Exchange servers for failover. Microsoft added some seamless new high-availability and site resilience features (backup and disaster recovery) to Exchange Server 2010 that do not involve any additional configuration or extraordinary work to establish. High availability (HA) in Exchange Server 2007 was a function of continuous cluster replication, which isn't perfect, but still a huge improvement over Windows Server 2003 active/passive failover. In that case, you could leverage Exchange 2007's log shipping and replay functions in conjunction with clustering, but you were still stuck with only one database per storage group. Exchange Server 2010 gives you multiple databases through the use of database availability groups, or DAGs, which automatically stay in sync with each other. These groups of up to 16 Exchange 2010 mailbox servers automatically replicate Exchange databases and create less of a dependency ... Access >>>

Access TechTarget
Premium Content for Free.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

What's Inside


More Premium Content Accessible For Free