Community

 Secure backups have always been important. But over the last few years, the requirements have shifted from “Yes, we should have backups — and ideally a second backup copy in another location and on another medium” to “Hopefully the backup still exists, is reachable, and really cannot be deleted.”Ransomware, compromised admin accounts, supply-chain attacks, and targeted attacks against backup infrastructures have made one thing very clear: a backup is only truly useful if, in the worst-case scenario, it is reliably available, usable, and uncompromised.Terms like WORM, immutability, Hardened Repository, Linux Repository, Veeam Infrastructure Appliance, single-use credentials, certificate-based authentication, Governance Mode, Single Disk, and Multi-Disk installation appear very quickly. But what is actually behind these terms, and what do I need for my use case?With Veeam Backup & Replication 13.1, the topic and the available options have been significantly improved and expanded. Bu

I just upgraded Veeam B&R from 12.3 to 13.1 and everything appears to have gone smoothly, with all components being upgraded without issue. The only problem we have is that we are notified each morning with a Software Update Summary email that our Veeam server ‘VBR’ Failed to synchronize update settings. Error: Failed to connect to the Veeam updater service.I was wondering if anyone is familiar with this error and how to resolve? Going through some steps online, I have verified the Veeam Updater service is running, backups are working, SQL connectivity and internet/DNS is working. Tried restarting service as well as a server reboot. Only the scheduled update-settings sync task is failing.My next step was going to be mounting the ISO and trying to repair the program, but wondering if anyone may know how to resolve this before I go that route. Everything else seems to be working just fine, so hoping to avoid a full reinstall. Thanks!

Hi All,I am new the the community and fairly new to Veeam and was wondering if anyone would mind sharing their own opinions and/or pitfalls  experienced using the Inline Entropy Analisis feature?My organization uses Veeam for Vsphere backup and DR and I have been asked to gather information prior to using in production.   I sounds great but from what I’ve read so far it has its limitations. Has anyone experienced any performance issues with backups or any other gotchas?   Have you found the feature useful?  Any feedback would be greatly appreciated.Thank you!

We’re having a major tape library issue with one of our clients. Do you perhaps have any ideas or solutions to suggest?(I’ve already asked the AI about this, but it didn’t help.)In their Veeam Backup & Replication environment, our client originally had four libraries:-    Scalar i3-i6 03255-    Scalar i3-i6 03256-    Scalar i3-i6 305G-    Scalar i3-i6 341G (Offline)I updated the Scalar i3-i6 03256 and Scalar i3-i6 03255 libraries at Quantum’s request following an incident involving one of the drives.Once the update was complete, Veeam took the Scalar i3-i6 03256 library offline and changed the status of the Scalar i3-i6 341G library—which had been offline—to bring it back online. Veeam thus reversed their statuses.I opened a ticket with Veeam Support, but I’m unable to provide them with the log bundles via SFTP (the file is empty every time, even though I verify that it isn’t before closing the connection), and they’re referring me to the standard documentation for tape libraries.

