Exchange 2003 Transaction Logs

Just ran into an issue where the mail store would not mount.  Deleted the Tranaction Logs, Restarted Exchange Services, and the Store Mounted successfully with new transaction logs.  Is there a negative impact to doing this?  What are the short/long term affects, if any, when transaction logs are deleted.

(The original logs are backed up in case i have to revert back)
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Malli BoppeCommented:
You should never delete transaction logs.You should have run a incremental or a full exchange backup to purge the logs.When your exchange receives an email its not straight away written to database, its written to  transaction logs first and  some time later its written to exchange database.You would loose emails if these transaction logs were not written to the database.
More info about transaction logs

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
an excerpt from MS on removing log files manually:
If you remove a log that contains data that has not yet been written to the database files, the databases will no longer be mountable after an abnormal stop. Therefore, you must determine which logs are safe to remove before you manually remove any Exchange Server transaction log files.
In your case they must've already committed the data to exchange and were no longer needed :-). For future reference if you don't have a current backup of the transaction logs move them instead of deleting them so you can back them up or restore ones that you may need to mount the store.
Sometimes you have to do this but it is better to be safe than sorry.
Hope this helps.
I would say you were pretty lucky with that.
1st the reason why your store would have dismounted is that the log file directory drive would have run out of space.
2nd Once the log drive fills up the exchange application shuts down the stores bringing the database files into consistent state. A consistent database file would not require any log file. Hence after deletion of log files you were able to mount the stores.
(Incase the database would be inconsistent with even a single log file required, you would have regretted on your decision. Unable to retrieve the deleted log file would have cost you to either restore database from backup or  else to repair. Both are time consuming)

Following are few articles which you can refer for better maintainace of log files:

How to remove Exchange Server transaction log files

Transaction Logs, The Lifeblood of Exchange

Understanding the Exchange Information Store
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

The logs can be used to restore lost data to your database after you have restored it from a backup.

With no logs you can not update the restored database & then you will have missing emails.

The logs are wiped after a full backup.

If you need to remove them yourself you should keep a copy of them somewhere until a full backup of exchange is made.
If you are right out of space, a quick trick is to compress the oldest 95% (or so) of transaction logs - compress, not zip up - just select the oldest ones, right click, advanced, compress. They are text files so compress quite well.

Then, as stated, do a backup - the real issue with messing with transactions logs is that a) it is abundantly clear that your backup is inadequate (otherwise you wouldn't have log problems) and b) if your databases are even just a little unhappy with life, you now have unmountable stores AND weak backups.

capitalcitycomputersAuthor Commented:
Thanks for the feedback.  Everyone gets points
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.