Transcript
8/9/2019 Messaging Backup and Restore
1/15
Messaging Backup and Restoreat Microsoft
Published:June 2003
8/9/2019 Messaging Backup and Restore
2/15
Situation As part of the internal rollout of Microsoft Exchange 2003 and the Microsoft Windows
Server System at Microsoft, Microsoft IT began to consolidate messaging servers toreduce operating costs. High availability requirements for the clustered server redesignprompted Microsoft IT to examine its backup and restore solution.
Solution Microsoft IT implemented a two-step backup solution and the Exchange 2003 Recovery
Storage Group (RSG) feature that minimizes user downtime during a databaserecovery. The new solution supports server consolidation with high availability whileproviding greater backup and restore flexibility.
Benefits Increased server ability during single node failures Reduced operating costs from server consolidation Minimized impact to users during backup using an alternate passive node in the
clustered configuration Flexible recovery solution allowed users to continue working while restoration of
mailbox/database was done offline and merged later
Solution Overview
8/9/2019 Messaging Backup and Restore
3/15
Products and Technology
Microsoft Exchange Server 2003 Microsoft Windows Server 2003Enterprise Edition
Veritas Network StorageExecutive (NSE)
HP StorageWorks EnterpriseVirtual Array 5000 storage areanetwork (SAN) solution
Microsoft Operations Manager
(MOM) Exchange 2003Management Pack (MP)
8/9/2019 Messaging Backup and Restore
4/15
Situation
As of July 2003 the Microsoft corporate e-mailinfrastructure is comprised of:
Global mail flow of 6,000,000 messages per day onaverage, with 2,500,000 average Internet mailmessages per day.
20 databases per server, with 50 gigabyte (GB)maximum database size on new clustereddeployments. 200 MB per user mailbox limits.
Global service availability of 99.9% with a target toachieve 99.99% on clustered designs.
Worldwide mail delivery in less than 90 seconds, 95%of the time.
Backup and restore operation SLA of less than onehour per database.
8/9/2019 Messaging Backup and Restore
5/15
Old Configuration
RegionalRegionalConfigurationConfiguration
1K Mailbox1K MailboxExchange 2000Exchange 2000
1K Mailbox1K MailboxExchange 2000Exchange 2000
1K Mailbox1K Mailbox
Exchange 2000Exchange 2000
DedicatedDedicatedExchange 2000Exchange 2000Restore Server Restore Server
100MBLAN
100MBLAN
TapeTape
8/9/2019 Messaging Backup and Restore
6/15
AA BB
CC DD
EE
SG1SG1
AA BB
CC DD
EE
SG2SG2
Backup Solution Architecture
Production DataProduction DataFour storageFour storage groups (SG) per server groups (SG) per server
Five databases per storage groupFive databases per storage group
DD
EE
AA
BB
CC
DD
EE
AA
BB
CC
Pool of BackupPool of BackupDisksDisks
AA
BB
CC
DDEE
AABB
CC
DD
EE
AA
BB
CC
DD
EE
AA
BB
CC
DD
EE
Linear TapeLinear TapeLibraryLibrary
BackupBackup~~60GB/hr/SG60GB/hr/SG
BackupBackup~~60GB/hr 60GB/hr streamstream
RestoreRestoreRestoreRestore~~100GB/hr 100GB/hr
AA
BB
CC
DD
EE
DD
EE
AA
BB
CC
DD
EE
AA
BB
CC
8/9/2019 Messaging Backup and Restore
7/15
Recovery
Service RecoveryService Recovery
Data RecoveryData Recovery
>5 DB>5 DB(1000 users)(1000 users)
8/9/2019 Messaging Backup and Restore
8/15
Cluster Design Specifications
4 CPU Active Nodes4 CPU Active Nodes 33 44
Mailboxes per Cluster Mailboxes per Cluster 8,0008,000 16,00016,000
RegionaRegionall
HeadquarHeadquartersters
GoalGoal
4 CPU Passive Nodes4 CPU Passive Nodes 33 44
2 CPU Alt Passive Nodes2 CPU Alt Passive Nodes 33 44
EVAEVA 33 44
8/9/2019 Messaging Backup and Restore
9/15
Benefits
Clustered design with 2-stage backups Provided greater flexibility to back up and restore
data when needed Minimized impact on users Increased server ability during single node failures Reduced operating costs
8/9/2019 Messaging Backup and Restore
10/15
Best Practices
Two-step Backup Minimized user impact Allowed 2nd stage backups to occur at any time
Backup Throughput Registry Adjustment Doubled throughput per storage group
Server Design Base multi-node cluster design on active and primary alternate
servers Manage Transaction Logs Use MOM to Monitor Backup and Restore
8/9/2019 Messaging Backup and Restore
11/15
Summary
Microsoft IT benefited from implementing atwo-step backup operation and a newclustered design.
Increase in number of supported mailboxes per
server Doubling of user mailbox limits while maintaining
the 1-hour SLA per database for backup andrestore operations
Reduced operating costs Improved existing uptime SLA
8/9/2019 Messaging Backup and Restore
12/15
For More Information
Additional content on Microsoft ITdeployments and best practices can befound on http://www.microsoft.com Microsoft TechNet
http://www.microsoft.com/technet/itshowcase
Microsoft Case Study Resources
http://www.microsoft.com/resources/casestudies
http://www.microsoft.com/http://www.microsoft.com/technet/itshowcasehttp://www.microsoft.com/technet/itshowcasehttp://www.microsoft.com/8/9/2019 Messaging Backup and Restore
13/15
This document is provided for informational purposes only.
MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
2004 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THISSUMMARY. Microsoft, Microsoft Press, Visual Studio, Visual SourceSafe, Windows and Windows NT are either registered trademarksor trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and productsmentioned herein may be the trademarks of their respective owners.
8/9/2019 Messaging Backup and Restore
14/15
Appendix
8/9/2019 Messaging Backup and Restore
15/15
Cluster Architecture
top related