Make sure platforms that you plan to use for various operations are supported.
Veeam Backup & Replication provides support for the following versions of the Microsoft Hyper-V platform.
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.
Depending on your Windows Server version, some additional hot fixes not included in the Windows Update must be installed. For more information, see this Veeam KB article.
Management Server (optional)
2 This version is supported starting from Veeam Backup & Replication 11a (build 220.127.116.111).
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.
Hyper-V integration components (optional, required for application-aware processing).
1 This version is supported starting from Veeam Backup & Replication 11a (build 18.104.22.1681).
Mind 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. Bear it in mind 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.
Supported File Systems
Windows file-level restore to original location is supported for Microsoft Windows 2008/Windows Vista or later except Nano Server.
DRBD (Distributed Replicated Block Devices) are not supported.
HFS, HFS+ (volumes up to 2 TB)
The FLR 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.
Consider the following:
- You cannot restore pipes and other file system objects. File-level restore supports recovery of files and folders only.
- [For Microsoft Windows workloads] You can restore files from basic disks and dynamic disks (including simple, mirrored and striped volumes).
- [For Linux workloads] You can restore files from basic disks, Linux LVM (Logical Volume Manager) and ZFS pools. Encrypted LVM volumes are not supported.
- [For backups of BSD, Mac and Solaris VMs] You cannot restore files directly to the original location. Use the Copy to option instead.
Veeam Backup & Replication supports backup of file shares from the following sources:
- Microsoft Windows- or Linux-managed server
- Enterprise NAS systems: NetApp Data ONTAP, Lenovo ThinkSystem DM Series, Dell EMC Isilon
- NFS file shares
- SMB file shares
Consider the following requirements and limitations:
- Only 64-bit versions of operating systems are supported for Microsoft Windows- or Linux-managed 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.
- 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 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.
For more information on NAS backup, see NAS Backup Support.
Domain names of all managed servers added to the Veeam backup infrastructure and machines you want to back up must be resolvable into IPv4 addresses.