Mission-Critical Microsoft Exchange 2003: Designing and Building Reliable Exchange Servers (HP Technologies)

Chapter 1: Has Anyone Seen My Mission-Critical Microsoft Exchange Server?

Figure 1.1: The four pillars of a mission-critical system.

Figure 1.2: How mission critical Exchange Server 2003 is organized.

Chapter 2: Public Enemy #1: Exchange Downtime

Figure 2.1: Illustrating lost client opportunity downtime measurement.

Figure 2.2: The cost of downtime.

Figure 2.3: The black box of Exchange downtime.

Figure 2.4: Categorizing the leading causes of downtime.

Chapter 3: The Heart of Exchange: Exchange Store Technology

Figure 3.1: Exchange storage design: version 5.5 and earlier.

Figure 3.2: Exchange Server 2000/2003 storage design.

Figure 3.3: Exchange 2000/2003 storage layout.

Figure 3.4: Exchange database logical view.

Figure 3.5: Message receive actions for Exchange Server Store.

Figure 3.6: Message move actions for Exchange Server Store.

Figure 3.7: Basic B-Tree database structure.

Figure 3.8: Exchange Extensible Storage Engine B-Tree structure.

Figure 3.9: Exchange ESE page structure.

Figure 3.10: The Exchange database engine at work.

Figure 3.11: Exchange transaction log file header format.

Figure 3.12: Example ESE transaction log file contents.

Figure 3.13: Interactions between ESE, ExIFS, and IIS when storing Exchange data.

Figure 3.14: Exchange single instance storage illustrated.

Chapter 4: When Exchange Servers Fall Down

Figure 4.1: The impacts of write-back caching on disk I/O operations.

Figure 4.2: ESEUTIL command line options and parameters.

Figure 4.3: Using the ESEFILE utility to check physical database page integrity.

Chapter 5: Protecting and Recovering Exchange Data

Figure 5.1: Exchange 2003 backup operation.

Figure 5.2: ESE’s patching operation during backup (Exchange 2000 SP1 and earlier).

Figure 5.3: Enabling ESE Page Zeroing in Exchange system manager.

Figure 5.4: Exchange 2003’s restore operation.

Figure 5.5: Snapshot technology illustrated.

Figure 5.6: Clone technology illustrated.

Figure 5.7: Windows Volume Shadow Copy Services architecture.

Figure 5.8: Typical VSS Shadow Copy operation.

Figure 5.9: Exchange 2000 recovery server scenario.

Figure 5.10: Exchange Server 2003’s Recovery Storage Group feature.

Chapter 6: Exchange Server Disaster-Recovery Best Practices

Figure 6.1: Exchange Server transacted storage architecture.

Figure 6.2: Partitioned versus monolithic storage in Exchange Server.

Figure 6.3: Comparing backup strategies in terms of time, tapes, and volume.

Figure 6.4: Using snapshot/ clone (BCV) technology with Exchange Server.

Chapter 7: Mission-Critical Server and Storage Technologies

Figure 7.1: Typical simplified server architecture.

Figure 7.2: Server outages due to memory failures.

Figure 7.3: Illustration of RAID levels 0, 1, 0+1, and 5.

Figure 7.4: FCAL-based storage attachment.

Figure 7.5: FCS-based storage attachment.

Figure 7.6: The paradigm shift from host-based storage to networkbased storage.

Figure 7.7: Using data replication with Exchange Server.

Figure 7.8: Implementation of software-based data-replication technology

Figure 7.9: An illustration of BCVClone.

Figure 7.10: Illustration of BCVSnap.

Figure 7.11: Using NAS with Exchange server.

Figure 7.12: Optimizing performance: separation of random and sequential I/O.

Chapter 8: Leveraging Exchange Clusters

Figure 8.1: Microsoft’s three-pronged approach to clustering.

Figure 8.2: Comparing shared nothing to shared disk cluster architectures.

Figure 8.3: A basic two-node MSCS configuration.

Figure 8.4: MSCS architecture and components.

Figure 8.5: The Exchange Cluster Administration DLL and the Exchange resource DLL.

Figure 8.6: Exchange 2000 Cluster resource dependency tree.

Figure 8.7: Windows virtual memory model.

Figure 8.8: Exchange Server 2003 Cluster resource dependency tree.

Figure 8.9: Cluster service interaction with Exchange 2003 via IsAlive and LooksAlive.

Figure 8.10: Exchange 2003 Cluster design utilizing mount points.

Figure 8.11: 4-Node (N+1) Exchange 2003 Cluster configuration (7,500 users).

Figure 8.12: 2-Node (A/A) Exchange 2003 Cluster configuration (4,000 users).

Figure 8.13: Configuring Exchange system attendant resource dependencies.

Figure 8.14: Exchange Cluster View from Cluster Administrator.

Figure 8.15: Exchange Cluster view from Exchange System Manager.

Chapter 9: Locking Down Mission-Critical Exchange Servers

Figure 9.1: ient authentication to Exchange using Windows Kerberos.

Figure 9.2: Kerberos authentication used with an Exchange front-end/back-end architecture.

Figure 9.3: Windows and Exchange services dependencies.

Figure 9.4: Example of firewall architecture Alpha.

Figure 9.5: Example of firewall architecture Bravo.

Figure 9.6: Example of firewall architecture Charlie.

Figure 9.7: On access virus scanning mode.

Figure 9.8: Proactive virus scanning mode.

Figure 9.9: Background virus scanning mode.

Figure 9.10: Exchange 2003/ Outlook 2003 end-to-end antispam solution.

Figure 9.11: A simplified PKI design.

Chapter 10: Proactive Management for Mission-Critical Exchange Servers

Figure 10.1: A three-pronged approach to proactive management.

Figure 10.2: Performance monitoring with Windows Server System Monitor.

Figure 10.3: HP’s Insight Manager version control feature.

Figure 10.4: Example of MOM architecture for Exchange monitoring.

Figure 10.5: Microsoft Operations Manager console view.