Shulou(Shulou.com)06/02 Report--

A netizen mistakenly deleted the log file of the mailbox database resulting in an error and the mailbox database could not be mounted.

Error report:

Solution:

First, use the data recovery software to find the mistakenly deleted log file and report the following error after recovery: (you can only have a try, it may be useful to delete it just now)

"Morning 10:20:40 on 2018-06-04

Information Store-Mailbox Database B (50196) Mailbox Database B: database recovery failed with error-1216 due to a reference to a database "E:\ Database\ Mailbox Database B.edb" that no longer exists. The database is not in the Clean closed state until it is deleted (or possibly moved or renamed). For this example, the database engine does not allow the recovery process to complete until the lost database is reset. If the database is no longer available and no longer needed, refer to the steps provided in the Microsoft knowledge Base to resolve the error, or click the details link at the bottom of this message. "

Note: the isinteg command mentioned below does not necessarily apply to higher versions of EXCHANGE, nor is it a necessary command for repair.

TIPS: Isinteg is a utility that searches the offline information store for integrity defects. You can also fix problems detected by Isinteg. Isinteg runs at the command prompt.

Second, use the eseutil command to repair

Execute ESEUTIL / MH to see if state is dirtyshutdown or cleanshutdown.

1. Soft repair can be performed if it is in clean shutdown state

Note: a basic assumption of the soft recovery process is that the failure did not move, delete, or destroy any database or log files, nor did the administrator do so after the failure.

Run exeutil / r, then use isinteg.exe to repair the Pub1 and Priv1 database isinteg-s (servername)-fix-test alltests, restart the information storage service, and mount the database.

two。 Hard repair needs to be performed in the case of dirtyshutdown status. (more often in this state)

2.1 eseutil / r E01 / D / I

Even if you run a hard fix, it is recommended that you first use the eseutil / r command to try to fix the logic error.

TIPS: here are some things about soft fixes:

1. One of the basic requirements of soft repair is: {the fault did not move, delete, or destroy any database or log files, nor did the administrator do so after the failure.

two。 Introduce the parameters.

/ R: soft repair parameter

/ E01: the name of the logging file and cannot contain a suffix. 01 is the sequence number created by the ex database, for example, the first database log file is E00.LOG, the second database log file is E01.LOG, and so on.

The name of the log file is found under the installation directory-- "mailbox directory -" under the database name!

/ I: the restored database is in an abnormal shutdown state (Dirty shutdown state), please use this parameter

/ D: ignore database errors.

2.2 eseutil / mh

Then execute eseutil / mh again to check the status

2.3 eseutil / p

Cut all the log, chk, temp.edb files in the database folder to another folder and execute the eseutil / p command until the repair is complete.

{Note: you can also repair ESEUTIL / P directly, and remove all files such as log, chk, temp.edb and so on when you try to mount them.

2.4 eseutil / d

Perform eseutil / d for defragmentation, and failure to defragment may result in database indexing and space allocation errors. (recommended implementation of the production environment, or can be skipped)

2.5 isinteg-s (servername)-fix-testalltests (skipped, EX13\ 16 did not test this command)

You should be able to mount the database normally at this point. In order to repair the database at the application level to execute the above command, the database must be offline. If mounted, dismount the database.

After the isinteg is complete, zero errors should be reported in the database. If the error count is greater than zero, run Isinteg again until the count changes to zero, or does not decrease in subsequent runs. If the error count cannot be returned to zero, it is recommended to migrate the database later.

Third, after the repair, mount the database and restart the information storage service.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.