General discussion


Exch 2K3 Transaction logs.

By Tim Marshall - Houston ·
Is there a way to manually flush the Exchange 2003 Transaction logs, by shutting down the services or dismounting the store. I thought that if you did this then Exchange would commit those transactions and then flush the logs. I haven't been able to do a backup for several days and until I can fix that I would like to this manually. Thanks.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by Arne.Tredal In reply to Exch 2K3 Transaction logs ...

The transaction logs are there to keep track of what has happened since your last successful backup. If you remove any of them you are in danger of loosing data.

If you take the risk, you can turn circular logging "ON" until you are able to do backup again. BUT be aware of potential dataloss.

Collapse -

by azizhakim In reply to Exch 2K3 Transaction logs ...

Transaction logs are there as a recovery measure and performance.Before data gets written to database the logs are temporary repository.the checkpoint file monitors which logs have been indeed flushed to database.When you dismount the database that is when Exchange flushes all logs to respective Db.Then your DB is in consistent state(If by accident your server loses power and shuts off you are in inconsistent state and Exchange does a soft recovery where it goes thru all logs and commits and starts service)
Now from your question it appears you are low on disk space and want to remove old log files CORRECT?
Old log files will be purged when you do an inc or full backup.if you dismount and mount the db's,you log files will be commited to db but will not be purged.NB this setting can be configured in ESM/server/properties/remove log file age.To manually remove the committed log files from disk you will need to do a checkpoint file dump and find find which log files are the current and remove earlier.I will refer youto KB Article 240145 and 182961 for method.NB microsoft points to it for Exchange 5.5 but although I have done this it should work for exch 2000 & 2003.Perhaps another techie can contribute on this issue.Hope this helps

Related Discussions

Related Forums