Community

Sizing Veeam environments has always been a mix of experience, assumptions, and spreadsheets. But that just changed. With the new Scenario Builder, Veeam takes a big leap forward, making multi-site sizing clearer, smarter, and far more predictable—turning complex design decisions into a structured, repeatable process.          RESULTS !!!!  😎📊  To wrap it up, the Scenario Builder turns sizing from assumptions into facts. By modeling real workloads, data flows, and site-to-site constraints, it delivers a clear, defensible, and repeatable design for Veeam deployments. Instead of guessing, you end up with a sizing you can explain, justify, and trust—ready for production from day one.  

How can I import information from a Nutanix platform into the Veeam calculator (https://www.veeam.com/calculators), given that the platform is only compatible with RVTools?I am working on a Nutanix AHV environment with around 660 virtual machines, and I need to perform a proper sizing for my infrastructure.  The Nutanix Collector XLSX file is not compatible with the RVTools format required.  

 Veeam Community Hub | World Backup Day 2026 Contest Entry | Working in the managed services space teaches you pretty quickly that good architecture isn't about optimizing IOPS or storage densities. It's about keeping a business alive when things go wrong. That mindset proved its worth late last year during one of the most stressful weekends my team has ever worked.Our NOC woke me up at 3 AM on a Saturday. Medium-sized regional manufacturing client, three facilities running around the clock, roughly 200 VMs, about 80TB of production data. The client's IT Director was already on the bridge call. A ransomware strain had bypassed their endpoint protection and moved laterally. By the time the anomalies were flagged, the payload had encrypted their core ERP system, SQL databases, and primary file servers. All three production lines were stopped.The threat actors left a ransom note demanding Bitcoin. They also claimed they had successfully deleted every backup repository.The IT Director aske

 Every backup admin eventually gets the same question: how do you know the backup will really work when you need it?A successful backup job only tells you the data made it to the repository. It does not prove the VM will boot, the services will start, or the application will behave the way it should. That is the gap SureBackup is meant to close.SureBackup boots VMs directly from backup files inside an isolated virtual lab, runs health checks and application tests, and gives you a result that means something. Instead of assuming a restore point is good because the job was green, you can verify that the workload actually comes up and responds. What SureBackup is really doing Under the hood, SureBackup uses the vPower NFS service to present the backup files to an ESXi host as a datastore. VMs are then registered and powered on straight from those backup files. Nothing gets fully extracted first, and the original backup chain is not modified.Any writes generated during the verification ses

I was deploying Veeam Backup & Replication v13 in my lab and reviewing the Security & Compliance Analyzer when I noticed a new requirement that I hadn’t seen before: “Credential Guard should be enabled.” I also checked Product KB 4252, but this setting is referenced there but can’t enable it.Can anyone clarify where “Credential Guard” can be enabled for VBR, and whether there is any official documentation from Veeam that covers this requirement?  

I have a single VBR server, using a Data Domain as a repo, and it’s running on VMware. We are migrating from VMware to Nutanix AHV. We’ve already migrated a couple hundred VMs already, and now I’m getting down to needing to move the Veeam server.Doing the migration results in some downtime - the migration process requires that new NIC drivers, etc be installed on the VM. I can easily set the services to manual for that duration, and then restart them when it’s done. BUT … is that the best way to do this? I considered installing a new VBR server natively on Nutanix, and then (somehow) migrating all jobs, etc to it. But the problem is, I only have 1 repo, and I know that multiple VR servers shouldn’t share the same repo. Don’t wanna risk corrupting anything.Has anyone else done this? (migrate a VBR server from one hypervisor to another) If so, what did you do? What should I look out for. Any advice appreciated.

So, I have recently deployed Veeam in my lab.My Jobs are configured. Backups are running. Everything looks… green.Cool.Now comes the part most people skip—and regret later.Because here’s the reality:Day 1 is the best time to break your backup environment on purpose.If something’s going to fail, you want it to fail now—not during an outage when everyone’s watching.Let’s walk through what you should actually test immediately after setup so you know your backups work when it matters. 1. Test a Full VM Restore (Don’t Skip This)What most people do:Assume backups = recoverable.What you should do:Actually restore a VM.Test:Perform a full VM restore to a test location Power it on Verify OS boots and services startWhat you’re validating:Backup integrity Restore process works end-to-end You’re not missing dependenciesIf you’ve never restored a VM, your backup strategy is still theoretical. 2. Test Instant Recovery This is your fastest path to uptime.Test:Use Instant Recovery to start a VM from b

A lot of service providers running Cloud Connect either never deployed it, stood it up once and barely touched it again, or still treat it like an optional extra. That is a mistake. Once you understand what it actually handles, it stops looking optional and starts looking like the management layer you should have put in place earlier.VSPC sits above Veeam Backup & Replication and gives you one place to manage tenant onboarding, license distribution, usage reporting, billing data, and day-to-day monitoring across the customer environments you support. Without it, you end up doing too much by hand and logging into too many individual systems just to answer routine operational questions.This article walks through a production VSPC deployment: how to think about the architecture, how to onboard tenants in the right order, how the Pulse integration changes license management, what usage reporting looks like when you need billing data every month, which dashboards actually matter, and wh

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 module full of practical guidance: how to optimize for performance, time-saving strategies when building recovery plans, and how to troubleshoot the most common issues customers run in

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 manual checks and patch installs work fine

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 has 11 virtual disks A couple of disks reside on a different datastore Veeam successfully creates the VMware snapshot Failure occurs during HotAdd disk attach Behaviour ObservedWhen the job runs: Snapshot creation suc

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 posts in the next few d

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 compromised accounts Shut down affected workloads if neededWhy it matters:If ransomware is still active,

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 Port 2500 is listening Firewall rule for 2500 exists iSCSI NIC has no gateway Management NIC has lower metric Windows DNS API returns192.168.10.191172.16.100.11So management IP is first.  

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 - Malware detection methods in Veeam Backup & Replication 13 - https://vinfrastructure.it/2026/02/malware-detection-methods-in-veeam-backup-replication-13/ ​@be

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 challenges you to think through your own environment before you start building plans. What are you trying to orchestrate? Where does the workload live? What does success actually look like? Th