Guys, I'm looking for a little help. Last Wednesday, we had a UPS failure that triggered a dirty shutdown of Exchange. I run two 64-bit servers on the backend for mailboxes (one for Students and one for Faculty/Staff). The Fac/Staff box came up fine with no issues. The student server is another story. By the way, our backups were not valid so I can't go that direction (another story another day). When it came back up, there were two storage groups with databases that would not mount. My storage groups and DB's are arranged by year, so the 2010-11 and 2011-12 mailstores were the ones affected. After following several threads and links here, I was finally able to recover and restore the 2011-12 SG and mailstore. It is fine. A couple of passes with eseutil to repair and defrag. Attempted the same process on the 2010-11 box. At first, all seemed OK. But we started getting reports from students that messages in their accounts were empty or they couldn't access it at all after logging in via OWA. I ran the database recovery tool under EMC and it fixed a handful, but others remained problematic. Now it appears that it hasn't completed the recovery due to lack of disk space. I now have three .edb files with a Temp#### prefix. The current 2010_11.edb file is 42GB in it's current storage group. The temp edb files are scattered randomly across other drives. Question: Are all 3 needed for a full recovery? They are 40GB, 30GB, and 7.5GB in size. I'm assuming that they are all from the same 2010_12.edb file, but stopped in various stages of repair/defrag due to lack of drive space. Should I re-run eseutil /d against them all or what do you advise? I know I need 110% of free space to run the tool through it's completion. I'm heading out for a few hours but will check back in later tonight. Thanks in Advance!
↧