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

Barracuda Backup Vx Functionality Differences

  • Last updated on

While the software and general functionality is the same between the physical and virtual appliances, there are some important differences between the two deployment models:

  • Barracuda Backup Vx protects all of the same environments as the physical Barracuda Backup appliance including virtual and physical servers, however, Barracuda Backup Vx can only be deployed on VMware ESXi and Microsoft Hyper-V.
  • Barracuda Backup Vx is deployed on customer infrastructure; the customer must provide a hypervisor (VMware or Hyper-V), the computer environment, and storage.
  • Barracuda Backup Vx is licensed by the number of physical CPU sockets for virtual hosts that need protection or by the number of physical machines.
  • Barracuda Backup Vx is an annual subscription. Unlike the physical appliance, customers do not need to pay for the appliance plus annual subscriptions. With Barracuda Backup Vx, they only pay the subscription price.
  • For offsite replication and disaster recovery, Barracuda recommends customers replicate to Barracuda Cloud Storage. A metered cloud storage subscription plan is available for the Barracuda Backup Vx. Note that the metered cloud pricing is only for the Barracuda Backup Vx, it cannot be applied to a physical Barracuda Backup appliance.
  • Each Backup Vx includes a second license for a Receiver Vx for basic replication. The Receiver Vx can only be used for receiving and storing data replicated from the Backup Vx and cannot be used to backup data.
  • Customers may also elect to replicate data to a physical Barracuda Backup appliance.
  • Barracuda Backup Vx can scale up to a larger capacity at any time simply by expanding the virtual disk size; no data migration is necessary.
Last updated on