Link to home
Start Free TrialLog in
Avatar of reditsolutions
reditsolutions

asked on

Backup completed with errors

Hi,
I have an SBS2008 that has been reporting backup completed with errors due to a corrupt log file.
I ran eseutil /k  on the logs and confirmed a log file as corrupt.
 /mh on the database shows the database is in clean shutdown state.
My next step as per https://support.microsoft.com/en-us/kb/2616952?wa=wsignin1.0 would be to move the log files to another folder.

Does this mean:
A - Move every single log file, except for E00.log
B - Move all files ending in .log including E00
C - Move only the corrupt log file(s)

I think it is A but I thought best to confirm.

Thanks
Avatar of Mark Bill
Mark Bill
Flag of Ireland image

How big is the DB ? How many Mailboxes is it hosting? Have you checked the consistency of the databases?

If youve checked the consistency of the DB and its fine.

I would seriously consider making a new Exchange DB here, this avoids the ESE Util stuff and try migrating a couple of mailboxes accros. Then test the backup.
Avatar of reditsolutions
reditsolutions

ASKER

Thanks Mark,
The database mounts fine and eseutil /mh reported the database is in a clean shutdown state.
I have made a full copy (eseutil /y) of the database and the logs to another folder.

Exchange has been working for months without any issues but there are these errors coming up on the backup.

The database is 79GB and there are about 76GB worth of log files.
Create a mailbox store and move a couple of mailboxes to it as a test, start migrating off onto this one mailbox by mailbox whilst testing it.

Leave it behind make sure to skip plenty of corrupt msgs! :o
ASKER CERTIFIED SOLUTION
Avatar of reditsolutions
reditsolutions

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
My solution did not result in any data loss, SBS is now backing up properly