asked on

Exchange NTBackup Corruption

Recently our EXchange NTBackups have become corrupted, the backup file size reaches roughly 51 gig and is completely corrupt every night. We have gone through and had users clean our their mailboxes, after cleaning the mailboxes, the "supposed" size is about 40gig but the backup keeps backing up 51 gig everyday as if nothing changed. I there anything we can do?

recruitit

ASKER

Our event logs are showing the error with Event ID 613

DMTechGrooup

Have you took a look at this KB?

http://support.microsoft.com/kb/318429

Make sure you don't have any disk errors.. if you can you should shut down the exchange services make a full backup up of your store then try an offline defrag and check of your store.

http://www.msexchange.org/tutorials/exchange-isinteg-eseutil.html

http://www.petri.co.il/defragment_exchange_2000_2003_server_databases.htm

lucid8

Agree with DM this is not so much an NT backup issue as it is an Exchange database issue. I would suggest that you look closely at your SYSTEM event log for disk related issues and also your application event log for ESE DB related issues.

This can be caused by a failing hard drive, bad controller card, cable, motherboard, memory etc. Also if you recently did any firmware or other hardware related issues i would look at the event log pre/post update

denbosse

If you're looking to reclaim space after the cleanup, you need to do an offline defrag. http://technet.microsoft.com/en-us/library/aa997972(EXCHG.80).aspx. That's the only way the database will go back to 40GB.
That may be a dangerous operation if you have no backup though.
You could take Exchange offline, copy the database and log files to another space on the disk and then do the defrag. Be aware that to do the defrag, you also will need another 56Gb (110%) of free space.

ASKER CERTIFIED SOLUTION

lucid8

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

recruitit

ASKER

We are going to proceed with the recommended actions.

lucid8

great let us know how things progress

recruitit

ASKER

eseutil /P done

"Operation completed successfully with 595 (JET_wrnDatabaseRepaired, Database cor
ruption has been repaired) after 10313.0 seconds."

just defragging now, watching event log, no disk related issues appearing

lucid8

Thanks for the update and that's great that there are no errors...

recruitit

ASKER

jobs done, no major issues, ran isinteg once and there were about 30 fixes, will need to run again another day but so far it looks good, will find out if the backups work properly tonight, thanks for the guidance!

lucid8

Excellent news and look forward to the update