mattx Posted October 30, 2013 Posted October 30, 2013 Exchange 2007 ( note at default level, no SP installed ) Backups keep failing so logs getting larger Running out of physical space because of growing log files Can move the log files but would rather not Can't perform fake backup because diskcopy only in SP2 ( I think ) Questions: Consequences of simply deleting logs ? How to determine using eseutil on what logs can be safely deleted ( which ones have been committed so they can be deleted ) How bad is actually turning on circular logging and will it purge the current back log of logs ? Any other suggestions to get rid of the log files so I can then work out what is wrong with the backup.
DrPerceptron Posted October 31, 2013 Posted October 31, 2013 incomplete backups are usually caused by corrupt items in mailboxes (I believe that was what was causing mine to fail in 2010 at least) How to remove Exchange Server transaction log files Have a read through that, it should cover everything you've asked about. 1
mattx Posted October 31, 2013 Author Posted October 31, 2013 I have that already booked marked... :-) I was looking for other solutions just in case anyone had them. I'm going for a backup to file now on a USB drive as it keeps failing on the tape drive. Currently at 240 gig of around 800 it needs to do. If this fails then it's going to be a long Sunday working out what logs I can get rid of or at least move.
DrPerceptron Posted October 31, 2013 Posted October 31, 2013 (edited) the eseutil command should tell you what the last transaction was and you can delete anything from up until then - a working solution should have committed pretty much everything but the last several minutes (if not everything). I went through a phase of being rather gung-ho about deleting transaction logs... I would leave the last several weeks, but delete anything older than that. I wouldn't really recommend that though Part of this is why I'm looking at Office 365 though Edited October 31, 2013 by DrPerceptron
glennda Posted October 31, 2013 Posted October 31, 2013 Turning on circular logging will require the Information store service to be restarted.
mattx Posted October 31, 2013 Author Posted October 31, 2013 Turning on circular logging will require the Information store service to be restarted. The other thing is the overhead on that too - its something I have suggested but I don't think the boss is too keen. Problem is as we are a 24/365 company, downtime is not really an option. 30,000 E-mails + daily. Sunday is normally a quiet day so much of this may be done then.
glennda Posted October 31, 2013 Posted October 31, 2013 The other thing is the overhead on that too - its something I have suggested but I don't think the boss is too keen. Problem is as we are a 24/365 company, downtime is not really an option. 30,000 E-mails + daily. Sunday is normally a quiet day so much of this may be done then. Then Ideally you want to be doing exchange 2010/2013 with DAG groups it is a hell of an improvement.
mattx Posted October 31, 2013 Author Posted October 31, 2013 Then Ideally you want to be doing exchange 2010/2013 with DAG groups it is a hell of an improvement. Hell yeah we know that :-) Bit of good news, 25GB of logs have been purged on one of the storage groups - waiting now for it to hopefully move on to the next one which has over twice that amount.......
mattx Posted October 31, 2013 Author Posted October 31, 2013 The consistency check on one of our other storage groups seems ok and now it's backing up - hopefully when this is done there will be around 50,000 logs to purge. Now I think on going through reams of logs that the problem as stated earlier by the Dr is that there is a corrupt mailbox as I see quite a few 1025 events - I have an idea who it is as they are only now appearing and our offices in the USA are now logging on - just need to work out ( somehow ) which one.
mattx Posted October 31, 2013 Author Posted October 31, 2013 9 hours in and it's cleared another load of logs - now on to the largest storage group and this has 130,000 log files - this is where I think it will fall over.
mattx Posted November 6, 2013 Author Posted November 6, 2013 how did it go? Arrrrr - 36 hours later and the backup failed however, the logs did get deleted. The byte rate was terrible to the USB disk however at least the logs purged. I popped in on Sunday with the manager and we re-started exchange and started another backup to tape however it failed again. We are now positive that the tape drive is to blame. So at the moment the backup to file on the USB is working, it fails but at least it's clearing the logs - replacement drive now on order. Have to admit - the amount of logs was scary - on one storage group alone it was over 50GB by the time it got to them.
sukh Posted November 6, 2013 Posted November 6, 2013 You probably want to move the logs on a daily or weekly basis depending on how busy the server is. This will keep the TL down and will be there if you need them.
mattx Posted November 6, 2013 Author Posted November 6, 2013 You probably want to move the logs on a daily or weekly basis depending on how busy the server is. This will keep the TL down and will be there if you need them. Well with the logs being purged now this is not a problem, also the backup to disk is only taking 12 hours to run. Once we have a working tape drive again this will be down to 5 / 6 hours - we are getting there....s l o w l y.....
mattx Posted November 6, 2013 Author Posted November 6, 2013 Not considered Exch 2013 /DAG or O365? Yep, or at least something clustered. Hopefully in budget for next year along with the option of some of the larger offices having their own mail server.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now