Designing a backup less Exchange 2010 Architecture
Microsoft Exchange Server 2010 features a new platform for high availability and site resilience that makes deploying redundant and highly available mailbox databases easier than before. But even the most extreme forms of redundancy and fault tolerance can't protect against every possible failure or disaster. Ensuring there's sufficient protection for the critical data in the Exchange organization is a necessary operational task for all organizations.
As part of data protection planning, it's important to understand the ways in which data can be protected, and to determine of those ways, which best suits the organization's needs.
Exchange 2010 provides native data protection that eliminates the need to make traditional backups of your data. The following table helps to decide whether you need to continue utilizing a traditional backup model or whether you can implement the native data protection features built within Exchange 2010:
Issue |
Mitigation |
Software failure |
Mailbox Resiliency (multiple database copies) |
Hardware failure |
Mailbox Resiliency (multiple database copies) |
Site/datacenter failure |
Mailbox Resiliency (multiple database copies) |
Accidental or malicious deletion of item |
Single Item Recovery and deleted item retention with a window that meets or exceeds the item recovery SLA |
Physical corruption scenarios |
Single Page Restore (HA database copies) |
Logical corruption scenarios |
Single Item Recovery |
Calendar Repair Assistant |
|
Mailbox Moves |
|
New-MailboxRepairRequest |
|
Point-In-Time Backup (PIT) backup |
|
Administrative errors |
PIT backup |
Automation errors |
PIT backup |
Rogue administrators |
PIT backup |
Corporate/Regulatory Compliance requirements |
PIT backup |
Logical corruption is typically a scenario that requires a PIT backup. However, with Exchange 2010, there are several options now available that can mitigate the need for PIT backup:
- With Single Item Recovery, if the user changes certain properties of an item in any mailbox folder, a copy of the item is saved into the Recoverable Items folder before the modification is written to the store. Therefore, if the modification of the message results in a corrupted copy, the original item can be restored.
- The Calendar Repair Assistant detects and corrects inconsistencies that occur for single and recurring meeting items for mailboxes homed on that Mailbox server so that recipients won't miss meeting announcements or have unreliable meeting information.
- During mailbox moves, the Mailbox Replication Service detects corrupted items and will not move those items to the target mailbox database.
- Microsoft Exchange Server 2010 Service Pack 1 introduces the New-MailboxRepairRequest which can address corruptions with search folders, item counts, folder views, and parent/child folder issues.
Note that several of the mitigations mention PIT backup. A PIT backup can be either a traditional backup, or a lagged database copy. Both provide the same capabilities; however, the choice between the two will depend on your recovery SLA. The Recovery SLA will define the Recovery Point Objective (in the event of a disaster the data must be restored within a certain timeframe of the disaster), as well as, how long the backups must be retained. If the recovery SLA is 14 days or less, then a lagged database copy can be utilized; if the recovery SLA is greater than 14 days, then a traditional backup must be used. For the rogue administrator and corporate/regulatory compliance scenarios, the PIT backup typically is Isolated and maintained separately from the messaging infrastructure and messaging IT staff, which dictates a traditional backup solution.
Thanks to Ross for assisting me on this document.
Comments
Anonymous
January 20, 2011
A very nicely written and useful article.Anonymous
December 18, 2013
We are pleased to announce the RTM availability of version 9.0 of the Microsoft Assessment and PlanningAnonymous
December 18, 2013
I’ve written a few blog posts now that get into the deep technical details of Managed Availability. IAnonymous
December 26, 2013
Recently I was involved in a Private Cloud project and as part of the project, we were migrating someAnonymous
January 14, 2014
Recently, we have seen some questions about what the Update-DatabaseSchema cmdlet in Exchange 2013 isAnonymous
January 30, 2014
This has been a great new feature added in Windows Server 2012 R2. The possible scenario of the usageAnonymous
February 09, 2014
Many users rely on their smart phones and other mobile devices to access their email and calendar usingAnonymous
February 25, 2014
With Exchange 2013, we released a new data loss prevention (DLP) capability based on deep content analysisAnonymous
February 26, 2014
Exchange Server 2013 Service Pack 1 (SP1) is now available for download! Please make sure to read theAnonymous
March 05, 2014
This article is part 2 in a series that discusses namespace planning , load balancing principles, clientAnonymous
March 10, 2014
Microsoft Exchange Server 2003 entered the market on September 28, 2003 and continued the great messagingAnonymous
March 20, 2014
Now that we understand the load balancing and namespace planning principles and how clients connect inAnonymous
April 18, 2014
We’re happy to announce updates to the Exchange Server Deployment Assistant ! These updates offer youAnonymous
April 21, 2014
During my session at the recent Microsoft Exchange Conference (MEC), I revealed Microsoft’s preferredAnonymous
May 02, 2014
With the huge scale environment I currently work in my team has had some difficulty when it comes toAnonymous
May 25, 2014
I recently did an Exchange 2013 deployment at one of our customers and also integrated with ADRMS soAnonymous
June 18, 2014
In the last week there have been two big improvements related to CalCheck and OffCAT that will make lifeAnonymous
June 18, 2014
I was recently helping a customer in ADRMS design and deployment where we faced an issue with ADRMS URLAnonymous
June 27, 2014
We are pleased to announce the availability of version 9.1 of the Microsoft Assessment and PlanningAnonymous
July 02, 2014
Recently I was working for ADRMS integration with Exchange which is rather simple however it became quiteAnonymous
August 11, 2014
Probes are one of the three critical parts of the Managed Availability framework (monitors and respondersAnonymous
August 19, 2014
In the last related blog post we gave some introduction about Exchange Online Protection (EOP), whatAnonymous
August 26, 2014
The Exchange team is announcing today the availability of our most recent quarterly servicing updateAnonymous
September 16, 2014
Occasionally I am asked the following question – how can I protect the messaging environment from a rogueAnonymous
September 28, 2014
Bulk mail is often mistaken for spam and is starting to become a larger problem for organizations. EOPAnonymous
October 20, 2014
At The Official Microsoft Blog , we revealed more details about our unified technology event for eventAnonymous
October 25, 2014
We recently released updated versions of both the Exchange 2010 Server Role Requirements Calculator andAnonymous
November 09, 2014
What are we talking about today? In Exchange 2013 CU5 (yes 5, V, cinco, fem, and cinque) we started implementingAnonymous
November 30, 2014
I was recently working with one of our customers on Lync 2013 project and one of the questions customerAnonymous
December 23, 2014
I was recently working on a project using Security Compliance Manager (SCM) for Active Directory basedAnonymous
December 31, 2014
I was recently working with a customer helping them migrate to the Eliminated state of Sysvol migrationAnonymous
January 13, 2015
Back at the release of Exchange Server 2013 CU1 we made some necessary changes to the way OWA logoffAnonymous
January 31, 2015
This morning we published the first look at the Ignite session catalog providing you a better view ofAnonymous
February 08, 2015
Sometime ago, I wrote a blog about upgrading from Windows 2003 based Active Directory to Windows 2008Anonymous
February 09, 2015
Exchange team has written below blog on the remote connectivity analyzer tests for mail flow testingAnonymous
February 09, 2015
Exchange team has released a blog about Office 365 best practices analyzer for Exchange 2013 as belowAnonymous
February 09, 2015
Exchange team has written a blog about new Exchange Server deployment assistance as below:
We’veAnonymous
February 09, 2015
After a long wait, the calculator is there. The calculator recommends mailbox and CAS sizing as wellAnonymous
February 13, 2015
Exchange team blogged about post TMG world. R ead the blog at http://blogs.technet.com/b/exchange/archiveAnonymous
February 13, 2015
Exchange team blogged about OffCAT as below:
On Friday, July 19, the OffCAT team released OffCAT versionAnonymous
February 13, 2015
Read the blog at http://blogs.technet.com/b/exchange/archive/2013/07/16/owa-for-iphone-and-owa-for-ipadAnonymous
February 13, 2015
Exchange team has released Hosting and Multi-Tenancy Guidance for Exchange Server 2013 document. It isAnonymous
February 13, 2015
The Exchange team has released the following update rollups to the Download Center. All three releasesAnonymous
February 13, 2015
Exchange team has released a fantastic blog about publishing Exchange 2013 with TMG server.
ReviewAnonymous
February 15, 2015
You can protect your organizational Units from accidental deletion by using Power Shell scripts to applyAnonymous
March 23, 2015
I was recently working with a customer where one of their Active Directory would not replicate. TheyAnonymous
April 24, 2015
Recently Microsoft Exchange team has written a blog about large messages in Office 365. I see many customersAnonymous
May 12, 2015
Microsoft has recently released an initial look at Exchange 2016 architecture and Exchange team has writtenAnonymous
June 30, 2015
Recently Exchange team has written an excellent article on Exchange processor and memory usage and howAnonymous
July 31, 2015
In a recent project I was working on ADFS with multiple applications and customer also had SAP to beAnonymous
December 13, 2015
Recently i was troubleshooting some integration issues between SCVMM, SPF and Windows Azure Pack (WAPAnonymous
March 08, 2016
Pingback from 8dot3 and the Exchange 2010 SP3 LAG Copy | Doug's Think-Tank