Hardware requirements

There are many hardware configurations supported and described in "System requirements" in the Administrator Guide. However, for the evaluation purposes, we recommend deploying three nodes. This is to ensure that the cluster can survive the failure of one node without data loss. The following table lists the minimum hardware requirements for each of the three nodes. To enable high availability, you will need three nodes meeting the requirements for the management node with storage and compute.

Minimum node hardware requirements
Type Management node with storage and compute Secondary node with storage and compute Management node with storage and Backup Gateway
CPU 64-bit x86 processors with AMD-V or Intel VT hardware virtualization extensions enabled
16 cores* 8 cores* 4 cores*
RAM 32 GB 16 GB 8 GB
Storage

1 disk: system + metadata, 100+ GB SATA HDD

1 disk: storage, SATA HDD, size as required

1 disk: system, 100 GB SATA HDD

1 disk: metadata, 100 GB SATA HDD (only on the first three nodes in the cluster)

1 disk: storage, SATA HDD, size as required

1 disk: system + metadata, 120 GB SATA HDD

1 disk: storage, SATA HDD, size as required

Network

10 GbE for the private network

1 GbE for the public network

* A CPU core here is a physical core in a multicore processor (hyperthreading is not taken into account).

You will also need at least two IPs in the public network (for the highly available admin panel and for each NFS share), one IP in the private network (for the highly available management node), and two DNS names (for S3 and Backup Gateway).

Following is a sample network layout for our evaluation scenario. Your host names and addresses may differ depending on your settings.

The DNS names are used by backup agents to send backups to and retrieve them from cloud storage. If your client machines and Virtuozzo Hybrid Infrastructure nodes are located in different datacenters, we strongly recommend configuring the DNS name in one of your preferred DNS services: Azure DNS for Azure, Amazon Route 53 for Amazon, or Google Cloud DNS for Google. If it is not possible for some reason, you have to manually add the DNS name to the /etc/hosts file on each node. On the other hand, if the client machines and Virtuozzo Hybrid Infrastructure nodes are located in the same datacenter, you can use a local DNS instead of a public one to speed up the backup. A local DNS can work only with a local IP address, so we recommend using NAT in this case.

We recommend using the Google Chrome browser for accessing Virtuozzo Hybrid Infrastructure and S3 storage in our evaluation scenario.