This is an archive version of the document. To get the most up-to-date information, see the current version.System Requirements
Make sure that servers that you plan to use as backup infrastructure components meet the system requirements listed below.
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 to install Veeam Backup & Replication and its components on mission-critical machines in the production environment such as Microsoft Hyper-V 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.
Native Hyper-V Replication
Do not use native Hyper-V replication especially if replication is targeted at the same scope (host, cluster, SCVMM) where the source VM resides. This can cause VM ID collision. Instead, we recommend you use Veeam replication. For more information, see Replication.
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.
Mind that you cannot install Veeam Backup & Replication and Veeam Backup Enterprise Manager on a machine running Microsoft Windows Server Core.
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.
Linux Server
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 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:
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 NAS backup components may consume up to 4 GB RAM per task (in case of deduplicating storage appliances, up to 8 GB RAM): backup repository, backup proxy, cache repository. Make sure you allocate enough memory resources for your installation. For all-in-one installations, the server where all the components are installed must have enough memory resources for all components.
Sharing Backup Infrastructure Components Across Veeam Installations
We do not recommend to use shared backup infrastructure components 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: 4 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. Additionally, for users with tape installations (for file to tape jobs processing more than 1,000,000 files):
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). 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 | Only 64-bit version of the following 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 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article.
|
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:
[Optional] To add SCVMM servers to Veeam Backup & Replication infrastructure, the following software is required:
The version of SCVMM Admin UI installed on the backup server must match the SCVMM server version. Make sure that versions of updates also match. 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. |
SQL Database | Local or remote installation of the following versions of Microsoft SQL Server:
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. Veeam Backup & Replication and Veeam Backup Enterprise Manager configuration databases can be deployed in Microsoft SQL AlwaysOn Availability Groups. For more information, see this Veeam KB article. 1 For machines running Microsoft Windows Server 2012 or later. |
For more information, see Backup Server.
Veeam Backup & Replication Console
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor. Memory: 2 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 | Only 64-bit version of the following operating systems are supported:
1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article. |
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 Backup & Replication Console.
Off-Host/On-Host Backup Proxy Server
Specification | Requirement |
|---|---|
Hardware | CPU: modern x86-64 processor with minimum of 2 cores (vCPUs). It is recommended to add 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 2 GB for each concurrent task. Using faster memory (DDR3/DDR4) improves data processing performance. Disk Space: 300 MB. 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 | The following operating systems are supported, including Core edition:
The Hyper-V role must be enabled on a machine performing the role of an off-host backup proxy server. Note: Versions of a Microsoft Hyper-V host and off-host backup proxy must coincide. For example, if you use a Microsoft Windows Server 2012 machine with the Hyper-V role enabled as a Microsoft Hyper-V host, you must deploy the off-host backup proxy on a Microsoft Windows Server 2012 machine with the Hyper-V role enabled. 1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article. |
Software | For off-host backup from CSV (SAN): VSS hardware provider that supports transportable shadow copies. The VSS hardware provider is typically distributed as a part of client components supplied by the storage vendor. Not required for off-host backup from SMB shared storage. |
For more information, see Off-Host Backup Proxy.
If you use the on-host backup mode, note that the source Hyper-V host that performs the role of the backup proxy will require additional computing resources similar to those specified as the off-host backup proxy requirements. For more information, see On-Host Backup.
File Share Backup Proxy Server
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor (minimum 2 cores or vCPUs). Using multi-core processors improves data processing performance and allows for more tasks to be processed concurrently. Memory: 4 GB RAM for each concurrent task. Using faster memory (DDR3/DDR4) improves data processing performance. 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:
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. 1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article. |
For more information on using the file share backup proxy in NAS backup, see Backup Proxy in NAS Backup Support.
Specification | Requirement |
|---|---|
Hardware | CPU: x86 processor (x86-64 recommended). The number of cores depends on the concurrent task settings. For more information, see Limitation of Concurrent Tasks. Memory: Not less than 2 GB RAM for each concurrently processed machine disk or file share. For more information, see Limitation of Concurrent Tasks. For RAM allocation recommendations for NAS backup, see Limitations and Recommendations for NAS backup. 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 | Both 32-bit and 64-bit (recommended) versions of the following operating systems are supported, including Core edition:
In addition, both 32-bit and 64-bit (recommended) versions of the following Linux distributions are supported:
Bash shell and SSH are required. Perl is required only for non-persistent Veeam Data Movers. Check the full list of required Perl modules in this Veeam KB article. 64-bit edition of Linux must be able to run 32-bit programs. Persistent Veeam Data Movers (pure 64-bit Linux editions) are not supported, Perl installation must support 32-bit variables. 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. 1 This version requires Veeam Backup & Replication 11a (build 11.0.1.1261) with Cumulative Patch P20230227. For more information, see this Veeam KB article. |
For more information, see Backup Repository.
Note |
If you plan to use a Microsoft Windows backup repository with Data Deduplication, make sure that you set up the Microsoft Windows server correctly. For more information, see this Veeam KB article. |
The following storage types can be used as a cache repository for NAS 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 repository servers that can be used as a cache repository, see Backup Repository Server.
For more information on the cache repository, see Cache Repository in NAS Backup Support.
Specification | Requirement |
|---|---|
Hardware | CPU: x86 processor (x86-64 recommended). Memory: 2 GB RAM plus 200MB 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 virtual disk size. Additionally (for file to tape jobs processing more than 1,000,000 files):
Disk Space: 300 MB, plus 10 GB for temporary data storage for backup and restore operations. Network: 1 Gbps or faster. |
OS | Both 32-bit and 64-bit (recommended) versions of the following operating systems are supported, including Core edition:
1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article. |
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 (DDR3/DDR4) 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 | Only 64-bit versions of the following operating systems are supported, including Core edition:
1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article. |
For more information, see WAN Accelerators.
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. |
Backups can be performed to the following disk-based storage:
- Local (internal) storage of the backup repository server.
- Direct Attached Storage (DAS) connected to the backup repository server, including external USB/eSATA drives, USB pass through and raw device mapping (RDM) volumes.
- Storage Area Network (SAN). Backup repository server must be connected into the SAN fabric through hardware or virtual HBA, or software iSCSI initiator.
- Network Attached Storage (NAS) able to present its capacity as NFS share (protocol version 3.0 and 4.1 only) or SMB/CIFS share (any protocol version). Using SMB protocol for non-continuously available (CA) file shares is not recommended for reliability reasons. NFS shares are supported both for direct operation and when mounted to a Linux repository server.
- Dell EMC Data Domain (DD OS version 6.2 to 7.131) with DDBoost license. Both Ethernet and Fibre Channel (FC) connectivity is supported.
- ExaGrid2 (firmware version 5.0.0 or later).
- HPE StoreOnce (firmware version 3.15.1 or later) with Catalyst license. Both Ethernet and Fibre Channel (FC) connectivity is supported. HPE Cloud Volumes Backup is supported. Note that HPE StoreOnce Federated Catalyst is not supported.
- Quantum2 and OEM partners2 (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 The version 7.10 requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). The version 7.11-7.13 require Veeam Backup & Replication 11a P20230227 (build 11.0.1.1261 P20230227). For more information, see this Veeam KB article.
2 These storages use the Veeam Transport Service. Make sure that they also meet system requirements for the backup repository server.
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:
- Amazon S3 (including AWS Snowball Edge)
- Google Cloud Storage
- IBM Cloud Object Storage
- Microsoft Azure Blob storage (including Microsoft Azure Data Box)
- Any S3-compatible object storage (on-premises appliance, or cloud storage provider)
Once backups are copied or offloaded to Amazon S3 or Microsoft Azure Blob storage, they can be further d to one of the following respective cold object storage classes using the scale-out backup repository Archive Tier:
- Amazon S3 Glacier
- Amazon S3 Glacier Deep Archive
- Microsoft Azure Archive Tier
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 NAS backup target, see Backup, Archive, Secondary Repositories in NAS Backup Support.Tape
Specification | Requirement |
|---|---|
Hardware | LTO3 or later tape libraries (including VTL) and standalone drives are supported. Tape device must be directly attached to the backup server, to a tape server via SAS, FC or iSCSI interface. |
Software |
|
Veeam Backup & Replication offers integration with the following storage systems:
Dell EMC Isilon/PowerScale (NAS Backup only)
- NFS or CIFS connectivity
- OneFS 8.1.2 to 9.1
Dell EMC VNX, VNX2, VNXe and Unity XT/Unity
- NFS, Fibre Channel (FC) or iSCSI connectivity
- Dell EMC VNX/VNX2 all OE versions are supported
- Dell EMC Unity XT/Unity, VNXe OE versions 3.x up to 5.1
- Fibre Channel (FC) or iSCSI connectivity
- 3PAR OS versions 3.2.2 up to 3.3.1 MU5
- WSAPI 1.5 and later
- iSCSI VLAN tags are supported
- Virtual Domains are supported
HPE Nimble Storage AF-Series, HF-Series and CS-Series
- Fibre Channel (FC) or iSCSI connectivity
- Nimble OS from 2.3 up to 6.1.2
- HPE Nimble synchronous replication is not supported
- Fibre Channel (FC) or iSCSI connectivity
- OS version 6.0
- Synchronous replication is not supported
- Fibre Channel (FC) or iSCSI (starting from OS versions 4.3 or later) connectivity
- OS versions 4.x
- Virtual Domains are supported
- Fibre Channel (FC) or iSCSI connectivity
- OS version 9.3 or later
- Virtual Domains are supported
HPE StoreVirtual/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
IBM FlashSystem (StorWize), IBM SVC, Lenovo Storage V Series
- Fibre Channel (FC) or iSCSI connectivity
- IBM Spectrum Virtualize OS from version 7.6 or later*
* If you use iSCSI connectivity and your IBM Spectrum Virtualize OS version is later than 8.4.1, you need an IBM hotfix to enable support for the storage system. Please, contact IBM support to get the hotfix.
NetApp FAS/AFF/ASA, FlexArray (V-Series), ONTAP Edge/Select/Cloud VSA and FAS OEM (Fujitsu ETERNUS HX/AX, IBM N series and Lenovo DM series)
- NFS, Fibre Channel or iSCSI connectivity
- ONTAP 7-mode versions 8.2 up to 8.2.5
- ONTAP cluster-mode versions 8.3 to 9.13.1 (Version 9.13.1 has some issues. For more details, see this Veeam KB article.)
- MetroCluster is supported
- ONTAP features application-aware data management and SVM-DR are not supported
- NetApp Synchronous SnapMirror is not supported
Universal Storage API Integrated Systems
To start working with the following storage systems, you must install storage system plug-ins.
- Fibre Channel (FC) or iSCSI connectivity
- DataCore SANsymphony 10.0 PSP12 or later
- Fibre Channel (FC) or iSCSI connectivity
- Dell EMC 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 EMC PowerStore T and PowerStore X series (PowerStore OS 2.0 or later)
- Fibre Channel (FC) or iSCSI connectivity
- Storage Center OS 7.4.2 or later
- FluidFS volumes and Live Volumes are not supported
- 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
- 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
- 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)
- NFS, Fibre Channel (FC) or iSCSI connectivity
- InfiniBox 3.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)
- iSCSI connectivity
- NetApp SolidFire support requires Element OS 9.0 or later
- NetApp HCI support requires Element OS 10.0 or later
- Fibre Channel (FC) or iSCSI connectivity
- Purity 4.10 or later
- Purity ActiveCluster is supported. Direct access to a single proxy server from both storage arrays in the cluster is required.
- Replicated volume snapshots on the target array are supported. For details, see this Veeam KB article.
Tintri IntelliFlash/Western Digital IntelliFlash/Tegile
- NFS, Fibre Channel (FC) or iSCSI connectivity
- Tintri IntelliFlash 3.9.2, 3.10.1 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 or file share. For more information, see Limitation of Concurrent Tasks. For RAM allocation recommendations for NAS backup, see Limitations and Recommendations for NAS backup. Disk space: 2 GB per TB of data processed during a SOBR offload job for a machine that acts as a gateway server for an Object Storage Repository. For more information, see this Veeam KB article. 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 | Both 32-bit and 64-bit versions of the following Microsoft Windows operating systems are supported:
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:
1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article. |
For more information, see Gateway Server.
The mount server role must be assigned to a 64-bit Microsoft Windows machine added to the backup infrastructure. For the list of supported OSes, see Veeam Backup & Replication Console.
On the mount server machine, Veeam Backup & Replication installs the Veeam Mount Service. The Veeam Mount Service requires Microsoft .NET Framework 4.7.2. If Microsoft .NET Framework 4.7.2 is not installed on the machine, Veeam Backup & Replication will install it automatically.
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 Microsoft Windows 2008R2/7] Make sure that you have SHA-2 code signing support installed. Normally, this component is included in Microsoft Windows updates. For more information, see Microsoft Docs.
Starting from Veeam Backup & Replication 10, the following jobs consume 512 MB RAM per guest VM disk on mount server + 100 MB RAM per VM:
- SureBackup
- Instant Recovery
- Instant Disk Recovery
For more information on the mount server, see Mount Server.
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:
Veeam Plug-In | Requirement |
|---|---|
AWS Plug-in for Veeam Backup & Replication version 11.0.5.xxx | Microsoft .NET Core Runtime 6.0 or later Microsoft ASP.NET Core Shared Framework 6.0 or later |
AWS Plug-in for Veeam Backup & Replication version 11.0.4.xxx or 11.0.3.xxx | Microsoft .NET Core Runtime 3.1.10 or later Microsoft ASP.NET Core Shared Framework 3.1.10 or later |
Microsoft Azure Plug-in for Veeam Backup & Replication version 11.0.4.xxx | Microsoft .NET Core Runtime 6.0 or later Microsoft ASP.NET Core Shared Framework 6.0 or later |
Microsoft Azure Plug-in for Veeam Backup & Replication version 11.0.3.xxx or 11.0.2.xxx | Microsoft .NET Core Runtime 3.1.10 or later Microsoft ASP.NET Core Shared Framework 3.1.10 or later |
Google Cloud Plug-in for Veeam Backup & Replication version 11.0.3.xxx | Microsoft .NET Core Runtime 6.0 or later Microsoft ASP.NET Core Shared Framework 6.0 or later |
Google Cloud Plug-in for Veeam Backup & Replication version 11.0.2.xxx | Microsoft .NET Core Runtime 3.1.10 or later Microsoft ASP.NET Core Shared Framework 3.1.10 or later |
Nutanix AHV Plug-in for Veeam Backup & Replication version 11.1.3.xxx or 11.0.3.xxx | Microsoft .NET Core Runtime 3.1.10 or later Microsoft ASP.NET Core Shared Framework 3.1.10 or later |
Nutanix AHV Plug-in for Veeam Backup & Replication version 11.0.2.xxx | Microsoft .NET Core Runtime 2.1.23 or later Microsoft ASP.NET Core Shared Framework 2.1.23 or later |
RHV Plug-in for Veeam Backup & Replication version 11.1.2.xxx or 11.0.2.xxx | Microsoft .NET Core Runtime 3.1.32 or later Microsoft ASP.NET Core Shared Framework 3.1.32 or later |
You can create transactionally-consistent backups or replicas of VMs that run the following applications. For more information on transactionally-consistent backups, see Application-Aware Processing.
Application | Requirement |
|---|---|
Microsoft Active Directory | Veeam Backup & Replication supports domain controller backup for the following operating systems:
Minimum supported domain and forest functional level is Windows 2008. 1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article. |
Microsoft Exchange | The following versions of Microsoft Exchange are supported:
|
Microsoft SharePoint | The following versions of Microsoft SharePoint Server (virtualized either on VMware or Hyper-V platform) are supported:
All editions are supported (Foundation, Standard, Enterprise). |
Microsoft SQL Server | The following versions of Microsoft SQL Server are supported (for application-aware processing and transaction log backup):
All editions of Microsoft SQL Server are supported. The database whose logs you want to back up must use the Full or Bulk-logged recovery model. In this case, all changes of the Microsoft SQL Server state will be written to transaction logs, and you will be able to replay transaction logs to restore the Microsoft SQL Server. You can use the Microsoft SQL Server Management Studio to switch to one of these models. For more information, see Microsoft Docs. |
Oracle on Windows OS | Veeam Backup & Replication supports backup of the following Oracle Database versions:
For supported operating systems, see Oracle documentation.
For supported operating systems, see Oracle documentation.
For supported operating systems, see Oracle documentation.
For supported operating systems, see Oracle documentation.
For supported operating systems, see Oracle documentation.
For supported operating systems, see Oracle documentation. 1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article. |
Oracle on Linux OS | Veeam Backup & Replication supports backup of the following Oracle Database versions:
For supported operating systems, see Oracle documentation.
For supported operating systems, see Oracle documentation.
For supported operating systems, see Oracle documentation.
For supported operating systems, see Oracle documentation.
For supported operating systems, see Oracle documentation.
For supported operating systems, see Oracle documentation. 1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article. |
Oracle Database configuration | Consider the following:
|
Note |
Consider that 32-bit Oracle running on 64-bit operating systems and Oracle Express Edition (XE) on Linux are not supported. |
