jbreg
asked on
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
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
Lee W, MVP
This may not be the best answer, but.... why don't you just get more disk space?
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.
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.
cant you put the logs and the store on a seperate HDs?
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.
Have you run perfmon or use message tracking to see what sort of message numbers are going through the server?
Simon.
ASKER
Not really--can you suggest exactly how?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.