http://blog.mpecsinc.ca/2013/03/our-largest-disaster-recovery-navigated.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+MpecsIncBlog+%28MPECS+Inc.+Blog%29

The first heart stopping, cold hands inducing, and sinking stomach moment:

• (SBS, ShadowProtect, and an Event ID 55 NTFS Error …)

The second heart stopping, cold hands inducing, and sinking stomach moment where server death was now known to be immanent:

• (Images No Good … Catastrophic SBS Failure … Down What?!?)

Now, becoming less and less relevant but having a second DC on an SBS STD network can be a killer when recovering:

SBS – Exchange Information Store is Corrupt? Recreating the Store

• Once we were down the line from point of recovery we still had issues with the Exchange databases we forklifted into place. This post outlines all of the steps to get content out of Exchange, create a new database set, and merge it back in. Exchange 2003.

SBS & ShadowProtect – Some Hardware Independent Restore considerations

• This post is relevant for any full bare metal or hypervisor restore of a server.

SBS Disaster Recovery – Finished