Hello, I have an Exchange 2007 environment on Windows 2003 R2, 3 virtual boxes, (VM vSphere 4.0), Mailbox, Hub T and Client Access. BackupExec is failing on brick level backups stating that the database is currupt. I'd like any suggestions about my best and least time consuming options, if possible. Instead of taking the database off-line for what would be an extended downtime to run ESEUTIL /P & /D and ISINTEG, my thought is to create another database and move mailboxes to it. Is there any utility I can use to isolate the corruption that would help me avoid moving the problem to the new database? We're at about 91Gig. Before the failure started we were at around 78Gig. The increase happened at the same time as the failure. Thank you for any help.

That's most likely a bogus error and something that has plagued brick level backups for years.Can you do regular, full online backups of the Info Store? Are they successful? If so , that is the only backup you need. Brick Level backups are a waste of time and backup space.Use deleted item retention and/or the recovery storage group to retrieve a database backup and then extract the contents of a mailbox from there.I wouldnt run eseutil against the server - especially not with the /p switch.Its always better to move mailboxes to a new store then do an offline defrag. In this case however, I dont see the need to do anything except stop Brick Level Backups unless there are other errors or problems with that store.

Please don't do brick level backups. Life will be better if you don't.Active Directory, 4th Edition - www.briandesmond.com/ad4/