Video Screencast Help

Disaster Recovery for Windows 2008 R2

Created: 25 Apr 2012 | 12 comments

What do people use to recover physical Windows 2008 R2 to dissimilar physical hardware as well as to virtual hardware.

We tried going the BMR route but uEFI servers are not supported.

We have also attempted the steps in this technote, but receive nothing but windows stop error 0x000007B and blue screen - http://www.symantec.com/business/support/index?pag...

Has anyone found a way around the uEFI server problem?  Using other software, different procedures, etc. 

When we used Arcserve we had no issues recovering over a fresh Windows install, but since moving to NetBackup we have not been able to recover a Windows 2008 R2 with uEFI to physical or virtual, which severly impacts our conversion to NetBackup.

We have opened a support ticket but so far the only direction is the technote referenced above.

Thanks

Lowell

Comments 12 CommentsJump to latest comment

Nicolai's picture

Step 9 in the recovery procedure is very important to do. It sound triviel but is the root cause for most failed restores. If bpinetd is not stopped, some values may not flush into registry. 

Our full restore success rate has raised after this step has been emphasised.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Lowell F's picture

Hi Nicolai, what has been your success rate using this method?

Thanks

Lowell

Lowell F's picture

Hi Nicolai, are your recovering to similar hardware or Physical to Virtual?

Thanks

Lowell

Nicolai's picture

We use this method for both physical and virtual servers. 

We always restore to "different hardware" (default ) as this methods does not overwrite some very important device drivers that usally result in blue screen if  overwritten (see the text in italic). 

I was told only to use "same hardware" if the hardware was exactly the same box. If any component was swapped you -  use "different hardware".

NOTE:  By default, the System State/Shadow Copy Components assumes the restore is to different hardware (and NOT the original machine) and does not restore the registry hive: HKLM:\System\CurrentControlSet\Control\BackupAndRestore\KeysNotToRestore.  This will result in the loss of certain hardware driver and configuration information noted by Microsoft here: http://technet.microsoft.com/en-us/library/cc737538.aspx (this means you may have to [re]install drivers if restore/reboot is successful.

 

Hope this info helps :-)

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Lowell F's picture

Hi Nicolai, what Intel hardware do you use?

Thanks

Lowell

Nicolai's picture

Mostly HP

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Marianne's picture

Lowell, you will agree that Nicolai has assisted as much as possible?

The only way to know if procedure will work for you is to TEST before dissaster strikes....

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Lowell F's picture

Hi Marianne, I do agree that Nicolai has had some valuable suggestions. 

We have tried this procedure multiple times with absolutely NO success. 

This is what lead me to start this thread to see what other people are doing to recover their Windows 2008 R2 uEFI systems to dissimilar hardware or virtual servers with NetBackup, since there is no support for uEFI in BMR.

The disappointing factor about this whole thing is there is no mention in the compatibility documentation that uEFI systems are unsupported by BMR.  I see this referenced in a forum thread that this was the case in 2011 and the documentation still hasn't been updated to reflect this.  The technote stating the unsupport of uEFI even references this compatibility document.

We were recommended to go the BMR route by Symantec support because lack of success we were having with the procedure and this above work around is not supported by Symantec.

The funny thing is that we 85% through a project to migrate from Arcserve to NetBackup and are finding there are things we could do, like recover to dissimilar hardware and virtual servers, with a very old version of Arcserve but can not do with the latest version of NetBackup.

Is this the only way to recover a Windows 2008 R2 uEFI system?  If so it looks like we maybe staying with Arcserve or buying another product to bridge the gap.

Needless to say it is very frustrating.

mandar_khanolkar's picture

FYI:

BMR support for uEFI and GPT based partitions is there on roadmap and would be supported in next NetBackup major release or a next patch going on top of it.

Thanks.

Mandar

Lowell F's picture

Thanks Mandar, we have been told that this is most likely scheduled for the 7.6.1 release which would put us a year or so out from now.  We are looking for alternatives at the moment.

I am curious on what other NetBackup users are doing to get around this issue.

Thanks

Lowell

mjt123's picture

Hi Everyone,

Was there ever a solution to this as we have excly the same issue needing to restore IBM servers EFI to HP servers running BIOS