System Requirements

Before you start deploying Veeam Backup for Nutanix AHV, make sure the Nutanix AHV cluster meets system requirements.

Platform

  • Nutanix AHV versions 5.5.x up to 5.18.x
  • CE 2019.11.22 or later for Community Edition

Important

To integrate with Veeam Backup for Nutanix AHV, you must define the iSCSI Data Services IP address in settings of the AHV cluster. For instructions, see the Modifying Cluster Details section of the Prism Web Console Guide.

Virtual Hardware for AHV Backup Proxy VM

During the deployment process, AHV Backup Proxy is deployed as an independent Linux-based VM on a Nutanix AHV cluster that you want to protect. The AHV Backup Proxy VM must meet the following requirements.

  • CPU: x86-64 processors. 4 CPU cores plus 1 CPU core for each additional concurrent task.*
  • Memory: 4 GB RAM plus 1 GB RAM for each additional concurrent task.*
  • Disk Space: 1 GB for product installation.

*AHV Backup Proxy creates one task per every VM processed by the job. CPU and hardware resources for the AHV Backup Proxy VM are calculated automatically based on specified number of concurrent tasks. VMs with multiple CPU cores can handle more concurrent tasks. For example, for 4 concurrent tasks, it is recommended that you specify minimum 4 CPU cores and 4GB RAM, for 8 concurrent tasks — 8 CPU cores and 8 GB RAM. When defining the number of concurrent tasks, keep in mind the network traffic throughput in the virtual infrastructure.

Veeam Backup & Replication

Veeam Backup for Nutanix AHV 2.0 supports integration with Veeam Backup & Replication version 10 or later.

Important

The hostname of AHV Backup Proxy VM must be resolvable on the Veeam Backup & Replication server, and the hostname of the Veeam Backup & Replication server must be resolvable on the AHV Backup Proxy VM. Otherwise, Veeam Backup & Replication cannot connect to AHV Backup Proxy. The issue is also valid if AHV Backup Proxy is running behind NAT.

For details, see Solving Hostname Resolution Problem.

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.