[ExchangeList] Re: Exchange Transaction Logs

  • From: Rick Boza <rickb@xxxxxxxxxxxxxxx>
  • To: exchangelist@xxxxxxxxxxxxx
  • Date: Wed, 28 Jan 2009 10:44:20 -0500

There's a version of NTBackup that ships with Exchange server that will work just fine.  Or, if you already have a backup solution, chances are that has an Exchange agent capable of online Exchange backups which would then roll the logs for you.

There's no administrative overhead to rolling the logs, that happens automatically when the backup completes (well, as it completes, but that's a nit).

Presumably you're already backing up all your data, so expanding that to cover your Exchange data shouldn't be all that complicated, and is a good investment of both time and resources.


On Wed, Jan 28, 2009 at 9:32 AM, Ben Zaki <abenzaki@xxxxxxxxxxx> wrote:
Thanks for the info. Just thought there was a seamless way to manage these logs. Any recommendations on a not-so-expensive backup solution?

Sent: Tuesday, January 27, 2009 11:06 AM
Subject: [ExchangeList] Re: Exchange Transaction Logs

Each time you generate a full backup of your Exchange system, old transaction logs are automatically flushed (that is, removed).


Apparently, you are not doing full backups of Exchange. You should start doing this. Preferably, at least daily.




Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP

My blog: http://TheEssentialExchange.com/blogs/michael

I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php


From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Ben Zaki
Sent: Tuesday, January 27, 2009 11:02 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Exchange Transaction Logs




I would like to know what you would recommend as the best way to manage the exchange transaction logs. How are you managing your transaction log files?


We are a small organization with one exchange server but the amount of logs it generates is overwhelming. This is due to the numerous system and network email alerts that are generated and sent to the network and production support group. The server has two partitions (C and D drives) and exchange is on C. Currently, what I do on a weekly basis is simply copy the old logs (any logs older than two weeks ) to the D drive, zip the logs and then go back and delete the copied logs from the C drive. I then keep the zipped logs on the D drive for 1 month before deleting them. This way I have a backup if I need them. This is now getting to be old and tiresome and I'm looking for a better way to manage these logs.


I have considered circular logging but since this is not recommended in a production environment I don't know if that's the way to go. Any help would be appreciated.



Other related posts: