MS Exchange 2010 corrupt EDB Headers

Following a complete hardware failure of our Exchange 2010 Server (on 2008R2), we have had to move Exchange to a new Server.

The old Databases are still there - somewhere. But we can't access them. Every time we have tried, we are told that the EDB Headers are corrupt. ESEUtil does not work with any of the usual switches and we have tried Stellar Phoenix Mailbox Exchange Recovery (a full version, which had worked in the past) and that finds no information despite the Databases being multiple GB in size!

We have restored Exchange DBs from the backups, but they also have the same problem - going back a month or more before the Server failed completely. This, despite the fact that we had no indication of Exchange problems before the Server collapsed into its own personal hell.

We are reaching the very limit of what we can do now and are unsure where to go next. Any ideas would be appreciated!
winstallaAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
winstallaConnect With a Mentor Author Commented:
Hi all, sadly MS were unable to help us, these DB files are corrupted in a big way.

Thanks for any and all help on this guys

Kind Regards
0
 
AmitIT ArchitectCommented:
I assume you have recovered the server with recover switch. If not, please recover the server with recover swtich.  http://technet.microsoft.com/en-us/library/dd876880%28v=exchg.150%29.aspx

If this doesn't work and you have backup corruption issue, then last option is to use 3rd party tool, like one from digiscope http://www.lucid8.com/product/digiscope.asp

So, in your case, first create dial tone db, that will bring the user back to production, then use digiscope tool and extract data into pst and merge to user mailbox.

Hope this helps
0
 
Simon Butler (Sembee)ConsultantCommented:
There is only one thing I would suggest now - call Microsoft support.
If you have recovered the databases and they are showing the same error, that would tend to suggest there is a wider problem. Microsoft support are going to be the best people to assist here.

Simon.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
winstallaAuthor Commented:
We have tried several tools like this and they keep showing the Databases as being empty (including this one). The file sizes on the Disk are huge, but the recoveries result in no records at all.
0
 
winstallaAuthor Commented:
We have an existing call open with MS Support for the failed Server. We will get back in touch with them on this, I was just hoping that there might be another way!
0
 
winstallaAuthor Commented:
Closing call
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.