Hi, How to validate the exchange logs that is written to the database and flush the logs to free memory ? Right now i'm using ESEUTIL to check the log and db integrity. If the database is very large in numbers and size then ESEUTIL takes too long time to validate. The following are the tests done to validate the logs, 1. Eseutil with /k /i <edb file path> for checksum verification 2. Eseutil with /mk <chk file path> 3. Eseutil with /mh <edb file path> 4. Eseutil with /k <log prefix file path> So, i want to know that all these checks are necessary or only integrity check for log file (E00) with /k and database integrity check with /g is enough. Is it possible to check using any APIs ? Suggestions please.......... Thanks Inmar

Hi,so when you say DB and Log Validation, are you trying to check teh consistency of the Databse or you want to check the last log file which got committed to the DB or trying to get any logical error on the DB.I am not sure if any API is available that you can use to instead of eseutil commands.Raj

Hi, Thanks for the reply. I want to check both consistency of database and the last log file committed to the db with minimum type of test. should all the below mentioned test to be carried or can be reduced to check db consistency and last log file committed ? 1. Eseutil with /k /i <edb file path> for checksum verification 2. Eseutil with /mk <chk file path> 3. Eseutil with /mh <edb file path> 4. Eseutil with /k <log prefix file path> what about the CHKSGFILES API ? Any idea......... Thanks Inmar

So run eseutil /mh which will tell you the DB consistency. Any ways if the DB is not consistent, the stores will not mount.Eseutil /ml Similar to the /mh, except this switch performs an integrity check on log files, for example, E00.log. Eseutil /mm Dumps metadata from the database file (not the logs). Specialist use only, I find the output fascinating but not very useful. Eseutil /mk Provides information about the checkpoint file. Handy for troubleshooting backup / restore problems. Where /mh used priv1.edb, remember to substitute the name of the checkpoint file E00.chk with /mk.For more eseutil switches and commands http://www.computerperformance.co.uk/exchange2003/exchange2003_eseutil.htmRaj

Hi, Your information is very useful for me. ThanksAlso, is it possible to delete upto particular log using eseutil?ThanksInmar

You dont need to use eseutil to delete logs. I will not recommend this , still if you are sure that logs are already committed to the DB, you can delete the logs.I will suggest , let the incremental back up delete the logs. dont delete them manually.Raj

Thanks for your valuable suggestions. Here are my requirements, 1. Take a backup of a set of logs and a database file. 2. Run eseutil with required options (as you suggested) against logs and database. 3. Once those set of logs are written to the database is confirmed then delete those set of logs from the original exchange server. So, I have the options to check the log integrity and database consistency. But I don't find any options with eseutil to delete upto a particular log file. Is it possible to delete logs using eseutil ? For example, eseutil <delete option> <E00000017.log> for deleting upto E00000017.log file If so, Please provide the option. Is there any option or command to delete the logs other than eseutil? Thanks Inmar

Never heard of any command as such which can delete exchange transsaction logs. Always its either the incrmental back up or its a manual deletion after confirming, till which logs files are committed to the DB.Raj

ThankQ