In this series we will be going over setting up the full Veeam Data Platform suite ready for configuration of each of the services it offers, but what do you get with the different subscription levels of VDP
Veeam have information on the feature comparison here, but here is a rough breakdown
Foundation
- Full hypervisor/agent support
- Instant recovery
- Backup for Entra
- Inline ransomware detection
- Immutability
- Syslog event forwarding
- Security Analyzer for VBR
- SureBackup
- Cloud VM support
Advanced
- Everything in Foundation
- Veeam Threat Center And Threat Hunter
- Integrated AV
- Veeam ONE reporting and monitoring
- Veeam Enterprise Manager
Premium
- Everything in Advanced
- Proactive threat assessment
- Orchestrated data recovery with the Recovery Orchestrator
- VBR HA – Linux Appliance Only
Personally I found the sweet spot to be in the Advanced tier, Foundation offers the basics but misses a lot of really good features, and Premium brings some nice features mainly with the orchestrator and VBR HA
The this deployment we will be using the following systems
- VBR – Linux
- VEM – Linux
- Veeam ONE – Windows
- VRO – Windows
- Repository – Linux immutable
- Proxy – Linux/Windows
The per VM specs for all of these are
VBR
For VBR HA clusters, you cannot use it as a local repository, the repository must be a dedicated phsyical server with storage in this type of setup
HA nodes must have the exact same build installed and be on the same L2 subnet
The secondary HA server must always be fresh, you can use an existing primary server, if you are setting HA up after the initial installation
VDP premium is also required for HA
- 8vCPU
- 16GB RAM
- 2x240GB Disk
- 3 IPs – HA Only
VEM
- 8vCPU
- 16GB RAM
- 2x240GB Disk
Veeam ONE
- 4vCPU
- 16GB RAM
- 120GB Disk
VRO
- 6vCPU
- 24GB RAM
- 180GB Disk
Proxy
Generally Linux proxy servers can do most tasks, however as of 13.0.1, there are a couple of limitations
- Linux-based guest interaction proxies do not support group Managed Service Accounts (gMSAs)
If the account specified in the Guest OS credentials field is a gMSA, Veeam Backup & Replication will automatically select a Microsoft Windows machine for the guest interaction proxy role for this VM - Linux-based backup proxies use the transport service for connection with backup infrastructure components, if the transport service cannot be installed, Linux-based backup proxy require SSH connection
- You can assign the role of a VMware backup proxy to a Linux server added with single-use credentials, for example, a Linux server used as a hardened repository
For this configuration, only the Network mode (NBD) is supported, other transport modes will not be available for selection - Linux-based backup proxies cannot be used with VMware Cloud on AWS. This is because VDDK settings required by VMware cannot be enabled on Linux-based backup proxies
- Linux-based backup proxies that use virtual appliance (HotAdd) transport mode do not support the VM copy scenario
- For Direct SAN with iSCSI access, note that Linux-based backup proxies must have the Open-iSCSI initiator enabled
- For Direct NFS access, consider the following
Linux-based backup proxies must have NFS client package installed
Debian-based backup proxies must have the nfs-common package installed
RHEL-based backup proxies must have the nfs-utils package installed - In Hyper-V environments, a Windows Proxy is required for application aware backups
More information can be found here, here and here
Spec wise, the following works very well
If you need more concurrent tasks, each VM disk is a task, add more vCPU and scale the RAM proportionally
- 4vCPU – 8 Concurrent Tasks
- 12GB RAM
- 90GB Disk (Windows)
- 2x120GB Disk (Linux)
Mount Server
Generally Linux mount servers can do everything a Windows Mount server can, however there are some limitations as of 13.0.1
Veeams information on this is here
Generally, its recommended to have a Windows mount server thats local to a repository, this can be a dedicated server, or a Windows Proxy that doubles up as one
The following features require a Microsoft Windows mount server and may fail if the Windows mount server or the default Windows mount server is not configured
- VMware replication job with Re-IP rules
- Application item restore
- Secure restore for workloads with ReFS volumes
- SureBackup
- Guest OS file restore for Microsoft Windows workloads with ReFS volumes, or from workloads with data deduplication enabled for some volumes
Repository
This will depend on what you have for the physical server, this must be its own server, and should not be backed by a SAN, it needs to be direct attached storage, or an immutable object based storage, like an Object First OOTBI, or Wasabi cloud storage
The full article with all parts can be found here:
https://blog.leaha.co.uk/2025/12/23/veeam-data-platform-13-ultimate-deployment-guide/
