By LeahaLast updated on March 12th, 2026 at 12:48
In this article we will be going over setting up the full Veeam Data Platform suite ready for configuration of each of the services it offers in the new version 13, but what services are these
- Veeam Backup Replication
- Veeam ONE Monitoring
- Veeam Enterprise Manager
- Veeam Recovery Orchestrator
So 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
- Veeam Enterprise Manager
Advanced
- Everything in Foundation
- Veeam Threat Center And Threat Hunter
- Integrated AV
- Veeam ONE reporting and monitoring
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
Important – By continuing you are agreeing to the disclaimer here
1 – Overview
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
2 – VBR
2.1 – Veeam Software Appliance Deployment
2.1.1 – ISO
For deployments on physical hardware or other hypervisors we will need the ISO
To get this click this direct download link here
The VM will need to be specced with whats listed in the overview, the VM compatibility is Rocky Linux and the ISO will need to be mounted to the server, if this is a physical server ensure you burn it with Rufus in DD mode else it will fail to install
When you boot the server, you will see this screen, press Enter on Veeam Backup & Replication
Then press Enter on Install
Click Yes here
And the system will automatically install everything
2.1.2 – OVA
For deployments in a VMware environment we can install this directly with an OVA template downloaded from Veeam’s website
To get this click the direct download link here
In VMware, right click the cluster and click Deploy OVF Template
Click Local File, then Upload Files
Double click the OVA file
Then click Next
Give the VM a name and optionally select a folder, then click Next
For the compute, select the cluster and check the box to automatically power the VM on, then click Next
Click Ignore, then Next here
Select a datastore and change the virtual disk format to Thin Provision, then click Next
Select the vSphere network and click Next
Check everything is setup as you need and when you are happy, click Finish
2.2 – Veeam Software Appliance Configuration
When the VM or physical server has booted, you’ll need to be able to get to the console
From there, press Tab till you land on Accept and hit Enter to accept the EULA
Enter a hostname and press Enter on Next
On the adapters screen you likely have just the one, VBR should be a VM, press Enter on Static
If you are deploying this on a physical server and want network redundancy look at the configuration of the backup repository in section 2.9.3, its the same here
Enter the IPv4 address, subnet mask, then add DNS, comma separated and press Enter on Apply
Here when selecting the adapter, you should see the assigned IP address below
You can also run a ping test to verify the IP address is reachable
When you are happy thats reachable, press Enter on Next
If you want to change the NTP server press Enter on Edit
Enter the NTP server and press Enter
You can optionally add more with the Add button, or press Enter on Next when you are done
We then need to set password requirements, this needs to be 15 characters, there is also a link to the requirements here
Once you have your password set, press Enter on Next
We then need to setup MFA, press Enter on this pop up screen for the QR code to add to your authenticator app
You can press Enter to dismiss the QR code
Enter the OTP code and press Enter on ok
Then press Enter on Next
Optionally, setup a security officer account, I dont really need this, so I am skipping it and pressing Enter on Next
Check you are happy with the summary and click Finish
When, all the services have restarted, you should see this and we can access the WebUI
We have the WebUI on port 443 and the management on 10443
And we can use the veeamadmin credentials to login
2.3 – Adding A DNS Suffix
Id recommend adding this to the VBR Management server, but its also required for Veeam ONE
Log into the management interface on
https://fqdn:10443
And log in with the veeamadmin account
If you setup HA later on in this guide, you’ll need to do this on the secondary HA VBR server
Click Network and under Additional DNS Suffixes click Configure
Click Add
Enter the DNS search domain and click Add
Then click Apply
2.4 – Installing The Remote Console
As of 13.0.1, not all VBR functionality is available within the WebUI, and the console is required for some configuration, this can be installed on any Windows Server/PC you want to be able to access VBR on
We can find the download link by going to the WebUI for VBR and click the link under the login to download the console
Double click the exe
You may need to run this as an administrator
Accept the EULA by clicking I Accept
A system configuration check will run, wait for this to finish
When thats done, click Install
When thats done, click Finish
2.5 – Windows Firewall
Before we start, VBR needs to be able to connect to any Windows servers via the ADMIN$ share, and the default is for the Windows firewall to block it
This is needed for Windows Proxies, as of 13.0.1 in November 2025, the Linux proxies cannot do application aware processing on Windows servers, so a Windows proxy is required
Search for and open the Windows defender Firewall With Advanced Security
Right click Inbound Rules and click New Rule
Select Port and click Next
Select TCP and enter the ports
135,137-139,445
And click Next
Make sure you have Allow The Connection selected and click Next
Apply this to all and click Next
Name it, including TCP and click Finish
Right click the rule and click Properties
Click Scope, and under Remote IP addresses check These IP Addresses and click Add
Add the IP address of VBR and all proxies, if you have VBR HA, add both VBR server and the VIP, when we set them up later we can come back and edit the GPO, then click ok
And click ok again
Repeat for a new rule but selecting UDP instead of TCP
It should then look like this
2.6 – Licensing VBR
We will need to add our license before we can setup HA, dont worry if you are planning to use Enterprise Manager for licensing
If you arent setting up HA and want to use Enterprise Manager, skip this section
We first need our license, and this can be downloaded from your myveeam page here
Then log into the web portal on the first VBR server, what will be the primary, you cna access this on
https://fqdn
Then log in with the veeamadmin credentials you should see this prompt, click Install
Double click your license file
You may see this, click Yes, these are usually just OS security updates, services will be restarted as needed, but as we have no jobs configured, this is fine
2.7 – Installing The Deployment Kit
As we dont want to join servers to AD, the recommended way to add Windows servers is by the Veeam Deployment Kit, this uses certificate based authentication and is the recommended way of adding Windows Servers in VDP 13
We first need to create a deployment kit, log into the VBR WebUI and click Manager Servers and then Create Veeam Deployment Kit on the right
Save the zip folder and copy it to the Windows server you want to use add to Veeam
On the Windows server, right click the Zip folder, and click Extract All
Then click Extract
Right click on the bat file and click Run As Administrator
Click Run, then wait for the cmd prompt to close
2.8 – Adding Managed Servers
2.8.1 – Windows
For this we will want a standard Windows Server 2022/2025 server off domain, the spec depends on the use
We also need the deployment kit installed on the server
We now need to log into the VBR with the setup veeamadmin account, then head to Infrastructure/Managed Servers and click Add Server
Click Microsoft Windows
Enter the Proxy FQDN, give it a description and click Next
Select Connect using Certificate-Based Authentication and click Next
Click Next
And click Finish
When its done, click ok
2.8.2 – Linux
2.8.2.1 – Veeam Infrastructure Appliance Deployment
We can get the infrastructure appliance from this direct download link here
We then need to boot our VM to this ISO
The guest OS type, if available, needs to be Rocky Linux
When booted it will load this splash screen, select Veeam Infrastructure Appliance and press Enter
Press Enter on Install
Click Yes here, and the installer will automatically begin
When that has installed you will be brought back to the installation screen
2.8.2.2 – Veeam Infrastructure Appliance Configuration
Use tab to scroll and press Enter on Accept, to accept the EULA
Set a hostname and press Enter on Next
Press Enter on Static
Enter an IPv4 address, subnet mask, gateway and comma separated DNS servers, then press Enter on Apply
We can then test this with a ping test
When thats working, press Enter on Next
Optionally, press Enter on Edit to change the NTP server menu
Enter the NTP server and press Enter
You can use Add for additional NTP servers, if required, when you are happy, press Enter on Next
Enter a complex 15 character password, the same requirements as VBR, then press Enter on Next
Press Enter to show the QR code for MFA
You can press Enter to dismiss the QR code
Enter the code and press Enter on ok
Then press Enter on Next
Optionally, setup a security officer account, and press Enter on Next
When you are happy, press Enter on Finish
When its done, you will see a menu like this
2.8.2.3 – Adding The Server To VBR
Log into VBR and click Managed Servers/Add Server
Click Veeam Infrastructure Appliance
Enter the FQDN and a description, then click Next
Click Yes to accept the TLS certificate
Click Next
Click Finish
I got some update sync issues, this looks to be from a GPG signing issue, so not sure why thats occurring, but if in doubt contact Veeam support
2.9 – Linux Immutable Repository
2.9.1 – Configuring RAID
2.9.1.1 – Dell
You will need a RAID array of sorts for this, I recommend the following type due to their better overall resiliency, as this is our backups we need to ensure this is a resilient as is reasonable, from disk failure
- RAID 6
- RAID 60
Log into the iDRAC and head to Storage/Overview/Physical disks and click Create Virtual Disk
Give a name to the disk and select the layout, I want RAID 6 as this is backup server so resiliency is important
For advanced settings, make sure Read Ahead is selected for the read policy for a backup server this gives extra performance, and write policy should be write back only if your controller has a battery backup onboard so you dont loose data in the event of a power outage, the Dell H700 series have one by default, and write through if you dont
Then click Next
Select all the disks you want in this RAID pool and click Next
Click Next here
Then select a time to apply, I am using Apply Now as this is a new server and its not doing anything yet
Once thats applied you will likely need to reboot the server
2.9.1.2 – HPE
You will need a RAID array of sorts for this, I recommend the following type due to their better overall resiliency, as this is our backups we need to ensure this is a resilient as is reasonable, from disk failure
- RAID 6
- RAID 60
This for an older HPE Gen 8 model, but having done this on a G11 the process is largely very similar
To do this you’ll need to reboot the server, during the boot, press F10 when this pops up, at the bottom of the screen, for Intelligent Provisioning
You may get a screen asking you to setup intelligent provisioning, you can just click through it as we wont be needing it
When it loads you’ll want to click Perform Maintenance, on newer models you may not be given this option but just get a list of options
We then want to click into the option for the Array Configuration Utility
You may have multiple devices, as I have a low end integrated B120i, I have installed a separate P420 which I am running my drives through, so I will select that, the Configure
Then click Create Array
Select the disks you want in your pool then click Create Array
Select RAID 6, this allows you to have two disks fail, which is a must for a backup repository
Leave stripe size, sector track and size on the default, then scroll down
Leave parity on Default, and ensure caching is enabled for a massive performance gain, then click Create Logical Array
Click Finish
Id then give it 15 mins before rebooting to initialize
2.9.2 – Veeam Infrastructure Appliance Deployment
We can get the infrastructure appliance from this direct download link here
We then need to boot our immutable repository, a physical server, into this ISO
The easiest option is to boot this via your system IPMI, Eg Dell iDRAC or HPE iLO
Alternatively you can create a bootable USB using Rufus, just ensure you write the ISO in DD Image Mode, else the installer will fail
When booted it will load this splash screen, select Veeam Hardened Repository and press Enter
Press Enter on Install
Click Yes here, and the installer will automatically begin
When that has installed you will be brought back to the installation screen
2.9.3 – Veeam Infrastructure Appliance Configuration
Press Tab to scroll down to I accept and press Enter to accept the EULA
Enter a name and press Enter on Accept
We can then see our network adapters, and there should be two, going into two separate redundancy Switches
Mine shows as connecting/disconnected, this is fine, if they are disconnected they will have the state, Unavailable
Note down the names, in my case its ens33 and ens35, we will need those, then press Enter on Advanced on the right
Press Enter on Add
Press Enter on Bond
Give the profile a name, I entered Bond1, then press Enter on Add
Press Enter on Ethernet
Leave the profile name as the default and for the adapter add the first adapter we noted down earlier, in my case its ens33, then press Enter on ok
Repeat for our other adapter, in my case ens35
It should now look like this
Press Enter on Mode, the default is Round Robin, there are two choices that fit most environments
- XOR, select this for a port channel/LAG, in static/passive mode
- 802.3ad, select this for an LACP enable port channel/lag
I am using XOR in my instance, just because I always have issues with LACP in active mode, press Enter on your selection
Scroll down and press Enter on the IPv4 configuration, the default is automatic, and press Enter on Manual
Press Enter on Show
We will now have all the IPv4 info configuration, for the Addresses part, press Enter on Add
Enter the IP address in CIDR format, add the gateway and press Enter on Add by DNS servers
Enter your DNS server, you can use Add for multiple, then press Enter on Add by Search Domains
Enter your search domain, and when you are happy, scroll to the button and press Enter on ok
We can test the connection with a ping test and it should work
When you are happy with the networking, press Enter on Quit
The screen here wont update, press Enter on Prev
Press Enter on Next
We will then see the bond, and the assigned IP address, then press Enter on Next
Optionally, you can change the NTP server by pressing Enter on Edit
Enter a server IP/FQDN and press Enter
You can use the Add button to add extra servers, when you are happy, press Enter on Next
We then need to set password requirements, this needs to be 15 characters, there is also a link to the requirements here
Once you have your password set, press Enter on Next
We then need to setup MFA, press Enter on this pop up screen for the QR code to add to your authenticator app
You can press Enter to dismiss the QR code
Enter the OTP code and press Enter on ok
Then press Enter on Next
Optionally, setup a security officer account, I dont really need this, so I am skipping it and pressing Enter on Next
Check you are happy with the summary and click Finish
When thats done you will see this screen and its fully configured
2.9.4 – Adding The Repository To VBR
We now need to log into the VBR with the setup veeamadmin account, then head to Infrastructure/Managed Servers and click Add Server
Click Veeam Infrastructure Appliance
Add the server FQDN and a description, then click Next
Click Yes and accept the TLS key
Then click Next
And click Finish
Wait for all the jobs to finish and click ok
Mine did throw a warning about being unable to check for updates, I am not entirely sure what that is as they can get access to the Internet when checking via SSH
Then click Infrastructure/Repositories/Add Repository/Hardened Repository
Add a display name and a description, then click Next
Use the drop down to select the repository we just added
There should only be one volume, for the LVM created on the repository server for your data, select that and click Next
Leave the location as the default, ensure XFS fast clones is checked, set the immutability period, I recommend lining this up with your daily backup retention, just ensure you dont set this too aggressive, if the repository fills up, you must erase everything as nothing can be deleted
Then set the max number of concurrent tasks, setting this to 3-4x your CPU cores is a good idea, you dont want this bottle necking your system, when you are happy, click Next
Then select a mount server, VBR is fine for the Linux Mount Server, for the Windows Mount Server select a managed Windows server, in my case, a Windows Proxy, then click Next
Click Next
Then click Finish
When thats all done, click ok
I got some update sync issues, this seems to have been due to a GPG signing issue, not sure what caused it, but if in doubt raise a ticket with Veeam for assistance
2.10 – Moving The Configuration Update
By default, the configuration goes to the local default backup repository, now we have an external hardened repository, we need to move it there
We need to connect to this VBR server with the remote console we setup earlier
Enter the server FQDN and click Connect
Click Yes to trust the server
Enter the veeamadmin credentials and click Sign In
In the top left click the three lines and click Configuration Backup
Use the drop down to set this to the immutable repository
At the bottom enable configuration backup password and click Add
Set something secure, and ensure you dont forget it, then click ok
Then click ok
2.11 – VBR HA Cluster
To start with, we will need a second VBR server, setup like the first, but dont add any of the other components, like the repository or managed servers, on a different FQDN and IP
On our first VBR server, log in with the veeamadmin account on the management interface on
https://fqdn:10443
Click Backup Infrastructure then under High Availability, click Submit Request
We will need to repeat this for the other, secondary, blank VBR server
This must be approved by the security officer, if you didnt configure one, like me, its auto approved, it should show up like this
We then need to connect to this VBR server with the remote console we setup earlier
Enter the server FQDN and click Connect
Click Yes to trust the server, if you get the popup
Enter the veeamadmin credentials and click Sign In
We first need to remove the local backup repository, on the bottom left, click Backup Infrastructure, then Backup Repositories, select the Default Backup Repository and click Remove Repository
Click Yes
Wait while it is removed
Now Click Managed Servers/Linux, click the VBR server and click Create HA Cluster
Add the cluster DNS name, in FQDN format, and a VIP address, this should be registered in DNS, then click Next
Use the drop down to select the primary node, it should be the only one there, and enter the IP address for the second VBR node, then for credentials, click Add
Then enter the credentials for the veeamadmin user on the second blank VBR server and click ok
Then click Next
Click Continue on the certificate alert
Then click Finish
Then we wait for the configuration database for the HA cluster to be created
When thats done, click Close
To connect to the HA cluster, we can close the console and reconnect to the cluster FQDN instead, same with the UI on port 443
3 – VEM
3.1 – Veeam Software Appliance Deployment
To get this click this direct download link here
For the hypervisor, this example will be done in VMware
We need to right click the cluster and click New Virtual Machine
Click Next
Enter a VM name and optionally select a VM folder, then click Next
For the computer resource, select the cluster and click Next
Select a shared datastore then click Next
Select the VM compatibility and click Next
The guest OS type must be the Linux family and for the OS version, Rocky Linux, then click Next
For the spec, this should have 8vCPU, 16GB RAM and 2x240GB disks, ensure you change the Disk Provisioning to Thin in VMware
Veeam’s documentation on the spec can be found here
Now, for the ISO you’ll need that uploaded to a datastore or content library, expand the CD/DVD drive and use the drop down to select the option matching your environment, in my case its a Datastore ISO File
Browse to the ISO and click ok, then check the Connect At Power On button and click ok
Then click ok
Make sure you are happy with the config and click Finish
Then, select the VM and click Power On
3.2 – Veeam Software Appliance Configuration
On the VM console, press Enter on Veeam Backup Enterprise Manager
Press Enter on Install
Click Yes here and the install will automatically start
Wait for the install to complete and the server to boot and load the initial configuration wizard, here press Tab to select Accept and press Enter
Enter a hostname and press Enter on Next
For the network adapter, press Enter on Static
Enter the IPv4 address, subnet mask, gateway and DNS servers, comma separated and press Enter on Apply
Then press Enter on Next
To change the NTP server, press Enter on Edit
Enter an NTP server and press Enter, I am using Cloudflare, but you likely have one on prem
You can optionally use Add for additional server, when you are done press Enter on Next
We then need to set password requirements, this needs to be 15 characters, there is also a link to the requirements here
Once you have your password set, press Enter on Next
We then need to setup MFA, press Enter on this pop up screen for the QR code to add to your authenticator app
You can press Enter to dismiss the QR code
Enter the OTP code and press Enter on ok
Then press Enter on Next
Optionally, setup a security officer account, I dont really need this, so I am skipping it and pressing Enter on Next
Check you are happy with the summary and click Finish
When, all the services have restarted, you should see this and we can access the WebUI
We have the WebUI on port 443 and the management on 10443
And we can use the veeamadmin credentials to login
We will need to apply the DNS suffix like we did for VBR in section 2.3
3.3 – Installing Our License
We first need our license, and this can be downloaded from your myveeam page here
Log into the VEM server with the veeamadmin account and click Configuration in the top right
Under Licensing, click Install License
And double click your license file
Click Yes here
3.4 – Adding VBR
Log in to VEM with the veeamadmin account and click Configuration in the top right
Then click Backup Servers/Add
Enter the VBR FQDN and enter the veeamadmin username/password, optionally add a description and click ok
Its important for a VBR HA cluster you add the cluster DNS entry
Click Yes to trust the certificate
Now we need to wait ~10 mins for everything to sync
4 – Veeam ONE
4.1 – Windows Install
We will also be domain joining this as it is significantly less secure
To get the installer head here and click Download on Veeam ONE 13, you will need a valid Veeam login for this
On the Veeam ONE server, double click the ISO
Double click the Setup.exe file
Click Install
Click Install Veeam ONE
Click I accept to accept the EULA
We need to add our license, you can sign in with Veeam or Browse to the file
For a file, find it and double click it
Then click Next
Use the default administrator account for the service account, enter that users password and click Next
A system configuration check will then run
You may see an error like this, its often caused by pending windows updates, as my template is outdated, applying all Windows updates and rebooting, then retrying the installer has always fixed this for me
When the precheck is done click Install
When its done, click Finish
Then click Yes, you will need to log back in
4.2 – Upgrading SQL
By default, the version of SQL Express thats installed is the RTM version of 2017, so this needs updating to the latest version
As of December 2025 the latest is CU31 build 14.0.3515.1, which we can get here
For a list of all updates, Microsofts own KB is out of date listing the March 2025 release as the latest, however this site has a much more up to date list of all patches which is here
If we scroll down, we can see it in Method 3 for obtaining the release, and click Download The Package Now
Then click Download
Double click the exe
Accept the EULA and click Next
Click Next
Wait for the check and click Next
Click Update
When its done, click Close
4.3 – Prepping VBR/VEM
Before we can add anything we need to allow data collection in the host management page
For a VBR HA cluster, repeat this on both individual nodes, starting with the primary
Log into the host management portal on
https://fqdn:10443
And click Backup Infrastructure, then under Data Collection, click Submit Request
And the same on VEM
4.4 – Manually Installing The Analytics Agent
There is a known limitation that prevents the automated install by Veeam ONE to Linux server managed by VEM, which we have, Veeams documentation can be found here
But the limitation is
[For Linux servers] Veeam Analytics service cannot be automatically installed on Veeam Backup & Replication servers managed by Enterprise Manager
You must install Veeam Analytics service on such servers in Veeam ONE Web Client or manually
So, we will be installing this manually on both VBR HA nodes and VEM first
Open the Veeam ONE WebUI on
https://fqdn:1239
Login with the local Administrator account
The format for the username should be servername\username
Eg
Click ok here
Optionally skip the Welcome walk through, if you are new you should have a look though this
The default screen will be blank, click the Settings Cog in the top right
Click Data Collection/Overview/Veeam Analytics Service/Download Package/Linux
Save the .bndl file
We will need to repeat this all the nodes, both VBR and the VEM server
Log into the admin portal on
https://fqdn:10443
My server is throwing an error connecting to updates but it seems intermittent so I am not 100% what is causing this, if yours is contact Veeam support
Click Updates and at the bottom click Upload A HotFix
Click Browse
Double click the bundle file
Then click Upload
Then click Install Now
For VBR, click Next here, this warning is to say this needs doing on both nodes in the HA cluster
When its done it will look like this, click Finish
4.5 – Adding VEM/VBR
In Veeam ONE, if you have been logged out, you can get back to where we downloaded the package by clicking the Settings Cog in the top right
Click Data Collection/Overview/Data Source/Add Server
Click Veeam Backup And Replication
If you have VEM, enter the FQDN and select the server type as Enterprise Manager, if you dont have this, enter the VBR FQDN, for standalone VBR, if you have a HA cluster, use the cluster FQDN
In my case, I am using the VEM FQDN, which has my VBR HA cluster added
When you are happy click Next
Click Add Credentials
Click ok here
Select Standard Account and click Next
Enter the veeamadmin credentials and a description, then click Finish
Click Next
For the certificate, click Trust And Continue
there may be a few of these
When thats done, click Finish
Give VeeamONE plenty of time, as we manually installed the agents, we may see duplicated entries in the Data Collection menu, it will sort them out
When its done it should look like this, the secondary node will be unhealthy as only the active node will be sending metrics
If you fail over it will look like this, I had a ghost entry for the secondary server that wouldnt disappear, but it isnt an issue, the primary is unhealthy as its now not sending metrics, which is expected
5 – VRO
5.1 – Windows Install
We first need a VM with the following specs, running Windows Server 2022/2025
- 6vCPU
- 24GB RAM
- 180GB Disk
We then need to get the VRO ISO, we can find Veeams latest releases here
We then need to scroll down and find the Veeam Recovery Orchestrator section and click Download
Double click the Veeam Data Platform Premium ISO
Double click the Setup.exe application
Click Install
Then click Veeam Data Platform 13 – Premium Edition
Accept the EULA by clicking I Accept
Click Next
We can either sign in with Veeam or manually upload our license file, for the latter, click Browse To Local File
Double click the license
Then click Next
Enter the details for the service account, the default administrator is fine for this, then click Next
Wait for the system configuration to pass
Then click Install
When its done click Finish
Then click Yes to reboot
5.2 – Upgrading SQL
By default, the version of SQL Express thats installed is the RTM version of 2017, so this needs updating to the latest version
As of December 2025 the latest is CU31 build 14.0.3515.1, which we can get here
For a list of all updates, Microsofts own KB is out of date listing the March 2025 release as the latest, however this site has a much more up to date list of all patches which is here
If we scroll down, we can see it in Method 3 for obtaining the release, and click Download The Package Now
Then click Download
Double click the exe
Accept the EULA and click Next
Click Next
Wait for the check and click Next
Click Update
When its done, click Close
5.3 – Prepping VBR/VEM
Much like Veeam ONE, we need to allow data collection in the host management page
For a VBR HA cluster, repeat this on both individual nodes, starting with the primary
Log into the host management portal on
https://fqdn:10443
And click Backup Infrastructure, then under Data Collection, click Submit Request
And the same on VEM
5.4 – Initial Configuration
We can now access the VRO WebUI from
https://fqdn:9898
And login with the Windows administrator account
Fill in the server details on the initial configuration wizard, you can add what you like here, then click Next
We then need to add administrators for VRO, click Add
We can add users or groups from the local server, I am going to add the local administrators group, and click Add
Then click Apply
We then need to add our VBR instance, on the Connect Veeam Backup And Replication Servers, click Deploy
Click Deploy Agent/Linux
If you have VEM, select that, if not use VBR, if you have HA without VEM, ensure you add the cluster FQDN in
Then by Credentials, click Add
Enter the username/password for the account you are trying to add, in my case, its the VEM server, and click Add
Select the credential below and click Apply
Click Apply again
For any certificate pop ups, click Remember And Continue
Then click Apply
Click Next here
And click Finish
You may see VBR with the install failed error when adding VEM
To fix this, click the VBR instance and click Repair Agent
You may need to specify additional credentials if they are different to VEM
And accept the certificate, this is what caused the failed install error
When its done it should look like this, and for HA clusters, you’ll see both nodes
