We had a client lose power and for some unknown reason it decided to trash the C: Drive of the SBS VM. So after recovery of the C: Drive using shadow protect, the system booted fine.
I was expecting an issues but this one annoyed me a bit.
After starting up i noticed the exchange databases were not mounting, after trying to mount it and it saying that there were missing committed transaction logs i realised that i had only restored the C: drive which restored older logs and the main database being on another drive was the current version and had already committed logs that now didn't exist. This occurred because we had to restore from 11am and the power loss occurred at 11:50am which meant that the 12pm backup didn't run.
After figuring this out for 2 hours (OMFG 2 hours), i then mounted through SP both drive and exactly the same point in time from the backups. I then copied both the log folders and the database folder to their respective places in the system and SUCCESSFULLY mounted the databases, unfortunately there was a loss of email, but a small loss is better than no database.
So to sum up when restoring an exchange database that is split on 2 different drives make sure you are either restoring ALL Hard drives or restoring the entire database directory and the log directory from the SAME point in the backup.
-Fr33ze
No comments:
Post a Comment