Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Exchange 2010 daily backup but growing logs - 14 E00000xxxxx.log files corrupt
Hi
Working Exchange 2010 with mounting mailbox databases, daily windows backup completing with errors.
Background
The harddisk on the server developed disk faults and the VMware host and Windows 2008 guest were rebuilt on new harddisk. The Exchange Server was restored (by someone else).
Appeared to be working well and backed up daily with windows backup.
But the backup started to report completed with errors.
It has not been possible to take the server down for business reasons until now.
When the disk space was running very low,
The mailbox database is 44GB and the logs have grown to 22GB there is less than 8GB of disk space free.
--------------------------
Have dismounted the mailbox databases and run ESEUTIL /K E00 and it reports thousands of log files ok but 14 are corrupt with
ERROR: Log damaged (unusable). Last Lgpos: (0x14da1,9,0). Error -501.
The E00 is OK
Was able to mount the mailbox after this.
Have space on a NAS drive to copy the logs to if required or can increase the disk space on the exchange drive but prefer not to.
1. Have not attempted to repair the 14 logs individually, is it worth trying?
Looking for the best way to resolve this issue as it is some time since the server restore and the exchange backup used it way out of date.
Not sure if the user mailboxes are missing mails from these logs but incoming and outgoing mail is functioning and no apparent losses.
-------------------
Previously in repairing exchange databases
Have just deleted all the log files and then mounted the mailbox database in the past with Exchange 2003 but is it safe to attempt this with Exchange 2010?
The corrupt log files all occurred over a period of 45 days in 2013.
Thanks for looking, any questions / clarification, please let me know.
TL
Working Exchange 2010 with mounting mailbox databases, daily windows backup completing with errors.
Background
The harddisk on the server developed disk faults and the VMware host and Windows 2008 guest were rebuilt on new harddisk. The Exchange Server was restored (by someone else).
Appeared to be working well and backed up daily with windows backup.
But the backup started to report completed with errors.
It has not been possible to take the server down for business reasons until now.
When the disk space was running very low,
The mailbox database is 44GB and the logs have grown to 22GB there is less than 8GB of disk space free.
--------------------------
Have dismounted the mailbox databases and run ESEUTIL /K E00 and it reports thousands of log files ok but 14 are corrupt with
ERROR: Log damaged (unusable). Last Lgpos: (0x14da1,9,0). Error -501.
The E00 is OK
Was able to mount the mailbox after this.
Have space on a NAS drive to copy the logs to if required or can increase the disk space on the exchange drive but prefer not to.
1. Have not attempted to repair the 14 logs individually, is it worth trying?
Looking for the best way to resolve this issue as it is some time since the server restore and the exchange backup used it way out of date.
Not sure if the user mailboxes are missing mails from these logs but incoming and outgoing mail is functioning and no apparent losses.
-------------------
Previously in repairing exchange databases
Have just deleted all the log files and then mounted the mailbox database in the past with Exchange 2003 but is it safe to attempt this with Exchange 2010?
The corrupt log files all occurred over a period of 45 days in 2013.
Thanks for looking, any questions / clarification, please let me know.
TL
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
No, do not delete the logs, otherwise it may then be impossible to mount the database again.
Best things is to move the logs to a new working disk and then use ESEUTIL.exe to try to recover (/r) or repair (/p) the database so that you can mount it and then back it up properly which will remove the logs and apply the changes to the main database.
Best things is to move the logs to a new working disk and then use ESEUTIL.exe to try to recover (/r) or repair (/p) the database so that you can mount it and then back it up properly which will remove the logs and apply the changes to the main database.
I would try putting it in to circular logging first, restart the information store and see if Exchange will flush the logs out on its own. If it does, then once they have gone, do a backup, then disable circular logging.
Otherwise a repair as advised above is going to be the next move.
Simon.
Otherwise a repair as advised above is going to be the next move.
Simon.
OK thanks, will try the circular logging to see if it will clear down the good logs and hopefully the corrupt ones.
If this minimises the volume of logs, it will speed up the recover or repair.
If this minimises the volume of logs, it will speed up the recover or repair.
This was a perfect solution. Cleared all the logs including the corrupted logs in a few minutes.
Hopefully the backup will work without error this evening.
Hopefully the backup will work without error this evening.
However the full windows backup after the clear down of the logs through circular logging did not complete without errors!
The logs were cleared by the backup but still getting failed consistency check
The application will not be available for recovery from this backup.
The consistency check failed for the component Microsoft Exchange Server\Microsoft Information Store\server name \e83nnnnnnnnnnnnnnnnnnn358
Looks like the repair will have to be done to over come this consistency check.
The logs were cleared by the backup but still getting failed consistency check
The application will not be available for recovery from this backup.
The consistency check failed for the component Microsoft Exchange Server\Microsoft Information Store\server name \e83nnnnnnnnnnnnnnnnnnn358
Looks like the repair will have to be done to over come this consistency check.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial