We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Backup

Microsoft Windows Systems Recovery

  • Last updated on

In addition to restoring files and folders backed up using the Barracuda Backup Agent for Windows, you can also perform volume-based recovery, system state (OS) recovery, physical-to-virtual recovery, and perform bare metal recovery of a Microsoft Windows system.

To restore data that was backed up using the Barracuda Backup Agent, the Agent must be installed on the restoration target. The exception to this is a file or folder download, which does not require the Barracuda Backup Agent to be present. Data can be restored to any target that has the Agent installed; whether or not it was backed up previously with Barracuda Backup.

Bare Metal Recovery

The bare metal recovery method can be used to recover entire Microsoft Windows systems in the event the system has completely failed and no other recovery options are available. With a bare metal recovery, all data, settings, applications, and operating system are installed to a bare metal system (no operating system installed).

In order to perform a bare metal restore, all system volumes and the system state must be backed up on the data source. Bare metal restore requires that the target system is exact or similar hardware to the originally backed up system (source). Bare metal restore supports the following Microsoft Windows operating systems:

  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2
  • Windows Server 2008
  • Windows 10
  • Windows 8.1
  • Windows 8
  • Windows 7
Bare Metal Live ISO

Bare metal restore uses Barracuda's Bare Metal Live ISO, which the target system boots off of to create an environment that Barracuda Backup can restore to. Download the Bare Metal Live ISO from the System > Software Downloads page. Select the appropriate version, 32-bit or 64-bit, depending on the system you are restoring. Once downloaded, the Bare Metal Live ISO file can be used on a bootable disk or flash drive.

The Bare Metal Live environment is based on the Windows 8.1 pre-environment (PE). Currently, Windows Server 2016 ReFS partitions using a 4K cluster size are not supported by bare metal restore because Windows 8.1 only supports a 64K cluster size.

Once the Bare Metal Live ISO is applied to bootable media and the target system is booted from that, perform bare metal recovery of a Microsoft Windows system using the following steps:

  1. The Bare Metal Restore Utility welcome/warning screen displays. Ensure that no data is present on the target system, and click Next:
    AgentWarning.png
  2. On the Network Configuration screen, choose a network interface, configure an IP AddressSubnet Mask, and Default Gateway:
    Start.png
  3. Click Next. The Awaiting connection screen displays:
    IP_Address.png
  4. Log in to the Barracuda Backup local or cloud interface, and go to the Restore > Restore Browser page.
  5. Click Restore to the right of the Microsoft Windows system you want to restore. If you want to restore to a different backup revision of the system other than the latest, click on the system, and click View all revisions up to: <date>, and click Restore next to the backup revision:
    restore_link.png
  6. In the Restore dialog box, select Other Hostname or IP Address, and type the IP Address configured for the target system in the Bare Metal restore Utility:
    restore_dialog.png
  7. Click Start Restore.
  8. After several minutes the target system should receive the restore job from Barracuda Backup and display a list of recoverable volumes:
    Select.png

  9. Select the volumes you want to recover.

    You cannot deselect boot and system volumes as these are required for the Bare Metal restore.

    If you choose to restore to a server that does not have identical volumes as the original machine the data was backed up from, the Barracuda Backup appliance will still attempt to restore all drives even though you may have only selected one of these on the Bare Metal Restore screen. The restore will throw errors for these missing drives, but will restore the drives that exist on the target machine.

  10. Click Next to begin the system restore:
    Confirm.png

  11. When the restore is complete, click OK in the Confirmation dialog box. 

  12. Remove the bare Metal Live CD, and reboot the system.

    If the server being restored was an Exchange, SQL, or Hyper-V server, the application is installed after the bare metal restore; however, the databases or guest virtual machines (VMs) must be restored separately. 

Physical-to-Virtual Recovery of Microsoft Windows Systems

You can use the physical-to-virtual recovery (P2V) method to recover entire physical Microsoft Windows systems to a VMware or Hyper-V environment in the event the system has completely failed and no other recovery options are available. With P2V, all data, settings, applications, and operating system are installed to a VMware or Hyper-V system with no operating system installed.

In order to perform a P2V, all system volumes and the system state must be backed up on the data source. P2V requires that the target virtual system is configured with similar virtual hardware to the originally backed up physical system (source). P2V supports the following Microsoft Windows operating systems:

  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2
  • Windows Server 2008
  • Windows 10
  • Windows 8.1
  • Windows 8
  • Windows 7
Prepare the Virtual Target

Before starting the restore, you must configure the system firmware option—BIOS or Extensible Firmware Interface (EFI)—on the target virtual system to match the original physical system (source). When you select a guest operating system, BIOS or EFI is selected by default, depending on the firmware supported by the operating system. If the operating system supports BIOS and EFI, you can change the default from the Options tab of the Virtual Machine Properties editor after you create the VM and before you install the guest operating system. If you select EFI, you cannot boot an operating system that supports only BIOS, and the reverse.

When creating the target VM in VMware or Hyper-V, use the same operating system architecture and configuration as the physical target system, for example, CPU (x86 or x64), RAM, and disk configuration.

Bare Metal Restore Utility

