Deploy a Barracuda Backup Virtual Appliance
To create a successful data protection and disaster recovery plan, Barracuda Networks strongly recommends following the 3-2-1 backup rule:
3 – You must have at least 3 copies of your data; the original production data and 2 backup copies.
2 – You must use at least 2 different types of media to store the copies of your data, for example, your production storage and the local Barracuda Backup virtual appliance data storage.
1 – You must keep at least 1 backup offsite, for example, in the cloud or in a remote site.
For deployment of the Barracuda Backup virtual appliance (Vx), Barracuda Networks recommends a completely separate virtual infrastructure from that of the data in which the Vx will be protecting. This means running in a separate virtual cluster, dedicated virtual host, and/or separate storage from the production environment. This will help avoid situations where the production virtual infrastructure or storage fails or is impacted by ransomware and impacts both the production virtual machines and the Barracuda Backup virtual appliance.
The following sections walk you through the process of deploying a Barracuda Backup Virtual (Vx) appliance.
System Platform Requirements
Barracuda Networks provides the following types of virtual images for the Barracuda Backup Vx deployment.
Table 1. System Platform Requirements
Image Type | Platform | Version |
|---|---|---|
OVF | VMware | See Virtual Infrastructure for supported versions. |
VHD | Microsoft Hyper-V | See Virtual Infrastructure for supported versions. |
System Resource Requirements
The most common mistake when designing an environment for Barracuda Backup Vx is to size only for capacity as opposed to sizing for capacity and performance. Tasks such as backup, offsite replication, data restoration, and purging can use a significant amount of system resources. When considering a Barracuda Backup virtual deployment, it is best to consider the use cases of the Backup Vx in addition to needed storage.
Table 2. vCPU Recommendations
Backup Volume | Minimum Recommended vCPUs | High Performance Recommended vCPUs |
|---|---|---|
1-2 TB | 2 vCPUs | 4 vCPUs |
2-6 TB | 4 vCPUs | 6 vCPUs |
6-12 TB | 6 vCPUs | 8 vCPUs |
12-24 TB | 12 vCPUs | 16+ vCPUs |
Table 3. RAM Recommendations
Backup Volume | Minimum Recommended RAM | High Performance Recommended RAM |
|---|---|---|
1-2 TB | 4 GB | 8 GB |
1-4 TB | 8 GB | 12 GB |
4-12 TB | 12 GB | 16 GB |
12-16 TB | 16 GB | 32 GB |
16-24 TB | 32 GB | 64 GB |
Storage Recommendations
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
Notes and Considerations
Barracuda Backup utilizes memory (RAM) for database queries during backup, restore, and offsite replication. Barracuda Networks highly recommends following the recommended minimum resources for memory in the RAM Recommendations table above.
Barracuda uses CPU resources for hashing blocks during deduplication, compression for offsite replication, and rehydration of data during restoration. Barracuda Networks highly recommends following the recommended minimum resources for vCPUs in the vCPU Recommendations table above.
At a minimum, memory resources should 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 recommended 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 need to be sized accordingly to prevent them from becoming a bottleneck.
It is important that snapshots are not used 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 are the default selection and highly recommended to avoid snapshots.
Use only a single attached virtual volume when deploying the Barracuda Backup Vx appliance. When expanding Barracuda Backup Vx capacity, expand only the current volume. Adding and expanding a new volume can potentially cause loss of data and unit corruption.
All Backup Vx disk, vCPUs, and RAM can be adjusted later by shutting down the system properly and making the necessary changes through the hypervisor.
VMware vSphere Deployment
To deploy Barracuda Backup Vx in VMware vSphere:
Microsoft Hyper-V Deployment
To deploy a Barracuda Backup Vx in VMware vSphere:
Configure and Provision the Barracuda Backup Vx
You must configure a valid external DNS to resolve to certain Barracuda infrastructure components requiring DNS entries.
If you did not recieve your Barracuda Vx license token via email or from the website when you downloaded the Barracuda Backup Vx package, request an evaluation on the Barracuda website at https://www.barracuda.com/purchase/evaluation or purchase one from https://www.barracuda.com/purchase/index. The license token looks similar to the following: 01234-56789-ACEFG.
In your hypervisor client, start the virtual appliance and allow it to boot up, then complete the following steps:
From the console, log in as admin. Your password is based on the preboot version of your virtual machine image. To find the preboot version number, look at the downloaded virtual image file. The number between -vm and -fw is the preboot version number.
For help finding the serial number of your Vx appliance, see Serial Number for Hardware and Virtual Appliances.Use your keyboard arrows to select TCP/IP Configuration, enter your network settings, and then select Save:
Use your keyboard arrows to select Licensing, enter your Barracuda license token, and then select Save:
Type YES, and press Enter to apply the license and provision the virtual machine (VM):
Allow the provisioning to complete; this may take several minutes.
Once the license is installed, press Enter to reboot the VM.
After the VM reboots, log in with username admin and password, which is either:
The numeric part of the serial number if your Vx preboot version is 4.6.1 or higher. To find the preboot version, check the name of downloaded Vx image (zip file) which is something like
BarracudaEmailSecurityGateway-p2-vm4.6.1-fw8.1.0.003-20200113-esx-vbox.zip. The text between "vm" and "-fw" in the filename is the preboot version. In this example, it is 4.6.1. The serial number of your Vx is in your invoice and in your VM Setup email.The word "admin" if your Vx preboot version is below 4.6.1.
For help finding the serial number of your virtual appliance, see Serial Number for Hardware and Virtual Appliances.
Verify both Local and Internet values are Up; Cloud changes to Up once the appliance is linked in the next step:
Activate the Barracuda Backup Vx
If you are a Barracuda MSP customer, see MSP App before proceeding.
To activate your virtual appliance,
Log into https://login.barracudanetworks.com. If you do not have an account, click Create a User, follow the account creation instructions, and log in.
Click Backup in the left pane. If this is your first time activating a Barracuda Backup appliance, click Start Backup Setup; otherwise, go to Admin > Activate Barracuda Backup.
Enter the Serial number and the Linking code from the sticker on the back of the Quick Start Guide, and click Next.
The wizard launches. In the Your Info page, enter your contact information, and click Continue.
In the Device Info page, enter a Device Name to represent the device in the UI. If you previously defined display groups, select the Display Group to which to add the device to from the drop-down menu.
Select the Time Zone from the drop-down menu.
In the Enter device location section, enter the geographical location.
Select whether to Automatically update device firmware after activation, and click Continue.
The Terms of Service page displays. Read the Terms and Conditions, and click I have read and agree to complete the linking process. Click Done.
Once your device is linked, click Go to Dashboard.
How to Expand Barracuda Backup Vx Capacity
This section describes how to scale capacity.
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 are the default selection and highly recommended to avoid snapshots.
When expanding Barracuda Backup Vx capacity, expand only the current volume. Adding and expanding a new volume can potentially cause loss of data and unit corruption.
Local Control is not supported for Barracuda Backup Vx.
Expand Barracuda Backup Vx Capacity for VMware
With the Barracuda virtual appliance powered off, right-click the appliance, and click Edit Settings.
In the Hardware tab, click Hard disk 1.
Change the Provisioned Size to the desired capacity:
Increase the amount of Memory or the number of CPUs to match the new disk capacity; refer to the tables in the System Resource Requirements section of this article for minimum recommendations.
Click OK to configure the VM.
Power on the VM. The additional disk space is detected; select Yes to format and use it:
The additional disk space is formatted and the disk resized; this may take several minutes.
Once formatting and resizing is complete, the appliance reboots:
Expand Barracuda Backup Vx Capacity for Hyper-V
With the Barracuda virtual appliance powered off, right-click the appliance, and click Settings.
In the Hardware section, click Hard Drive.
Under Virtual hard disk, click Edit:
Click Next. Choose Expand as the action:
Click Next. Specify the new disk size:
Click Next, and click Finish.
Increase the amount of Memory or the number of CPUs to match the new disk capacity; refer to the tables in the System Resource Requirements section of this article for minimum recommendations.
Click OK to reconfigure the VM.
Power on the VM. The additional disk space is detected; select Yes to format and use it.
The additional disk space is formatted and the disk resized; this may take several minutes.
Once formatting and resizing is complete, the appliance reboots:
How to Set Up a Barracuda Receiver Vx
Barracuda Backup Vx includes one-way basic software replication to a Barracuda Receiver Vx. A single Barracuda Receiver Vx license is included with each Barracuda Backup Vx subscription for one-way replication.
You can use the Barracuda Receiver Vx as a replication target and for restores. With a Receiver Vx subscription, you can pair a physical appliance and a Barracuda Receiver Vx, one-to-one. Additionally, it can be used for site-to-site replication or in conjunction with Barracuda Cloud Storage for multiple offsite copies.
To generate a license, link to your account, and provision the Barracuda Receiver Vx:
Log in to Barracuda Backup, go to the Backup > Replication page, and click Add Target.
In the Site-to-Site Replication section, click Activate:
The confirmation dialog box displays:
Contact Us
Barracuda Campus
Barracuda Support