Community

 Since a lot of blogposts have been written on this topic and various issues resolved, I will share the link to my blogpost “Upgrade Path and In-Place Upgrade for VBR v13 and Known Fixes”. The article walks through upgrading Veeam Backup & Replication (VBR) to version 13 (13.0.1) with a focus on real‑world experience, known issues, and practical fixes during the process. It’s based on both official guidance and community feedback.Key Sections & Takeaways 1. Pre‑Upgrade Checks Port Requirement: VBR v13’s REST/Web UI requires port 443; if it’s in use by another app, the VBR services will fail to

Hi All, Job type on Prod is forever forward incremental on Disk -  ReFS formatDR has a repo in XFS formatI’m setting up a new Veeam environment and using Cloud Connect to copy backups from Prod site to DR (single tenant / one client).On the Cloud Connect side, the XFS repository is assigned 100TB and the actual storage usage is only around 56TB.However, the Backup Copy Jobs keep reporting that the cloud repository quota is filling up / quota exceeded, even though there should be plenty of space available.As a workaround, I increased the tenant quota on cloud connect server from 100TB to 150TB, and after that the copy jobs started working normally again and has used like 130TB. But this doesn’t make sense because: The physical repo capacity is still 100TB Actual used space is sti

After Part 1 Pi-Hole and Part 2 DuckDNS, Now, Let´s install WireGuard - Part 3!to be full set,We are going to use this command, its awesome and prepared for raspberry pi, but also work with many distros and platforms, making the deployment super easy and smooth!Follow the screenshots!sudo curl -L https://install.pivpn.io | bash

What happened to the Status column when viewing a backup job’s statistics?  After upgrading to version 13, I no longer see this column.  If a backup object fails, the job shows failed however you have to view each backup object in the job to see which one failed.  Prior to v.13, the status column would show which object failed. Was this intended in v.13 or am I missing it somewhere?  

I get this errors on one of my clients VBR. Fails when running the copy job to our Qnap NAS running Quts Hero, Immutable setup with Quobjects. When it fails we don’t have several copy jobs running at the same time.Any ideas of what i can try next to solve this?  

Hello!Following up on my previous post about V13 for Windows, I wanted to dive into something I mentioned there: the storage integration angle. Specifically, how Pure Storage's Fusion integration with Veeam changes the game for customers managing multiple FlashArrays.If you're running Pure Storage, this is relevant now. If you're evaluating storage platforms, this is worth understanding as a differentiator.The Problem: Single-Array Management at ScaleIf you're already using the Pure Storage FlashArray plug-in for Veeam, you know the value: snapshot-based backup orchestration, instant recovery from metadata-driven snapshots, offloading backup burden from ESXi hosts. It works.But the plug-in has always operated at the individual array level. You configure each FlashArray in V

Moving nearly 360TB of backups is always interesting, but it becomes much more challenging when object lock and immutability are enabled and the repositories live in different cities. I wanted to share how I executed a large migration using only Veeam capabilities, while keeping performance high and the customer’s WAN usage low. Project background Our customer needed to migrate over 360TB of backups off an object storage platform that was being decommissioned. Both the source and target object repositories were located in separate datacenters in different cities, each reachable over the internet. It is worth noting that with object storage object re-use, the object storage usage was around 360TB, but the actual amount of restorable backup data was over 590TB. Key constraints:The customer did not want to use their limited internet bandwidth for such a large data move. Both source and target object repos