P2V uses Barracuda’s Bare Metal Live ISO, which the target virtual system boots off of to create an environment that Barracuda Backup can restore to. Download the Bare Metal Live CD from the System > Software Downloads page. Select the appropriate version, 32-bit or 64-bit, depending on the system you are restoring. Once downloaded, the Bare Metal Live ISO file can be used to boot the target virtual machine. Once downloaded, the Bare Metal Live ISO file can be used on a bootable disk or flash drive.

The Bare Metal Live environment is based on the Windows 8.1 pre-environment (PE). Currently, Windows Server 2016 ReFS partitions using a 4K cluster size are not supported by bare metal restore because Windows 8.1 only supports a 64K cluster size.

Once the Bare Metal Live ISO is downloaded, boot the target virtual system with it, and use the following steps to perform P2V recovery of a Microsoft Windows system:

  1. The Bare Metal Restore Utility welcome/warning screen displays. Ensure that no data is present on the target system, and click Next:
    AgentWarning.png
  2. On the Network Configuration screen, choose a network interface, configure an IP AddressSubnet Mask, and Default Gateway:
    Start.png
  3. Click Next. The Awaiting connection screen displays:
    IP_Address.png
  4. Log in to the Barracuda Backup local or cloud interface, and go to the Restore > Restore Browser page.
  5. Click Restore to the right of the Microsoft Windows system you want to restore. If you want to restore to a different backup revision of the system other than the latest, click on the system, and click View all revisions up to: <date>, and click Restore next to the backup revision:
    restore_link.png
  6. In the Restore dialog box, select Other Hostname or IP Address, and type the IP Address configured for the target system in the Bare Metal restore Utility. Select Destination is a VMware or Hyper-V guest:
    Restore_VM.png
  7. Click Start Restore.
  8. After several minutes the target system should receive the restore job from Barracuda Backup and display a list of recoverable volumes:
    Select.png

  9. Select the volumes you want to recover, and click Next.

    You cannot deselect boot and system volumes as these are required for the Bare Metal restore.

    If you choose to restore to a server that does not have identical volumes as the original machine the data was backed up from, the Barracuda Backup appliance will still attempt to restore all drives even though you may have only selected one of these on the Bare Metal Restore screen. The restore will throw errors for these missing drives, but will restore the drives that exist on the target machine.

  10. Select which disks on the target VM will be used in the recovery operation:
    BMR_new.png

  11. Click Next, then click Yes to confirm your selection:
    ClickYes.png

  12. An additional warning displays:
    warning.png
  13. Click Yes to proceed, and click Next to begin the system restore:
    Confirm.png

  14. When the restore is complete, click OK in the Confirmation dialog box.

  15. Remove the bare Metal Live CD, and reboot the system.

    If the server being restored was an Exchange, SQL, or Hyper-V server, the application is installed after the bare metal restore; however, the databases or guest virtual.

Microsoft Windows System State Recovery

A Microsoft Windows system state backup protects operating system files, enabling you to recover when a machine starts but you have lost system files and/or the registry. A system state backup includes the following:

  • Domain member – Boot files, COM+ class registration database, registry
  • Domain controller – Active Directory (NTDS), boot files, COM+ class registration database, registry, system volume (SYSVOL)
  • Machine running cluster services – Additionally backs up cluster server metadata
  • Machine running certificate services – Additionally backs up certificate data

The Barracuda Backup system state restore performs a non-authoritative restore.

Incorrectly restoring the system state of a machine can make it unusable. Ensure that all troubleshooting and corrective options have been exhausted before attempting to restore the Windows system state.

Windows System State Restore

Use the following steps to perform a Windows system state restore:

  1. Boot the server into Directory Services Restore Mode (DSRM).
    1. Restart the server.
    2. When the BIOS information appears, press F8.
    3. Select Directory Services Restore Mode, and press Enter.
    4. Log in by using the Directory Services Restore Mode password.
  2. Log in to Barracuda Backup,and go to the Restore > Restore Browser page.
  3. Select the data source you want to recover, navigate to the Backup Agent container, and click the Restore link next to the System State container:
    SystemStateContainer.png
  4. In the Restore dialog, select Original Location, or manually enter the Hostname or IP address if this information has changed since the last backup:
    SelectOriginalLocation.png
  5. Click Start Restore.

  6. Go to the Reports > Restore page to monitor the progress of the restore job.

  7. When the restore job is complete, reboot the server normally.

Recover Microsoft Windows Active Directory

Before attempting to recover a domain controller, first review the following Microsoft TechNet articles for a complete list of recommendations:

Restoring a domain controller or Windows system state should only be used as a last resort or in a disaster recovery situation. Restoring the system state on a domain controller can have severe consequences. 

Per Microsoft:
If there is a working domain controller in the infrastructure, you should recover from an Active Directory domain controller failure by building a new domain controller, joining it to the existing domain, and allowing Active Directory replication to update it to the current state.

The only time you should use domain controller backup images is when the failure has resulted in loss of all the domain controllers in the infrastructure or if one or more objects have been deleted from Active Directory by accident and need to be authoritatively restored.

To recover an entire Active Directory (AD) domain controller using bare metal recovery, see the Bare Metal Recovery section.

To recover the system state of an AD domain controller, see the Recover Microsoft Windows Active Directory section. This can be used to recover from AD data corruption. AD data corruption occurs when the directory contains corrupt data that has been replicated to all domain controllers or when a large portion of the AD hierarchy has been accidentally changed (such as deletion of an OU) and this change has replicated to other domain controllers.

Last updated on