![]() For instructions, see Error 0x0000005D (Unsupported Processor) when booting Release 7.4 Integrated Bare Metal restore media. You might need to enable these features on the recovery target machine before booting from the ISO image. WinPE requires that these processor features are enabled on the recovery target machine: NX, PAE, and SSE2. Processor features on the recovery target These drivers are included in the unified BMR ISO image. If recovering to a virtual machine, you must inject ESX, Hyper-V, or XenServer guest storage drivers, depending upon your virtual environment. It is recommended that you verify whether the operating system of the asset you are recovering requires additional drivers to run on the hardware of the recovery target machine before you begin the recovery. If recovering to a physical machine, required drivers vary by hardware and operating system. Injecting drivers into the recovered operating system - After the critical volumes have been recovered, you must inject drivers into the recovered operating system if you are recovering to dissimilar hardware or to a virtual machine. If WinPE 10.0 cannot detect a network adapter or storage disks, you must load Windows 11 or Server 2022 drivers into WinPE during recovery. WinPE 10.0 is based on Windows 11 or Server 2022. Loading WinPE drivers for unified bare metal recovery - The Unified BMR wizard uses WinPE 10.0 for the recovery. You might need to add drivers during different stages of the recovery. Wireless network adapters cannot be used for the recovery.ĭrivers needed for unified BMR are determined by the operating system of the asset you are recovering and the operating system and hardware of the target recovery machine. ![]() Software RAID configurations are not supported. Once the critical volumes have been restored, recover data on the iSCSI volumes as described in Recovering File-level Backups. Recover the critical (non-iSCSI) volumes as described in Performing unified bare metal recovery. The firmware interface type (BIOS or UEFI) of the recovery target machine must match that of the failed asset. Supported for BIOS- and UEFI-based assets. Save the ISOs to your hypervisor (so you can quickly recover to a virtual machine target).įor details, see Step 1: Access the unified bare metal recovery ISO image. Ĭreate bootable CDs of these ISOs and store them in a safe place (so that you can quickly recover to a physical machine target).To prepare for DR, it is recommended that you do the following: The ISOs contain WinPE (a minimal version of Windows used for installations) and the Unitrends Unified Bare Metal Recovery wizard that guides you through the recovery. For details, see To create a file-level backup job.įor the recovery, you must use the 32-bit or 64-bit unified BMR ISO image provided on the your Unitrends appliance. If system state was excluded, you need to modify the backup job to include all critical volumes to create a backup that can be used for unified BMR. In the Backup Status: Report Entry dialog, check the Output area for System State Excluded or Included. To check whether the system state is included in a backup, run the Backup History report and select the backup in the list. Disk metadata is captured in file-level backups unless you have opted to exclude critical volumes or to exclude the system state. It is a full, differential, or incremental file-level backup that contains disk metadata (known as the asset's system state). The backup used for recovery must meet these requirements: Windows Small Business Server 2003 and later, 32-bit and 64-bit See the Compatibility and Interoperability Matrix for details.) Recovery to dissimilar hardware is NOT supported for 2003/2003 R2 and is supported for the others in this list. ![]() Recovery to identical hardware and virtual machines is supported for the server operating systems listed below. Windows XP, 32-bit and 64-bit (SP2 and later) See the Compatibility and Interoperability Matrix for details.) Recovery to dissimilar hardware is NOT supported for XP and is supported for the others in this list. Recovery to identical hardware and virtual machines is supported for the client operating systems listed below. The following requirements must be met to recover from a file-level backup.
0 Comments
Leave a Reply. |