Blogs and Podcasts

I currently need to migrate my system from VMWare to OLVM, but I can't find an option for instant recovery of a virtual machine from VMWare to OLVM. I also can't find anywhere I can use this feature to recover a virtual machine from one OLVM to another.

TL;DR With Veeam Backup & Replication v13, every PowerShell cmdlet now goes through the same service layer used by the REST API and Web UI. That layer enforces request throttling. The tape cmdlets are extremely chatty, so when scripts call them in quick succession (as most reporting scripts do), you’ll hit TooManyRequests.Fix summary: Wrap tape calls with a retry/backoff helper, prefetch once (no calls inside loops), and serialize tape inventory access (don’t overlap reports, rescans, and tape jobs).  What Changed in v13? Veeam v13 moved PowerShell off the old .NET Framework RPC and onto .NET + a service backend shared with REST and the Web UI. The upside: one consistent platform. The downside: you now inherit API-style throttling that didn’t exist in v12.Symptom: Import-Module works, RBAC is fine, the first few tape calls may succeed, but bulk/sequential tape calls fail with TooManyRequests. Important: This is rate limiting, not permissions. Being Local Admin + Veeam Admin doesn’t

Upgrades - at least with Veeam - usually go smoothly. But every now and then, one catches you off guard. After upgrading Veeam Backup & Replication (VBR) to version 13, we ran into an issue that completely blocked access to the VBR console.I’m sharing this here in case it helps others who might hit the same problem.The Problem: No Console Access After UpgradeImmediately after the upgrade to VBR v13, the Veeam Backup & Replication console refused to connect to the VBR server.Instead of the expected login screen, we were greeted with a certificate error. What made troubleshooting especially confusing was that the error occurred regardless of how we tried to connect: localhost server IP address fully qualified domain name (FQDN)All resulted in the same error. From a Veeam perspective, everything on the server side looked healthy, services were running, and nothing in the upgrade logs indicated a failure. Before the upgrade with V12, we did not have any issues here.Root Cause: S

Hi ALL,I would like to ask for assistance with the following scenario. I am planning to purchase two StoreOnce systems and use Veeam as the backup software. I plan to use Catalyst and Backup Copy jobs to transfer backup data from StoreOnce #1 to StoreOnce #2.My question is: in this case, assuming that there is already existing backup data on StoreOnce #2, if a new Active Full backup is approximately 100 GB in size, will the data synchronized be the full 100 GB, or will only the changed blocks from StoreOnce #1 be transferred to StoreOnce #2?In other words, will this behave similarly to the replication of two NAS shares on StoreOnce, where only changed blocks are synchronized?”Thank you so much.RgdsHieuht 

The various discussion in the below article gave rise to the creation of this article. In previous discussions on the community and my blog, we have extensively covered the steps for performing a clean installation of Windows Server, reinstalling Veeam Backup & Replication (VBR), and migrating the configuration database.If you wish to have your VBR running on the latest Windows Server 2025. I have crafted a very detailed article discussing the steps here “how to perform an in-place upgrade from Windows Server 2022 to Windows Server 2025”. Windows Server 2025 comes in the following editions tailored to different organisational needs. They are the Essential Edition, the Standard Edition for lightly or non-virtualized environments, the Datacenter Edition for highly virtualised datacenter and cloud environments, as it is in my case, and the Datacenter: Azure Edition for seamless integration with Microsoft Azure in hybrid cloud scenarios.In this article, I touched on “Microsoft Windows

