The Exchange transaction logs are 5 MB files that are used to ensure database integrity. When handling the storage of transaction log files, it is best to have separate mirrored disks that are dedicated for the storage of these files. The main advantage of this is that in the event of a disk failure the other mirrored disk will contain current logs that are necessary for the operation of the Exchange database.
The transaction log files tend to grow rapidly, especially if circular logging is disabled. This uses up a lot of disk storage space. Disabling circular logging, however, has its advantages, especially in the event that any of the Exchange database becomes corrupted. To reduce buildup of these logs, perform daily backups of the Exchange database.
If the Exchange server contains one disk that handles both the transaction logs and the Exchange database, and this disk becomes full DO NOT DELETE THE TRANSACTION LOGS. Perform a full database backup that will then flush out the old log files.
Adesh Rampat has 10 years experience with network and IT administration. He is a member of the Association of Internet Professionals, the Institute for Network Professionals, and the International Webmasters Association. He has also lectured extensively on a variety of topics.
Did you like this tip? If so, (or if not) why not let us know. Send an email to us and sound off. Or visit our tips page to rate this tip, or submit one of your own.
Related Book
Exchange 2000 Server Administration : A Beginner's Guide
Author : Bill English and Nick Cavalancia
Publisher : Osborne
Published : Mar 2001
Summary :
Implement and manage Microsoft's leading messaging and collaboration system using this instructive guide. You'll quickly learn everything you need to deploy and administer the system effectively, and learn about migration and coexistence with Exchange 5.5 Server. If you are a Windows administrator new to Exchange 2000 Server, this is the book for you.
