Exchange 2013 database restore successful - but database not mountable / dirty shutdown
Hi, Currently testing disaster recovery of an exchange 2013 server with Backup Exec 2014. Backup job taken successfully with BE Windows Agent. Successfully restored the server into a VM using SDR. Afterwards restored Exchange database and logfiles to original location. Instructed BE to overwrite existing. The Exchange restore job is successful - but store is not mounted automatically. Manual mount not possible - getting dirty shutdown error code. Have tried soft repair with eseutil - but it fails and reports that some logfiles are missing. Only option that works is hard repair - but my logfiles should be OK.. 1. Circular logging is disbled on the production server 2. No other backup software in used for Exchange backup - that could possibly interfere with the logfiles /flush them. 3. Log files are flushed correctly after each full backup job What am I missing here? We run full backup job each friday and differential other days. Differentials are logfiles only (logfiles not deleted until after successful full backup) Could there be an inconsistency in my Exchange database that could cause the replaying of log files to fails - or am I just doing the restore wrong? Regards ThomasSolved1.8KViews0likes4Comments