XCP-ng stands for Xen Cloud Platform, next generation and it is an open-source virtualisation platform that allows you to manage virtual machines and networks efficiently.XCP-ng delivers high-performance enterprise-level virtualization with a rich ecosystem. You can integrate it into your full stack for management and backups. It serves as the modern successor to XCP, which developers originally created as an open-source version of Citrix XenServer back in 2010. XCP-ng ArchitectureXCP-ng is a secure platform by default and enables you to run any kind of virtualisation workload . It contains multiple components, built around the Xen Hypervisor. It’s meant to run on top of bare-metal machines.XCP-ng runs Xen hypervisor on bare metal hardware (CPU, RAM, disk, GPU) to host VMs and PVs (paravirtualized guests). Dom0 (control domain) manages everything via tools and APIs, while backend drivers handle storage/network/QEMU emulation for guest domains.You can download the latest installer for X

     I have been talking with several service providers over the past 2 years around Broadcom. These conversations have shifted over the past few months. The initial conversations were around the price increase and change of functionality, but more recently around partners being kicked out of the program and no longer able to transact with Broadcom. This shift has forced service providers to reconsider how they would provide services to their customers and what options are out there.    I compare this to trying to get into fishing. You could just show up at the lake without any information and just start casting lures or live bait, but you have no plan on what fish species are in the lake, what depth you are at, is there any cover on the bottom. Although you could catch fish this way, your chances are more based on luck. The other option is to use technology to help you be more successful, things like a fish finder, live scope, lake maps with topographical detail, information on what f

In te Part I We saw How→ Two Node Red Hat OpenShift 🤓 (TNA & TNF) Part1In Part II, we will walk through the officially documented failure scenarios for: Two Node OpenShift with Arbiter (TNA) Including scenarios such as: Arbiter node outage Single control plane node failure Double node outage Quorum loss       

IntroductionThe Veeam Software Appliance (VSA) v13 comes packed with a lot of new features and one of my favorite, is the ability to enable High Availability for the Veeam Backup and Replication server.The business outcomes for our customers are huge:Reduced Business Disruption Faster, More Predictable Recoveries Operational Confidence SLA ProtectionIn this article, we walk through how Veeam ONE acts as a Cluster Witness, how automated remediation enables hands‑off failover, and what operators should expect during failure, recovery, and cluster rebuild scenarios.HA Cluster Failover automation is one of these capabilities that made it late into the release and probably went unnoticed for most. I won’t go into the setup details as they can be found in the user guide and community members have covered that topic extensively (see Marvin’s or Leaha’s posts for instance).We will focus on the steps to automate VSA HA Cluster Failover by leveraging Veeam ONE’s remediation actions. Let’s dive i

Hi!I would like to share with y’all my initial “hands on” the VBR13 - Linux Based OVAPublishing the entry here, so you dont have to leave the Community Site:-----------------------------------------------------------------------------------------------------------------------I want to share my initial screenshots of the Linux-based Veeam Backup & Replication Server.Tech Preview: VBR on Linux (v13)Private technology preview for Veeam 100, for non-production use only. Let’s get started:As you may know, let’s deploy the OVA in our Vsphere Host:As always, follow the wizard…Select where the VM is going to be storedImportant, LAB, so, Thin Prov.Detailed resume, no worries for the error, is ok! It’s just lab and non-production, remember?Booting and great looking…Easy step, to see the assigned IP address to the VM, quick look into the VM propertiesNow, it is time to open your favorite browser, and call the URL from the VBR IP Address, for the web consoleBoom!Look at this console, beautiful

hi,i try to install veeam  agent (i try with multiple version) on windows server 2025 but when i get to the point of installation it fails.on the log i see “ another installation is in progress” but i don’t have nothing in pending.

First of all, a very happy New Year to everyone of the best community there is 😉It truly feels great to be writing here again.For those who already know me: I’ve been part of the Veeam Community Hub since the very beginning and had the honor of being a Veeam Legend for four consecutive years. The community has always been an important part of my professional journey, so stepping away wasn’t an easy decision.Some of you may have noticed that I was completely absent last year—and that I didn’t attend the  latest Veeam 100 Summit in Prague. Unfortunately, throughout 2025 my time was extremely limited, and I simply couldn’t engage in the way this community deserves. I made the conscious decision to take a sabbatical year from community activities. It was a hard call, but ultimately the right one.The good news?After a year, there’s once again room to focus on what I love:✔ sharing quality-driven content✔ participating in meaningful discussions✔ helping others within the communityAnd I’m fu

