Platform Support
This section includes information about platforms that Veeam Backup & Replication supports.
Note |
The information on this page is valid as of the date of the last page update. |
Veeam Backup & Replication provides support for the following versions of the Microsoft Hyper-V platform.
Specification | Requirement |
---|---|
Platform |
For the supported versions, see this Veeam KB article.
|
Hypervisor |
Server Core installations are fully supported. Microsoft Nano Server with Hyper-V role installed cannot be added to the backup infrastructure as a managed server and no role can be assigned to it. However, you can back up and replicate such servers, but application-aware processing is not supported for them. Note that you must keep your servers up-to-date. |
Management Server (optional) |
|
1 Windows 10/11 is supported only as a target for Instant Recovery and as a host on which a virtual lab for SureBackup jobs can be created.
Specification | Requirement |
---|---|
Hardware |
|
OS | All operating systems supported by Hyper-V. Note: You can back up VMs of Hyper-V clusters in rolling upgrade. However, Veeam Backup & Replication does not use the Resilient Changed Tracking mechanism in such scenario. To perform backup with RCT enabled, make sure your Microsoft Hyper-V environment meets these requirements. It is recommended to complete the rolling upgrade within four weeks. For more information, see Microsoft Docs. |
Software | Hyper-V integration components (optional, required for application-aware processing). |
Consider the following:
- [For Microsoft Windows 2003 and Nano Server] Application-aware processing is not supported due to the absence of VSS framework.
- [For Hyper-V 2016 and later] Application-aware processing for Microsoft Windows VMs with volumes larger than 64 TB is not supported, because Veeam Backup & Replication uses the Microsoft Software Shadow Copy Provider to create a volume shadow copy during the backup or replication. For more information, see this Microsoft KB article.
- [For Hyper-V 2016 and later] Veeam Backup & Replication cannot interact with the guest OS of a shielded VM and get information about its OS, IP address and so on. For this reason, the following operations are not supported for shielded VMs:
- Application-aware image processing
- Restore of VM guest OS files to the original location
- Restore of application items to the original location
- [For Hyper-V 2016 and later] Shielded VMs can run only on trusted hosts guarded with the Host Guardian Service. Consider that when selecting a target host for VM replication or VM restore. If the target host is not guarded with the same Host Guardian Service as the source host, you will not be able to power on the replicated or restored VM.
- The two previous limitations also apply to Generation 1 of Microsoft Hyper-V VMs that use Key Storage Drive. For more information about Key Storage Drive, see Microsoft Docs.
- Guest processing (which includes application-aware processing and indexing) is supported for 64-bit versions of the following Linux operating systems:
- CentOS 7.x
- Debian 10.0 to 12.11, 12.21
- Oracle Linux 7 (UEK3) to 9 (UEK R7)
- Oracle Linux 7 to 9 (RHCK)
- RHEL 7.0 to 9.31
- SLES 12 SP4 or later, 15 SP1 or later
- Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS
1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.
OS | Supported File Systems |
---|---|
Microsoft Windows |
Windows file-level restore to original location is supported for Microsoft Windows 2008/Windows Vista or later except Nano Server. |
Linux |
DRBD (Distributed Replicated Block Devices) are not supported. |
BSD | UFS, UFS2 |
Mac | HFS, HFS+ (volumes up to 2 TB) |
Solaris |
The helper appliance uses module ZFSonLinux version 0.7.0. For this reason, Veeam Backup & Replication supports only those versions of pools and features that are available in ZFSonLinux version 0.7.0. |
For other requirements and limitations of guest OS file restore, see Requirements and Limitations.
You can create transactionally-consistent backups or replicas of VMs that run the following applications.
Application | Requirement |
---|---|
Microsoft Active Directory | of domain controllers for the following operating systems:
Minimum supported domain and forest functional level is Windows 2008. |
Microsoft Exchange | of the following Microsoft Exchange versions:
|
Microsoft SharePoint | of the following versions of Microsoft SharePoint Server (virtualized either on VMware or Hyper-V platform):
All editions are supported (Subscription, Foundation, Standard, Enterprise). Restore of Microsoft SharePoint data may require an available staging Microsoft SQL Server. To learn how to configure this server, see . |
Microsoft SQL Server | of the following Microsoft SQL Server versions:
All editions of Microsoft SQL Server except LocalDB 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. Restore of Microsoft SQL Server data may require an available staging Microsoft SQL Server. To learn how to configure this server, see . |
Oracle on Windows OS | of the following Oracle Database versions on Microsoft Windows machines:
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. |
Oracle on Linux OS | of the following Oracle Database versions on Linux machines:
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. Starting from version 12.1 (build 12.1.0.2131), Veeam Backup & Replication supports the backup of Linux-based VMs with several Oracle homes of different versions. |
Oracle Database configuration | Consider the following:
|
PostgreSQL | of the following PostgreSQL versions on Linux machines:
|
Note |
Consider that 32-bit Oracle running on 64-bit operating systems and Oracle Express Edition (XE) on Linux are not supported. |
Veeam Backup & Replication supports backup of files and folders from the file servers managed by the following operating systems:
- 64-bit versions of the Microsoft Windows operating systems:
- Microsoft Windows Server 2022
- Microsoft Windows Server 2019
- Microsoft Windows Server 2016
- Microsoft Windows Server 2012 R2
- Microsoft Windows Server 2012
- Microsoft Windows 11 (versions 21H2, 22H2)
- Microsoft Windows 10 (from version 1909 to version 22H2)
- Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)
- 64-bit versions of the Linux operating systems:
- CentOS 7.x
- Debian 10.0 to 12.21
- Oracle Linux 7 (UEK3) to 9 (UEK R7)
- Oracle Linux 7 to 9 (RHCK)
- RHEL 7.0 to 9.31
- SLES 12 SP4 or later, 15 SP1 or later
- Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS
1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.
Unstructured Data Backup Support
Veeam Backup & Replication supports backup of data from the following sources:
- Object storage repositories1:
- S3 compatible object storage repositories
- Amazon S3 object storage
- Microsoft Azure Blob storage
- Managed Microsoft Windows or Linux server
- Enterprise NAS systems: NetApp Data ONTAP, Lenovo ThinkSystem DM Series, Dell PowerScale (formerly Isilon), Nutanix Files Storage
- NFS file shares
- SMB file shares
1 The object storage backup feature is available starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131).
Requirements and Limitations for File Shares
Consider the following requirements and limitations for file shares:
- Only 64-bit versions of operating systems are supported for managed Microsoft Windows or Linux server file share.
- Backup of file shares on Linux hosts added with single use credentials is not supported.
- NFS file share must run NFS protocol version 3 or 4.1.
- Network shares and files on them targeted to 3rd party storage devices may have difficulties being restored, or may not be restored at all. Such shares/files often rely upon specific software/OS filters to be recalled from the alternate storage location, which is not available when performing a file share data recovery. See your software vendor documentation to learn how to back up such files.
- Anonymous or AD/Kerberos authentication is not supported for access to file shares through NFS.
In NFS settings of the source file share, you must explicitly specify what servers will have access to the file share.
- SMB file share must run on SMB version 1.x, 2.x or 3.x.
- To support the VSS for SMB File Shares feature, make sure that requirements listed in this Veeam KB article are met.
- To correctly back up SACL (Ownership) files and folders from the SMB file share and restore them:
- When you are specifying access settings for the SMB file share, select the This share requires access credentials check box.
- Make sure that the account you use to Unstructured Data Backup access the file share is either added to the Backup Operators group or has the SeBackupPrivilege and SeRestorePrivilege privileges in Windows Server on the file share.
Requirements and Limitations for Object Storage
Consider the following limitations for object storage added as a source of unstructured data:
- Veeam Backup & Replication does not support backup from and restore to the following types of Azure Blob Storage: Azure Data Box Storage, Azure Stack Edge.
- Veeam Backup & Replication does not support backup from and restore to AWS Snowball Edge Storage.
For more information on unstructured data backup, see the Unstructured Data Backup section.
Consider the following requirements and limitations:
- Names of port groups/segments/networks must be unique.