Community

Prepping VBR/VEMMuch like Veeam ONE, we need to allow data collection in the host management pageFor a VBR HA cluster, repeat this on both individual nodes, starting with the primaryLog into the host management portal onhttps://fqdn:10443And click Backup Infrastructure, then under Data Collection, click Submit RequestAnd the same on VEM  Initial ConfigurationWe can now access the VRO WebUI fromhttps://fqdn:9898And login with the Windows administrator accountFill in the server details on the initial configuration wizard, you can add what you like here, then cl

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 VDPVeeam have information on the feature comparison here, but here is a rough breakdownFoundationFull hypervisor/agent support Instant recovery Backup for Entra Inline ransomware detection Immutability Syslog event forwarding Security Analyzer for VBR SureBackup Cloud VM supportAdvancedEverything in Foundation Veeam Threat Center And Threat Hunter Integrated AV Veeam ONE reporting and monitoring Veeam Enterprise ManagerPremiumEverything in Adv

We have a few clients that have a single physical server and have a service or application that is already using port 443.  So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used and v13 uses it for the Veeam Web Service.  Assuming we can temporarily disable this service/app to get the upgrade to complete, is there a way once v13 is installed to get the Veeam Web Service to use a different port?

Hi everyoneAfter christmas, I had some time to improve my lab a little bit.I decided to setup a Pi-Hole to use it as my main DNS and filtering app, and why not, use it also over my VPN with WireGuard , and be able to use it all the time reaching my Server from anywhere with a FQDN instead of an IP (Dynamic), with DuckDNS.As a base system, I chose Ubuntu Server, with the minimum installation, choose your own, maybe you will need to adapt some commands or content.After login into my clean ubuntu server machine, and update all the packets, I went to the Pi-Hole website, and click into

We first need a VM with the following specs, running Windows Server 2022/20256vCPU 24GB RAM 180GB DiskWe then need to get the VRO ISO, we can find Veeams latest releases hereWe then need to scroll down and find the Veeam Recovery Orchestrator section and click DownloadDouble click the Veeam Data Platform Premium ISODouble click the Setup.exe applicationClick Install

 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 rightClick Data Collection/Overview/Data Source/Add ServerClick Veeam Backup And ReplicationIf 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 FQDNIn my case, I am using the VEM FQDN, which has my VBR HA cluster addedWhen you are happy click Next

Prepping VBR/VEMBefore we can add anything we need to allow data collection in the host management pageFor a VBR HA cluster, repeat this on both individual nodes, starting with the primaryLog into the host management portal onhttps://fqdn:10443And click Backup Infrastructure, then under Data Collection, click Submit RequestAnd the same on VEM Manually Installing The Analytics AgentThere 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

By default, the version of SQL Express thats installed is the RTM version of 2017, so this needs updating to the latest versionAs of December 2025 the latest is CU31 build 14.0.3515.1, which we can get hereFor 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 hereIf we scroll down, we can see it in Method 3 for obtaining the release, and click Download The Package Now

We will also not be domain joining this as it is significantly less secureTo get the installer head here and click Download on Veeam ONE 13, you will need a valid Veeam login for thisOn the Veeam ONE server, double click the ISODouble click the Setup.exe fileClick InstallClick Install Veeam ONE

Adding Our LicenseWe first need our license, and this can be downloaded from your myveeam page hereLog into the VEM server with the veeamadmin account and click Configuration in the top rightUnder Licensing, click Install LicenseAnd double click your license fileClick Yes here  Adding VBRLog in to VEM with the veeamadmin account and click Conf

On the VM console, press Enter on Veeam Backup Enterprise ManagerPress Enter on InstallClick Yes here and the install will automatically startWait for the install to complete and the server to boot and load the initial configuration wizard, here press Tab to select Accept and press EnterEnter a hostname and press Enter on NextFor the network adapter, press Enter on

To get this head here and click Download on the Veeam Software Appliance 13 section, you will need a valid Veeam login for thisWe need the ISO for this, so click the Bootable ISO button and click DownloadFor the hypervisor, this example will be done in VMwareWe need to right click the cluster and click New Virtual MachineClick NextEnter a VM

VBR HA ClusterTo 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 IPOn our first VBR server, log in with the veeamadmin account on the management interface onhttps://fqdn:10443Click Backup Infrastructure then under High Availability, click Submit RequestWe will need to repeat this for the other, secondary, blank VBR serverThis must be approved by the security officer, if you didnt configure one, like me, its auto approved, it should show up like thisWe then need to connect to this VBR server with the remote console we setup earlierEnter the server FQDN and click Connect

