Exchange Transport queue What about the queue database getting bigger?

Hello everyone, today to share some of the maintenance operations of the Exchange database in daily management. We know that when I send a message, the message comes first to an exchange's staging queue database before it is submitted to the user's mailbox. Over time, the queue database size increases continuously (view the transport Queue database location to view the Queuedatabasepath in the EdgeTransport.exe.config file and the path that Queuedatabaseloggingpath points to as the queue database and log Location), the administrator is required to maintain the transport queue database, reduce the size of the transmission queue database, or move the transfer queue database to another disk. The increase in the size of the transmission queue database is typically caused by a large number of messages being sent or messages that send large attachments.

First, take a look at the file structure of the queue database. Where Mail.que is the queue message file, which is the queue database. Because the queue database is an Extensible Storage Engine (ESE) database, all have log checkpoint files. chk. log files. When the transmission queue database is designed, the circular log is automatically turned on, and the logs that have been written to the database are automatically purged.

650) this.width=650; "height=" 310 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/9E/D1/ Wkiol1mwupazfuudaam-hrbqchy783.png "border=" 0 "/>

What to do when transferring a queue database file:

Method One, regenerate the new transport queue database.

Method Two, the transmission queue database is organized to release the transmission queue database blank space. (This method also applies to the transport queue database because a large number of message deliveries are forced to stop and fail to start)

Method I believe that many people have tried to stop the Exchange transport service first and then C:\Program the directory to Files\Microsoft\Exchange Server\v15\transportroles\ The queue under data is renamed to a different name (for example: Queue.old), and then the transport server is restarted, which regenerates an information queue database. Before doing so, make sure that there are no messages in the current server's transport queue that are not yet posted, in order to prevent the loss of messages you can use the command get-queue to view the message queue situation.

650) this.width=650; "height=" 222 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/9E/D1/ Wkiol1mwupeqsgnxaadsbhbzmws806.png "border=" 0 "/>

The following is an emphasis on sharing method two, before the method two operations to determine which of the scenarios this method can be applied to:

1), when a large number of unsent messages are piled up in the transport queue database, the transport service does not start properly.

Method Two of the specific idea is to first copy and paste the transmission queue database to another alternate location (at this time the transport service should be in a stopped state), and then to the transmission queue database for log replay, disk defragmentation and repair operations, It is best to copy and copy the repaired queue database to the corresponding location in the queue database to replace the existing Queue database files (corresponding to the production server if the server transport service fails to start, but also timely resume normal mail delivery, but also to ensure that the data do not lose; At this point we can resume normal mail delivery , and then replicate the recovered queue database to another Exchange server's transport queue database, which is the responsibility of other Exchange servers to send unsent messages. It is important to note that the new Exchange server must be consistent with the version of the source Exchange server)

Below I share a step that I tested before

1. Copy the transfer queue database to the temp directory.

2. Open PowerShell, use the command eseutil.exe/mh "Queue database full path " To view the status of the database, if State:dirty Shutdown, the database is in an abnormal shutdown state, Log replay and database repair are required.

650) this.width=650; "height=" 357 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/9E/D1/ Wkiol1mwupirxsrfaadc7zhntym748.png "border=" 0 "/>

3, next use the command: esetuil/r trn/d "Queue database path"//"Log file path" to the database for log replay, if it fails, the fourth step.

650) this.width=650; "height=" title= "image" style= "Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/00/21/ Wkiom1mwupzr38rwaacz-h4ywla234.png "border=" 0 "/>

4, the transfer queue database after the log replay failed (soft repair), can only be hard fixed. Use the command: eseutil.exe/p "Database full path"/T "temp file directory"

650) this.width=650; "height=" 282 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/9E/D1/ Wkiol1mwupriz77uaacrbymplew516.png "border=" 0 "/>

5, next use the command: eseutil.exe/d "Database path"/t "temporary file storage path" to the transmission queue database data collation, free space.

650) this.width=650; "height=" 387 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/9E/D1/ Wkiol1mwupytej2-aajtvvrwegu096.png "border=" 0 "/>

6. Stop the transport server again, overwrite the repaired queue database with the existing transport queue database, and then start the transport service. (If the transport service fails to start, you need to cut out the rest of the files in the C:\Program files\microsoft\exchange server\v15\transportroles\data\queue directory, Keep only the Mail.que file, and then start the transport service. This is done to ensure that there are no undelivered messages in the current server's transport queue.

I encountered the following problem during execution, my workaround is to copy the queue database file to a different empty directory, and then run the command again to fix it.

650) this.width=650; "height=" 255 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/00/21/ Wkiom1mwuqddczagaacd3svpqbc248.png "border=" 0 "/>

This article from "Jialt blog" blog, declined reprint!

Exchange Transport queue What about the queue database getting bigger?