NBU 7.1 BMR异机恢复出错

牛奶加蛋

老神奇了，BMR恢复了三个不同客户端的系统，
有一个能正常启动，进入红屏，继续恢复。直至正常

不过其中俩系统起不来

备份、恢复的方法都一样
为啥呢？？？

报错如下：

因以下文件损坏或者丢失，windows无法启动
<windows root>\system32\ntoskrnl.exe
请重新安装以上文件的拷贝

重启后，报错：

因为计算机硬盘硬件的配置问题，windows无法启动
不能读取所选的引导盘，请检查引导路径和磁盘硬件
请参阅windows文档中有关磁盘配置的信息并参阅您的硬件参考手册，以获得进一步的信息

huanglao2002

不知机器型号一样吗？
硬盘分区一样吗？
最好那台备的，就用来恢复那台。

牛奶加蛋

回复 2# huanglao2002


    那要bmr还干啥啊

huanglao2002

当然如果异机恢复步骤当然是不同的咯。

牛奶加蛋

回复 4# huanglao2002


    我有能成功恢复的，我觉得步骤肯定是没问题的。

牛奶加蛋

symantec给的solution

这两个问题都是与微软OS的某些限制（如File Protection feature）有关，具体描述如下。

首先针对文件丢失的问题，请参考如下文档解决
因以下文件损坏或者丢失，windows无法启动
<windows root>\system32\ntoskrnl.exe
请重新安装以上文件的拷贝

Title
Windows could not start because the following file is missing or corrupt: <Windows root>\system32\ntoskrnl.exe

Problem
Windows could not start because the following file is missing or corrupt: \system32\ntoskrnl.exe

Error
Windows could not start because the following file is missing or corrupt

Solution
When rebooting a Microsoft Windows Server 2003 server after using NetBackup to perform a full system restore, the following message is encountered:

Windows could not start because the following file is missing or corrupt.
<Windows root>\system32\ntoskrnl.exe.
Please re-install a copy of the above file.

The above may be due to the Microsoft Windows File Protection feature preventing critical system files from being overwritten by restored system files on reboot.  This mechanism is described in Microsoft Knowledge Base article 222193 (formerly Q222193) available from Microsoft at:

Description of the Windows File Protection feature
http://support.microsoft.com/kb/222193

Upon completion of a full system recovery (see NetBackup Technote 329471), before rebooting the server disable the Windows System File Checker as described in the Microsoft Knowledge Base article above.

The SfcScan value in the following registry key has three possible settings:

Note:  Refer to the Microsoft Article for the specific operating system versions this applies to and for possible updates or corrections to this information.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

The settings for the SfcScan value are:

0x0 = do not scan protected files after restart. (Default value)
0x1 = scan all protected files after every restart (set if sfc /scanboot is run).
0x2 = scan all protected files one time after a restart (set if sfc /scanonce is run).

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
Windows could not start because of a computer disk hardware configuration problem

针对另外一个报错，请参考如下文档：
因为计算机硬盘硬件的配置问题，windows无法启动
不能读取所选的引导盘，请检查引导路径和磁盘硬件
请参阅windows文档中有关磁盘配置的信息并参阅您的硬件参考手册，以获得进一步的信息
http://www.symantec.com/business ... nt&id=TECH64943
http://support.microsoft.com/kb/314477

Title
Upon reboot after restoring a system using the Restore Anyware Option, Windows fails to load with error; "Windows could not start because of a computer disk hardware configuration problem"

Problem
Upon reboot after restoring a system using the Restore Anyware Option, Windows fails to load with error; "Windows could not start because of a computer disk hardware configuration problem"
  
Solution
The following errors appear after rebooting a system that has just been restored (prior to the mini-setup wizard)

=====
Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware.
Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.
=====

To resolve this issue, follow the instructions in the following Microsoft Knowledge Base article.
http://support.microsoft.com/kb/314477

If additional partitions restored in the recovery environment are not visible, continue with the following steps.

1. Delete the existing partition.
2. Restore the partition from within the Operating System.

xzc999

自己给自己找麻烦，
不如用BESR。
我个人还是相信GHOST。整个raid启动盘就ok。

牛奶加蛋

回复 7# xzc999


    用户买了就得做啊，再说存在即合理么。呵呵。ghost毕竟得冷着来，大部分用户接受不了。besr其实也没方便多少

anyway，解决了。用2003系统盘重新修复下就搞定了，还是按照微软的kb做的。





使用恢复控制台中的 Bootcfg 实用工具更正 Boot.ini 文件：
        1. 使用 Windows XP CD-ROM 启动计算机。
        2. 当收到按 R 以使用恢复控制台修复 Windows 的消息时，请按 R 键。
        3. 选择所需的 Windows 安装，然后在系统提示时键入管理员密码。
        4. 键入 bootcfg /rebuild，然后按 Enter。
        5. 找到 Windows 安装后，将显示以下说明：
“将安装添加到启动列表吗?(是/不/全部)”
[键入 Y 响应此消息。]

输入加载标识符:
[这是操作系统的名称。键入 Windows XP Professional 或 Windows XP Home Edition。]

输入 OS 加载选项:
[将此字段保留为空，然后按 Enter]。
执行上述步骤后，重新启动计算机，然后选择引导菜单中的第一项。这应该能正常启动 Windows XP。

成功加载 Windows XP 后，可以修改 Boot.ini 以删除不正确的项。

xzc999

谁让你们卖的时候忽悠来着呢
我一般都不给客户介绍这个功能
系统都有自带的功能，干嘛用这个。
从靠谱来讲，我压根不信任BMR