Manuals / Brands / Computer Equipment / Server / Microsoft / Computer Equipment / Server

Microsoft 1 Extensible Storage Engine (ESE) Heaps, Store-Database Cache Size

1 122

Download 122 pages, 488.87 Kb

Chapter 2: Capacity and Availability Management 29

Extensible Storage Engine (ESE) Heaps

When Exchange 2000 is installed on servers with more than four processors, you might

notice high virtual memory usage by the Extensible Storage Engine (ESE) multi-heap. This

can lead to performance problems, especially when the server has more than one GB of

memory, and many databases and storage groups have been configured. It is recommended

that you add the following registry parameter to all servers with more than four processors:

Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ESE98\Global\OS\Memory

Parameter: MPHeap parallelism (REG_SZ)

Default setting: (Doesn’t exist) = Parallelism set to four times the number of processors

installed.

Recommended For up to four processors, take no action. If the server has four or more

setting: processors and has the maximum number of storage groups and MDBs, set

the value to “0.” When set to zero, the parallelism is set to three plus the

number of processors on the computer. For example, on eight-processor

computers, it is recommended that this registry key be set to “11.”

Note: You must restart the Exchange information store process after the preceding registry

parameter has been changed.

Store-Database Cache Size

Exchange 2000 is configured with a hard-coded maximum store-database cache size. This

default value is 900 MB. On servers with more than 2 GB of memory, it can be beneficial

to increase the size of this cache. Due to virtual address space limitations, this value should

never be set higher than 1200 MB.

Note: The 900-MB limit is in place to ensure that the store process always has ample virtual

address (memory) from which to allocate. Increasing this value too much can lead to system

instability. For more information regarding virtual address space, see Knowledge Base article

Q266096 available at:

http://support.microsoft.com/support/kb/articles/Q266/0/96.ASP?LN=EN-

US&SD=gn&FR=0&qry=Q266096&rnk=1&src=DHCS_MSPSS_gn_SRCH&SPR=MSALL

Contents

Main ii Contents Chapter 1 Introduction 1 Chapter 2 Capacity and Availability Management 11 Change and Configuration Management 37 Chapter 4 Enterprise Monitoring 53 Chapter 5 Protection 71 Chapter 6 Glossary 97 Support 89 Page Page Page Introduction Microsoft Operations Framework (MOF) Page How to Use This Guide Efficiency, Continuity, and Security Figure 1.2 Efficiency Continuity Security Chapter Outlines Planning and Deployment Service Level Agreements Features Performance Recovery Support Related Topics Page Capacity and Availability Management Capacity Management Page Page Availability Management Service Hours Service Availability Minimizing System Failures Decreasing Single Points of Failure Increasing the Reliability of Exchange 2000 Minimizing System Recovery Time Performance Tuning Making Changes to the Registry No Performance Optimizer Optimizable Features Tuning Considerations Upgrading from Exchange 5.5 to Exchange 2000 Tuning the Message Transfer Agent (MTA) Tuning SMTP Transport Mailroot Directory Location SMTP File Handles Page Store and ESE Tuning Online Store Maintenance Online Backups Choosing the Correct Maintenance Strategy Extensible Storage Engine (ESE) Heaps Store-Database Cache Size Page Log Buffers Tuning Active Directory Integration Page Tuning Outlook Web Access (OWA) Page Hardware Upgrades Page Change and Configuration Management Prerequisites Change Management Defining Change Type Step 1 Request for Change Is Submitted to Change Manager Step 2 Change Manager Assesses the RFC Step 3 Change Is Passed to IT Executive Committee for Approval Step 4 Change Is Passed to the Change Advisory Board for Scheduling Step 5 Change Is Passed to the Change Owner Step 6 Change Process Evaluation Minor and Standard Changes Scripting Minor and Standard Changes Security Software Control and Distribution Documentation Configuration Management Tools for Configuration Management Configuration Management and Change Management Configuration Items Page Page Page Defining Configuration Items Configuration Management and Exchange Maintaining the Configuration Management Database Change Management Ownership Security Backup Exchange System Policies Administering System Policies Page Enterprise Monitoring Prerequisites Performance Monitoring System Monitor Exchange 2000 Objects and Counters to Monitor Service or Resource Performance Object Information Store Counters SMTP Server MSExchangeMTA and MSExchangeMTAConnections MSExchangeIM Virtual Servers MSExchangeAL Windows 2000 Objects and Counters to Monitor Table 4.2 Subjects and Associated Objects and Counters Subsystem Object Counter Exchange Comments Subsystem Object Counter Exchange Comments Centralized Monitoring Event Monitoring Event Viewer Log Files Centralized Event Monitoring Availability Monitoring Monitoring and Status Tool Adding Services to the Default Configuration Monitoring Resources Notifications Status Disabling Server Monitoring Centralized Availability Monitoring Client Monitoring Page Page Protection Chapter Start Point Chapter End Point Protection Against Hacking Firewall Operations Maintaining Firewall Availability Ensuring That Only the Correct Traffic Passes Through the Firewall Monitoring Against Hacker Intrusion Dealing With Security Breaches Anti-Virus Measures Staying Current Dealing With Virus Infection Blocking Attachments at the Client Page Disaster Recovery Procedures Backing Up Page Offline Backup Disk Imaging Restoring Recovering Individual Messages Recovering Lost Mailboxes Recovering Exchange Stores and Storage Groups Full Exchange Server Recovery Recovering Exchange After Active Directory Failure Alternate Server Recovery Recovery Testing Page Page Support Providing Support for End Users Reducing End User Support Costs Page Problem Reporting Dealing with User Problems Notifying Users Exchange Problem Management Page Page Glossary