Blogs and Podcasts

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 stored

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-dr

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

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 Archite

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 exis

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

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 -

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.

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

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:

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 n

 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

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

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 ***

 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:

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

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