Moving The Configuration BackupBy default, the configuration goes to the local default backup repository, now we have an external hardened repository, we need to move it thereWe need to connect to this VBR server with the remote console we setup earlierEnter the server FQDN and click ConnectClick Yes to trust the serverEnter the veeamadmin credentials and click Sign InIn the top left click the three lines and click Configuration BackupUse the drop down to set this to the immutable rep

Adding The Repository To VBRWe now need to log into the VBR with the setup veeamadmin account, then head to Infrastructure/Managed Servers and click Add ServerClick Veeam Infrastructure ApplianceAdd the server FQDN and a description, then click NextClick Yes and accept the TLS keyThen click NextAnd click Finish

Veeam Immutable Repository Configuration ContinuedPress Enter on Mode, the default is Round Robin, there are two choices that fit most environmentsXOR, select this for a port channel/LAG, in static/passive mode 802.3ad, select this for an LACP enable port channel/lagI am using XOR in my instance, just because I always have issues with LACP in active mode, press Enter on your selectionScroll down and press Enter on the IPv4 configuration, the default is automatic, and press Enter on ManualPress Enter on ShowWe will now have all the IPv4 info configuration, for the Addresses part, pres

Veeam Immutable Repository DeploymentTo get this head here and click Download on the Veeam Software Appliance 13 section, you will need a valid Veeam login for thisScroll down to Additional Downloads and click the download Icon by the Veeam Infrastructure ApplianceWe then need to boot our immutable repository, a physical server, into this ISOThe easiest option is to boot this via your system IPMI, Eg Dell iDRAC or HPE iLOAlternatively you can create a bootable USB using Rufus, just ensure you write the ISO in DD Image Mode, else the installer will fail

DellYou 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 failureRAID 6 RAID 60Log into the iDRAC and head to Storage/Overview/Physical disks and click Create Virtual DiskGive a name to the disk and select the layout, I want RAID 6 as this is backup server so resiliency is importantFor 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 dontThen click Next

Veeam Infrastructure Appliance ConfigurationUse tab to scroll and press Enter on Accept, to accept the EULASet a hostname and press Enter on NextPress Enter on StaticEnter an IPv4 address, subnet mask, gateway and comma separated DNS servers, then press Enter on ApplyWe can then test this with a ping testWhen thats working, press Enter on NextOptionally, press Enter

WindowsFor this we will want a standard Windows Server 2022/2025 server off domain, the spec depends on the useWe also need the deployment kit installed on the serverWe now need to log into the VBR with the setup veeamadmin account, then head to Infrastructure/Managed Servers and click Add ServerClick Microsoft WindowsEnter the Proxy FQDN, give it a description and click NextSelect Connect using Certificate-Based Authentication and click NextClick Next

Licensing VBRWe will need to add our license before we can setup HA, dont worry if you are planning to use Enterprise Manager for licensingIf you arent setting up HA and want to use Enterprise Manager, skip this sectionWe first need our license, and this can be downloaded from your myveeam page hereThen log into the web portal on the first VBR server, what will be the primary, you cna access this onhttps://fqdnThen log in with the veeamadmin credentials you should see this prompt, click InstallDouble click your license fileYou may see this, click Yes, these are usually just OS security updates, ser

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 itThis 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 requiredSearch for and open the Windows defender Firewall With Advanced SecurityRight click Inbound Rules and click New RuleSelect Port and click NextSelect TCP and enter the ports135,137-139,445And click Next

Adding A DNS SuffixId recommend adding this to the VBR Management server, but its also required for Veeam ONELog into the management interface on https://fqdn:10443And log in with the veeamadmin accountIf you setup HA later on in this guide, you’ll need to do this on the secondary HA VBR serverClick Network and under Additional DNS Suffixes click ConfigureClick AddEnter the DNS search domain and click AddThen click Apply Installing Th

 Veeam Software Appliance ConfigurationWhen 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 EULAEnter a hostname and press Enter on NextOn the adapters screen you likely have just the one, VBR should be a VM, press Enter on StaticIf 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 hereEnter the IPv4 address, subnet mask, then add DNS, comma separated and press Enter on Ap

Veeam Software Appliance Deployment - ISOFor deployments on physical hardware or other hypervisors we will need the ISOTo get this head here and click Download on the Veeam Software Appliance 13 section, you will need a valid Veeam login for thisThen select the Bootable ISO and click DownloadThe 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