Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 422
  • Last Modified:

Way to Reduce Size of Exchange 2003 Transaction Logs While Preserving Incremental Backup Ability?

We've got limited space on our exchange server. Although the db is only about 16gb, and we've got 55 gb, believe it or not the daily transaction logs build up to almost fill the drive to capacity each day. If our backup fails for some reason, the store dismounts because the disk is full.

Is there a way to reduce the volume of transaction logs without compromising our ability to do incremental backups or any other big issues?

Cheers,

Jay
0
jbreg
Asked:
jbreg
  • 3
  • 3
  • 2
  • +1
2 Solutions
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
This may not be the best answer, but.... why don't you just get more disk space?
0
 
SembeeCommented:
Are you doing full backups every day?
If not, then you should. I don't do incremental backups of Exchange unless really tight on backup space. With a store of 16gb you shouldn't have any difficulties doing a full backup every day.

You can't compress transaction logs, as that will kill the performance of the server.

Simon.
0
 
bilbusCommented:
cant you put the logs and the store on a seperate HDs?
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
jbregAuthor Commented:
We do backups (incrementally) each day but the backups truncate the transaction logs. This is because we back up to a remote location over the Net (making full backups difficult because of bandwidth considerations).

Can't put logs and store on separate HDD as there is no other drive on the machine with nearly enough capacity.

I suppose we could add another few disks to the machine and store the logs there, but I'd rather not do that if there is some other way. The transaction logs are building up 30+ gb per day prior to the backup.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
I think your backup plan is not sufficient.  And the server lacks capacity.  You may be able to work around things, but your BEST option is to manage the server in a manner that makes sense.  Add capacity and change your backup plan.  You need to do full backups that truncate the transaction logs - if the remote backups won't cut it, then you need a different backup solution.  Probably an external hard disk or two cycled so you can take one off site.
0
 
jbregAuthor Commented:
The backups we do do truncate the transaction logs, I just was interested as to why they grow from 0 to 30gb each day (they are truncated each night) and whether anything can be done about it.
0
 
SembeeCommented:
A daily 30gb of transaction logs is an awful lot of email. If your database isn't growing by that much, then a lot of email is not being retained by the store.

Have you run perfmon or use message tracking to see what sort of message numbers are going through the server?

Simon.
0
 
jbregAuthor Commented:
Not really--can you suggest exactly how?
0
 
SembeeCommented:
First thing I would do is run the Exchange Best Practises tool on the machine.

http://www.microsoft.com/technet/prodtechnol/exchange/downloads/2003/analyzers/default.mspx

Message tracking needs to be turned on.
http://www.amset.info/exchange/message-tracking.asp

For perfmon, click Start, Run and type perfmon.
Change the type of display to Report by pressing CTRL and R

Then you need to add counters to the system. You can delete the ones that already there as they aren't relevant to this problem.

The counters are since the server or services were last restarted.

I would probably start with SMTP Server performance objects.

Inbound Connections Total
Messages Delivered Total
Messages Received Total
Messages Sent Total
Total Messages Submitted

Then move on to MSEXCHANGEIS Mailbox

Messages Submitted
Messages Sent
Messages Delivered

Repeat with the same counters for MSEXCHANGEIS Public

That will give you some idea of the message flow.

I can't tell you what is high or low numbers because every site is different.
However if you have 10 users and you have processed 250,000 messages since the server was last rebooted (which, if you are keeping it up to date will be at most 25 days ago) that would mean that your users are sending 1000 messages a day or 41 messages an hour - 24 hours a day, seven days a week.

You can get Perfmon to tell you how long the server has been up - (System, System Up time) but it shows it in seconds.

Simon.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 3
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now