Solved

Symantec System Recovery 2013 - restore to new VM

Posted on 2014-04-23
15
1,990 Views
Last Modified: 2014-09-27
We're running Symantec System Recovery 2013 on Windows Server 2012.  It's scheduled to create recovery point sets with a "full" backup once a week, then "incremental" ones in between.  That's all working fine, and we can restore individual files from the backups with no problems.

However, we'd also like this to work as a form of disaster recovery, in that if the building were to burn down, we'd like to be able to restore an offsite copy of the latest recovery point to a new virtual machine at a datacentre.  I've been testing this process by creating a new VM, and booting with the Symantec Recovery DVD to perform the restore.  Although the restore process runs to completion, there seems to be a problem with drivers, and the newly-created VM doesn't boot properly to Windows.  The "Restore Anywhere" feature of Symantec System Recovery 2013 is definitely enabled.

The newly-created VM gets most of the way through the initial boot process but, before the logon screen is reached, an alert box appears "Windows Setup could not configure Windows to run on this computer's hardware".  I'm using the latest version of Oracle Virtualbox for the VM host, with default virtual hardware, which normally Windows Server 2012 supports with no problems.  I've also tried using a virtual IDE drive or virtual SCSI drive for my VM, instead of the default SATA virtual hardware.  The original physical server has an LSI MegaRAID SAS Adapter and a RAID-5 array.

I've also tried using the feature built in to Symantec System Recovery which allows the conversion of the latest recovery point to a VHD file.  I've tried the file it creates both with Virtualbox and with "proper" Hyper-V running under Windows Server 2012 R2, and in both cases I get the same error message when the VM boots.

I'm not clear why this isn't working - any ideas, please?  I'm assuming it's something to do with mass storage drivers, but perhaps I'm barking up the wrong tree?
0
Comment
Question by:wakatashi
  • 9
  • 6
15 Comments
 
LVL 119
ID: 40018089
This works for us from an System Recovery Image, we pick-up the image, and use the One-Time Conversion process to convert to a virtual machine.
0
 
LVL 1

Author Comment

by:wakatashi
ID: 40018467
Hi Andrew, do you convert to a VHD as we do, or something else, such as VMware's VMDK format?
0
 
LVL 119
ID: 40018511
We use One time Conversion and browse to the Symantec Recovery format backup image.

It is possible to convert the native Symantec Recovery Image using VMware Copnverter to a VMware vSphere VM also.
0
3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

 
LVL 1

Author Comment

by:wakatashi
ID: 40018588
The trouble is, we're not using VMware - we're using Hyper-V.
0
 
LVL 119
ID: 40018600
That was an -aside.

We use One time Conversion and browse to the Symantec Recovery format backup image, e.g. to convert to VHD.

If you have Symantec Support, I would escalate a support call.
0
 
LVL 1

Author Comment

by:wakatashi
ID: 40018607
Unfortunately, we don't have Symantec Support.  I do understand that the conversion process is working for you, but it ain't working for us, and that's the problem!
0
 
LVL 119
ID: 40018672
What is the physical hardware, we spend most of our time troubleshooting P2V!

We use this technology as a last resort for conversion, its the last toolbox in the toolkit, and we uninstall all the vendor drivers and software, which can cause VM starting issues.

However, you are wanting to use this for DR, and we use a different product for that by Storagecraft and NetIQ Platespin Migrate, which can do P2V and V2V, and V2P.
0
 
LVL 1

Author Comment

by:wakatashi
ID: 40020639
0
 
LVL 119
ID: 40020732
I'm sorry, no experience of Fujitsu servers these days, IBM, HP and Dell.
0
 
LVL 1

Author Comment

by:wakatashi
ID: 40021071
OK, many thanks for your help Andrew - much appreciated.

Anybody else any ideas, please?
0
 
LVL 1

Author Comment

by:wakatashi
ID: 40160518
I booted the VM with a Linux recovery disk and looked at the C:\Windows\Panther\setupact.log file.  It gives details of where the boot process went wrong – it’s clearly related to the OS adjusting to the new hardware.  Here’s a snippet from it, showing the error “Failure occurred while executing ‘CryptoSysPrep_Specialize’ from C:\Windows\system32\capisp.dll”.  Googling this error hasn’t turned up anything useful.  Suggestions greatly appreciated!
3.PNG
0
 
LVL 119
ID: 40160620
I would escalate that issue to Symantec support.
0
 
LVL 1

Author Comment

by:wakatashi
ID: 40160697
Thanks Andrew, but as I said earlier in this thread, we don't have Symantec support.
0
 
LVL 1

Accepted Solution

by:
wakatashi earned 0 total points
ID: 40338539
Here's the solution, believe it or not - disable "Restore Anywhere", and it works!   Windows Server 2012 spends some time working out what drivers it needs for the new hardware on the first boot, and that's it.  So it seems that the "Restore Anywhere" feature of SSR actually gets in the way rather than helping.

When I've restored an image to different hardware in the past with older versions of Windows it's always ended up blue-screening on boot because the mass storage driver is wrong and it can't access the boot volume.  So I didn't even think to try disabling Restore Anywhere until now!
0
 
LVL 1

Author Closing Comment

by:wakatashi
ID: 40347439
Found solution myself.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn how the use of a bunch of disparate tools requiring a lot of manual attention led to a series of unfortunate backup events for one company.
In this article we will learn how to backup a VMware farm using Nakivo Backup & Replication. In this tutorial we will install the software on a Windows 2012 R2 Server.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question