Community

Today my fourth book announcement went live for the Mastering Veeam Backup & Replication series.  You can pre-order now.  Note the publishing date says May 11th but that will be moved up to April as that is what we are shooting for.Announcement - Amazon.com: Mastering Veeam Backup & Replication: Architect and deploy a resilient Veeam 13 backup platform with proven best practices: 9781806388899: Chris Childerhose, Rick Vanover: BooksGetting excited now. 

The Skill Your Team Is Probably MissingHere's something worth sitting with: most IT teams are great at backup. They know retention policies, job scheduling, repository sizing, all of it. But recovery orchestration is a different skill set, and it's one that's genuinely underrepresented on most teams.The VRO Essentials course is designed to change that. It covers application grouping and dependencies — a topic that sounds straightforward until you're dealing with a three-tier application where App, Web, and DB servers need to come back online in the right sequence, with the right network configuration, pointed at the right infrastructure. Get that wrong during a real incident and your "successful" recovery is actually still broken. The course also covers monitoring, testing strategy, and a tips-and-tricks

Hello,I noticed something very peculiar. We use the Infrastructure Appliance v13.0.1.1071 for VMware Proxies and hardened repositories. The Backup Server is a Windows box running same version.Every night, we get an eMail saying that check for updates was successful for the Windows Backupserver but failed for all the appliances.When we enable the WebGUI on the appliances and login to their WebGUI’s on port 10433, we go to “Updates” which will say that the last check failed. But when we click on “Check for updates” it works fine. Updates are found, downloaded and installed. All good.So what’s the difference between the automatic daily checks and clicking on “check for updates” on each appliance? We never see the firewall dropping outbound traffic from the appliances around the time the automated daily update checks are done. And the Veeam backup Server (Windows) is the only one, every day, which has no problems checking for updates.The fact that manu

I have two file shares: one for backing up my jobs and one for immutable backups. They are both backing up the same virtual machines. However, my immutable backups keep failing. The immutable repository also shows as Unavailable under Managed Servers.The error I’m getting is: ‘Failed to make the backup file immutable after applying the retention policy: Read-only file system. Unable to open file [.veeam.635.lock] in directory [/BACKUPS/"job_name"] — Error: Read-only file system (POSIX).’

Hello,We’ve recently had to move away from Direct SAN backups as we currently have an open ticket with HPE Nimble regarding an issue affecting that transport mode.In the meantime, we’ve configured Veeam to use HotAdd transport, which is working well for the majority of our environment.However, one specific VM refuses to back up via HotAdd.Environment Summary vSphere environment Backup proxy is a VM within the same cluster HotAdd transport mode (Automatic selection) Fallback to network mode disabled (initially) Veeam account used: adminaccount@vsphere.local (member of vsphere.local\Administrators, inherited from Global Permissions) No snapshot or consolidation warnings on the VM All hosts in cluster have access to the same datastores Problem VM Details VM ha

We’re in the process of migrating from VMWare to Nutanix and have a brand new Veeam installation and repo and we’re testing the backup configurations right now. What we’re seeing is that there is a 60 day expiration on the snapshots Veeam creates during a backup in Nutanix and it doesn’t clean any of them up following the backup. It just keeps stacking snapshots every time it runs and we need it to run daily. In the end we’ll have nearly 300 servers in this environment some of them absolutely massive. Is there a configuration I’m somehow missing here? 

Hi all,I am currently encountering an issue when backing up a very large NAS.Each file share is over 100 TB, and there are more than 3 backup jobs. The backup process has been running for 140 hours and is still only around 10-15% complete.We are currently backing up from a Nutanix file share and using the “Backup directly from file share” method in Veeam. I have split the proxy into two. The first proxy uses the VBR server itself, and the second proxy uses a VM from Nutanix.Is there another way to make the file share backup process faster? Or has anyone else experienced something similar? Because at this point, the backup process will not meet the RPO.  