Hello Veeam Community!I’m thrilled to write my first post here and what better topic than the big news that just dropped? For those who haven’t heard yet, Veeam have officially acquired Object First! 🎉 As someone who’s been working with Object First’s immutable storage solution a few month at G0T0, I can confidently say: this is a game-changer for data protection, and here’s why. 🔍 Why This Acquisition MattersObject First isn’t just another backup appliance—it’s purpose-built for immutability, designed to eliminate ransomware risks and simplify compliance. At G0T0, we’ve been deploying them for our clients, and the results speak for themselves: ✅ True Immutability Out of the BoxNo misconfigurations (the #1 cause of failed restores).Hardware-enforced immutability (not just software-based). ✅ Blazing-Fast DeploymentPre-optimized for Veeam, so setup takes minutes. ✅ Cost-Effective & PredictableNo hidden licensing fees or undesirable maintenance surprises.  🚀 What This Means for the

Hello, I need some advices for a new setup with VSA and Proxmox. The setup :1 cluster with 2 Proxmox node with 1 volume for the OS and 1 volume for the storage of the VMThe storage is done with Datacore Sansymphony (HCI solution). 1 VSA + 2 worker + 1 VIA repository for backup + 1 Synology NAS NFS for backup copy  I read Veeam documentation and limitation and I have 2 mainly questions :The Snapshot storage must be file level storage. In my scenario, that mean I need to use the volume available on the same disk as the OS right ? Because the storage used for the VM will be block storage …  For the worker, same issue if I understand it correctly, it must be file-level storage that supports snapshots. That mean I also need to use the same volume right ?How do you usually manage it ?  Finally, for the File system of it, do you use ZFS or XFS or EXT4 ?  Thanks for your answer 

Everybody keeps repeating the same headline numbers from the Veeam V13 release notes when it comes to the new Veeam V13 immutability model. 40% less storage, an 8x reduction in retention calls and more than 2x fewer object storage API calls in total. I recently presented this exact topic at our German Veeam Usergroup in Cologne, and the number one question afterwards was basically: “Falko, does it really work like that ?”So instead of trusting the marketing slides, I built a lab, turned on S3 audit logging and counted every single API call myself. I guess most people already know that I love object storage  In this blog post I want to walk you through what I did and what the logs actually revealed.Object Storage has quietly become the most important repository type in the whole Veeam world, and the reworked immutability engine in Veeam V13 pushes this even further. With V13, every job type can write directly to object so there are no exceptions and no workarounds. That is a pretty big

Hi,We have a 2-node Microsoft Hyper-V cluster managed by Veeam Backup & Replication Community Edition.The two nodes are:- BETELGEUSE – works normally- SAIPH – affectedThe problem is that Veeam sees SAIPH as a Hyper-V server, but its Physical Host association appears to be broken.Veeam shows:SAIPH → PhysHostId = 00000000-0000-0000-0000-000000000000and:Get-VBRPhysicalHostdoes not return SAIPH, while BETELGEUSE is returned normally.We verified that:- SAIPH is reachable- VeeamHvIntegrationSvc is installed and RUNNING- WinRM/DNS connectivity to SAIPH works- the Hyper-V host itself is operationalThe impact is that VMs hosted on SAIPH are not being backed up correctly. As a temporary workaround, we moved the VMs from SAIPH to BETELGEUSE using Failover Cluster Manager, and the existing backup jobs then work normally.An important detail: the problem appeared after the network interface cards (NICs) were replaced on SAIPH.We also checked the Veeam PostgreSQL configuration database. The hosts

2025-11-06 Subject: VBR 12.3.2.4165 Installation Failure Version provider was not found in suite context on Windows 11 Pro ARM ParallelsHello,I am attempting a fresh installation of Veeam Backup & Replication Community Edition (ISO: 12.3.2.4165) on a newly created virtual machine, but the Veeam Setup Engine consistently fails with the error: An error has occurred: Version provider was not found in suite context.Environment Details: My host is a MacBook Air running macOS Tahoe 26.1 and I am using Parallels Desktop 26 for Mac. The guest operating system is Windows 11 Pro, Version 25H2. The system type is a 64-bit operating system with an ARM-based processor. The ARM architecture may be a factor in the installer's execution checks.Troubleshooting Steps Completed:I have tried running Setup.exe as administrator, unblocked the ISO file in its Properties, and also extracted the entire ISO contents to a local folder and tried the setup again.I have confirmed that .NET Framework 4.8.1 or la

Hello, Veeam Community! In this newsletter, I'll be sharing some awesome content on the latest version of Veeam v13.1. Authors focused on topics like appliance-based architecture, upgrade planning, changes to the web UI and RBAC, monitoring, and real-world migration considerations.  It also delves deeply into cyber resilience topics such as immutability, secure restore, ransomware-aware backup design and malware detection concepts, offering hands-on guidance on replication, recovery validation, configuration restoration and troubleshooting. Alongside the technical content, the newsletter features insights from the community on blogging, collaboration and operational best practices, making it a valuable resource for backup administrators, architects and engineers preparing for modernised Veeam deployments. Here are some external resources for your reference:Veeam Data Platform latest release: https://www.veeam.com/products/veeam-data-platform/latest-release.html Veeam Backup & Repli

 Hi everyone!I’m sharing what many of my clients ask me every day regarding the S3 protocol, and why it’s the best choice for a backup repository.From a security standpoint, S3 features native immutability rather than an artificially added layer. Unlike applying immutability to file or block storage—where an extra layer is imposed that can degrade performance and increase the likelihood of security vulnerabilities (most notably via administrator access).S3 provides it natively at its core.The S3 (Simple Storage Service) API has become the industry's de facto standard for cloud object storage, thanks to its unmatched scalability, stateless HTTP-based flexibility, and broad ecosystem support.Instead of rigid file structures, S3 flattens data into easily manageable objects inside buckets.While Block, File, and S3 are general-purpose storage protocols used across various use cases, S3 is the only protocol with a native mode designed specifically for the absolute immutable backup storage us

So I managed to get great feedback on my first Blog post here in the Veeam Community, and now that I have access to Claude Code i think it is time to update with my current version of the script. I now call it Get-RepositoryV2.ps1This blog post is an update to the first blog post I did 8 months ago (Part 1 / Version 1): https://community.veeam.com/blogs-and-podcasts-57/veeam-update-repository-mirror-on-iis-windows-server-12327 where the guide on how to set up the IIS and using the download script has not changed.So what changes in the new version 2? Well, I focus a bit on performance and the option to run in batch mode with a nice interface, and still have the option to output into a log file.I had the help of Claude to re-write most of the code, because getting performance means downloading multiple files at the same time.But I also found it nice to have a kind of process bar to see all the download status in parallel, that is why I made a “Live Panel” when downloading.Here are the st

On Feb 5, 2026, Microsoft officially announced that EWS in Exchange Online is being deprecated. Starting Oct 1, 2026, Microsoft will begin turning off EWS usage unless it is explicitly extended via a setting. With a deliberate “Not yet!” (aka OrganizationConfig -EwsEnabled $true), EWS is expected to remain usable until Apr 2027—however, this is not a permanent setting, just a temporary extension. So first…. What exactly is EWS? EWS stands for Exchange Web Services and was built almost 20 years ago. For many years—and up to today—it has been used as an API interface. In general, this interface no longer meets today’s requirements for security, scalability, or reliability, which is why Microsoft developed the Microsoft Graph API.By now, the Microsoft Graph interface provides near-complete functionality parity for most EWS scenarios. Microsoft’s own applications have either already migrated away from EWS or are close to finishing. Many third-party vendors have also already transitioned to

 When a Windows server or workstation suddenly consumes system storage, system administrators immediately face the challenge of isolating the cause. Standard built-in Windows diagnostic utilities show high-level storage categories, but they often fail to pinpoint the exact directories, application logs, or recent file system changes responsible for rapid disk growth.  Disclosure: SizeTrend provided a complimentary 10-machine Professional license to support this technical evaluation. The analysis below reflects an independent evaluation of the utility’s setup, feature set, and operational value for enterprise environments. Traditional utilities like TreeSize, WinDirStat, and WizTree solve part of this problem by enumerating current file sizes. However, SizeTrend Professional introduces historical disk scan comparison to address a more critical administrative question: “What changed on the file system? SizeTrend vs. Traditional Disk Space ToolsMany Windows administrators already have the

 Excited to share a new project with the Veeam community: MoovIf you run Veeam and you're staring down a move off VMware, you already know the awkward part: the backups are right there, your target hypervisor is ready, but getting the workloads across is still slow, manual, and one VM at a time.Moov closes that gap. It uses your Veeam Backup & Replication restore points as the source and brings VMs up directly on KVM platforms, Proxmox VE, oVirt / OLVM / RHV, and HPE VM Essentials, without ever touching the source vSphere environment during the migration.It's open to the community on GitHub (VeeamHub), currently in beta.https://github.com/VeeamHub/moovWhy another migration tool? Full-restore workflows work, but at scale is complex: extended downtime windows, manual VirtIO driver injection, and moving machines serially while you make some manual tasks. Moov was built for the fleet case, hundreds of VMs, in waves, with the boring parts automated.Three ideas drive it:- Veeam is the si

 Hey everyone!!😎I'm really excited about all the new features Veeam is bringing in this latest release, and one of them really caught my attention: the new approach to Active Directory Forest Recovery.VBR 13.1 brings some important improvements for Active Directory protection, especially when we think about recovery scenarios after a major failure, corruption, or even a security incident.One of the features I found most interesting is the ability to perform Active Directory Forest Recovery in a more automated and guided way.Active Directory Forest RecoveryIn a traditional recovery scenario, depending on what happened in the environment, the administrator may need to perform several manual steps to rebuild the Active Directory environment.With Veeam 13.1, the idea is to make this process much more structured by using the available backups to help recover the Active Directory forest.This becomes even more important when we think about Disaster Recovery and Cyber Recovery scenarios, espe

I want to upgrade my veeam one server and it crashed à stage 3 . every time I need to roll back on backup or snaphot because it uninstalls veeamone services 

IntroductionOne of the most exciting additions in Veeam Data Platform v13.1 is the introduction of the Application Backup Repository (ABR). While many organizations immediately understand the value of immutable backup storage for virtual machines, servers, and cloud workloads, a significant gap has always existed for applications that perform their own native backups.Oracle RMAN incremental merge backups, router and firewall configurations, custom-developed applications, database exports, and countless other workloads often create backup files outside of Veeam's traditional protection mechanisms. These backups are frequently written to standard file shares with little or no protection against ransomware, accidental deletion, or retention mismanagement.The Application Backup Repository addresses this challenge by providing a Veeam-managed, immutable NFS storage target specifically designed for native application backup data.The result is a simple but powerful concept:Let applications co

One of my VM is showing  FIB summary.txt issue in backup copy job. I would like to run Active full backup on only this problem VM . But this backup copy job has 20 VMs which i don’t want to run full backup as it will cause issue in wasabi bucket. Copy job goes to wasabi bucket. I know individual full backup can initiated in Backup job, but it is not showing BCJ . Please advise.Ver 12.1.2

What is SAML?It stands for Security Assertion Markup Language (SAML). It is a standardized way to tell external applications and services that a user is who they say they are. SAML makes single sign-on (SSO) technology possible by providing a way to authenticate a user once and then communicate that authentication to multiple applications.Veeam Software Appliance 13.1 supports SAML 2.0 single sign-on for the backup server level.This technical guide helps to configure it: we start from an empty Windows Server and a fresh appliance and ends at a working SSO login, with an AD FS server, exchanging metadata with the appliance, adding claim rules, and signing in with a domain account.SSO/SAML can't be used in the Host Management Console WebUI (port 10443) - it only uses local accounts by design.Local logins also remain always enabled alongside SAML, which is failback option if SAML stops operating, otherwise you would lock yourself out.Active Directory itself is NOT a SAML identity provider

Hi everyone,I'm running into a strange issue with a Veeam Backup & Replication Appliance v13.0.2.29 on a physical HPE Gen10 server with iLO 5 (firmware 3.13).The appliance boots normally and displays the Veeam Host Management screen, but I can't access the network configuration because the keyboard input doesn't seem to work correctly.ENTER to change the network config!What I've tried:HTML5 Remote Console Java Integrated Remote Console (v252) Different browsers Hotkey programming Ctrl+X Ctrl+Shift+X Fn combinations Java updated to the latest versionThe problem is that Enter does not activate the "Sign in" button, so I can't get into the Host Management menu to change the appliance IP address. The appliance currently has an incorrect IP configured, so I can't access the web interface or SSH.The server is in a remote datacenter, so connecting a physical keyboard isn't an easy option.Has anyone experienced this with the Veeam Appliance or iLO 5?Is there a known workaround to get Enter

Customers running earlier versions or relying on AWS default configurations remain vulnerable to overly permissive security group rules, broad endpoint access, and loosely scoped IAM roles.Gaps that 13.1 closes out-of-the-box. That's why we're asking: Why should customers upgrade to Veeam Data Platform 13.1 now?Because 13.1 makes secure-by-design the default.Tighter network controls, restricted endpoint access, zero-trust policies, and granular least-privilege IAM.It’s a meaningful security upgrade that reduces exposure without adding unnecessary operational complexity. The core AWS data protection challenge isn't just "does Veeam support this workload” it's time-to-protected. How long it takes to stand up a secure, compliant, air-gapped-from-the-internet backup environment before you can even start protecting anything.Cross-team dependencies (network, security, IAM approval, compliance sign-off) are usually where projects stall, not the Veeam install itself. High-Level Security Enhanc

 Original article: What's New in Veeam 13.1 for HPE Solutions - CloudnRoll #VeeamCommunityChallenge This article summarizes Veeam v13.1 and related release updates specifically relevant to the HPE and Veeam partnership, organized by product area: Veeam Backup & Replication, Veeam ONE, Veeam Recovery Orchestrator, Veeam Service Provider Console, and Veeam Kasten.This article includes the features and integrations that are clearly related to HPE solutions in the supplied release materials.The focus is on new HPE integrations, HPE platform support, and HPE-related feature enhancements that improve protection, recovery, observability, service provider operations, and protection for cloud-native applications.SummaryIn the v13.1 release and related release updates, Veeam significantly expands support for many HPE customers´ scenarios.In Veeam Backup & Replication v13.1, the most notable additions include native support and enhanced usability for HPE Morpheus VM Essentials, as well as

Veeam CDP Issue ConfirmationQuestion: Which version of Veeam includes Veeam CDP?