GravityZone Virtual Appliance
Supported formats and virtualization platforms
GravityZone is delivered as a virtual appliance (VA). It is available in the following formats, which support most common virtualization platforms:
OVA (compatible with VMware vSphere, View, VMware Player)
XVA (compatible with Citrix XenServer, XenDesktop, VDI-in-a-Box)
VHD (compatible with Microsoft Hyper-V)
VMDK (compatible with Nutanix Prism)
OVF (compatible with Red Hat Enterprise Virtualization)*
OVF (compatible with Oracle VM)*
RAW (compatible with Kernel-based Virtual Machine or KVM)*
*OVF and RAW packages are archived in tar.bz2 format.
For Oracle VM VirtualBox platform compatibility, refer to this section.
Support for other formats and virtualization platforms may be provided on request.
Hardware
The hardware requirements of GravityZone virtual appliance vary with the size of your network and with the deployment architecture you choose. For networks up to 3000 endpoints, you can choose to install all GravityZone roles on a single appliance, while for bigger networks, you need to consider distributing the roles among several appliances. The resources required by the appliance depend on the roles you install on it and whether or not you use Replica Set.
Note
Replica Set is a MongoDB feature that maintains replication of the database and ensures redundancy and high availability of the stored data. For more details, refer to MongoDB documentation and Managing the GravityZone Appliance.
If using Application Control, refer to the Application Control section.
If you are using role balancers in your environment, you can refer to this article for hardware recommendations.
AVX instructions must be enabled on your virtual machines to ensure compatibility and optimal functionality. As AVX is hardware-dependent, software or firmware updates cannot introduce the feature if your CPU does not support it.
The following CPU families are compatible with AVX, however, keep in mind, that not all processors support the instructions set. In general, CPUs commercially named Core i3/i5/i7/i9 support them, while Pentium and Celeron CPUs before Tiger Lake do not.
Intel: Alder Lake, Arrow Lake, Broadwell E, Broadwell, Cannon Lake, Cascade Lake, Coffee Lake, Comet Lake, Haswell E, Haswell, Ice Lake, Ivy Bridge E, Ivy Bridge, Kaby Lake, Lunar Lake, Meteor Lake, Raptor Lake, Rocket Lake, Sandy Bridge E, Sandy Bridge, Sapphire Rapids, Skylake, Skylake-X, Tiger Lake, Whiskey Lake.
AMD: “Heavy Equipment”, Bulldozer-based, Excavator-based, Jaguar-based, Piledriver-based, Puma-based, Steamroller-based, Zen 2-based, Zen 3, Zen 4, Zen+-based, Zen-based.
VIA: Nano QuadCore, Eden X4
Zhaoxin: WuDaoKou-based processors (KX-5000 and KH-20000)
Important
The measurements are a result of Bitdefender internal tests on basic GravityZone configuration and regular usage. Results may vary on the network configuration, installed software, number of generated events, etc. For custom scalability metrics, please contact Bitdefender.
vCPU
The following table informs you of the number of vCPU each role of the virtual appliance requests.
Each vCPU must be of a minimum 2GHz.
Component | Number of endpoints (up to) | |||||||
---|---|---|---|---|---|---|---|---|
250 | 500 | 1000 | 3000 | 5000 | 10000 | 25000 | 50000 | |
GravityZone basic features | ||||||||
Update Server* | 8 | 12 | 14 | 16 | 4 | 4 | 6 | 8 |
Web Console** | 6 | 10 | 12 | 12 | ||||
Communication Server | 6 | 10 | 12 | 18 | ||||
Database*** | 6 | 6 | 9 | 12 | ||||
Total | 8 | 12 | 14 | 16 | 22 | 30 | 39 | 50 |
GravityZone with Bitdefender HVI | ||||||||
Update Server* | 8 | 4 | 4 | 4 | 4 | 4 | 6 | 8 |
Web Console** | 6 | 8 | 8 | 10 | 10 | 12 | 12 | |
Communication Server | 6 | 8 | 8 | 10 | 10 | 16 | 20 | |
Database*** | 6 | 6 | 6 | 6 | 6 | 9 | 12 | |
Total | 8 | 22 | 26 | 26 | 30 | 30 | 43 | 52 |
Component | Number of Endpoints (up to) | |||||||
---|---|---|---|---|---|---|---|---|
250 | 500 | 1000 | 3000 | 5000 | 10000 | 25000 | 50000 | |
GravityZone basic features | ||||||||
Update Server* | 10 | 14 | 16 | 18 | 4 | 4 | 6 | 8 |
Web Console** | 6 | 10 | 12 | 12 | ||||
Communication Server | 6 | 10 | 12 | 18 | ||||
Database*** | 6 | 6 | 9 | 12 | ||||
Incidents Server | 4 | 4 | 6 | 6 | ||||
Total | 10 | 14 | 16 | 18 | 26 | 34 | 45 | 56 |
GravityZone with Bitdefender HVI | ||||||||
Update Server* | 10 | 4 | 4 | 4 | 4 | 4 | 6 | 8 |
Web Console** | 6 | 8 | 8 | 10 | 10 | 12 | 12 | |
Communication Server | 6 | 8 | 8 | 10 | 10 | 16 | 20 | |
Database*** | 6 | 6 | 6 | 6 | 6 | 9 | 12 | |
Incidents Server | 2 | 2 | 2 | 4 | 4 | 6 | 6 | |
Total | 10 | 24 | 28 | 28 | 34 | 34 | 49 | 58 |
* Recommended when no Relays are deployed.
** For each active integration, add one vCPU on the virtual appliance with Web Console role.
*** In case of distributed installation of roles, along with Replica Set: for each additional Database instance, add the specified number to the total amount.
RAM (GB)
Component | Number of Endpoints (up to) | |||||||
---|---|---|---|---|---|---|---|---|
250 | 500 | 1000 | 3000 | 5000 | 10000 | 25000 | 50000 | |
GravityZone basic features | ||||||||
Update Server | 16 | 16 | 18 | 20 | 2 | 2 | 3 | 3 |
Web Console* | 8 | 8 | 12 | 16 | ||||
Communication Server | 6 | 12 | 12 | 16 | ||||
Database** | 8 | 10 | 12 | 12 | ||||
Total | 16 | 16 | 18 | 20 | 24 | 32 | 39 | 47 |
GravityZone with Bitdefender HVI | ||||||||
Update Server | 16 | 2 | 2 | 2 | 2 | 2 | 3 | 3 |
Web Console* | 8 | 10 | 10 | 10 | 10 | 12 | 16 | |
Communication Server | 8 | 10 | 10 | 12 | 12 | 16 | 20 | |
Database** | 8 | 8 | 8 | 8 | 12 | 12 | 12 | |
Total | 16 | 26 | 30 | 30 | 32 | 36 | 43 | 51 |
Component | Number of endpoints (up to) | |||||||
---|---|---|---|---|---|---|---|---|
250 | 500 | 1000 | 3000 | 5000 | 10000 | 25000 | 50000 | |
GravityZone basic features | ||||||||
Update Server | 18 | 18 | 20 | 22 | 2 | 2 | 3 | 3 |
Web Console* | 8 | 8 | 12 | 16 | ||||
Communication Server | 6 | 12 | 12 | 16 | ||||
Database** | 8 | 10 | 12 | 12 | ||||
Incidents Sensor | 2 | 2 | 4 | 4 | ||||
Total | 18 | 18 | 20 | 22 | 26 | 34 | 43 | 51 |
GravityZone with Bitdefender HVI | ||||||||
Update Server | 18 | 2 | 2 | 2 | 2 | 2 | 3 | 3 |
Web Console* | 8 | 10 | 10 | 10 | 10 | 12 | 16 | |
Communication Server | 8 | 10 | 10 | 12 | 12 | 16 | 20 | |
Database** | 8 | 8 | 8 | 8 | 12 | 12 | 12 | |
Incidents Sensor | 2 | 2 | 2 | 2 | 2 | 4 | 4 | |
Total | 18 | 28 | 32 | 32 | 36 | 40 | 47 | 55 |
* For each active integration, add one GB RAM on the virtual appliance with Web Console role.
** In case of distributed installation of roles, along with Replica Set: for each additional Database instance, add the specified number to the total amount.
Free Disk Space (GB)
Component | Number of endpoints (up to) | ||||||||
---|---|---|---|---|---|---|---|---|---|
250 | 250* | 500 | 1000 | 3000 | 5000 | 10000 | 25000 | 50000 | |
GravityZone basic features | |||||||||
Update Server | 120 | 160 | 160 | 200 | 200 | 80 | 80 | 80 | 80 |
Web Console | 80 | 80 | 80 | 80 | |||||
Communication Server | 80 | 80 | 80 | 80 | |||||
Database** | 80 | 120 | 200 | 500 | |||||
Total | 120 | 160 | 160 | 200 | 200 | 320 | 360 | 440 | 740 |
GravityZone with Bitdefender HVI | |||||||||
Update Server | 120 | 160 | 80 | 80 | 80 | 80 | 80 | 80 | 80 |
Web Console | 80 | 80 | 80 | 80 | 80 | 80 | 80 | ||
Communication Server | 80 | 80 | 80 | 80 | 80 | 80 | 80 | ||
Database** | 80 | 80 | 100 | 100 | 160 | 300 | 700 | ||
Total | 120 | 160 | 320 | 320 | 340 | 340 | 400 | 540 | 940 |
Component | Number of endpoints (up to) | ||||||||
---|---|---|---|---|---|---|---|---|---|
250 | 250* | 500 | 1000 | 3000 | 5000 | 10000 | 25000 | 50000 | |
GravityZone basic features | |||||||||
Update Server | 150 | 160 | 190 | 230 | 230 | 80 | 80 | 80 | 80 |
Web Console | 80 | 80 | 80 | 80 | |||||
Communication Server | 80 | 80 | 80 | 80 | |||||
Database** | 110 | 150 | 230 | 530 | |||||
Total | 150 | 190 | 190 | 230 | 230 | 350 | 390 | 470 | 770 |
GravityZone with Bitdefender HVI | |||||||||
Update Server | 150 | 190 | 80 | 80 | 80 | 80 | 80 | 80 | 80 |
Web Console | 80 | 80 | 80 | 80 | 80 | 80 | 80 | ||
Communication Server | 80 | 80 | 80 | 80 | 80 | 80 | 80 | ||
Database** | 110 | 110 | 130 | 130 | 190 | 330 | 730 | ||
Total | 150 | 190 | 350 | 350 | 370 | 370 | 430 | 570 | 970 |
Important
It is highly recommended to use Solid-state drives (SSDs).
* Additional SSD space required when choosing the automatic installation, because it also installs the Security Server. After installation is complete, you can uninstall the Security Server to free disk space.
** In case of distributed installation of roles, along with Replica Set: for each additional Database instance, add the specified number to the total amount.
Application Control
Counting on the number of endpoints using Application Control, GravityZone has specific hardware and deployment requirements.
Number of endpoints | Minimum recommended GravityZone configuration |
---|---|
<500 | All roles installed on one appliance |
500 - 2999 | Distributed environment, one role per each appliance |
3000 - 4999 | Distributed environment:
|
5000 - 9999 | Distributed environment:
|
10000 - 24999 | Distributed environment:
|
25000 - 49999 | Distributed environment:
|
50000 < | Distributed environment:
|
If you have endpoints with a high volume of installed applications, meaning high volatility in the entire infrastructure, consider the next level of specifications to make sure that everything works as intended.
For distributed environments, each role should have this minimum hardware configuration:
4 x vCPUs
8 GB of RAM
120 GB thin provisioned SDD storage
Internet connection
The GravityZone appliance requires Internet access.