System Requirements

In this article

    Make sure that servers that you plan to use as backup infrastructure components meet the system requirements listed below.

    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 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.
    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.

    NAS Backup

    We recommend to allocate 4 GB RAM for each of the following NAS backup components: backup repository, backup proxy, cache repository. For all-in-one installations, make sure you allocate enough memory resources for all components at the same server.

    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.

    Backup Server

    Specification

    Requirement

    Hardware

    CPU: x86-64 processor (minimum 4 cores recommended).

    Memory: 4 GB RAM plus 500 MB RAM for each enabled 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):

    • 1.5 GB RAM for file to tape backup for each 1,000,000 files
    • 2.6 GB RAM for file restore for each 1,000,000 files
    • 1.3 GB RAM for catalog jobs for each 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). Additional free disk space for Instant VM Recovery cache folder (non-persistent data, at least 100 GB recommended).

    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.

    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:

    • Microsoft Windows Server 2019
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2008 R2 SP1
    • Microsoft Windows 10 (from version 1803 to version 20H2)
    • Microsoft Windows 8.1
    • Microsoft Windows 7 SP1

    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.

    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:

    • Microsoft .NET Framework 4.7.2
    • Microsoft Windows Installer 4.5
    • Microsoft PowerShell 5.1
    • Microsoft SQL Server Management Objects
    • Microsoft SQL Server System CLR Types
    • Microsoft Report Viewer Redistributable 2015
    • Microsoft Universal C Runtime

    The following software must be installed manually:

    • Firefox, Google Chrome, Microsoft Edge, or Microsoft Internet Explorer 11.0 or later.

    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:

    • Microsoft SQL Server 2019
    • Microsoft SQL Server 2017
    • Microsoft SQL Server 2016 (Microsoft SQL Server 2016 SP2 Express Edition is included in the setup)1
    • Microsoft SQL Server 2014
    • Microsoft SQL Server 2012 (Microsoft SQL Server 2012 SP4 Express Edition is included in the setup)2
    • Microsoft SQL Server 2008 R2
    • Microsoft SQL Server 2008

    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.
    2 For machines running Microsoft Windows 7 or Microsoft Windows Server 2008 R2.

    Mind the following:

    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:

    • Microsoft Windows Server 2019
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2008 R2 SP1
    • Microsoft Windows 10 (from version 1803 to version 20H2)
    • Microsoft Windows 8.1
    • Microsoft Windows 7 SP1

    Software

    • Microsoft .NET Framework 4.7.2 (included in the setup)
    • Windows Installer 4.5 (included in the setup)
    • Microsoft PowerShell 5.1 (included in the setup)
    • Firefox, Google Chrome, Microsoft Edge or Microsoft Internet Explorer 11.0 or later

    For more information, see Backup & Replication Console.

    Backup Proxy Server

    Specification

    Requirement

    Hardware

    CPU: x86-64 processor with minimum of 2 cores (vCPUs), plus 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 plus 50 MB for each concurrent task.

    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:

    • Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
    • Microsoft Windows Server 2019
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2008 R2 SP1
    • Microsoft Windows 10 (from version 1803 to version 20H2)
    • Microsoft Windows 8.1
    • Microsoft Windows 7 SP1

    64-bit versions of the following Linux distributions are supported. Note that bash shell, SSH, and Perl are required. Check the full list of required Perl modules in this Veeam KB article.

    • CentOS 7–8.3, CentOS Stream
    • Debian 9.0–10.8
    • Fedora 30–33
    • openSUSE Leap 15.2, Tumbleweed
    • Oracle Linux 6 (UEK3) to 8.3 (UEK R6)
    • Oracle Linux 6 to 8.3 (RHCK)
    • RHEL 6.0–8.3
    • SLES 11 SP4, 12 SP1–SP5, 15 SP0–SP2
    • Ubuntu: 14.04 LTS, 16.04 LTS, 18.04 LTS, 19.10, 20.04 LTS

    1 Linux distributions are not supported as a backup proxy in NAS backup.
     To check compatibility for storage integration, see the system requirements provided by the storage system vendor.

    For more information on the backup proxy, its requirements and limitations, see Backup Proxy.

    Important

    To protect VMs running on ESXi 5.5 and newer with Microsoft Windows, you must deploy backup proxies on machines running a 64-bit version of Microsoft Windows. VDDK 5.5 and newer does not support 32-bit versions of Microsoft Windows.

    The following table shows the minimum system requirements for a backup proxy used in NAS backup.

    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:

    • Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
    • Microsoft Windows Server 2019
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2008 R2 SP1
    • Microsoft Windows 10 (from version 1803 to version 20H2)
    • Microsoft Windows 8.1
    • Microsoft Windows 7 SP1

    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 more information on using the backup proxy for NAS backup, see Backup Proxy in NAS Backup Support.

    VMware CDP Proxy Server

    The following table shows the minimum system requirements for a VMware CDP proxy.

    Specification

    Requirement

    Hardware

    CPU : x86-64 processor with minimum of 8 cores (vCPUs). Using multi-core processors improves data processing performance and allows for more tasks to be processed concurrently.

    Memory: 16 GB RAM. 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: 1 Gbps or faster.

    OS

    64-bit versions of the following Microsoft Windows operating systems are supported:

    • Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
    • Microsoft Windows Server 2019
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2008 R2 SP1
    • Microsoft Windows 10 (from version 1803 to version 20H2)
    • Microsoft Windows 8.1
    • Microsoft Windows 7 SP1

    For more information on the VMware CDP proxy, see VMware CDP Proxy.

    Backup Repository Server

    These requirements also apply to mount servers (if separate from the repository server), gateway servers for file share and deduplicating appliance-based repositories, and cache repository servers (64-bit OS only).

    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 concurrently processed machine or file share. 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:

    • Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
    • Microsoft Windows Server 2019
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2008 R2 SP1
    • Microsoft Windows 10 (from version 1803 to version 20H2)
    • Microsoft Windows 8.1
    • Microsoft Windows 7 SP1

    In addition, both 32-bit and 64-bit (recommended) versions of the following Linux distributions are supported:

    • CentOS 7 to 8.3
    • CentOS Stream
    • Debian 9.0 to 10.8
    • Fedora 30 to 33
    • RHEL 6.0 to 8.3
    • openSUSE Leap 15.2, Tumbleweed
    • Oracle Linux 6 (UEK3) to 8.3 (UEK R6)
    • Oracle Linux 6 to 8.3 (RHCK)
    • SLES 11 SP4, 12 SP1-SP5, 15 SP0-SP2
    • Ubuntu 14.04 LTS, 16.04 LTS, 18.04 LTS, 19.10, 20.04 LTS

    Bash shell, SSH and Perl are required. 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. Pure 64-bit Linux editions are not supported (Perl installation must support 32-bit variables).

    For advanced XFS integration, only the following 64-bit Linux distributions are supported:

    • CentOS 8.2 and 8.3
    • Debian 10.x
    • RHEL 8.2 or later
    • SLES 15 SP2
    • Ubuntu 18.04 LTS and 20.04 LTS

    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 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.

    Cache Repository

    The following storage types can be used as a cache repository for NAS backup:

    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.

    Tape Server

    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):

    • 800 MB RAM for file to tape backup for each 1,000,000 files
    • 800 MB RAM catalog jobs for each 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:

    • Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
    • Microsoft Windows Server 2019
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2008 R2 SP1
    • Microsoft Windows 10 (from version 1803 to version 20H2)
    • Microsoft Windows 8.1
    • Microsoft Windows 7 SP1

    WAN Accelerator

    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:

    • Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
    • Microsoft Windows Server 2019
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2008 R2 SP1
    • Microsoft Windows 10 (from version 1803 to version 20H2)
    • Microsoft Windows 8.1
    • Microsoft Windows 7 SP1

    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.

    Backup Target

    Backups can be performed to the following disk-based storage:

    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:

    Once backups are copied or offloaded to Amazon S3 or Microsoft Azure Blob Storage, they can be further archived to one of the following respective cold object storage classes using the scale-out backup repository 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.

    Veeam CDP Source and Target

    The following source and target datastores are supported for Veeam CDP:

    Support for hyper-converged infrastructure (HCI) appliances other than VSAN is pending validation by Veeam. System requirements will be updated based on the testing results.

    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. Note that VMware does not support connecting tape libraries to ESXi for VM pass-through.

    Software

    • Tape devices without device-specific, vendor-supplied OEM drivers for Windows installed will appear in Windows Device Manager as Unknown or Generic and require enabling native SCSI commands mode.
    • If multiple driver installation modes are available for your tape device, use the one that allows for multiple open handles from a host to a drive to exist at the same time. Usually, such drivers are referred to as “non-exclusive”.
    • No other backup server must be interacting with the tape device.

    Storage Integration

    Backup from Storage Snapshots and Veeam Explorer for Storage Snapshots are supported for the following storage devices:

    Cisco HyperFlex (HX-Series/SpringPath)

    DataCore SANsymphony

    Dell EMC Isilon (NAS Backup only)

    Dell EMC PowerMax

    Dell EMC SC Series (formerly Compellent)

    Dell EMC VNX, VNX2, VNXe and Unity XT/Unity

    Fujitsu ETERNUS AF/DX series

    Hitachi VSP

    HPE 3PAR StoreServ

    HPE Primera

    HPE Alletra 9000

    HPE Nimble Storage AF-Series, HF-Series and CS-Series

    HPE Alletra 6000

    HPE StoreVirtual (formerly LeftHand / P4000 series) and StoreVirtual VSA

    HPE XP

    Huawei OceanStor

    IBM FlashSystem (StorWize), IBM SVC, Lenovo Storage V Series

    INFINIDAT Infinibox F-series

    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.

    NetApp FAS/AFF, 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 up to 9.8
    • MetroCluster is supported
    • ONTAP features application-aware data management and SVM-DR are not supported
    • NetApp Synchronous SnapMirror is not supported

    NetApp SolidFire/HCI

    • iSCSI connectivity
    • NetApp SolidFire support requires Element OS 9.0 or later
    • NetApp HCI support requires Element OS 10.0 or later

    Pure Storage FlashArray

    • NFS, 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 (formerly Western Digital IntelliFlash, Tegile)

    • NFS, Fibre Channel (FC) or iSCSI connectivity
    • Tintri IntelliFlash 3.9.2, 3.10.1 or later

    Gateway Server

    Specification

    Requirement

    Platform

    Physical or virtual machine

    OS

    Both 32-bit and 64-bit versions of the following Microsoft Windows operating systems are supported:

    • Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
    • Microsoft Windows Server 2019
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2008 R2 SP1
    • Microsoft Windows 10 (from version 1803 to version 20H2)
    • Microsoft Windows 8.1
    • Microsoft Windows 7 SP1

    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:

    • CentOS 7–8.3, CentOS Stream
    • Debian 9.0–10.8
    • Fedora 30–33
    • openSUSE Leap 15.2, Tumbleweed
    • Oracle Linux 6 (UEK3) to 8.3 (UEK R6)
    • Oracle Linux 6 to 8.3 (RHCK)
    • RHEL 6.0–8.3
    • SLES 11 SP4, 12 SP1–SP5, 15 SP0–SP2
    • Ubuntu: 14.04 LTS, 16.04 LTS, 18.04 LTS, 19.10, 20.04 LTS

    For more information, see Gateway Server.

    Mount 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 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 per guest VM disk on mount server + 100 MB per VM:

    • SureBackup
    • Instant VM 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.

    Veeam Cloud Plug-Ins

    The machine where you plan to install cloud plug-ins must meet the following requirements:

    Cloud Plug-In

    Requirement

    AWS Plug-in for Veeam Backup & Replication

    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

    Microsoft .NET Core Runtime 3.1.10 or later

    Microsoft ASP.NET Core Shared Framework 3.1.10 or later

    Veeam Backup for Nutanix AHV

    The machine where you plan to install Veeam Backup for Nutanix AHV must have Microsoft .NET Core Runtime 2.1.23 or later installed.

    Supported Applications

    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:

    • Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
    • Microsoft Windows Server 2019
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2008 R2
    • Microsoft Windows Server 2008

    Minimum supported domain and forest functional level is Windows 2008.

    Microsoft Exchange

    The following versions of Microsoft Exchange are supported:

    • Microsoft Exchange 2019
    • Microsoft Exchange 2016
    • Microsoft Exchange 2013 SP1
    • Microsoft Exchange 2013
    • Microsoft Exchange 2010 SP1, SP2, or SP3

    Microsoft SharePoint

    The following versions of Microsoft SharePoint Server (virtualized either on VMware or Hyper-V platform) are supported:

    • Microsoft SharePoint 2019
    • Microsoft SharePoint 2016
    • Microsoft SharePoint 2013
    • Microsoft SharePoint 2010

    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):

    • Microsoft SQL Server 2019 (only for Windows)
    • Microsoft SQL Server 2017 (only for Windows)
    • Microsoft SQL Server 2016 SP2
    • Microsoft SQL Server 2014 SP3
    • Microsoft SQL Server 2012 SP4
    • Microsoft SQL Server 2008 R2 SP3
    • Microsoft SQL Server 2008 SP4
    • Microsoft SQL Server 2005 SP4

    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:

    • Oracle Database 11g Release 2

    For supported operating systems, see Oracle documentation.

    • Oracle Database 12c Release 1

    For supported operating systems, see Oracle documentation.

    • Oracle Database 12c Release 2

    For supported operating systems, see Oracle documentation.

    • Oracle Database 18c

    For supported operating systems, see Oracle documentation.

    • Oracle Database 19c

    For supported operating systems, see Oracle documentation.

    Oracle on Linux OS

    Veeam Backup & Replication supports backup of the following Oracle Database versions:

    • Oracle Database 11g Release 2

    For supported operating systems, see Oracle documentation.

    • Oracle Database 12c Release 1

    For supported operating systems, see Oracle documentation.

    • Oracle Database 12c Release 2

    For supported operating systems, see Oracle documentation.

    • Oracle Database 18c

    For supported operating systems, see Oracle documentation.

    • Oracle Database 19c

    For supported operating systems, see Oracle documentation.

    Oracle Database configuration

    Consider the following:

    • Automatic Storage Management (ASM) is supported for Oracle 11g and later; requires ASMlib present.
    • Oracle Real Application Clusters (RAC) are not supported within the image-level backup functionality. Use Veeam Plug-in for Oracle RMAN. For details, see the Veeam Plug-in for Oracle RMAN section of the Veeam Plug-ins for Enterprise Applications User Guide.
    • Oracle Database Express Edition is supported for Windows-based machines only.
    • Configurations with different versions of Oracle Database deployed on the same server are not supported. Use Veeam Plug-in for Oracle RMAN. For details, see the Veeam Plug-in for Oracle RMAN section of the Veeam Plug-ins for Enterprise Applications User Guide.
    • To create Oracle database backups, all Oracle servers that use Data Guard must be added to the backup job.
    • The database must be in the ARCHIVELOG mode.
    • You can use Veeam Plug-in for Oracle RMAN to integrate RMAN with Veeam Backup & Replication repositories. For details, see the Veeam Plug-in for Oracle RMAN section of the Veeam Plug-ins for Enterprise Applications User Guide.

    Note

    Consider that 32-bit Oracle running on 64-bit operating systems and Oracle XE on Linux are not supported.

    Veeam Explorers