For the patch operation to complete successfully, the database must be set to allow being overwritten by a restore procedure. To enable this setting, click to select the
This database can be overwritten by a restore check box in the database properties in Exchange System Manager.
- Start Exchange System Manager.
- Click to expand Servers, click to expand the server on which the database is located, and then click Storage Group.
- Right-click on the database, and then click Properties.
- Click the Database tab.
- Click to select the This database can be overwritten by a restore check box.
When you click this check box, it sets the Active Directory attribute,
msExchPatchMDB, to a value of TRUE. This value is stored in Active Directory at the following location:
CN=Database Name,CN=Storage Group Name,CN=InformationStore,CN=Server Name,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Org Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain Name,DC=com
If this check box is not selected (that is, if this value is stored as FALSE in Active Directory), and this information store requires a patch operation to start, this information store will not start, and the following event is written to the Event Viewer application log:
Event ID: 1087
Source: MSExchangeIS Mailbox
Type: Error
Description: The Information Store was restored from an offline backup. Indicate that the database is allowed to be restored to, in the Microsoft Exchange System Manager, so the database can be patched.
If the
This database can be overwritten by a restore check box is selected and the database requires a patch operation, Store.exe automatically patches the information store upon startup and the following event is written to the Event Viewer application log:
Event ID: 9524
Source: MSExchangeIS
Category: General
Type: Warning
Description: The Information Store database <DatabaseName> was restored from an offline backup - it has been patched. Please back up this database.
After Store.exe performs a patch against a database, clients logging on to that database may encounter a slight slowdown when loading the client for the first time since the patch was performed. When a patch is performed, it resets the per-user read/unread GUID on this store, and forces all clients to re-load their per-user read information from this database.