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 Deployment

  • Last updated on

Do not use snapshots on the Barracuda Backup Vx appliance. Even if data is not being replicated to the Barracuda Cloud, configuration data is still sent to Barracuda so that the unit can be managed. Reverting to a previous state using snapshots can potentially cause loss of data and unit corruption. Independent disks (persistent mode) are the default selection and highly recommended to avoid snapshots.

Local Control is not supported for Barracuda Backup Vx.

Requirement: This virtual appliance requires a 64-bit capable host.

The Barracuda Backup Vx enables you to build a highly secure and scalable application infrastructure, and can be deployed in supported VMware vSphere and Microsoft Hyper-V environments.

Choosing the Right Platform

Before deploying Barracuda Backup Vx in a virtual environment, consider the following factors:

  • Barracuda Backup utilizes memory (RAM) for database queries during backup, restore, and offsite replication. For this reason, Barracuda highly recommends following the recommended minimum resources for memory as described below.
  • Barracuda uses CPU resources for hashing blocks during deduplication, compression for offsite replication, and data rehydration during restoration. It is imperative that the recommended number of cores is allocated for the virtual appliance as described below. 
  • At minimum, memory resources must be dedicated (reserved). It is also recommended that the CPU be dedicated to Barracuda Backup Vx and not shared with other virtual machines on the host. This aligns with VMware and Microsoft’s recommendations for virtualized Microsoft Exchange Server and SQL Server implementations.
  • A separate data store is recommend for use with the virtual appliance due to disk I/O constraints or an entirely separate storage server/environment altogether from the production environment.
  • Other system components such as network and storage must be sized accordingly to prevent them from becoming a bottleneck.
  • It is important that snapshots are not used on the Barracuda Backup Vx. Even if data is not replicated to the Barracuda Cloud, configuration data is still sent to Barracuda so that the appliance can be managed. Reverting to a previous state using snapshots can potentially cause loss of data and appliance corruption. Independent disks (persistent mode) are the default selection and highly recommended to avoid snapshots.

If the above considerations are acceptable and supported by your environment, then it is likely that virtualizing Barracuda Backup is a good fit for the organization.

Storage System Requirements

  • Any storage infrastructure consisting of Local/Direct-Attached, SAN, and NAS;

  • Storage with inadequate throughput, read, and write speeds will suffer;

  • Servers with software RAID, slow NAS, and low-RPM drives will yield poor performance

Table 1. VMware and Hyper-V System Requirements.

Image Type Supported Hypervisors
OVF VMware ESX and ESXi (vSphere Hypervisor) versions 4.x, 5.x, and 6.x
VHD Microsoft Hyper-V 2008, 2008 R2, 2012, 2012 R2, and 2016

Before deploying the Barracuda Backup Vx, verify your host has sufficient resources. If minimum required resources are not available, the Barracuda Backup Vx may be negatively impacted or the deployment may fail entirely. Size for capacity and performance. Tasks such as backup, offsite replication, data restoration, and purging can use a significant amount of system resources. When considering Barracuda Backup Vx deployment, take into account the use cases in addition to needed storage.

When deploying a Receiver Vx (V95), it is acceptable to use roughly 50% of the recommended vCPUs. Less resources can be used since the Receiver Vx will not be backing up or replicating data offsite. In the event of a restore or disaster recovery scenario, more resources can be added to the Receiver Vx to improve performance.


Table 2. vCPU Recommendations.

Backup Volume Minimum Recommended vCPUs High Performance Recommended vCPUs
0-2 TB 1 vCPU 2 vCPUs
2-6 TB 2 vCPUs 4 vCPUs
6-16 TB 4 vCPUs 8 vCPUs
16-32 TB 8 vCPUs 16 vCPUs
32-100 TB 16 vCPUs 32+ vCPUs

When deploying a Receiver Vx (V95), it is acceptable to use roughly 50% of the recommended RAM. Less resources can be used since the Receiver Vx will not be backing up or replicating data offsite. In the event of a restore or disaster recovery scenario, more resources can be added to the Receiver Vx to improve performance.


Table 3. RAM Recommendations.

Backup Volume Minimum Recommended RAM High Performance Recommended RAM
0-1TB 2 GB 4 GB
1-4 TB 4 GB 8 GB
4-12 TB 8 GB 16 GB
12-16 TB 16 GB 32 GB
16-24 TB 32 GB 64 GB
24-48 TB 64 GB 128 GB
48-100 TB 128 GB 256+GB


Next Step

Deploy Barracuda Backup Vx.

See Also

 

Last updated on