If you do choose the ESEutil route and it does repair the DB you will have to move all the mailboxes to a new DB or you will be unsupported from Microsoft.
Also get up to 2013 / 2016 if possible. Lots of new changes to make your life a whole lot easier. On Wed, Jun 1, 2016 at 11:07 AM, Ryan Ray <[email protected]> wrote: > Do you have backups Gino? You'll need to restore a DB backup and then > replay the transaction logs into the DB. Or try your luck with ESEutil. > Depending on how big your DB is it could take a while. > > On Wed, Jun 1, 2016 at 11:05 AM, Gino Villarini <[email protected]> > wrote: > >> Thanks for the feedback. Ist Exchange 2010, we had a powerdown event on >> the server, the DB got corrupted >> >> On Wed, Jun 1, 2016 at 1:56 PM, Andreas Wiatowski < >> [email protected]> wrote: >> >>> Gino, >>> >>> >>> >>> What are you running…server SBS 2003? If you have a database size over >>> 7GB it will not mount once it reaches that level… if you make a few >>> registry changes…all will be well. >>> >>> >>> >>> Cheers, >>> >>> ______________________________ >>> >>> Andreas Wiatowski | CEO >>> >>> Silo Wireless Inc. >>> >>> Email [email protected] >>> >>> 19 Sage Court >>> >>> Brantford, Ontario N3R 7T4 (CANADA) >>> >>> Tel +1.519.449.5656 Extension-600|Fax +1.519.449.5536 |Toll Free >>> +1.866.727.4138 >>> >>> >>> >>> *From:* Af [mailto:[email protected]] *On Behalf Of *Gino Villarini >>> *Sent:* Wednesday, June 1, 2016 1:32 PM >>> *To:* Animal Farm <[email protected]> >>> *Subject:* [AFMUG] Urgently need Exchange DB Guru >>> >>> >>> >>> We have a issue with our Exchange server. The database does not mount. >>> Any recommendations for a Exchange Professional? >>> >> >> >
