It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Campus Help Center / Reference

What is the recommended hardware configuration for deploying the Barracuda SSL VPN Vx Virtual Appliance?

  • Type: Knowledgebase
  • Date changed: 3 years ago

Solution #00004522


This solution applies to all Barracuda SSL VPN Vx Virtual Appliances.


The Barracuda SSL VPN Vx hardware requirements listed below are in addition to whatever the Virtual Machine environment itself needs to run. Please refer to the appropriate documentation (e.g. the VMWare ESXi documentation) for exact requirements.


Also, VMWare products tend to measure CPU utilization in number of Megahertz (MHz) used by the Virtual Machine. This depends on:


  1. Type of processor(s) used (Intel vs AMD, Core vs Xeon vs Athlon/Phenom vs Opteron etc.)
  2. The specific amount and type of traffic going through each connection.


CPU capacity:

10 users:  350MHz

25 users:  575MHz

50 users:  950MHz

100 users: 1,750MHz (or 1.75GHz)

250 users: 3,950MHz (or ~4GHz)


To provide maximum compatibility, a Barracuda SSL VPN Vx instance is preconfigured for a single virtual processor.  If higher performance is required, the number of processors assigned can be manually adjusted so that the Virtual Machine instance can use more than 2.4GHz.



The default 1GB of RAM should be sufficient for up to 250 users, though it is recommended to use 2GB for better performance. 


The vSphere client used by VMWare ESX and ESXi displays the amount of RAM used by the appliance on the Summary tab. The following values are typical when running nominal tunnels:


Active Guest Memory:  50-250MB

Consumed Host Memory: 750-800MB


Please increase the RAM allocated if Consumed Host Memory exceeds 950MB or Active Guest Memory exceeds 500MB.


Disk Space:

- 40GB for the disk image (the download image is 2.3G, but it then allocates 40GB when installed).

- We recommend at least an additional 20GB for snapshots and other system maintenance tasks.


Additional Notes:

Users anticipating significantly more than 250 concurrent users should distribute the load over multiple Virtual Machine hosts.

Link to this page: