Release Notes for Unitrends EndPoint Backup 1.24

 

What's new in release 1.24

This document describes new features introduced in release 1.24.

 

Endpoint Backup agent

This release includes agent version 1.24. Unitrends recommends upgrading to the latest agent  version to benefit from fixes and performance enhancements. A system state backup run by  Agent version 1.24 is required to use the new bare metal recovery feature.


Bringing Full System Recovery Protection to Endpoint Backup


We are incredibly excited to announce the general availability of bare metal recovery in Endpoint Backup. Adding on to our existing and robust file & folder protection, Endpoint Backup now allows you to take a full system backup and restore either a few business-critical files or the entire system back to the same hardware, dissimilar or virtualized.


Profile changes

To take a backup sufficient for bare metal recovery, the system state and all critical volumes essential to OS functions must be backed up with agent version 1.24 or higher. Endpoint Backup now supports profiles that can capture this data during scheduled backups.

A system state backup behaves in a few different ways:

  • Critical volumes cannot be excluded
  • Unlike a file & folder backup, it includes the system state
  • System state backups are typically larger in average than targeted data backups
  • System state backups allow for both file/folder-level and bare metal recovery

System state profile:

pict_1.jpg

 

Prerequisites for bare metal recovery


The following requirements must be met to perform a bare metal recovery (BMR).

Requirement Description
Operating
systems

Recovery to identical or dissimilar physical hardware and VMware virtual machines is supported
for the operating systems listed below.
Supported client operating systems:

  • Windows 8, 64-bit only
  • Windows 10, 64-bit only

Supported server operating systems:

    • Windows 2016, 64-bit only, support does not include Nano Server
    • Windows 2019, 64-bit only
NOTE:

Unitrends supports the most recent two Service Pack (SP) versions on all releases of
Windows Server.

An eligible
system state
backup

The backup used for recovery must meet these requirements:

  • It is successful.
  • It is a full or incremental system state backup that contains all critical system volumes.
Recovery ISO

For the recovery, you must use the Endpoint Backup BMR ISO image, baremetal-recoverymedia.iso, provided on the Endpoint Backup Restore > Recovery Media page. The ISO contains WinPE (a minimal version of Windows used for installations) and the BMR UI. To prepare for DR, it is recommended that you do the following:

  • Create a bootable DVD or USB of the ISO and store it in a safe place, so that you can quickly recover to a physical machine target. (For details on creating bootable media, see this KB article.)
  • Save the ISO to your hypervisor, so that you can quickly recover to a virtual machine target).
Firmware
interface type
  • GPT disks are supported.
  • Dynamic disks are not supported.
  • iSCSI disks are not supported. Perform a bare metal recovery to recover the critical (noniSCSI) volumes. Once the critical volumes have been restored, run a file/folder recovery to restore data on the iSCSI volumes.
Disk
configuration
  • Resolved an issue where upgrading the appliance could break trap notifications if SNMP was configured with a custom Community.
Software RAID
volumes
Software RAID configurations are not supported.
Network
adapter
Wireless network adapters cannot be used for the recovery.
Processor
features on the recovery target
These processor features must be enabled on the recovery target machine: NX, PAE, and SSE2. Ensure that these features are enabled on the target before booting from the ISO image. For instructions, see KB 360013249658. Machines that do not have these processor features cannot be used for the recovery.
Disk space on recovery target Make sure the target machine has enough disk space for the recovery. The recovery target can have smaller disks than the failed asset, but the recovery fails if the disks do not have enough space for the data on the critical volumes.
Supported
recovery
scenarios

Use the procedures in Performing unified bare metal recovery for the following recovery scenarios:

    • Recover to the same physical hardware as the failed asset.
    • Recover a failed physical asset to dissimilar hardware.
    • Recover a failed physical asset to dissimilar hardware with fewer disks.
    • Recover a failed physical asset to hardware with smaller or larger disks.
    • Recover a failed asset BIOS/MBR configuration to a dissimilar BIOS/MBR configuration.
    • Recover a failed asset UEFI/GPT configuration to a dissimilar UEFI/GPT configuration.
    • Recover multi-boot configured BIOS servers.
    • Recover a failed physical asset to a VMware virtual machine (VM).
    • Recover a failed VM to a physical asset or to a VMware VM.
NOTES:
  • IaaS VMs – BMR recovery of a failed Azure, AWS, or Google Cloud Computing (GCP) VM that was configured with IaaS roles is not supported.
  • Recovering to a VMware VM – The virtual host must support the OS of the Windows asset
    you are recovering. For example, you cannot recover Windows 2016 to ESXi 5.1. See the
    VMware documentation for details.

 

 

Recovery Changes


Once you’ve successfully taken a system state backup, you have the option to perform either a file/folder-level or bare metal recovery.
File and folder recovery works the same way it does today.
To perform a bare metal recovery:

1. On the Restore > Recovery Media page, click Download ISO. The ISO, baremetal-recovery-media.iso, is downloaded.

pict_2.jpg

2. Click Create Access Key.
The key is created and displays in the list below. For easy identification, you can click above and add a custom label.

pict_3.jpg

3. Prepare the recovery media:

      • To recover to a VM, save the ISO in a location that you can access from your hypervisor. Power down the recovery VM and edit its settings to boot from the ISO.
      • To recover to a physical machine, burn the ISO to USB or DVD (see this KB article for details). Power off the recovery machine and attach the recovery media.

4. Power on the recovery target machine. The machine boots from the ISO and the BMR interface displays.

5. In the Access Key field, enter the access key you created in step 2. Be sure to include the hyphen (-).

6. Click Create Session.

pict_4.jpg

7. The key is saved and a secure session is created between the VM and Endpoint Backup in the Unitrends Cloud. (This may take a few minutes.)

Note the session ID as you will use it to identify your recovery session in Endpoint Backup.

pict_5.jpg

8. Return to the Endpoint Backup Restore > Recovery Media page.

9. Select the customer whose backup you will recover

10. Locate your recovery session and click Restore.

   NOTE:

To view information about the machine you are recovering to, click > to expand session details.

pict_6.jpg

11. Select the failed asset and the backup to recover.

   NOTE:

You can filter the asset list by entering text in the Choose Asset field. Only assets containing the string you entered display in the list.

pict_7.jpg

12. Select disks to recover by dragging each source disk to a disk on the target machine. In our example, source disks 2, 3, and 4 will be recovered to Disk 0 on the target machine.

 

   NOTES:
  • You must recover all critical disks.
  • You cannot recover disabled disks.

13. Click Restore. Click Delete Data & Start Restore to confirm.

pict_8.jpg

14. The recovery starts. When recovery is complete, simply restart your machine and get back to business!

 

Known bare metal recovery issue

In certain cases the Windows Start button does not function on the recovered asset. This will be fixed in an upcoming release.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us