Bare Metal Restore Limitations • When you perform a failback to restore a VMware‑based protected node to a dissimilar hardware or virtual environment, Windows might require reactivation. • When a Windows 2008 system with a system hidden partition is restored, Windows might require manual intervention before starting the restored node. For more information, go to Perform Bare Metal Restore. • When a Windows 2008 system with an EFI partition is restored, you will need to manually perform some pre and post BMR tasks. For more information, go to Perform Bare Metal Restore. • BMRs that are performed to the same or new hardware require that you upload specific drivers for any disk, network adapter, and any other hardware. • After an incremental failback to a non‑Xen PN (physical PN, ESX PN, Virtual PC PN), users are required to reinstall drivers. • For a Windows 2012 server, a REF’s partition/volume will be restored as standard NTFS. • For a Windows 2012 server, if you choose to restore a volume with deduplication enabled, the data will be restored to its full size. Simply enable deduplication after the BMR completes. • For restored images of Windows 2008 and later, the boot correction script needs to be manually executed while in the QUARK environment. Failure to do so will result in the restored image not booting with its operating system. • Volume Mount Points need be configured manually before starting to restore the image. Volume Mount Points created this way are not listed in the disk configuration interface along with other volumes. • Disk configuration interface does not display the file format type for a volume created without a drive letter assigned. • When adding each volume in the disk configuration interface, you might need to wait a short period of time while the volumes are being created. • There is a maximum allowed duration of 72 hours for a restore to complete. Exceeding 72 hours might result in a reboot of QUARK and a loss of the restored image to that point.
