Using ESEUTIL to diagnose/repair an Exchange 2007 database
Eseutil: Exchange 2007 Help
Anyone who has dealt with Exchange knows that ESEUTIL is the tool you can use to do any type of repair or integrity check on your database. With Exchange 2007 this utility has been expanded to include repairing the new queue database for your Hub or Edge Transport servers as well.
Using ESEUTIL still requires that the database be offline so that you can do any type of activity to the database such as defragging to gain the free space back from an EDB file. Normal online maintenance can run while the database is up and functional but you cannot use those tools manually on your own. Normal defragmentation can take up to two weeks to occur in an online state so if you need the additional space immediately you will have to take the database offline in order to use ESEUTIL.
The major difference in the past is now the queues are in a database format and are no longer individual flat files that are kept in various folders on your server. This can be a good or bad thing depending on how you look at it. It is more difficult to get an idea if your queue is hosed or what the offending message may be so you will need to use the queue viewer in your toolbox of the Exchange Management Console or a PowerShell cmdlet in order to figure out what is going on. This database as I have recently learned can get corrupted so it is important to know that you may have to use ESEUTIL against this database as well - it is called mail.que by default on your box.
Anyone who has dealt with Exchange knows that ESEUTIL is the tool you can use to do any type of repair or integrity check on your database. With Exchange 2007 this utility has been expanded to include repairing the new queue database for your Hub or Edge Transport servers as well.
Using ESEUTIL still requires that the database be offline so that you can do any type of activity to the database such as defragging to gain the free space back from an EDB file. Normal online maintenance can run while the database is up and functional but you cannot use those tools manually on your own. Normal defragmentation can take up to two weeks to occur in an online state so if you need the additional space immediately you will have to take the database offline in order to use ESEUTIL.
The major difference in the past is now the queues are in a database format and are no longer individual flat files that are kept in various folders on your server. This can be a good or bad thing depending on how you look at it. It is more difficult to get an idea if your queue is hosed or what the offending message may be so you will need to use the queue viewer in your toolbox of the Exchange Management Console or a PowerShell cmdlet in order to figure out what is going on. This database as I have recently learned can get corrupted so it is important to know that you may have to use ESEUTIL against this database as well - it is called mail.que by default on your box.
posted by Rick Mitchell Solutions @ 12:30 PM
0 Comments:
Post a Comment
Links to this post:
Create a Link
<< Home