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.
- Backup server
- Veeam Backup & Replication console
- Off-host backup proxy server
- Backup repository server
- WAN accelerator
- Backup target
- Tape
- Tape server
- Gateway server
- Mount server
- Veeam Backup Enterprise Manager
- Supported Applications
- Veeam Explorers
Limitations and Recommendations
Coexistence with Mission-Critical Production Servers
It is not recommended that you 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.
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.
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.
Specification | Requirement |
|---|---|
Hardware | CPU: x86-64 processor (4 cores recommended). Memory: 4 GB RAM plus 500 MB RAM for each concurrent job. Memory consumption varies according to number of VMs in the job, size of VM metadata, size of production infrastructure, etc. Additionally, for users with tape installations (for file to tape jobs processing more than 1,000,000 files):
Disk Space: 15 GB* for product installation and 4.5 GB for Microsoft .NET Framework 4.6 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 offsite backup and replication. High latency and reasonably unstable WAN links are supported. * 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 supported*:
* 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. |
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 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. |
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. * For machines running Microsoft Windows Server 2012 or later. |
Mind 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 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.5.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:
|
Software |
|
For more information, see Backup & Replication Console.
Specification | Requirement |
|---|---|
Hardware | CPU: modern x86 processor with minimum of 2 cores (vCPUs). It is recommended to add 1 core (vCPU) for each additional concurrent task. Using faster processors improves data processing performance. For more information, see Limitation of Concurrent Tasks. Memory: 2 GB RAM plus 200 MB 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:
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. |
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.
Specification | Requirement |
|---|---|
Hardware | CPU: x86 processor (x86-64 recommended). Memory: 4 GB RAM, plus up to 2 GB RAM (32-bit OS) or up to 4 GB RAM (64-bit OS) for each concurrent job depending on backup chain’s length and backup files sizes. For more information, see Limitation of Concurrent Tasks. 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:
|
For more information, see Backup Repository.
|
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. |
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. 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 version of the following operating systems are supported:
|
For more information, see WAN Accelerators.
|
Global cache is not leveraged by Source WAN Accelerators, and so does not need to be allocated and populated on WAN Accelerators used only as source ones. |
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 via hardware or virtual HBA, or software iSCSI initiator.
- Network Attached Storage (NAS) able to represent itself as SMB (CIFS) share (direct operation), or NFS share (must be mounted on a Linux backup repository server).
- Dell EMC Data Domain (DD OS version 5.6 to 7.0) with DDBoost license. Both Ethernet and Fibre Channel (FC) connectivity is supported.
- ExaGrid (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.
- Quantum DXi (firmware version 3.4.0 or later) with NAS support (DXi4700, DXi4700, DXi6900, DXi6900-S).
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 |
|
Specification | Requirement |
|---|---|
Hardware | CPU: x86 processor (x86-64 recommended). Memory: 2 GB RAM plus 200MB for each concurrent task. 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:
|
Specification | Requirement |
|---|---|
Platform | Physical or virtual machine |
OS | Both 32-bit and 64-bit versions of the following operating systems are supported:
|
For more information, see Gateway Server.
On the mount server machine, Veeam Backup & Replication installs the Veeam Mount Service. The Veeam Mount Service requires .NET 4.6 If .NET 4.6 is not installed on the machine, Veeam Backup & Replication will install it automatically. For more information, see Mount Server.
If you plan to restore VM guest OS files from VMs running Microsoft Windows ReFS, you must install Veeam Backup & Replication components on machines running specific OS versions. For more information, see Veeam Backup & Replication Console.
[For Microsoft Windows 2008R2/7, Microsoft Windows 2008] 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.
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.
You can create transactionally consistent backups or replicas of VMs that run the following applications.
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 2003. |
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. |
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. |
Oracle Database configuration | Consider the following:
|
* Veeam Backup & Replication supports set of technologies, features, and services of Microsoft Exchange 2016.
** Veeam Backup & Replication supports set of technologies, features, and services of Microsoft SharePoint 2016.
|
Consider that 32-bit Oracle running on 64-bit operating systems and Oracle XE on Linux are not supported. |