Troubleshooting : BMR Problems
  
BMR Problems
Use the following table to help you troubleshoot PN problems after performing a BMR. If you are receiving errors from the BMR wizard itself, go to (Step 4) To interpret QUARK errors:.
Symptom
Possible Cause
Solution
PN will not boot and results in a BSOD (Blue Screen Of Death).
You might be trying to restore a XenTools 6.0.2‑based RN image onto a virtual machine with XenServer 6.1 or later.
Modify the restored PN’s vm device_id parameter to 0001 so that XenServer 6.1 or later host presents the disk properly to the operating system:
• Shut down the virtual machine.
• Retrieve the virtual machine UUID for the PN.
• SSH to the XenServer and execute the following xe command: xe vm-param-set uuid=VM-UUID platform:device_id=0001
• Boot the virtual machine.
You’re missing boot-critical drivers and the P2P tool did not or was not able to properly adjust your PN’s operating system for the new hardware (rare).
(Step 3) To manually adjust a PN’s operating system for new hardware:
PN boots, but the onQ Portal indicates a Connection Status of PN offline.
Your PN might have acquired a DHCP IP address, not the original static IP address.
Modify the PN’s configuration to reflect its original, static IP address. Afterward, onQ can resume backups of the PN.
After a full cross‑hypervisor BMR, the BMR'd image comes up with a DHCP address. Original network adapter is hidden and the image has a second, additional NIC with a DHCP address.
This is a known issue in a cross‑hypervisor scenario.
See VMware’s Knowledge Base article. It's not possible for QUARK’s BMR process to manipulate the image registry and preset a static IP for a given PN.
When a restored, VMware‑based PN initially boots, it might bring online only the OS disk—all other disks remain offline.
In this case, the PN loses some of its protected volumes if they reside on any of those offline disks. When onQ backs up this PN in this state, the backup fails, reporting that some of those protected volumes are missing in the PN.
Because this issue reveals itself during a restore, QUARK might appear to be the cause, but that’s not the case: QUARK always comes up with all attached disks and shows an online status for all target disks.
Using the OS’s Disk Management interface, bring online all offline disks before onQ attempts a backup of the PN. This best practice is also outlined in Step 13 of (Step 2) To restore data to your PN:. After an offline disk is brought online, it stays online indefinitely, regardless of the number of PN reboots.
When you attempt to manually inject drivers into the target using QUARK’s third‑party P2P tool, the tool reports that it loaded the drivers, but doesn’t actually load them.
Most of the time P2P works beautifully, and does so better than other, third‑party tools; however, in some configurations, the tool isn’t able to inject drivers.
Use another third-party tool (for example, DISM, if the target OS is 64‑bit and Windows Server 2008 or above), to inject the drivers:
> Dism.exe /Image:C:\ /add-driver /driver:fullPathToDriverINFfile
After a restored PN reboots, video reverts to 640x480 or 800x600 resolution.
BMR process sets PN boot parameters to Base video. When set to Base video, Windows loads standard VGA drivers instead of display drivers specific to the video hardware on the computer.
After the restore and on the BMR target, launch the System Configuration utility (msconfig.exe), then go to Boot tab > Boot Options pane. Clear the Base video check box.