I recently went through the Veeam Recovery Orchestrator Essentials course in Veeam University Pro and I will post some of my impressions on the course and about why recovery orchestration is essential to any data resilience plan.When I was growing up, my dad used to take me to see the symphony and I always thought the conductor had the easiest job in the whole symphony. He just waved his baton during the whole concert! But then I realized that it only looks easy because of all the preparation done before the concert. All the hours, days, weeks of preparation and practice made the performance look easy.It’s exactly the same way with recovery orchestration. As my friend Scott says in his post about Disaster Recovery at 4AM, no one wants to be doing the planning and thinking at the time of DR. If things can be planned and tested beforehand, at the time of DR, you look as calm as the conductor of a symphony.Today I’m going to post an overview of the course. In other

Hi,I needed to open a support case, however, when clicked on “Open a case” button I was presented with https://www.veeam.com/upgrade.html?return_url=https%3A%2F%2Fmy.veeam.com page requesting additional details to upgrade my profile. Filled out the form, clicked on “Upgrade profile” button - the page basically just refreshes with my data in it, doesn’t proceed further. Tried several times, also in a different browser.Thank you!

In this article, I will talk about Recovering Fast after a Ransomware attack using Veeam. I have tested this in my lab and educated my customers on every demo on the importance of having this all-in place. You would be amazed at the responses I get and how unimportant backups seem to everyone until they're neededRansomware doesn’t give you time to think.One minute everything’s running fine. The next, files are encrypted, systems are offline, and someone is asking how long recovery will take.That’s the moment where your backup strategy stops being theory—and becomes reality.If you want to recover fast, you need more than backups. You need a recovery plan that actually works under pressure.Let’s walk through what that looks like using Veeam. Step 1: Contain the Damage (Immediately)Before you recover anything, stop the spread.What to do:Isolate infected systems from the network Disable

we have initiated veeam replication job from pr site to dr site and failover to dr site,at dr site after failover we imported vm to VCD and renamed vm to new one and makes changes to replica on VCD,after this we failback to production and commit failback,but changes done on dr site vm are not showing up on pr site vm, what could be the possible issues.  

.

Hi everyone,I have a SureBackup issue and I’m trying to understand the IP selection behavior.SetupRepository server has two NICs:Management NIC 192.168.10.191 Has gateway Domain profile iSCSI NIC 172.16.100.11 No gateway No DNS Used only for iSCSI to Synology ProblemSureBackup fails with: Failed to connect to the endpoint [172.16.100.11:2500]Veeam is trying to connect to the iSCSI IP instead of the management IP.What I verified VBR can connect to 192.168.10.191:2500 → OK VBR cannot reach 172.16.100.11 → expected VeeamTransportSvc is running

I have a 7 node HyperV failover cluster and each host is running Windows server 2022. I have about 20 Red hat linux VMs in my cluster and added the cluster to my Veeam inventory. Most of the VMs added sucessfully with the cluster, but about 6 of them are added with all blank fields. There's no name, no node info and the host OS says unknown. When I try to add these VMs to a backup job in Veeam 12.3.2.3, they show the accurate disk capacity on the VM page, but when I run the job they all fail. I get an error about how Veeam failed to get the VHDX information.Many of the VMs had multiple HyperV checkpoints that were all deleted and merged. There was also an issue where our HyperV cluster had cluster traffic blocked on certain nodes in the past, which may have cause some Cluster synchronization/ownership permission.  Please advise on how to make Veeam able to read these VMs.  I understand this may be a more of a Microsoft issue, but any assistance is appreciated.  

Happy Friday, dear community!  I hope you all had a great week, and here's a veeamazing selection of reading materials for you! As you are probably aware, over the last three weeks, we have announced the new classes of 2026 for all three community programms at Veeam. This February Vanguard Newsletter reflects the announcement of the new Veeam Vanguard Class, and also features content from our new Vanguard members. 🤓 I am excited to see how many insightful articles reflecting product updates have been shared over the last month, and I am already looking forward to the next one, which will follow soon! We will soon have the updated Veeam100 Directory up and running, where you will be able to view the profiles of all members of each of our community programms, such as the Veeam Vanguards, Legends and VeeaMVPs. ​@AndreTheGiant 