ChallengeAfter upgrading a customer environment from Veeam Backup & Replication v12 to v13.0.1.1071, everything initially worked as expected. Existing SAP HANA plug‑ins on several systems (still in v12) continued to run without issues.Problems started when we upgraded the managed HANA plug‑ins to v13 using the Protection Group. Although the upgrade completed and the plug‑in showed v13 in the GUI, backups began to fail immediately.Error MessageError: The issuer certificate does not have a Basic Constraints extension.(Parameter 'issuerCertificate')The error appeared:During the Protection Group rescan (post‑upgrade)   During every backup attemptRoot CauseWith v13, the SAP HANA plug‑in and assumedly all other enteprise plugins perform stricter certificate validation. An internal issuer certificate used for plug‑in communication was missing the required Basic Constraints (CA:TRUE) extension, which was previously tolerated in v12.SolutionThere is a KB that mentions this very error, but

Veeam continues to innovate, develop and release enhancements for Veeam plug-in Backup for Nutanix v9. Our customers keep asking for improvements and Veeam is delivering them. One major improvement was to eliminate the proxy appliance. This new version uses a worker architecture like some of our other cloud products. The worker VM is configured during the addition of the Nutanix plugin. This dramatically improves manageability and simplifies job management.  Everything is now configured in the Veeam Data Platform console. We also added the additional features below. For other improvements see the “What's New in VDP 13”. Key Architectural ImprovementWorker Architecture Security Enhancement: vTPM SupportVirtual trusted platform module for Virtual Machines. For customers looking for that added security enhancement in Windows 11 VM. This is a requirement from Microsoft. Please see link for more details Nutanix vTPM vTPM protected VM vTPM VM Configuration Email Notification ImprovementsThe

Hi all,Just a quick blog post to summarise the findings from a question that was recently posed to me.Background on VB365 Retention Modes:When using Veeam Backup for Microsoft 365, there are two retention modes possible. These are called ‘snapshot-based’ retention and ‘item-level’ retention. I won’t repeat Veeam’s documentation and you can have a full deep dive into the topic here if you’d like, but to provide a brief summary:Item-level retention leverages the creation date and last modified date to determine if an item is older than the retention period. If it is not, then it will backup the item. Snapshot-based retention protects everything that currently exists within the container (mailbox/OneDrive/SharePoint/Teams) regardless of creation date or last modified date. Once the item no longer exists within the Microsoft 365 container, Veeam Backup for Microsoft 365 determines if how long ago it was last protected is older than the retention period, and if so, purges the item from the

The other night, I had a weird dream. It wasn't one of those confusing dreams, but a clear vision of what our lives as backup administrators would be like in a few months. In the dream, Veeam's recent acquisitions — Securiti AI, Coveware and Object First — were no longer just logos on a slide, but a single living organism. The previews at the Veeam 100 Summit in Prague last November got me fired up to work even more. In the midst of all this confusion, I tried to bring some order, and this is what I 'saw' in my dream.(generated with Nano Banana)The evolution of the species: beyond simple recoveryRecently, us backup administrators have been talked a lot about recovery. "How secure are my backups?" How quickly can I get back online?" So, over the next few months, we'll be asking ourselves: "What am I recovering and where's the rest of it?"The deal with Securiti AI is going to change the game for Veeam. They're already top-notch when it comes to keeping data safe (backups and all), but th

Dear community, Let me take this opportunity to wish you a happy new year and all the best for 2026. 🎉 I hope that your year has got off to a great start, and I have a fantastic selection of Veeamazing content for you from the Veeam Vanguards. Scroll down to see the content that our Veeam experts published in December. 🤓 ​@AndrePulia  - What would prevent migrating from Veeam v12.3 to Veeam v13 - https://pulia.com.br/what-would-prevent-migrating-from-veeam-v12-3-to-veeam-v13/ Block Repository – DAS Using Internal Disks – Part II - https://pulia.com.br/block-repository-das-using-internal-disks-part-ii/ What does a SOBR have in common with a wardrobe? - https://pulia.com.br/what-does-a-sobr-have-in-common-with-a-wardrobe-2/  Veeam Backup & Replication v13.0.1 – Course experience recommendations - https://pulia.com.br/veeam-backup-replication-v13-0-1-course-experience-recommendations/​@AndreTheGiant  - Veeam beta support for HPE VM Essentials - https://vinfrastructure.it/2025/12/vee

