Access your Pro+ Content below.
When disaster strikes in Exchange Server 2010
This article is part of the April 2010, Vol. 5 issue of Exchange Insider
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...
Features in this issue
Disaster can strike at any time. Microsoft Exchange Server must be configured to seamlessly fail over without data loss. Can Exchange Server 2010's native database availability groups minimize an admin's backup and DR efforts?
Take a deep dive into Forefront Protection 2010 for Exchange Server and see how it helps defend Exchange 2010 from spam and malware attacks in multiple types of environments.
Learn Exchange Server email archiving and e-discovery best practices, including how to implement backups, email retention and archiving strategies.