Community

I already have a ticket open on this, but while Im waiting does anyone have any suggestions on things to try. Unfortunately, to make things complicated this only started happening after we upgraded to V13 and also upgraded the firmware on our exagrids. We are using storage integrated backups with Pure. I have not updated the Storage Array plugin yet. I have rescanned everything I could possibly rescan and all backups still sit at 0% 

 We recently completed an upgrade of Veeam Service Provider Console (VSPC) from version 8.1 to version 9.1 in a large-scale, multi-tenant service provider environment. From an infrastructure standpoint, the upgrade was uneventful in the best possible way. All core services came online cleanly, communication between components remained stable, and backup operations continued without disruption. Pre and post-upgrade validation confirmed that the platform was operating as expected. During routine post-upgrade review, particularly within the Managed Computers section, we observed that a subset of endpoints had management agent upgrades that were not completing successfully. After reviewing task logs across multiple tenants, it became clear that these were not platform-related issues, but conditions specific to individual endpoints that surfaced during the agent upgrade cycle. Given the scale and diversity typical in service

I am trying to restore Ubuntu VM to Azure but never got any success. We had issue with ver 12.3 where it never create helper appliance for the region so we upgraded to ver 13. It now try to create helper appliance but never complete succesfully. When restore process starts, it creates helper appliance in Azure with status running but never get pass that stage. Internet access is restricted to outbound access to windows update, azure & Veeam.I even tried restoring the Azure environment where we have ipsec tunnel but not luck, still fail with same error.  

TLDR;set up a linux server as a veeam repository on a proxmox server for local VBR proxmox proxy target? I searched around the community for a bit, so if I missed a good post can you point me at it? We stood up a new site last year and I initially deployed Hyper-V server to run a DC and a file share server at the remote site/branch. Using Hyper-V and Veeam I was happily surprised that Veeam deploys a proxy to back up Hyper-V (mostly was using vmware).I had a local disk attached to the Hyper-V server which acted as a Veeam backup repository. This as a pretty awesome surprise how easily and fast the Veeam backups and restores happened on the Hyper-V server using a USB 3 external hard drive.So Veeam would run jobs to hopefully back up the Hyper-V servers locally and then I would run a disk copy job to pull those backups back to the main site periodically for just in case scenarios, and would also copy the disk copy jobs to a rotating offlin

Hey Veeamers – I just completed the Veeam Data Platform: Monitor, Manage, Analyze (Veeam ONE) training, and this release is packed with power! If you haven’t explored 12.3 yet, you're missing out. This version elevates visibility, analytics, and proactive monitoring to a new level.  Veeam has a reputation for robust data protection, and Veeam ONE 12.3 expands on that with smarter insights, deeper automation, and cleaner, more intuitive dashboards. After the Essentials training, I’m even more excited about its capabilities in real-world environments. What Makes Veeam ONE 12.3 So Exciting?- Next-Level Monitoring & Reporting: From backup job health to infrastructure performance, Veeam ONE provides even more actionable intelligence. The updated alarms and dashboards enhance efficiency by addressing issues before they arise. - Automation that Actually Helps: The remediation actions in 12.3 are seamless. You can observe Veeam ONE diagno

Hello everyone,We are a cloud backup provider and I would like to clarify some doubts before migrating to version 13.We currently use version 12 in the latest available build and will soon migrate to version 13, however my question is:After the update, is it possible to restore the settings in the VSA?And will all Cloud Connect configurations be done in the VSA or in the Veeam Infrastructure Appliance?

 VBR v13 defaults to PostgreSQL for new installs, so for a lot of environments the question is no longer “Should we care about PostgreSQL?” It is “When do we move, and what do we need to fix after we do?”If you are still running SQL Express, the answer is usually sooner than later. If you are running a licensed SQL Server only because VBR needs it, there is a good chance you are carrying cost and patching overhead you no longer need. And if you already migrated but the console feels slower than it used to, that is usually not because PostgreSQL is a bad fit. It is because the default PostgreSQL settings are conservative and generic, while VBR is not.This is the part people miss. The migration itself is usually the easy piece. The performance conversation starts after the restore, not before it. First question: do you actually need to migrate now? Not every environment needs to sprint in

I want to introduce you to another community project I worked on: The Veeam Data Platform Content Pack for Graylog. Graylog is a Security Information and Event Management (SIEM) solution that enables the efficient collection, search, analysis, and alerting of various types of machine-generated data. More details about their products can be found on the official website.Content Pack DescriptionThe first version of the Content Pack enables the visualization of security-relevant events transmitted by Veeam Backup & Replication via Syslog. In addition to a pre-configured Dashboard, further information is extracted from the Syslog data, which allows the ingested data to be analyzed further. For more details about the Content Pack, see

OverviewIn this post, I’ll walk through a practical, step-by-step job configuration (from the lab) with real-world best practices to help you get it right from Day 1.Configuring backup jobs in Veeam is where your data protection strategy truly comes to life. A properly configured job ensures your data is not just backed up—but recoverable, efficient, and aligned with business requirements. Why Job Configuration MattersIt’s easy to click through a wizard and create a backup job—but misconfigured jobs can lead to: Failed recoveries Poor performance Storage inefficiencies Gaps in protection Key takeaway: A successful job ≠ a recoverable backup. Step 1: Choose the Right Job TypeStart by identifying what you’re protecting: Virtual Machines (VMware / Hyper-V / Scale Computing / HPE VM Essentia

For years, the Veeam Health Check Report has been a trusted resource for assessing configuration drift, security posture, and operational gaps across Veeam Backup & Replication (VBR) environments. But as cyber‑resilience expectations evolve, organizations require continuous insight—not periodic manual reports.Note: This is a lab environment and was setup with error for this purpose of this blog.  Why Automate the Health Check?The traditional Health Check tool delivers exceptional detail, but it remains a point‑in‑time assessment. Modern resilience requirements—CPS 234, ASD Essential Eight, ISM, NIST frameworks—expect continuous monitoring, not periodic snapshots.Integrating this logic directly into Veeam ONE Intelligence would:Eliminate manual execution of the standalone Health Check tool Provide continuous diagnostic, configuration, and compliance insights E

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.    

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 al

 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

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:Back

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 lic

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