Understanding the Exchange 2010 Store

Artikel
05/20/2011

[Dieses Thema ist in Bearbeitung.]

Gilt für: Exchange Server 2010

Letztes Änderungsdatum des Themas: 2009-10-14

The Exchange store is a storage platform that provides a single repository for managing multiple types of information in one infrastructure. The Exchange store (store.exe) is the core data storage repository for Exchange Server 2010.

Logical Components of the Exchange Store

The primary components of the Exchange store are mailbox databases and public folder databases. These components can reside on a single server, or they can be distributed across multiple servers.

Mailbox databases contain the data, data definitions, indexes, checksums, flags, and other information that comprise mailboxes in exExchange2010. Mailbox databases hold data that is private to an individual user and contain mailbox folders that are generated when a new mailbox is created for that user. A mailbox database is stored as an exExchangeNoVersion database (.edb) file.

Public folder databases contain the data, data definitions, indexes, checksums, flags, and other information that comprise any public folders in your exExchangeNoVersion organization.

In Exchange 2010, you manage public folders by using the Exchange Management Shell. (You can also perform a limited number of public folder database management tasks in the Exchange Management Console.) For more information about managing public folders, see Verwalten von Öffentlichen Ordnern and Grundlegendes zu Öffentlichen Ordnern.

File Structure of the Exchange Store

You manage the Exchange store by working with its logical components, such as databases. However, Microsoft Exchange 2010 stores data in a specialized set of data files, such as Exchange database (.edb) files, transaction logging (.log) files, and checkpoint (.chk) files. Unless you are backing up or restoring data, you will rarely interact with these files directly.

exExchangeNoVersion database (.edb) files are the repository for mailbox data. They are accessed by the ESE directly and have a B-tree structure that is designed for quick access, thereby enabling users to access any page of data within four I/O cycles. The exExchangeNoVersion database is composed of multiple B-trees, with ancillary trees that work with the main tree by holding indexing and views.

Checkpoint (.chk) files store information that indicates when a transaction is successfully saved to the database files on the hard disk. exExchange2010 uses checkpoint files to allow an instance of the ESE to automatically replay log files into an inconsistent database when recovering from a service interruption, starting with the next unwritten transaction. The checkpoint files are placed in the same log location as the log files.

Understanding Transaction Logging

This section describes the details of transaction logging in Exchange 2010 and includes a brief description of circular logging.

Exchange Server transaction logging is a robust recovery mechanism of the Extensible Storage Engine (ESE) that is designed to reliably restore an Exchange database to a consistent state after any sudden stop of the database. The logging mechanism is also used when restoring online backups.

Exchange Transaction Logging

Before changes are made to an Exchange database file, Exchange writes the changes to a transaction log file. After a change has been safely logged, it can then be written to the database file. It is common for these changes to become available to end users just after the changes have been secured to the transaction log, but before they have been written to the database file.

Exchange employs a sophisticated internal memory management system that is tuned for high performance and can efficiently manage the caching of dozens of gigabytes (GBs) of database pages. Therefore, physically writing out changes to the database file is a low-priority task during normal operation.

If a database suddenly stops, cached changes are not lost just because the memory cache was destroyed. When the database restarts, Exchange scans the log files, and reconstructs and applies any changes not yet written to the database file. This process is called replaying log files. The database is structured so that Exchange can determine whether any operation in any log file has already been applied to the database, needs to be applied to the database, or does not belong to the database.

Rather than write all log information to a single large file, Exchange uses a series of log files, each exactly one megabyte, or 1,024 kilobytes (KB), in size. When a log file is full, Exchange closes it and renames it with a sequential number. The first log that is filled ends with the name Enn00000001.log. The nn refers to a two-digit number known as the base name or log prefix.

Log files for each database are distinguished by file names with numbered prefixes (for example, E00, E01, E02, or E03). The log file currently open for a database is simply named Enn.log—it does not have a sequence number until it has been filled and closed.

