Solved Unable to mount Exchange 2013 Database
-
A reboot later and eseutil is working this time
-
@JaredBusch said in Unable to mount Exchange 2013 Database:
Yes, but a week old. So the time to attempt a recovery for a couple hours is worth it.
Sounds like the backup process should be revisited.
-
@JaredBusch said in Unable to mount Exchange 2013 Database:
A reboot later and eseutil is working this time
Well that's good, odd but good
-
Damnit.
-
I possibly have not enough space for the temp file. I cannot find a way to tell
eseutilto write the temp file to another location. -
@JaredBusch What is the error in the Windows Event Logs?
Any mention of Fragmentation?
-
@JaredBusch said in Unable to mount Exchange 2013 Database:
Damnit.
Forgot to restart EMS as admin after the reboot.
Fucking EMS, no idea why it ever executes without self elevating..Running recovery again.
-
@JaredBusch /t“E:\TempDefrag.edb” from my old Exchange notes
-
@JaredBusch take a look here it seems this guy was able too from a while back.
http://blog.mpecsinc.ca/2012/05/exchange-eseutil-d-defragment-temp-file.html?m=1
-
@DustinB3403 said in Unable to mount Exchange 2013 Database:
@JaredBusch take a look here it seems this guy was able too from a while back.
http://blog.mpecsinc.ca/2012/05/exchange-eseutil-d-defragment-temp-file.html?m=1
Heh ... that looks familiar.
-
@jt1001001 said in Unable to mount Exchange 2013 Database:
@JaredBusch /t“E:\TempDefrag.edb” from my old Exchange notes
That works with
/dnot/r -
the soft recovery succeeded
But the system still reports dirty shutdown. so on to hard recovery with
/p -
@JaredBusch said in Unable to mount Exchange 2013 Database:
the soft recovery succeeded
But the system still reports dirty shutdown. so on to hard recovery with
/pEver done a forklift recovery?
Also, to get mail flowing set up a Dial Tone database.
-
@JaredBusch Ahh correct my bad was looking at defrag.
-
Moving along....
-
@JaredBusch Fingers crossed.
-
Final verdict, it completed and showed clean shutdown.
I deleted all the log files at this point and the database mounted.
Email flow resumed around 4pm with no lost email as the spam filter kicked delayed messages in response to inbound email.