VSPC from version 9.0 offers new option how to connect directly VBR and EM (not only via cloud gateways), which is via port 9999/tcp from VBR/VEM → VSPC I have added my Windows VBR, where is installed VEM as well Management Agent could run under local System account or under service account Server is after installation of management agent appeared twice as VBR and VEM is installed on this VM. In License section is option to enable “”License Auto Update”Is not working, because VEM is managing license for VBR So for VEM is needed to skip pushing of license and let to handover this action to VSPC.Is it done over registry key - reboot is required. SkipLicensePush Type: REG_DWORD   Default value: 0   Description: prevents Enterprise manager from pushing the license to B&R server ([HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup Reporting])  After reboot of that server could be enabled License Auto Update 

The ProblemLast week we were troubleshooting a Veeam Backup & Replication environment, where jobs were slowing down since some time.Looking at the jobs, the backup performance itself was quite good, but the processing of some VMs took longer then expected.The task log of those VMs showed that "Collecting disk files location data" was the cause; for some VMs it lasted 20 minutes, others were waiting for several hours.I first suspected a vCenter problem, as the debug logs showed timeouts and an unsupported API, but after patching and some restarts the problems persisted.The ResolutionDoing some research I’ve stumbled over an R&D forums digest from @Gostev from the year 2018 (Veeam Community Forums digest at that time ). And this one brought us in the right direction as Anton mentioned disk fragmentation as a pausible cause for this issue.I’ve opened up a Veeam support case just to be sure, before approaching the storage team, but later on our customer discovered some left-over s

I wanted to let you know that the Hitachi Vantara Universal Storage API (USAPI) plugin that supports Veeam Backup & Replication V13 servers running on both Linux and Windows is generally available and posted on the Veeam downloads page (Veeam KB4191). This new plugin also supports immutable snapshots and works with Hitachi Vantara’s VSP One High End enterprise storage system.Here is the link to last year’s white paper on Hitachi Vantara and Veeam integration as a reminder of the plugin’s capabilities before this release.And here is a link to the hitachivantara.community.com blog I posted: https://community.hitachivantara.com/discussion/accelerating-cyber-resilience-whats-new-in-hitachi-vantara-veeam-usapi-plug-in-v22

Upgrading Veeam Backup & Replication v13 often fails during the "Component update" phase with the error “unable to deploy the Veeam Deployer service due to SSH credentials not specified”. Veeam generates Single-Use Credentials as temporary, ephemeral credentials to securely deploy and upgrade VHR components. Veeam requires Single-Use Credentials to meet modern security and compliance expectations. As mentioned above, this is because of the unavailable Single-Use Credentials (SUCs) at the time of the upgrade as shown below. Note: You cannot perform this upgrade over the ribbon or right-clicking on the VHR in the working area of the console. This will not work. This is similar to navigating to the main menu (hamburger menu) and selecting update (update components). This will also not work because we are yet to specify the SH credential. The FixTo fix this, we will have to navigate to the Backup Infrastructure, select the server and click on “Edit Server”. Here is a link to the origin

 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 bind and won’t start. 2. Supported In‑Place Upgrade Path You can only perform an in‑place upgrade to v13.0.1 from v12.3.1 (build 12.3.1.1139) or later. Older versions need to upgrade to an intermediate supported release first. A helpful upgrade path table shows recommended steps from older VBR versions up to v13.0.1. 3. Hardware & OS Requirements 64‑bit OS support (Windows Server 20

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 | bashAs you can see here, we must select WireGuard!!Port! I leave the default one, to be opened later on in our router.Super Important! the script detected we have deployed in the same machine Pi-Hole, so say yes and continue.here, Important step, select DNS as shown, to be able to call our service via DuckDNS Subdomain and not Public IP Address!!Done!Now our server is full setup with PiHole, DuckDNS and Wireguard.Now we need a few adjustments in PiHole and create users in WireGuard.Important!The Server has not a fixed IP Address, I do assign an IP address on my DHCP, if you want to do so, please setup a fix IP address into the machine.Open your port on the router to

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 Veeam, set up your jobs, manage your snapshots, all per array.For two or three arrays? Fine. For a significant fleet (dozens of arrays across multiple sites)? Operational overhead compounds fast.What Changes with Fusi

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 repositories had object lock and immutability enabled, which ruled out many traditional ob