分类：
2006-10-29 11:22:07
如何更改Exchange2003邮件数据库16GB的限制How to change Exchange 2003 Database size limited to 75GB
How to increase the Exchange Server 2003 Service Pack 2 18GB database size limit
周从所知，Exchange2003 standard标准版及Exchange2003 SBS(small business)版的数据库都有16GB的限制，但在Exchange server 2003 SP2了布后，这个问题得到进步的放宽，数据库可达75GB，而，即使你安装SP2后，你的数据库的默认大小仍在18GB的限制中，这时你在系统日志中会收到如下“事件ID:9690”的事件提示，那么，要怎样才能解除Exchange 2003数据库的18GB限制呢？本文指引用户通过修改注册表的方式来解除18GB的限制。为防止数据库的不良急速增大，文中还有如何设置数据库大小限制及预警的相关说明。
事件类型: 错误
事件来源: MSExchangeIS Mailbox Store
事件种类: 常规
事件 ID: 9690
日期: 2006-10-29
事件: 5:00:47
用户: N/A
计算机: SERVER
描述:
Exchange 存储“第一个存储组\邮箱存储(SERVER)”: 此数据库的逻辑大小(逻辑大小等于 .edb 文件和 .stm 文件的物理大小减去各自的逻辑可用空间)为 18 GB。此数据库大小已超出大小限制 18 GB。
此数据库将被立即卸除。
有关详细信息，请单击 。
事件类型: 错误
事件来源: MSExchangeSA
事件种类: MAPI 会话
事件 ID: 9175
日期: 2006-10-29
事件: 5:09:07
用户: N/A
计算机: SERVER
描述:
MAPI 调用“OpenMsgStore”失败，返回以下错误:
试图登录到 Microsoft Exchange Server 计算机失败。
MAPI 提供程序失败。
Microsoft Exchange Server 信息存储
ID 号: 8004011d-0512-00000000
有关详细信息，请单击 。
事件类型: 错误
事件来源: MSExchangeFBPublish
事件种类: 常规
事件 ID: 8197
日期: 2006-10-29
事件: 7:17:00
用户: N/A
计算机: SERVER
描述:
初始化虚拟机 SERVER 的会话时出错。错误号码: 0x8004011d。请确保 Microsoft Exchange 存储正在运行。
详细信息，请单击 。
事件类型: 信息
事件来源: MSExchangeIS Mailbox Store
事件种类: 常规
事件 ID: 1216
日期: 2006-10-29
事件: 8:43:54
用户: N/A
计算机: SERVER
描述:
Exchange 存储“第一个存储组\邮箱存储(SERVER)”被限制为 18 GB。此数据库(.edb 文件和 .stm 文件)的当前物理大小为 18 GB。如果此数据库的物理大小减去其逻辑可用空间后超出 18 GB 的限制，则此数据库将被定期卸除。
有关详细信息，请单击 。
Prior to Microsoft Exchange Server 2003 Service Pack 2 (SP2), there was no method to configure database size limits for Exchange Server 2003. Exchange Server 2003 SP2 introduces the following new features: 在发布SP2前，用户是无法自行设置数据库大小限制的。SP2提供了这个特性设置。
| • |
For the Standard Edition, the default configured database size limit will now be 18 GB, a 2 GB addition to the previous limit, with a new maximum size of 75 GB.标准版在安装SP2后，默认限制为18GB，比之前增大了2G，但最大可达75GB。 |
| • |
For the Enterprise Edition, there is no default configured database size limit, and no software set maximum size.企业版中，默认没有限制数据库大小，但在安装SP2之前不提供限制大小设置。 |
| • |
Both versions of Exchange Server 2003 with SP2 have the ability to configure a limit, a warning threshold, and a warning interval set through registry keys.2003的所有版本在安装SP2后都提供通过修改注册表来进行数据库大小限制、预警阀值及警示间隔等的设置。 |
| • |
Size check done against the database now uses logical database size. Empty or white space in the database does not count against the configured database size limit; therefore, no offline defragmenting is required for recovery exceeding the configured or licensed database limits. |
| • |
Limit checks, done at regular intervals, are now controlled by the store process instead of JET. The time interval is 24 hours and this interval is configurable through the registry. |
| • |
The database size limit registry keys are read when the database mounts (not when the service starts up), and when each limit check task runs.注册表中相关的限制值是在数据库加载时读取的，而不是在服务启动时加载的。当然在下一次的计划检测时也会被自动读取。 |
You must set registry parameters for each database targeted for size limit modification. The registry entries should be located under each database entry in the local server registry. Accordingly, you must reset the registry keys manually if the server has to be rebuilt using the /disasterecovery setup switch.你必须为每个数据库单独进行相关参数设置(如果你有多个储存组/数据库)，在进行数据恢复后，你要去检查一遍相关的设置，因为这些参数都是在本地保存的。
Note小心注意Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.请谨慎操作注册表，不当的操作可能会带来灾难性的后果，甚至要重装你的系统。请操作前进行备份，以便恢复需要。
All registry settings discussed in this topic are created in the following registry location:所有的相关设置都是在下面这个注册表子键下面进行操作的。
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\
The GUID in this key (Private-013e2e46-2cd7-4a8e-bfec-0e4652b94b00) is an example and should match the value of the objectGUID attribute on the database’s Active Directory object.最末的那串值须视你的实际GUID而定。
Note小提示By default, registry entries mentioned in this article are not present; when you create the entry, you override the default value set in code.下文提到的默认值仅供参考，你可以不作理会，视实际情况而自行设定。
Note备注All of registry values mentioned in this article are in decimal, not hexadecimal.所有提及的值是十进制的数值，而不是十六进制。请注意选择!
| • |
The following new registry settings are available with SP2: 所有设定只在安装了SP2的环境下才生效。 |
| • |
Database Size Limit in GB数据库大小限制的单位是GB。 |
| • |
Database Size Buffer Warning in Percentage数据库缓冲池的警示阀值是百分比值 |
| • |
Database Size Check Start Time in Hours from Midnight数据库大的检测时间是由午夜0:00起计。 |
The Database Size Limit in GB setting is the configurable maximum size of a database not to exceed the maximum licensed size of your database. For Standard Edition, you can set the database size limit between 1 and 75 GB. By default, the limit is 18 GB. For Enterprise Edition you can set the database size limit between 1 and 8,000 GB. By default, there is no limit.我老婆蝈蝈在催我去买菜了，我就不翻译下去了，下面的内容没有什么重要的了，照着下面的表新建几个DWORD值就可以了。PLUMLEE下次有空再翻译吧。
The following registry value controls the Configurable Database Size Limit:
| Data type | Name | Value (in GB) | Default (in GB) |
|
REG_DWORD |
Database Size Limit in GB |
Standard: 1-75 Enterprise: 1-8000 |
Standard: 18 Enterprise: 8,000 Unlimited |
The Database Size Buffering Warning in Percentage setting is a configurable error threshold that will warn you with an event log entry when your database is at or near capacity, and will shut down within 24 hours of the event being logged. By default, Exchange Server 2003 SP2 logs events when the database has grown to within 10 percent of the configured database size limit. This threshold is configurable. The smallest buffer is 1 percent of the configured size limit.
The following registry value controls the Database Size Buffer Warning:
| Data type | Name | Value (in %) | Default (in %) |
|
REG_DWORD |
Database Size Buffer Warning in Percentage |
1 - 100 |
10 |
The Database Size Check Start Time in Hours from Midnight setting allows you to configure when the system will check your database to see if it is over the currently configured Database Size Limit. By default, the database size check happens at 05:00 (5:00 A.M.) every day. This time can be changed. If 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 at least 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 Hours from Midnight |
1 - 24 |
5 |
Determines the hour the first database size check will occur after a database is mounted. |
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 below this 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 is less than the warning threshold, so the size check should take under a millisecond to complete. If the free space calculation must be performed, the size check 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 is reached:
| • |
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 corrective actions.
Exchange Server 2003 Standard Edition is limited to a single storage group with a single private information store database and a single public folder database. Prior to SP2, each database was limited to 16 GB of total physical size. SP2 increases the licensed database size limit for Exchange Server 2003 Standard Edition from 16 GB to 75 GB; the default configured database size limit will be 18 GB. Exchange Server 2003 Enterprise Edition storage group and Exchange 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 |
NoteThe current hard coded limit of the JET database is 8,192 GB, or 8 terabytes (TB).
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 you increase 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 that you 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 level agreement 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 mailbox store to 20 GB or larger.
For information about service level agreements, see "Establishing a Service Level Agreement" in "Setting Availability Goals" in the .
For information about how to configure database size limit options, see "Configure Database Size Limits" in the Exchange Server 2003 SP2 online Help.