From Install to Orchestration — What You'll Actually LearnOne of the things that makes the VRO Essentials course stand out is how practical it is. This isn't a high-level overview that leaves you with a slide deck and no idea what to do next. By the time you've worked through it, you'll have touched nearly every part of a real VRO deployment.The course walks you through installation, initial configuration, and the dashboard — then gets into the meat of how VRO works: Orchestrator Agents, Recovery Locations (VMware, Storage, and Azure), Virtual Labs, DataLabs, scopes, roles, credentials, YARA rules, and more. Each topic is paired with clickable labs so you can see exactly how things look in the UI and follow along step by step. There's also a genuinely useful module called "Recovery Homework" that challeng

My recent discovery so it could help someone not to loose time. And maybe if there is a solution I’ll be most thankful.So with Proxmox version 9 you need to set Machine type to version 9.2 instead of Default as it defaults to 10 and that causes Veeam backup to fail.  That will insure that your backup will be sucesful and restore will work too. I have issue, where I am migrating servers from Hyper-v to Proxmox and usual and most painless solution was to use Veeam Backup&Restore as intermediary as we are already using it.But in this case restore to proxmox fails as when VM is created is created with default version for machine type and this defaults to 10 and this results in: Failed to prepare disks for restore. (If anybody knows how to convince the process to default to 9.2 Mychine type I’

Hey guys,I’m installing a VM on our Synology NAS to act as a Veeam Hardened Repo. I already had it before but now doing it trough Infrastructure Appliance.When I start the installation I get’s stuck in this process: Any recommendations for it? 

In this article, I will discuss the mistakes being made with backups, which I frequently hear about from my customers.Let’s be honest—most backup environments look perfectly fine… right up until you actually need them.Jobs are green. Reports look clean. Nobody’s complaining.Then something breaks.And suddenly you’re discovering—live—whether your backups are real or just a comforting illusion.Here are the 10 most common backup mistakes I’ve seen (and probably fixed at inconvenient hours), plus how to actually solve them using Veeam. I've tested all of these in my lab environment. 1. Not Testing RestoresThe problem:A successful backup job does NOT mean you can restore.The reality:If you haven’t tested it, it doesn’t exist.The fix:Use Veeam’s SureBackup to automatically verify recoverability. It s

While managing and upgrading Linux agents through Veeam, you may encounter a seemingly misleading error:Host is unreachable. Failed to connect to <hostname>. Details: Cannot find a compatible console test instruction. All known instructions are not available or executed with errors. At first glance, this looks like a network connectivity issue, but in many cases it actually points to a failure during authentication or remote command execution.Problem analysisIn this scenario, the error occurred while attempting to connect to the Linux host server-vm1 for agent installation/upgrade operations.The root cause was traced back to the credentials used by Veeam for remote access (typically via SSH). When the password of the dedicated service account becomes inv

I wanted to abandon my bare-metal Windows Server/VBR12 instance because of Microsoft and finally switch to VSA.So I set up and configured a bare-metal test installation of VSA on the server.This server has a direct connection to the HPE MSL 4048 tape library via a SAS controller.Full of anticipation, I then read: "Note that Veeam Software Appliance cannot be used as a tape server." at: https://helpcenter.veeam.com/docs/vbr/userguide/connecting_tape_devices.html?ver=13Seriously? That's incredibly counterproductive!Now I'm supposed to set up and maintain another server because VSA doesn't have the usual integrated tape server role? I also haven't found any option in the web UI to integrate and use the currently running tape library via a tape server, as is usually the case.Seriously? Did the DevOps team drop the ball here?

 Is Your Disaster Recovery Plan Actually Ready — Or Just Ready on Paper?Let's be honest. Most IT teams have some kind of disaster recovery plan. A document somewhere, a few backup jobs running, maybe a virtual lab that hasn't been tested since it was set up. But when the moment comes — ransomware hits, a site goes down, VMs get corrupted — that's when you find out whether your plan is real or just a formality.That gap between "we have a plan" and "we can actually execute it" is exactly the problem Veeam Recovery Orchestrator (VRO) was built to close. And it's exactly why the VRO Essentials course exists.VRO isn't just another backup tool. It's a platform for building, automating, and testing full disaster recovery workflows — so that when something breaks, your team isn't scrambling through a checklist hoping nothing was missed. Recovery happens in the right order, at the right time, with the right verification baked in.The cours