The checkpoint file (Enn.chk) tracks how far Exchange has progressed in writing logged information to the database files. There is a checkpoint file for each log stream, and a separate log stream for each database. All the databases share a single log stream. Thus, a single log file often contains operations for multiple databases.

Log files are numbered in a hexadecimal manner, so the log file after E0000000009.log is E000000000A.log, not E0000000010.log. You can convert log file sequence numbers to their decimal values by using the Windows Calculator (Calc.exe) application in Scientific mode. To do this, run Calc.exe, and then, from the View menu, click Scientific.

To view the decimal sequence number for a specific log file, you can examine its header by using the Exchange Server Database Utilities (Eseutil.exe) tool. The first 4-KB page of each log file contains header information that describes and identifies the log file and the databases it belongs to. The command Eseutil /ml [log file name] displays the header information.

If you use the wrong switch for displaying a header (for example, by using /ml with a database header instead of /mh), an error is displayed or the header information that is displayed may be garbled or incorrect.

You cannot view the header of a database while it is mounted. You also cannot view the header of the current log file (Enn.log) while any database is mounted. Exchange holds the current log file open as long as one database is using it. You can, however, view the checkpoint file header while databases are mounted. Exchange updates the checkpoint file every thirty seconds, and its header is viewable except during the moment when an update is occurring.

As an Exchange administrator, it is valuable to understand Exchange file headers. If you understand the file headers, you can determine which database and log files belong together and which files are needed for successful recovery.

In the following log file header example, note the first four lines.

Base name: e00
Log file: e00.log
lGeneration: 11 (0xB)
Checkpoint: (0xB,7DC,6F)

These log file header lines show that this log file is the current log file because the log file name does not have a sequence number. The lGeneration line shows that when the log is filled and closed, its sequence number will be B, corresponding to the decimal value 11. The base name is e00, and therefore the final log file name will be E000000000B.log.

The Checkpoint value in the previous header example is not actually read from the log file header, but it is displayed as if it were. Eseutil.exe reads the Checkpoint value directly from Enn.chk, so you do not have to enter a separate command to learn where the checkpoint file is. If the checkpoint file has been destroyed, the Checkpoint value reads NOT AVAILABLE. In this case, the checkpoint is in the current log file (0xB), and the numbers 7DC and 6F indicate how far into the log file the checkpoint is. Note that you will seldom have a practical need for this information.

If the checkpoint file is destroyed, Exchange can still recover and replay log files appropriately. But to do so, Exchange begins scanning log files, beginning with the oldest file available, instead of starting at the checkpoint log. Exchange skips data that has already been applied to the database and works sequentially through the logs until data that must be applied is encountered.

Typically, it takes only one or two seconds for Exchange to scan a log file that has already been applied to the database. If there are operations in a log file that must be written to the database, it can take anywhere from 10 seconds to several minutes to apply them. On average, a log file's contents can be written to the database in 30 seconds or less.

When an Exchange database shuts down normally, all outstanding data is written to the database files. After normal shutdown, the database file set is considered consistent, and Exchange detaches it from its log stream. This means that the database files are now self-contained—they are completely up to date. The transaction logs are not required to start the database files.

You can tell whether a database has been shut down cleanly by running the command Eseutil /mh and examining the file headers.

With all databases disconnected and in a Clean Shutdown state, all log files can be safely deleted without affecting the databases. If you were then to delete all log files, Exchange would generate a new sequence of logs starting with Enn00000001.log. You could even move the database files to a different server that has existing log files, and the databases would attach themselves to a different log stream.

Hinweis

Although you can delete the log files after all databases have been shut down, doing so will affect your ability to restore older backups and roll forward. The current database no longer needs the existing log files, but they may be necessary if you must restore an older database.

If a database is in a Dirty Shutdown state, all existing transaction logs from the checkpoint forward must be present before you can mount the database again. If these logs are unavailable, you must repair the database by running the command Eseutil /p to make the database consistent and ready to start.

