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

Virtual Infrastructure

  • Last updated on

Barracuda Networks recommends ensuring the latest hotfixes, patches, and updates are installed on your data sources.

Barracuda Backup provides support for the versions and platforms listed in the following tables.

Virtual Infrastructure

Type Specification Requirements
VMware Platform
  • vSphere 6.7

  • vSphere 6.5

  • vSphere 6.0

  • vSphere 5.5

  • vSphere 5.1

  • vSphere 5.0

  Hypervisors
  • ESXi 6.7

  • ESXi 6.5

  • ESXi 6.0(1)
  • ESXi 5.5

  • ESXi 5.1

  • ESXi 5.0

Free ESXi is not supported. Barracuda Backup leverages vSphere and vStorage APIs which VMware has disabled in free ESXi.

  Management Server (optional)
  • vCenter Server 6.x (optional)
  • vCenter Server 5.x (optional)
Microsoft Hyper-V Platform
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2(2)
  • Windows Server 2008
  Hypervisors
  • Windows Server Hyper-V 2016
  • Windows Server Hyper-V 2012 R2
  • Windows Server Hyper-V 2012
  • Windows Server Hyper-V 2008 R2
  • Windows Server Hyper-V 2008
  • Microsoft Hyper-V Server (free hypervisor) is supported
  Management Server (optional)
  • Microsoft System Center Virtual Machine Manager 2016 (optional)
  • Microsoft System Center Virtual Machine Manager 2012 R2 (optional)
  • Microsoft System Center Virtual Machine Manager 2012 (optional)
  • Microsoft System Center Virtual Machine Manager 2008 R2 (optional)
  • Microsoft System Center Virtual Machine Manager 2008 (optional)

Notes:
(1) VMware has reported an issue with ESXi version 6.0.x where incorrect changed sectors are returned. When a virtual machine (VM) is running ESXi 6.0.x and Changed Block Tracking (CBT) is enabled, some change areas in data are not reported. When this occurs, that data is not recognized as changed and is not backed up; current and past incremental backups are potentially compromised. For more information, see the VMware knowledgebase solution Backing up a Changed Block Tracking enabled virtual machine in ESXi 6.0.x returns incorrect changed sectors (2136854). This issue is resolved in VMware ESXi 6.0 patch ESXi600-201511001. For more information, see VMware ESXi 6.0, Patch Release ESXi600-201511001 (2137545).

(2) Microsoft does not support running Windows Server 2008/2008 R2 on Hyper-V Gen 2 VMs. Therefore, Windows Server 2008/2008 R2 physical machines with UEFI cannot be restored to Hyper-V.

Guest Virtual Machines

Type Specification Requirements
VMware Virtual Hardware
  • All types and versions of virtual hardware are supported, including 62 TB VMDK.
  • VMs with disks engaged in SCSI bus sharing are not supported, because VMware does not support snapshotting such VMs.
  • RDM virtual disks in physical mode, independent disks, and disks connected via in-guest iSCSI initiator are not supported, and are skipped from processing automatically. Network shares and mount points targeted to 3rd party storage devices are also skipped as these volumes/disks are not visible in the VM configuration file.
  Operating Systems
  • All operating systems supported by VMware.
  Software
  • VMware Tools (optional, recommended). VMware Tools are required for the following operations: application-aware processing (quiesce).
  • All latest OS service packs and patches (required for application-aware processing).
Hyper-V Virtual Hardware
  • Supported virtual hardware versions are 5.0 and 8.0 (Hyper-V 2016).

  • Both Generation 1 and 2 VMs are supported, including 64 TB VHDX disks.

  • [For Microsoft Hyper-V 2016 Server VMs] Processing of VMs with pass-through virtual disks and disks connected via in-guest iSCSI initiator is not supported.

  • [For Microsoft Hyper-V 2012 R2 server and earlier VMs] Pass-through virtual disks and disks connected via in-guest iSCSI initiator are not supported, and are skipped from processing automatically.

  Operating Systems
  • All operating systems supported by Hyper-V.
  Software
  • Hyper-V integration components (required for application-aware processing)

File-Level Restore from Guest Virtual Machines (LiveBrowse)

Virtual Disk Formats
  • VHD/VHDX Fixed
  • VHD/VHDX Dynamic
  • VMDK Thin
  • VMDK zeroedthick
  • VMDK eagerzeroedthick
Partition/Volume Structure Support
  • Master Boot Record (MBR) Disks
  • Linux Logical Volume Manager (LVM), single disk/volume only
  • GUID Partition Table (GPT)
Supported File Systems
  • NTFS
  • FAT
  • FAT32
  • ext2
  • ext3
  • ext4
  • XFS
  • Btrfs
  • ReiserFS
Supported Windows Volumes

Supported:

  • Simple

Unsupported:

  • Spanned
  • Striped
  • Mirrored
  • RAID 5 volumes

VMware Virtual Machine (LiveBoot) Instant Recovery

Type Operating System Supported File Systems
VMware Operating Systems
  • All operating systems supported by VMware(1)
  File Systems
  • FAT
  • FAT32
  • NTFS
  • ext2
  • ext3
  • ext4
  • ReiserFS
  • JFS
  • XFS
  • Btrfs
Note: (1) See VMware Guest Operating System Installation Guide for a list of operating systems supported by VMware.

VMware and Hyper-V Virtual Machine Cloud Recovery (Cloud LiveBoot)

Type Operating System Supported File Systems
VMware Operating Systems
  • All operating systems supported by VMware
  File Systems
  • FAT
  • FAT32
  • NTFS
  • ext2
  • ext3
  • ext4
  • ReiserFS
  • JFS
  • XFS
  • Btrfs
  Other
  • Barracuda Cloud LiveBoot supports a maximum of 4 virtual disks per guest VM
Hyper-V Operating Systems
  • All operating systems supported by Hyper-V
  File Systems
  • FAT
  • FAT32
  • NTFS
  • ext2
  • ext3
  • ext4
  • ReiserFS
  • JFS
  • XFS
  • Btrfs
  Other
  • Both Generation 1 and 2 VMs are supported
  • Barracuda Cloud LiveBoot supports a maximum of 4 virtual disks per guest VM

 

 

 

 

Last updated on