System Requirements
Make sure that servers that you plan to use as backup infrastructure components meet the listed system requirements.
Note |
The information on this page is valid as of the date of the last page update. |
Limitations and Recommendations
Coexistence with Mission-Critical Production Servers
We do not recommend you to install Veeam Backup & Replication and its components on mission-critical machines in the production environment such as vCenter Server, Domain Controller, Microsoft Exchange Server, Small Business Server/ Windows Server Essentials and so on. If possible, install Veeam Backup & Replication and its components on dedicated machines. Backup infrastructure component roles can be co-installed.
Microsoft Windows Server Core
You can assign roles of a backup proxy, backup repository, WAN accelerator, Veeam Cloud Connect infrastructure components and tape infrastructure components to machines running Microsoft Windows Server Core.
Installing Veeam Backup & Replication and Veeam Backup Enterprise Manager on a Windows OS machine without Desktop Experience (Core) is not supported.
Windows Server IoT/Windows Storage Server Support
For information about support of Windows Server IoT/Windows Storage Server, see this Veeam KB article.
Domain Member
The machine on which you plan to install Veeam Backup & Replication does not necessarily need to be a domain member. However, if you plan to restore Microsoft Exchange items from the Veeam Backup Enterprise Manager UI, you must install Veeam Backup Enterprise Manager on the domain member server from the Microsoft Active Directory forest in which Microsoft Exchange mailboxes are located.
Veeam backup infrastructure components support the following TLS versions:
- TLS 1.3 is partially supported by backup infrastructure components installed on Microsoft Windows Server 2022. PowerShell components and components using OpenSSL do not support TLS 1.3.
- TLS 1.2.
Note |
For security reasons, disable outdated protocols TLS 1.0 and 1.1 if they are not needed. For more information, see this Microsoft article. |
To avoid negotiation problems between Veeam Backup & Replication and a Microsoft Windows server, ensure that both sides of communication support the same cipher suites.
To avoid negotiation problems between Veeam Backup & Replication and a Linux server, the latter should use ciphers, Key Exchange (KEX) algorithms, and MAC algorithms compatible with SSH libraries supported by Veeam Backup & Replication:
Algorithms | Supported values |
|---|---|
Ciphers | Recommended: aes128-ctr, aes192-ctr, aes256-ctr, aes128-gcm@openssh.com, aes256-gcm@openssh.com, chacha20-poly1305@openssh.com Supported for backward compatibility: 3des-cbc, 3des-ctr, aes128-cbc, aes192-cbc, aes256-cbc, arcfour, arcfour128, arcfour256, blowfish-cbc, blowfish-ctr, cast128-cbc, twofish-cbc, twofish128-cbc, twofish128-ctr, twofish192-cbc, twofish192-ctr, twofish256-cbc, twofish256-ctr |
KEX algorithms | Recommended: diffie-hellman-group-exchange-sha256, diffie-hellman-group14-sha256, diffie-hellman-group15-sha512, diffie-hellman-group16-sha512, ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, curve25519-sha256, curve25519-sha256@libssh.org Supported for backward compatibility: diffie-hellman-group1-sha1, diffie-hellman-group14-sha1, diffie-hellman-group-exchange-sha1 |
MAC algorithms | Recommended: hmac-sha2-256, hmac-sha2-512 Supported for backward compatibility: hmac-md5, hmac-md5-96, hmac-sha-256-96, hmac-sha1-96, hmac-sha2-512-96, hmac-ripemd160, hmac-ripemd160@openssh.com, hmac-sha1 |
Ensure that your SSH configuration on the Linux server allows you to use at least one cipher, KEX algorithm, and MAC algorithm from the table above. You can run the following command to verify the list of allowed algorithms:
sudo sshd -T | grep "\(ciphers\|macs\|kexalgorithms\)" |
All-in-One Installations
For all-in-one installations, you can subtract 2 GB of memory resources from each but one role. These 2 GB are allotted to the OS itself, assuming each component is installed on the dedicated server.
Each of the following components for unstructured data backup may consume up to 4 GB RAM per task (in case of deduplicating storage appliances, up to 8 GB RAM): backup repository, general-purpose backup proxy, cache repository. Make sure you allocate enough memory resources for your installation. For all-in-one installations, where the server performs several roles, it must have enough memory resources for all components.
Sharing Backup Infrastructure Components Across Veeam Installations
Using Linux-based shared backup infrastructure components across different Veeam installations is not supported.
As for non-Linux backup infrastructure components, we do not recommend using them shared across different Veeam installations due to several reasons:
- Veeam installations compete for resources.
- Backup components cannot simultaneously interact with Veeam Backup & Replication of different versions.
- Adding the same repository to different Veeam Backup & Replication installations may lead to corrupted backup and data in the database.
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor (minimum 4 cores recommended). Memory: 8 GB RAM plus 500 MB RAM for each concurrent job. Memory consumption varies according to the number of VMs in the job, size of VM metadata, size of production infrastructure, and so on. [For users with tape installations] For system requirements for large number of files in the file backup to tape job, see the Before You Begin section for file backup to tape. Disk Space: 5 GB1 for product installation and 4.5 GB for Microsoft .NET Framework 4.7.2 installation. 10 GB per 100 VM for guest file system catalog folder (persistent data). Additional free disk space for Instant Recovery cache folder (non-persistent data, at least 100 GB recommended). At least 10 GB for storing logs, although the disk space required for logging depends on the set of features used and may significantly increase. For details on logs locations, see Logging. When upgrading Veeam Backup & Replication, additional disk space is required. For details, see the Upgrade Checklist section. Network: 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported. 1 Here and throughout this document GB is considered as 2^30 bytes, TB as 2^40 bytes. |
OS | 64-bit versions of the following Microsoft Windows operating systems are supported1:
1 Running Veeam backup server or any of Veeam backup infrastructure components on Insider versions of Microsoft Windows OS (both Client and Server) is not supported. 2 VMware Cloud Director servers cannot be added or used in this version of Microsoft Windows OS. 3 There may be issues when using Veeam Backup for Nutanix AHV with backup server running on this version of Microsoft Windows OS. For more information, see this Veeam KB article. |
Configuration Database | Local or remote installation of the following versions of PostgreSQL1:
The PostgreSQL instance must have UTF-8 as the default encoding for the database. Local or remote installation of the following versions of Microsoft SQL Server1:
All editions of Microsoft SQL Server are supported. The usage of Microsoft SQL Server Express Edition is limited by the database size up to 10 GB. If you plan to have larger databases, use other editions of Microsoft SQL Server. If you plan to use a database engine other than PostgreSQL 15.x, included in the Veeam Backup & Replication setup, you must install it yourself. If you want to use an already installed PostgreSQL instance for the configuration database, make sure the instance contains the default postgres database. If you allow the setup to install a new PostgreSQL instance, the postgres database will be created on the instance automatically. Since Veeam Backup & Replication connects to the postgres database to access the configuration database, do not rename the postgres database upon the installation. Veeam Backup & Replication does not support Microsoft SQL Server database with case-sensitive collations. Veeam Backup & Replication and Veeam Backup Enterprise Manager configuration databases can be deployed in Microsoft SQL Always On Availability Groups. For more information, see this Veeam KB article. 1 Consider the following:
|
Software | During setup, the system configuration check is performed to determine if all prerequisite software is available on the machine where you plan to install Veeam Backup & Replication. If some of the required software components are missing, the setup wizard will offer you to install missing software automatically. This refers to:
The backup server installation also requires the automatic installation of the prerequisite software for Veeam Cloud Plug-Ins. The following software must be installed manually:
If you plan to install Veeam Backup & Replication in the unattended mode using the command line interface, manually install all prerequisite software before that. For more information, see Installing Veeam Backup & Replication in Unattended Mode. |
Consider the following:
- If you plan to back up VMs running Microsoft Windows Server 2012 R2 or later, and Data Deduplication is enabled for some VM volumes, it is recommended that you deploy the Veeam Backup & Replication console and mount server on a machine running same or later version of Microsoft Windows Server with Data Deduplication feature enabled. Otherwise, some types of restore operations for these VMs (such as Microsoft Windows File-Level Recovery) may fail.
- Due to its limitations, Microsoft SQL Server Express Edition can only be used for evaluation purposes or in case of a small-scale production environment. For environments with a lot of VMs, it is necessary to install a fully functional commercial version of Microsoft SQL Server.
For more information, see the Backup Server section.
Veeam Backup & Replication Console
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor. Memory: 8 GB RAM Disk Space: 500 MB for product installation and 4.5 GB for Microsoft .NET Framework 4.7.2 installation. Network: 1 Mbps connection to the backup server. High latency and low bandwidth impact user interface responsiveness. |
OS | 64-bit versions of the following Microsoft Windows operating systems are supported:
|
Software | During setup, the system configuration check is performed to determine if all prerequisite software is available on the machine where you plan to install the Veeam Backup & Replication Console. If some of the required software components are missing, the setup wizard will offer you to install missing software automatically. This refers to:
The following software must be installed manually:
|
For more information, see the Backup & Replication Console section.
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor with 2 cores (vCPUs) minimum, plus 1 core (vCPU) for each 2 additional concurrent tasks. Using faster processors improves data processing performance. For more information, see Limitation of Concurrent Tasks. Memory: 2 GB RAM plus 1 GB for each concurrent task. The actual size of memory required may be larger and depends on the amount of data to back up, machine configuration, and job settings. Using faster memory improves data processing performance. Disk Space: 750 MB for Microsoft Windows-based proxies; 400 MB for Linux-based proxies. Network: 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported. |
OS | 64-bit versions of the following Microsoft Windows operating systems are supported, including Core edition:
64-bit versions of the following Linux distributions are supported. Note that bash shell and SSH are required.
|
For more information, see the VMware Backup Proxies section.
Workers process the backup workload and distribute the backup traffic when transferring data to backup repositories. If you deploy a worker using the default configuration, the following compute resources will be allocated:
Specification | Requirement |
|---|---|
Hardware | CPU: 6 cores (vCPUs). Memory: 6 GB RAM Disk Space: 100 GB for product installation and logs. |
With the default configuration, the worker can handle up to 4 concurrent backup and restore tasks. While deploying a new worker or editing settings of an existing one, you can increase the maximum number of concurrent tasks. However, you must allocate 1 vCPU and 1 GB RAM for each additional task. When configuring the maximum number of concurrent tasks, you must also take into account the network traffic throughput in your virtual infrastructure.
For more information, see the Veeam Backup for Proxmox VE User Guide.
The following table shows the minimum system requirements for a general-purpose backup proxy used for unstructured data backup and Veeam Agent and storage system snapshot integration.
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor with 2 cores (vCPUs) minimum. Using multi-core processors improves data processing performance and allows for more tasks to be processed concurrently. Memory: [For unstructured data backup] 2 GB RAM plus 4 GB RAM for each concurrent task. [For Veeam Agent and storage system snapshot integration] 2 GB RAM plus 1 GB for each concurrent task. Using faster memory improves data processing performance. For all-in-one installations, where the server performs several roles, it must have enough memory resources for all components. Disk Space: 300 MB. Network: High latency and reasonably unstable WAN links are supported. |
OS | 64-bit versions of the following Microsoft Windows operating systems are supported, including Core edition:
Backup proxies running Microsoft Windows Server 2012 R2 or later support the VSS for SMB File Shares feature. To use it, make sure that all requirements listed in this Veeam KB article are met. For object storage backup, also 64-bit versions of the following Linux distributions are supported:
|
For more information, see the General-Purpose Backup Proxies section.
The following table shows the minimum system requirements for a VMware CDP proxy.
Specification | Requirement |
|---|---|
Hardware | CPU : x86-64 processor with 4 cores (8 cores before Veeam Backup & Replication 12.1 (build 12.1.0.2131)) minimum. Using multi-core processors improves data processing performance and allows for more tasks to be processed concurrently. Enabling the encryption may cause the performance reduction: in this case, increase the vCPU count up to 2 times. Memory: 8 GB RAM minimum (16 GB RAM before Veeam Backup & Replication 12.1 (build 12.1.0.2131)). Using more memory allows for longer peak write I/O periods before a CDP policy switches to the disk-based write I/O cache. Using faster memory improves data processing performance. Disk Space: 300 MB plus disk-based write I/O cache (non-persistent data, at least 50 GB recommended). Larger cache allows for longer network downtime periods before a CDP policy switches to the CBT mode. Network: 100 Mbps or faster. |
OS | 64-bit versions of the following Microsoft Windows operating systems are supported, including Core edition:
64-bit versions of the following Linux distributions are supported. Note that bash shell and SSH are required.
|
For more information, see the VMware CDP Proxies section.
These requirements also apply to separate mount servers (they can be only Windows-based), gateway servers for unstructured data backup, deduplicating appliance-based repositories and cache repository servers.
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor. The number of cores depends on the concurrent task settings. For more information, see Limitation of Concurrent Tasks. Memory: 4 GB RAM, plus not less than 1 GB RAM for each concurrently processed machine disk. For more information, see Limitation of Concurrent Tasks. [For unstructured data backup] Not less than 4 GB RAM for each concurrently processed unstructured data source (file share or object storage); in case of deduplicating storage appliances, up to 8 GB RAM. Additionally, 1GB RAM is required for indexing each 200 million objects (files and folders). In case of all-in-one installations for unstructured data backup, where the server performs several roles, it must have enough memory resources for all components. Network: 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported. |
OS | 64-bit versions of the following Microsoft Windows operating systems are supported, including Core edition:
64-bit versions of the following Linux distributions are supported:
Bash shell and SSH are required to deploy the management agent (SSH connection is not required for updating Veeam components and can be disabled afterwards). Perl is required only for non-persistent Veeam Data Movers. Check the full list of required Perl modules in this Veeam KB article. For advanced XFS integration (fast clone), only the following 64-bit Linux distributions are supported:
For other distributions, XFS integration support is experimental, with kernel version 5.4 or later recommended. For more information, see this Veeam KB article. |
For more information, see the Backup Repositories section.
Note |
Consider the following:
|
The following storage types can be used as a cache repository for unstructured data backup:
- Direct attached storage. You can add virtual and physical servers as cache repositories:
- Microsoft Windows server (only 64-bit versions are supported).
- Linux server (only 64-bit versions are supported).
- Network attached storage. You can add SMB (CIFS) Share or NFS Share as a cache repository.
For system requirements of backup repositories that can be used as a cache repository, see Backup Repository.
For more information, see Cache Repository in the Backup Infrastructure for Unstructured Data Backup section.
Cache Repository for Object Storage Repository
If the cache repository works with an unstructured data source being backed up to an object storage repository, it also processes active metadata that is heavily used during backup and restore operations. So you will require more disk space for the cache repository. The volume of this disk space depends on the number of the file versions on the data source and the number of unstructured data backup jobs that protect this data source. We recommend allocating not less than 1 GB of disk space for active metadata of each 1,000,000 file versions protected with 1 file backup job or object storage backup job. If you protect the same data source, for example, with 2 different backup jobs, the volume of metadata will double. For more information, see the Unstructured Data Backups in Object Storage Repositories section.
Tip |
We strongly recommend utilizing a fast storage disk, for example, an SSD in the role of the cache repository used for working with an object storage repository. |
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor with 2 cores (vCPUs) minimum. Using multi-core processors improves data processing performance and allows for more tasks to be processed concurrently. Memory: 2 GB RAM plus 500MB for each concurrent task. Depending on the source of tape jobs, different entities are considered tasks: for machine backup to tape, a task covers a source job or a source chain if tape paralleling is enabled; for file backup to tape, a task covers an entire server or a file share. Restoring VMs directly from tape requires 400MB of RAM per 1TB of the restored virtual disk size. Tape cloning requires 1GB RAM for each concurrent task. Disk Space: 300 MB, plus 10 GB for temporary data storage for backup and restore operations. Network: 1 Gbps or faster. For system requirements for backup to tape jobs, see the Before You Begin section for backup to tape. For system requirements for large number of files in the file backup to tape job, see the Before You Begin section for file backup to tape. |
OS | 64-bit versions of the following Microsoft Windows operating systems are supported, including Core edition:
64-bit versions of the following Linux distributions are supported1:
1 Note that the tape server requires root access rights. For this reason, hardened repository cannot be used as the tape server. |
For more information, see the Tape Servers section.
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor. Using multi-core processors improves data processing performance, and is highly recommended on WAN links faster than 10 Mbps. Memory: 8 GB RAM. Using faster memory improves data processing performance. Disk Space: Disk space requirements depend on the WAN Accelerator role. Source WAN Accelerator requires 20 GB per 1 TB of source data to store digests of data blocks of source VM disks. Disk space consumption is dynamic and changes as unique VMs are added to (or removed from) jobs with WAN Acceleration enabled. Target WAN Accelerator requires global cache size as defined by user (fixed amount). Disk space is reserved immediately upon selecting the WAN Accelerator as a target one in any job. For more information, see WAN Accelerator Sizing. Network: 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported. |
OS | 64-bit versions of the following Microsoft Windows operating systems are supported, including Core edition:
|
For more information, see the WAN Accelerators section.
Note |
Global cache is not leveraged by source WAN accelerators, or by WAN accelerators operating in the High bandwidth mode, so it does not need to be allocated and populated in such cases. |
Backed up data can be stored in the following disk-based systems:
- Local (internal) storage of the backup repository
- Direct Attached Storage (DAS)
The DAS must be connected to the backup repository, including external USB/eSATA drives, USB pass through and raw device mapping (RDM) volumes.
- Storage Area Network (SAN)
The backup repository must be connected into the SAN fabric through hardware or virtual HBA, or software iSCSI initiator.
- Network Attached Storage (NAS)
The NAS must be able to present its capacity as NFS share (protocol versions 3.0 and 4.1 only) or SMB (CIFS) share (any protocol versions). Using SMB (CIFS) protocol for non-continuously available (CA) file shares is not recommended for reliability reasons. Using consumer-grade NAS storage without an enterprise-grade RAID controller with battery-backed write cache (BBWC) is not recommended for reliability considerations.
- Veeam Data Cloud Vault
- Amazon S3
- Google Cloud Storage
- IBM Cloud Object Storage
- Microsoft Azure Blob Storage
- Wasabi Hot Cloud Storage
- Any S3-compatible object storage (on-premise appliance, or cloud storage provider)
- Dell Data Domain (DD OS version 7.3 to 8.0) with DDBoost license. Both Ethernet and Fibre Channel (FC) connectivity is supported.
- ExaGrid1 (firmware version 5.0.0 or later)
- Fujitsu ETERNUS CS8001 software version 3.4.0 or later
- HPE StoreOnce (firmware version 3.18.18 or later for Gen3 and 4.2.3 or later for Gen4) with Catalyst license
Both Ethernet and Fibre Channel (FC) connectivity are supported. Note that HPE StoreOnce Federated Catalyst is not supported.
- Infinidat InfiniGuard1 version 3.6 and later
- Quantum1 (DXi software 3.4.0 or later)
Supported Quantum DXi systems include DXi4700 (NAS configuration), DXi4700 (multi-protocol configuration), DXi 4800, DXi 6900, DXi 6900-S, DXi 9000, DXi 9100, and DXi V5000. FIPS-compliant operations mode requires DXi software 4.0 or later.
1 These storage systems use the Veeam Transport Service. Make sure that they also meet system requirements for the backup repository.
Once backups are created, they can be copied (for redundancy) or offloaded (for long-term retention) to one of the following hot object storage types using the scale-out backup repository Capacity Tier:
- Veeam Data Cloud Vault
- Amazon S3 (including AWS Snowball Edge)
- Google Cloud Storage
- IBM Cloud Object Storage
- Microsoft Azure Blob storage (including Microsoft Azure Data Box)
- Wasabi Hot Cloud Storage
- Any S3-compatible object storage (on-premises appliance, or cloud storage provider)
Once backups are created on Amazon S3, Microsoft Azure Blob Storage, or S3-compatible object storage systems with the archiving extension of Smart Object Storage API, they can be further archived to one of the following respective cold object storage classes using the scale-out backup repository Archive Tier:
- Amazon S3 Glacier Instant Retrieval
- Amazon S3 Glacier Flexible Retrieval
- Amazon S3 Glacier Deep Archive
- Microsoft Azure Archive Tier
- Microsoft Azure Cold Tier
- Any S3-compatible object storage with data archiving enabled
For the full list of partner-tested solutions including primary backup storage solutions, S3-compatible object storage solutions and offline storage solutions, see this Veeam page.
For information on unstructured data backup target, see Storage Repositories in the Backup Infrastructure for Unstructured Data Backup section.
Veeam CDP Source and Target Datastores
The following source and target datastores are supported for Veeam CDP:
- NFS on file storage
- VMFS on block storage
- VMFS on internal ESXi storage
- VSAN
VSAN is supported for all hyper-converged infrastructure (HCI) appliances.
- vVol
vVol is supported for the following vendors: NetApp, HPE Nimble, Pure Storage and HPE 3PAR. For the list of tested vendor product lines, see this Veeam KB article.
Support for HCI appliances is pending validation by Veeam. The documentation will be updated based on the testing results. For the updates, see CDP Requirements and Limitations.
Note |
Consider the following:
|
Specification | Requirement |
|---|---|
Hardware | The following types of tape libraries (including VTL) and standalone drives are supported:
Tape device must be directly attached to the backup server or to a tape proxy server through SAS, FC or iSCSI interface. Note that VMware does not support connecting tape libraries to ESXi for VM pass-through. |
Software |
|
For more information, see the Tapes section.
Veeam Backup & Replication provides different types of snapshot integrations and these integrations support different storage systems:
- NAS integration with built-in storage systems
- VMware and Veeam Agent Integrations with built-in storage systems
VMware and Veeam Agent Integrations with Universal Storage API integrated systems
NOTE |
[For VMware integration] You may encounter scenarios when Veeam Backup & Replication and the storage system support different versions of the virtual platform. In such cases, we recommend using versions supported by the storage system. If other versions are used, Veeam support will assist only with issues unrelated to version compatibility. |
NAS integration is possible with the following built-in storage systems.
Dell PowerScale (formerly Isilon)
- Filer integration for NAS backup functionality
- NFS or SMB (CIFS) connectivity
- OneFS 8.1.2 to 9.9
- NFS or SMB (CIFS) connectivity
- ONTAP 7-mode versions 8.2 up to 8.2.5
- ONTAP cluster-mode versions 9.1 to 9.15.1
- NFS, Fibre Channel or iSCSI connectivity
- ONTAP 7-mode versions 8.2 up to 8.2.5
- ONTAP cluster-mode versions 9.1 to 9.15.1
Lenovo ThinkSystem DM/DG Series
- NFS or SMB (CIFS) connectivity
- ONTAP 7-mode versions 8.2 up to 8.2.5
- ONTAP cluster-mode versions 9.1 to 9.15.1
NetApp ONTAP FAS/AFF/ASA, FlexArray (V-Series), Edge/Select/Cloud VSA
- NFS or SMB (CIFS) connectivity
- ONTAP 7-mode versions 8.2 up to 8.2.5
- ONTAP cluster-mode versions 9.1 to 9.15.1
- Filer integration for NAS backup functionality
- NFS or SMB (CIFS) connectivity
- Nutanix File Server 3.8.1.3 to 5.0
VMware and Veeam Agent Integrations with Built-in Storage Systems
VMware and Veeam Agent integrations are possible with the following built-in storage systems.
- VMware integration only
- NFS connectivity only
- HyperFlex 4.0(2x) or later (Backup from Storage Snapshots, Full Integration mode)
- Basic authentication is not supported for SSO users in HyperFlex
Dell VNX, VNX2, VNXe and Unity XT, Unity
- NFS, Fibre Channel (FC) or iSCSI connectivity
- Dell VNX/VNX2 all OE versions are supported
- Dell VNXe OE versions 3.x
- Dell Unity XT/Unity OE versions 5.0 to 5.4
- NFS, Fibre Channel or iSCSI connectivity
- ONTAP 7-mode versions 8.2 up to 8.2.5
- ONTAP cluster-mode versions 9.1 to 9.15.1
- Fibre Channel (FC) or iSCSI connectivity
- 3PAR OS versions 3.2.2 up to 3.3.2
- WSAPI 1.5 and later
- iSCSI VLAN tags are supported
- Fibre Channel (FC) or iSCSI (starting from OS versions 4.3 or later) connectivity
- OS versions 4.x
- Fibre Channel (FC) or iSCSI connectivity
- OS version 9.3 or later
- Fibre Channel (FC) or iSCSI connectivity
iSCSI is supported starting from OS version 10.3.
- OS version 10.2 or later
HPE Nimble Storage AF-Series, HF-Series and CS-Series
- Fibre Channel (FC) or iSCSI connectivity
- Nimble OS 5.0 and later
- Fibre Channel (FC) or iSCSI connectivity
- OS version 6.1
HPE StoreVirtual (formerly LeftHand/P4000 Series) and StoreVirtual VSA
- iSCSI connectivity only
- LeftHand OS versions 9.5 up to 12.8
- HPE SV3200 (LeftHand OS version 13) is not supported
- NFS, Fibre Channel or iSCSI connectivity
- ONTAP 7-mode versions 8.2 up to 8.2.5
- ONTAP cluster-mode versions 9.1 to 9.15.1
Lenovo ThinkSystem DM/DG Series
- NFS, Fibre Channel or iSCSI connectivity
- ONTAP 7-mode versions 8.2 up to 8.2.5
- ONTAP cluster-mode versions 9.1 to 9.15.1
NetApp ONTAP FAS/AFF/ASA, FlexArray (V-Series), Edge/Select/Cloud VSA
- NFS, Fibre Channel or iSCSI connectivity
- ONTAP 7-mode versions 8.2 up to 8.2.5
- ONTAP cluster-mode versions 9.1 to 9.15.1
VMware and Veeam Agent Integrations with Universal Storage API Integrated Systems
To start working with Universal Storage API integrated systems, you must install storage system plug-ins. VMware and Veeam Agent integrations are possible with the following storage systems.
- Fibre Channel (FC) or iSCSI connectivity
- DataCore SANsymphony 10.0 PSP12 or later
- Fibre Channel (FC) or iSCSI connectivity
- Dell PowerMax/VMAX All Flash (PowerMax OS microcode family 5978 or later)
- Unisphere for PowerMax 9.2.1.6 or later
- Fibre Channel (FC) or iSCSI connectivity
- Dell PowerStore (PowerStore OS 3.0 or later)
Dell SC Series (formerly Compellent)
- Fibre Channel (FC) or iSCSI connectivity
- Storage Center OS 7.4.2 or later
- FluidFS volumes and Live Volumes are not supported
Fujitsu ETERNUS AF and DX Series
- Fibre Channel (FC) or iSCSI connectivity
- ETERNUS AF series: AF250 S2, AF650 S2, AF150 S3, AF250 S3, AF650 S3
- ETERNUS DX series: DX60 S4, DX100 S4, DX200 S4, DX500 S4, DX600 S4, DX8900 S4, DX60 S5, DX100 S5, DX200 S5, DX500 S5, DX600 S5, DX900 S5, DX600 S6, DX900 S6, DX8900 S6
- Storage firmware version:
- ETERNUS AF S2 and DX S4 series (except DX8900 S4): V10L88-1000 or later
- ETERNUS AF S3 and DX S5 series, DX8900 S4: V11L30-5000 or later
- ETERNUS DX S6 series: V12L10-0000 or later
- Fibre Channel (FC) or iSCSI connectivity
- VSP E series (93-03-01-60/00 or later)
- VSP F series (88-07-01-x0/00 or later)
- VSP G series (88-07-01-x0/00 or later)
- VSP 5100 and VSP 5500 (90-05-01-00/00 or later)
- VSP 5200 and VSP 5600 (90-08-01-00/00 or later)
- Fibre Channel (FC) or iSCSI connectivity
- HPE XP8 (90-05-01-00/00 or later)
IBM FlashSystem (formerly Spectrum Virtualize, includes IBM StorWize and IBM SVC)
- Fibre Channel (FC) or iSCSI connectivity
- IBM Spectrum Virtualize OS version 8.2 or later
- Policy-based replication is not supported
- NFS, Fibre Channel (FC) or iSCSI connectivity
- InfiniBox 5.0 or later
Note |
You must add to the backup infrastructure only one of the two InfiniBox storage arrays for which Active/Active Replication is configured, or exclude the replicating volumes on one of these arrays from rescan. For details on how to exclude volumes from rescan, see Rescanning Storage Systems. |
- Fibre Channel (FC) or iSCSI connectivity
- M120, M320, M320F, M520, M720, M720F (Storage Control Software revision 1234 or later)
- Fibre Channel (FC) or iSCSI connectivity
- V100, V300 (93-04-21-XX or later), V10e (88-08-09-XX or later)
- iSCSI connectivity
- Element OS version 10.0 or later
- Fibre Channel (FC) or iSCSI connectivity
- Purity 4.10 or later
Tintri IntelliFlash (formerly Western Digital IntelliFlash, Tegile)
- NFS, Fibre Channel (FC) or iSCSI connectivity
- Tintri IntelliFlash 3.11 or later
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor, 2 or more cores. Memory: 4 GB RAM, plus up to 4 GB RAM for each concurrently processed machine, file share or object storage. For more information, see Limitation of Concurrent Tasks. For RAM allocation recommendations for unstructured data backup, see Limitations and recommendations for unstructured data backup. Disk space: 750 MB for Microsoft Windows-based proxies; 400 MB for Linux-based proxies. Note: If a unstructured data backup stored in an object storage does not have metadata in the cache repository, during the restore or health check operation this metadata will be downloaded to the gateway server. That can consume up to 80% of the gateway server disk space. Network: 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported. |
OS | 64-bit versions of the following Microsoft Windows operating systems are supported, including Core edition:
For the communication with object storage repositories, external repositories and NFS backup repositories, you can use machines running 64-bit versions of the following Linux distributions:
|
For more information, see the Gateway Server section.
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor with 2 cores (vCPUs) minimum, plus 1 core (vCPU) for each 2 additional concurrent tasks. Using faster processors improves data processing performance. Memory: 4 GB RAM, plus not less than 1 GB RAM for each concurrently processed machine disk. The following jobs consume not less than 400 MB RAM per guest VM on mount server:
The following jobs consume 1 GB RAM per guest VM disk on mount server + 100 MB RAM per VM:
Disk Space: 1.4 GB for product installation and 4.5 GB for Microsoft .NET Framework 4.7.2 installation. If Microsoft .NET Framework 4.7.2 is not installed on the machine, Veeam Backup & Replication will install it automatically. Network: 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported. |
OS | 64-bit versions of the following Microsoft Windows operating systems are supported, including Core edition:
Note: If you plan to restore VM guest OS files from VMs running Microsoft Windows ReFS or from VMs with data deduplication enabled for some volumes, you must assign the mount server role to machines running specific OS versions. For more information, see ReFS and Data Deduplication subsections in Restoring VM Guest OS Files (FAT, NTFS or ReFS). |
For more information, see the Mount Server section.
OS | Version/Distribution |
|---|---|
Linux | 64-bit versions of the following Linux distributions are supported. Note that bash shell and SSH are required.
|
For more information, see Restore from Linux, Unix and Other File Systems.
Veeam Backup Enterprise Manager Server
The machine where you plan to install Veeam Backup Enterprise Manager must meet the requirements listed in the System Requirements section of the Enterprise Manager User Guide.
The machine where you plan to install Veeam plug-ins must meet the following requirements:
Important |
The Microsoft .NET Core Runtime and Microsoft ASP.NET Core Shared Framework must be of the same version (up to the minor version number). Otherwise, starting the plug-in will fail. |
Veeam Plug-In | Requirement |
|---|---|
AWS Plug-in for Veeam Backup & Replication version 12.8.0.xxx and later | Microsoft .NET Core Runtime 8.0 or later Microsoft ASP.NET Core Shared Framework 8.0 or later For other system requirements of the plug-in, see the Veeam Backup for AWS User Guide. |
Microsoft Azure Plug-in for Veeam Backup & Replication version 12.7.0.xxx and later | Microsoft .NET Core Runtime 8.0 or later Microsoft ASP.NET Core Shared Framework 8.0 or later For other system requirements of the plug-in, see the Veeam Backup for Microsoft Azure User Guide. |
Google Cloud Plug-in for Veeam Backup & Replication version 12.0.3.xxx and later | Microsoft .NET Core Runtime 6.0 or later Microsoft ASP.NET Core Shared Framework 6.0 or later For other system requirements of the plug-in, see the Veeam Backup for Google Cloud User Guide. |
Nutanix AHV Plug-in for Veeam Backup & Replication version 12.6.0.xxx and later | Microsoft .NET Core Runtime 8.0 or later Microsoft ASP.NET Core Shared Framework 8.0 or later For other system requirements of the plug-in, see the Veeam Backup for Nutanix AHV User Guide. |
oVirt KVM Plug-in for Veeam Backup & Replication version 12.5.0.xxx and later | Microsoft .NET Core Runtime 8.0 or later Microsoft ASP.NET Core Shared Framework 8.0 or later For other system requirements of the plug-in, see the Veeam Backup for OLVM and RHV User Guide. |
Proxmox Virtual Environment Plug-in for Veeam Backup & Replication version 12.1.0.xxx and later | Microsoft .NET Core Runtime 8.0 or later Microsoft ASP.NET Core Shared Framework 8.0 or later For other system requirements of the plug-in, see the Veeam Backup for Proxmox VE User Guide. |
Veeam Kasten Plug-in for Veeam Backup & Replication version 12.1.3.xxx and later | Microsoft .NET Core Runtime 8.0 or later Microsoft ASP.NET Core Shared Framework 8.0 or later For other system requirements of the plug-in, see the Veeam Kasten for Kubernetes User Guide. |
- Veeam Explorer for Microsoft Active Directory
- Veeam Explorer for Microsoft Exchange
- Veeam Explorer for Microsoft SharePoint
- Veeam Explorer for Microsoft SQL Server
- Veeam Explorer for Microsoft Teams
- Veeam Explorer for Microsoft OneDrive for Business
- Veeam Explorer for MongoDB
- Veeam Explorer for Oracle
- Veeam Explorer for PostgreSQL
- Veeam Explorer for SAP HANA