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. • 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. • See the dynamic disk limitation outlined in Agent‑less PN Enrollment Limitations. • 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.