Hello Community!The Veeam Software Appliance grabbed all the headlines when V13 dropped, and rightfully so. But here's the thing: the Windows installable version received substantial upgrades that address real operational challenges. If you're running Veeam on Windows and thinking about when/how to adopt VSA, here's why your next move should be upgrading to V13 for Windows first.Why V13 Is DifferentEvery major version brings new features. Table stakes. V13 is different because it fundamentally modernizes the platform architecture in ways that affect your security posture, operational efficiency, and future flexibility.The case for adoption comes down to four things:Security debt reduction – RPC, WMI, and NTLM are attack vectors that have been exploited repeatedly. V13 eliminates them. Performance gains without hardware spend

 Recently, Veeam announced the release of Veeam Data Cloud, previously known as Cirrus by Veeam. Veeam Data Cloud will provide resilient data protection and recovery for multi-cloud data, all delivered through cloud-native backup and storage services.Veeam Data Cloud is available for Microsoft 365 and Microsoft Azure, and Veeam Data Cloud Vault is offered.Specifically, the Veeam Data Cloud for Microsoft 365 is a game-changing BaaS (Backup as a Service) offer. It arrives to meet a latent demand and brings it with many differentiators for customers, such as:Access the Veeam Data Cloud services in a Web browser. The cost of storing backups is included in the subscription, and storage is unlimited! *** WOW ***

Good day, everyone,I am seeking assistance in identifying the best method for migrating to new hardware.Current Environment:DC-A to DC-B bi-directional Veeam replication Old HP servers running Veeam Old HP StoreOnce appliances used as Catalyst repositoriesNew Hardware:New HP servers and HPE StoreOnce appliances procuredRequirements:Build two sets of new Veeam/HPE StoreOnce environments at DC-A Migrate old DC-A Veeam/HPE StoreOnce to new DC-A Veeam/HPE StoreOnce Migrate old DC-B Veeam/HPE StoreOnce to new DC-B Veeam/HPE StoreOnce Establish bi-directional Veeam replication between the new environments Decommission old Veeam/HPE StoreOnce hardware once backup and restore jobs are validatedBased on my previous experience with Veeam/Data Domain migrations, I have outlined the following proposed mi

 As organizations accelerate their adoption of cloud, SaaS, and AI-driven workloads, data protection alone is no longer enough. Today’s enterprises must not only back up and recover data — they must understand it, secure it, govern it, and ensure it can be trusted, especially when that data is used to power AI initiatives.This is where the integration of Securiti AI with Veeam represents a major step forward. Together, they bring data resilience, security, governance, and AI trust into a single, unified platform. The Challenge: Data Everywhere, Risk EverywhereModern data environments are complex by design. Data now exists across:On-premises infrastructure

After the First part,  Let`s continue with the second part,Let`s create our DuckDNS Sub domain before continuing:Go to the DuckDNS website, and create an account, is free.In my personal use case, I sing in with google, so the creation was super easy and smooth.In the page, write down the name you want to use in your subdomain, and click in add domainIn my case, I have two domains created, im showing you them right now:

Hi teamI was wondering if anyone has noticed some strange behavior when configuring network during ISO installer workflow?I have done two installs now. When I go into the network portion and I select the connection toggle, it stays in the connecting state and eventually disconnects.For one repo, one nic actually connected.From a switch perspective, all is up and connectedI made the changes as per documentationInstalling from Veeam Hardened Repository ISO - Veeam Backup & Replication User Guide for VMware vSphereFor the repo that manages to connect to one nic, I configured LACP as per document but only with one nic. This got the repo on the network and I manually added added the second nic the bond from the CLI.The second repo, in the netwo

Hello! I am attempting to set up SureBackup to test backups of VMs from my Hyper-V environment in a way that mimics production and simulates interactions of VMs in separate, routed subnets, but I am running into issues setting up the isolated network’s NICs on the proxy appliance. It is unclear if I’m misunderstanding the setup documentation or if I am running into a limitation caused by the logical network of my Hyper-V cluster.My Hyper-V hosts have a single logical switch for VM traffic with all VLANs trunked to it from the physical switch that the hosts are connected to. Each VLAN has a unique subnet of varying size, mostly /24 but there are some /23 and /27 networks.I am trying to create a Virtual Lab in advanced single-host mode with an isolated network for each subnet containing a VM being tested, with the proxy appliance acting as the router for each subnet.The two subnets I am testing with are:192.168.124.0/23 (VLAN 124) 192.168.196.

Hi All,My customer would like to continue to use an external USB hard drive as a backup repository on the new DELL physical VSA server they have stood up. It’s look as though it’s not supported in this release, but they would like confirmation that it’s on the roadmap for future releases.Any ideas? Thanks!

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

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