Highlighted

SSR 2011 - can not restore running system

We have a Hyper-V server HOSTA (Windows Server 2008 Std SP2 x64) with 2 guests SBSA (Windows SBS 2008 SP2 x64) and APPSA (Windows Server 2008 Std SP2 x64).

Both SBSA and APPSA have Symantec System Recovery 2011 (Build 10.0.0.39952) installed, and backup to share on HOSTA and Offsite to a FTP location.

The Offsite location has HOSTB (Windows Server 2008 R2 Std SP1 x64) with Symantec System Recovery 2011 (Build 10.0.0.39952) installed.

When the Restoring SBSA or APPSA it fails every time in all ways we have tried:

Convert sv2i to Hyper-V VHD fail:

Converts ok, then on start of VM guest runs the mini setup, then updates, then randomly reboots. after that we receive the stop 7b error, But the data on the .vhd can be mounted and accessed.

Create Hyper-V guest and use System Recovery Disk fails:
Towards the end of the restore a "Recover My Computer Wizard" box pops up with the message:

Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed,
Can::ReadFileFrameReal: .\Can.cpp(826): Read Failure.

Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed,
Can::ReadFileFrameReal: .\Can.cpp(826): Read Failure.

with an Ok button that takes you to the menu screen.

Convert to VMware Server Disk fails:
The convert stops at 99% with 3 seconds to go (With or without "Run Windows Mini-Setup")

Convert s2vi using VMware Player 3.1 fails:
Very slow reading the s2vi file and then I enter the password and straight away I get the error from VMware Player:
Failed to open virtual machine: Failed to query source for information.

We have tried a One off recovery point on-site and taken it to the off-site location and receive the same issues.

A convert to vhd of APPSA on APPSA:
converts ok, moved to HOSTA. on boot of the restored guest APPSA we receive:

Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the
cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. choose your language settings, and then click “Next.”
3. click “Repair your computer.”
If you do not have this disc, contact your system administrator or computer
manufacturer for assistance.
status: Oxc000000f
Info: Windows failed to load because the NL5 data is missing, or
corrupt.

Please can someone suggest any ideas

2 Replies

Convert sv2i to Hyper-V VHD


Convert sv2i to Hyper-V VHD fail:

Converts ok, then on start of VM guest runs the mini setup, then updates, then randomly reboots. after that we receive the stop 7b error, But the data on the .vhd can be mounted and accessed.


Powerdown the machine after the BSOD and go into the settings for that machine. Click on 'Network Adapter' and check if the MAC address is dynamic or static. If Static, change it to Dynamic to eliminate the MAC address causing the error.

Are you backing up the HOSTA along with the 2 guests?

we now have issue converting

we now have issue converting to vhd,

it see the recovery point file, accepts the password by when you click next to go the page where you set the destination we get this error:

------------------------------------------------------------------------------------------------------------------

Details
    Data
        System.Collections.ListDictionaryInternal
    Message
        Index was outside the bounds of the array.
    Source
        VProUI
    Stack Trace
           at Symantec.VPro.VProUI.UCtrlRecPointSystem.Next()
           at Symantec.VPro.VProUI.UCtrlRecPointSelection.Next()
           at Symantec.VPro.VProUI.WizPageConvertSource.Next()
           at Symantec.UI.Wizards.ClassicWizard.OnNext(Object sender, EventArgs e)
           at System.EventHandler.Invoke(Object sender, EventArgs e)
           at System.Windows.Forms.Control.OnClick(EventArgs e)
           at System.Windows.Forms.Button.OnClick(EventArgs e)
           at Symantec.UI.Controls.SymButton.OnClick(EventArgs e)
           at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
           at Symantec.UI.Controls.SymButton.OnMouseUp(MouseEventArgs e)
           at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
           at System.Windows.Forms.Control.WndProc(Message& m)
           at System.Windows.Forms.ButtonBase.WndProc(Message& m)
           at System.Windows.Forms.Button.WndProc(Message& m)
           at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
           at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
           at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
           at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
           at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
           at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
           at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
           at System.Windows.Forms.Application.RunDialog(Form form)
           at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
           at Symantec.VPro.VProUI.VProUtils.ShowWizardConvert(VProConnection conn, Form frm, String sDefaultFile)
           at Symantec.VPro.VProConsole.PaneTasks.OneTimeConversion_FeatureClicked()
           at Symantec.VPro.VProUI.UserControls.UCtrlFeature.OnFeatureClicked()
           at Symantec.VPro.VProUI.UserControls.UCtrlFeature.Name_LinkClicked(Object sender, LinkLabelLinkClickedEventArgs e)
           at System.Windows.Forms.LinkLabel.OnLinkClicked(LinkLabelLinkClickedEventArgs e)
           at System.Windows.Forms.LinkLabel.OnMouseUp(MouseEventArgs e)
           at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
           at System.Windows.Forms.Control.WndProc(Message& m)
           at System.Windows.Forms.Label.WndProc(Message& m)
           at System.Windows.Forms.LinkLabel.WndProc(Message& msg)
           at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
           at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
           at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
           at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
           at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
           at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
           at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
           at System.Windows.Forms.Application.Run(ApplicationContext context)
           at Symantec.VPro.VProConsole.MainForm.ShowForm(Form form)
           at Symantec.VPro.VProConsole.MainForm.RunCommandLine()
           at Symantec.VPro.VProConsole.MainForm.Run(String[] s_commandLineArgs)
           at Symantec.VPro.VProConsole.Program.Main(String[] args)
    Target Site
        Next
    ------------------------------------------------------------------------------------------------------------------

so we have decided to delete the job and all recovery points, create a new job that stops the "Hyper-V Integration Services" before the job and starts them after.

hopefully it works.