Video Screencast Help

Disaster Recovery of SBS 2008 Failed

Created: 08 Nov 2011 • Updated: 25 Jan 2013 | 1 comment
kwcompco's picture
This issue has been solved. See solution.


I have a client running SBS2008 SP2 on a 2 year old server, with BE 12.5 SP4 installed, backing up to Quantum DLT tape drive.

Last week, 2 drives in a RAID 5 scenario went down, lost the array.  We replaced the drives, recreated the array, and followed Symantec document TECH87893 to recover the server, followed the document to the letter.

At the point of rebooting after restoring the system partition, system state, and shadow copy components, the server blue screened with a stop code of x07b.  We followed the procedure another 2 times, changing the raid driver once, and changing the partition size once.  Again, the server blue screend with the same stop code, no driver information given.

I opened a ticket with Symantec support, who basically told me I was doing everything correct and I should call Microsoft to see if they can help.  I opened a ticket with Microsoft who for 4 hours attempted to change registry settings to disable services and devices from booting up, with no success.  Microsoft's response was that in most cases such as these, it is best to build the server from scratch and basically deploy a new active directory box.

At this point, I had reinstalled the SBS server 4 times, talked to support for a total of 7 hours, and the client had been down for 3 days.  My choices were limited to one, rebuild the server, restore data, take server on site, and eat crow with the client.  2 techs spent most of the day onsite joining 8 workstations to new domain, copying profiles, and rebuilding scripts and security.  There were 2 things that were in our favor, the data was recoverable, and there were only 8 workstations.

But what if this was not the case?  What if there were 30 workstations, remote users, what if Exchange was configured in a way that users did not have a local OST to export out and reimport?  We have many small business clients, with different versions of SBS and different versions of BE attempting to prevent scenarios such as these.  These clients look to us for advise on how to quickly recover from these failures and provide a comfort level that we can protect them from a lengthy downtime.  We are now faced with a huge dilema, have we been advising our clients incorrectly?

We have read the documentation on different backup product solutions from Symantec, and deployed based on 30 years of experience in the industry.  Yet, in all this time, I have never read a document that says "This is how you should back up your particular environment so you can recover in your acceptable time frame".  I know this is a reach, but is there a backup guru out there, somewhere in Symantec land, that can give us some sort of direction as to whether we are doing this right or wrong?  We believe that if change is needed, we will deploy the change at our clients' sites.

Thanks for letting me vent, I'd appreciate any comments.

Uval Lubarsky

Comments 1 CommentJump to latest comment

CraigV's picture


No backup company will do that...go do some research on IBM's site as well as CA. They will never tell you what needs to be backed up completely. IN effect, they'd regurgitate what Microsoft (or whatever OS vendor they use) indicates on THEIR website to back up.

They will also not give you an acceptable time-frame for restores, based primarily on the many different environments in which their applications run. Your restore time might take 20 hours, but mine will take 4 for the same amount of data. The difference being you might restore from an LTO2 drive attached with SCSI while mine is an LTO4 library connected to a SAN.

For recovering Server 2008 using BE, check the TN below:

there are also other applications like BE's built-in IDR and Symantec System Recovery that you can look into which should give better DR recoverability.


Alternative ways to access Backup Exec Technical Support: