8/6/2019 Database Size Limit Configuration and Management in Exchange 2003 Sp2

http://slidepdf.com/reader/full/database-size-limit-configuration-and-management-in-exchange-2003-sp2 1/2

8/6/2019 Database Size Limit Configuration and Management in Exchange 2003 Sp2

http://slidepdf.com/reader/full/database-size-limit-configuration-and-management-in-exchange-2003-sp2 2/2

modified, the next task is scheduled at the new Offset hour. Checks at Database Size Check Interval are skipped until new start time.

First database size check will not take the database offline if the size limit has been exceeded. Because the database does not go offline, you are ensured atleast 24 hour of availability after the limit is exceeded for default settings.

Data type Name Values Default Description

REG_DWORD Database Size Check Start Time in Hoursfrom Midnight

1 -24

5 Determines the hour the first database size check will occur aftera database is mounted.

Behavior When the Configured Database Size Limit or Licensed Database Size Limit Are Reached

When a database mounts, the store process compares the physical database size against the Configured Database Size Limit in GB. If the physical size is

within or exceeds the configured Database Size Warning Buffer in Percentage, the store performs a logical calculation of the database size. If it is belowthis warning buffer, there is no need to calculate the free space because the logical size will never exceed the physical size. Generally, the physical size isless than the warning threshold, so the size check should take under a millisecond to complete. If the free space calculation must be performed, the sizecheck may require a few seconds to parse through the database to generate the logical size calculation.

If the Database Size Warning Buffer in Percentage is reached or exceeded, an error event, event ID 9688, is logged in the Application event log.

With Exchange Server 2003 SP2 or later, the server performs the following tasks when the configurable (or default configured) database size limit isreached:

If the first check after a database mount finds the database size above the limit, the database will not be taken offline but an error event (ID

9689) will be logged in the Application event log.

If it is the second check, an error event will be logged in the Application event log and the database will be taken offline.

After the administrator remounts the database, he or she has 24 hours (or until the next database size check or 05:00 if the default is set) to take correctiveactions.

Licensed Database Size Limit

Exchange Server 2003 Standard Edition is limited to a single storage group with a single private information store database and a single public folderdatabase. Prior to SP2, each database was limited to 16 GB of total physical size. SP2 increases the licensed database size limit for Exchange Server 2003Standard Edition from 16 GB to 75 GB; the default configured database size limit will be 18 GB. Exchange Server 2003 Enterprise Edition storage group andExchange store options do not change with the application of SP2. However, a configurable Exchange store size limit is added to the Enterprise Edition.

Exchange Server 2003 version Licensed limit Default configuration limit

Standard Edition before SP2 16 GB Not applicable

Standard Edition with SP2 75 GB 18 GB

Enterprise Edition before SP2 8,000 GB (unlimited) Not applicable

Enterprise Edition with SP2 8,000 GB (unlimited) 8,000 GB

Note:

The current hard coded limit of the JET database is 8,192 GB, or 8 terabytes (TB).

Disaster Recovery Planning Considerations

If you change the size limit of your Exchange databases, you may want to re-evaluate your Exchange database backup and restore plan. Specifically, if youincrease the size limit of the Exchange databases, be sure to test your backup and recovery operations using the new database size limits to make sure thatyou can still meet your service level agreements. For example, if the previous size of a mailbox store was 15 GB and you were able to meet your service levelagreement by recovering the data in less than 8 hours, you may no longer be able to recover the database that quickly if you increase the size of a mailboxstore to 20 GB or larger.

For information about service level agreements, see "Establishing a Service Level Agreement" in "Setting Availability Goals" in the Exchange 2003 HighAvailability Guide [ http://go.microsoft.com/fwlink/?LinkId=47571 ] .

For information about how to configure database size limit options, see "Configure Database Size Limits" in the Exchange Server 2003 SP2 online Help.

Tags:

Community Content

Incorrect Registry value name.   Last Edit 8:03 PM by Thomas Lee

The Name of the registry value "Database Size Buffer Warning in Percentage" is incorrect in the article.

The correct name for this registry value is Database Size Buffer in Percentage.

All other values are correct. We are working to get this topic corrected. Thanks.

Tags: contentbug contentbugfix

ase Size Limit Configuration and Management http://technet.microsoft.com/en-us/library/aa998066(EXCHG.65,pri

22/02/20