exchange databases corrupt

I wonder if anyone can shed some light on a issue we came across over the weekend, we have a exchange 2010 DAG and we noticed 3 databases (same DBs) were showing as:

Failed and Suspended

When we tried to mount he DB online we kept on receveing an error about JET_errDiskIO...............I've never seen this myself but after logging a case with microsoft and trying to recover\repair the DB they were unsuccessful.

The DB in question is about 1.2Tb in size - running the eseutil reports back as dirty shutdown and unable to restore.

We have managed to restore the DB from backup and run eseutil which reported back clean shutdown which has enabled us to extract the data from the EDB.

What I want to know is are there any limits on databases, is 1.2Tb big?
Ian TaylorIT Infrastructure Architect .:|:.:|:.Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

StuartTechnical Architect - CloudCommented:
Exchange 2010 standard is limited to 1tb, however this can be overridden by a simple registry edit. Microsoft recommend not to exceed 2tb per database however from my experience this in the real world when it comes to recovery is way to large - I would recommend to split your database down to a few..
That error you are receiving is not related to the Error you are getting, have you tried doing a soft recovery? follow this article and see if it helps you.....
Naushad shaikhIT Consultant - Messaging SupportCommented:
JET_errDiskIO error show that there is corruption taking a place because of permission or because some problem  in disk, there will be series of event before it damage database. I believe those event are got ignore by responsible team.

It is not related with database size

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.