Warnung

If you have to repair a database, some data will be lost. Data loss is frequently minimal; however, it may be catastrophic. After running Eseutil /p on a database, you should completely repair the database with the following two operations: First, run Eseutil/d to defragment the database. This operation discards and rebuilds all database indexes and space trees.

In addition to allowing Exchange to recover reliably from an unexpected database stop, transaction logging is also essential to making and restoring online backups. For more information about making and restoring online backups, see Grundlegendes zu Sicherung, Wiederherstellung und Notfallwiederherstellung.

Circular Logging

Although it is not recommended as a best practice, you can configure Exchange to save disk space by enabling circular logging. Circular logging allows Exchange to overwrite transaction log files after the data that the log files contain has been committed to the database. However, if circular logging is enabled, you can recover data only up until the last full backup.

In the standard transaction logging that is used by Exchange 2010, each database transaction is written to a log file and then to the database. When a log file reaches one megabyte (MB) in size, it is renamed and a new log file is created. Over time, this results in a set of log files. If Exchange stops unexpectedly, you can recover the transactions by replaying the data from these log files into the database. Circular logging overwrites and reuses the first log file after the data it contains has been written to the database.

In Exchange 2010, circular logging is disabled by default. By enabling it, you reduce drive storage space requirements. However, without a complete set of transaction log files, you cannot recover any data more recent than the last full backup. Therefore, in a normal production environment, circular logging is not recommended.

For information about how to enable and disable circular logging, see Konfigurieren der Eigenschaften einer Postfachdatenbank.

Extensible Storage Engine

Exchange mailbox databases and the queue on Hub Transport servers and Edge Transport servers utilize the Extensible Storage Engine (ESE) database. ESE is a multi-user, indexed sequential access method (ISAM) table manager with full data manipulation language (DML) and data definition language (DDL) capability. ESE allows applications to store records and create indexes to access those records in different ways. For more information about ESE, see https://technet.microsoft.com/en-us/library/bb310772.aspx. For improvements in Exchange 2010 ESE, see New Exchange Core Store Functionality.

Storage Features in Editions of Exchange 2010

Exchange 2010 is available in two server editions: Standard Edition and Enterprise Edition. Exchange 2010 Standard Edition is designed to meet the messaging and collaboration needs of small and medium corporations, and it may also be appropriate for specific server roles or branch offices. Exchange 2010 Enterprise Edition is designed for large enterprises.

Exchange 2010 Standard Edition supports five databases. Exchange 2010 Enterprise Edition supports 100 databases.

Improvement to Store Health and Resilience

The Exchange Store has been improved to better handle poison mailboxes and thread timeouts. Improvements have also been made on the reporting and alert features to signal an unhealthy Exchange Store state.

Poison Mailbox Detection and Correction

A single mailbox with corrupt data (logical or physical) may in some cases cause the Exchange Store to crash, and deny service to all mailboxes hosted by the server. Similarly, a poison mailbox could also cause the Exchange Store to repeatedly crash. This section describes the actions the Exchange Store will take to detect and cut off poison mailboxes.

Isolating the Poison Mailbox

There are two types of events for which the Exchange Store will tag a mailbox as a potential threat:

if a thread that is doing work for that mailbox crashes
if there are more than 5 threads in that mailbox that have not made progress for a long time

A mailbox that is a potential threat will be tagged, along with a count of how many times it has been tagged as such. This information is stored in the registry. The Exchange Store will also keep timestamp information on when the mailbox was identified as a potential threat.

During a database mount, the Exchange Store will read the time which the mailboxes were identified as potential threats. If more than two hours has elapsed, the registry key for the mailbox will be wiped out. The advantage of keeping this information in the registry is that in a high availability environment, it is replicated by the cluster database, so even during an Exchange Store failover, the other machines have this information. The registry path used for isolating the poison mailbox will be:

HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server Name>\Private-{db guid}\QuarantinedMailboxes\{mailbox guid}

There will be the following keys for this path – CrashCount, LastCrashTime.

The settings for how many crashes lead to quarantining a mailbox as well as how long a mailbox should stay quarantined are stored as the following keys, MailboxQuarantineCrashThreshold and MailboxQuarantineDurationInSeconds in this registry path:

HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server Name>\Private-{db guid}\QuarantinedMailboxes

The default values for these keys are three crashes for MailboxQuarantineCrashThreshold and six hours for MailboxQuarantineDurationInSeconds.

Acting on the Poison Mailbox

By default, if a mailbox is identified as causing a crash/deadlock three times within two hours, the Exchange Store tags it as quarantined in the registry. No access is allowed to the mailbox unless OPEN_AS_ADMIN flag is passed. None of the Exchange processes (CI, Assistants, etc) will be allowed to logon. The QuarantineState and QuarantineTime registry keys will keep track of whether the mailbox is quarantined. If the mailbox hasn't caused any crashes in the last two hours and is not quarantined, the registry path for the mailbox will be cleaned up by the Exchange Store. If a mailbox has been quarantined for longer than MailboxQuarantineDurationInSeconds since it’s LastCrashTime, it will be released from quarantine automatically.

Resetting the Quarantined Mailbox

When the cause of the poison mailbox has been identified and corrected, the registry key for the quarantined mailbox should be reset manually by deleting it. However, if this manual step is forgotten, the Exchange Store will automatically reset quarantined mailboxes six hours after the quarantined flag was set. If the issue has not been debugged and fixed within that time period, this may lead to another set of crashes before the mailbox/message is re-quarantined.

Hinweis

The database hosting the mailbox needs to be remounted, or the Exchange Store restarted, for the reset of the quarantined mailbox to take effect.

The time period for resetting quarantined mailboxes can be controlled by the registry key:

HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<Server Name>\Private-{db guid}\QuarantinedMailboxes\MailboxQuarantineDurationInSeconds.

Reporting and Alerts

You can use the Get-MailboxStatistics cmdlet to report on the quarantined state of a mailbox. The Exchange Store has a performance monitor counter for the number of quarantined mailboxes. The counter name is MSExchangeIS Mailbox\Quarantined Mailbox Count.

The Exchange Store will also write an event whenever it quarantines a mailbox, with details on which mailbox and what time. The event 10018 identifies a quarantined mailbox.

Timeout Detection and Reporting

Another indication of an unhealthy Exchange Store is that threads are either deadlocked or otherwise not making any progress. If there are more than five threads on a single mailbox, ten threads on a single database or twenty threads on a single server that has not made progress in one minute, a timeout is reported on the server. The performance counter that indicates detected timeouts is MSExchangeIS\ RPC Request Timeout Detected.

The Exchange Store will also write the following events to the server:

10025 - reports a timeout on the Exchange server
10026 - reports a timeout on the database
10027 - reports a timeot on an individual mailbox

If the timeout is detected on a single mailbox, the mailbox is considered potentially poison, and is handled similar to a crash by increasing the CrashCount. This makes it susceptible to being quarantined.

Low Disk Space on Database Logs or Database Drives

When the Exchange Store detects that the space available on a log or database drive is below 1GB, it cuts off all transport delivery to that database(s). This is to prevent a disk running out of space. When a disk runs out of space the database can't be mounted or debugged. The database space also can't be reclaimed. This is a self-protecting mechanism that will only trigger if you don't react to the space issue warnings from your monitoring infrastructure.

When the disk space goes above 1.5GB, the Exchange Store will allow deliveries to continue. The following performance counter indicate this behavior:

MSExchangeIS Mailbox\ Delivery Blocked: Low Database Space
MSExchangeIS Mailbox\ Delivery Blocked: Low Log Space