News, guidelines and various community projects
Recently active
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
Hi everyone. I have a question: I want to upgrade from Veeam 12.3.2.4854 to Veeam 13.0.3.63. However, I have an immutable repository running on RHEL 10.2; as you know, the SSH port is disabled. Since the new version needs to be applied to the components on the immutable repository, is it necessary to enable port 22, or can the upgrade proceed even with that port disabled? I hope that makes sense.
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,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
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
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
With the Veeam Software Appliance and the Veeam Infrastructure Appliance, update distribution is fundamentally changing. The Veeam Appliances automatically install certain updates to ensure security and operational continuity. This represents a massive increase in security and compliance. What is updated?Operating system and security updates are installed centrally and automatically, cannot be deselected, and are mandatory for both appliances. Security updates for Veeam Backup & Replication are also installed automatically and without user intervention to ensure security.Both appliances can also optionally install feature and bug fix updates automatically, provided this is enabled in the configuration. Major updates (e.g., V14.0), minor releases (e.g., 13.x), and private fixes are optional by default.Here is a simplified overview:Mandatory updatesVeeam cumulative & security updates (e.g., 13.0.x) Operating system security updatesOptional updatesMinor product updates (e.g., 13.x
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
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
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
Veeam Backup & Replication 13.0.2 dropped yesterday — and if you manage a smaller environment where a single Windows Server hosts all the things (Proxy, Mount Service, vPowerNFS, Guest Interaction Proxy, you name it), you may have hit an annoying moment when tried to open the console after upgrading the VBR server. You open up the Veeam Backup & Replication console, enter your server's name, click Connect — and instead of the familiar dashboard, you get this: Failed to connect to the backup server: the connection has been established but client update is required, however this machine is hosting other roles. Make sure these following roles are not in use and uninstall them … The message is accurate: the console client is older than the freshly updated server, and the in-place update mechanism wants you to remove other roles before it allows the console to update itself. In a larger, role-separated architecture that is fine — but in a compact single-server se
Veeam CDP Issue ConfirmationQuestion: Which version of Veeam includes Veeam CDP?
For years, we have heard the same prediction: tape is dead.Earlier this year, I had the opportunity to take part in a Veeam Oxford Style Debate around the statement “Tape Is Dead”. The discussion brought up strong arguments on both sides, especially around object storage, immutability, cloud and modern archive solutions. But from my experience working with backup environments, I still believe tape has a place in a modern data protection strategy.Disk storage became faster and more capable, object storage became more accessible, immutable repositories became an important part of ransomware protection, and cloud changed the way organizations think about long-term retention.And yet, tape is still here.Veeam Data Platform 13.1 gave me another reason to revisit that discussion. The platform continues to evolve around new virtualization technologies, storage integrations, security and archive capabilities, while tape is still part of that evolution.So instead of looking at tape as an old tec
Well I have reached blog #10 and the final one in my series about v13. Check it out below and the link to my blog site as well. I will be thinking about some new blogs and might do some focused ones on Wasabi among other things. Stay tuned.Blog - Recon Scanner in v13: Why Backup Admins Should Care Recon Scanner in v13: Why Backup Admins Should Care Introduction Backup administrators are increasingly part of the security response path, whether they planned for that role or not. As backup platforms become more central to resilience planning, features like Recon Scanner matter because they can improve visibility into suspicious conditions that affect recoverability.That does not turn the backup team into a SOC. It does, however, mean that backup operations can no longer ignore security telemetry that may influence restore decisions, protection confidence, or the urgency of administrative action. Why It Matters Operationally A backup platform that can surface signs of abnormal behavior
In the dialog where I can add servers there is no ption for Proxmox.I have Veeam Backup & Replication 13.0.2.29 Enterprise Plus Edition.How do I get the option for Proxmox
Hi everyone, i’ve been having this problem for a while now…Email notifications after backup completion are not being sent anymore to the specified email address, but when i test the credentials the email arrives successfully to my email account. I’m using the Veeam Agent 5.0 on a windows server 2012 r2. No veeam B&R is implied, just the agent making backups to a local disk.Additional informations:i recently changed the email server for the email account, before changing it everything was fine and the backup emails arrived, so at a first glance it seemed a problem with the email server; but i made a clean installation of veeam agent 5.0 on another server, using the same credentials, and the emails for the backup job are arriving regularly; so this excludes the fact that it may be a problem of the new email server(and also the fact that the email tests arrive without any problem).So i thought this may be a problem related to some veeam files regarding the old installation, so here’s
Hello Veeam Community!We just wrapped up our Hackathon-themed August V100 Show: One (local) UI to Rule Them All. Thank you to @jorge.delacruz, @CMF, and @JonahMay for joining, and to @Dynamic for his involvement in this show’s content 🤗Register for the Veeam Community Hackathon today! Registration is open until September 30. If you missed the show or want to rewatch, catch it below ⬇Overview:Born from the Veeam Community Hackathon 2025, Open Backup UI is a unified, self-hosted dashboard that brings VBR, Recovery Orchestrator, and Backup for Microsoft 365 together in a single modern web UI — built entirely by the community, for the community. In this special edition of The V100 Show, we go behind the scenes and dive into:How Team 1 turned a hackathon idea into a working monitoring dashboard — live demo included The tech behind it: Next.js, TypeScript, and the Veeam REST APIs, container-ready with Podman/Docker Lessons learned from building as a distributed community team From Jorge
Is anyone else waiting for Veeam support for “Azure Database for PostgreSQL Flexible Server Support” ? It’s been GA since November 2021 and replaced the Single Server which was retired in March 2025, so it seems a bit surprising there is no support to back it up using Veeam, and my support ticket indicated there is no ETA for this feature !This seems a big gap in Azure PaaS support to me. I’d also be interested in any work arounds people have in place. Thanks, Graham
In today’s digital world, data security is a top priority for organizations. Veeam Backup & Replication has evolved to meet these needs, and one of its key innovations is the Veeam Hardened Repository ISO—a solution designed to protect backup repositories from ransomware and other cyber threats.What Is the Veeam Hardened Repository ISO?The Veeam Hardened Repository ISO is a Linux-based solution that secures backup data by making it immutable. This ensures that data cannot be modified, deleted, or encrypted by unauthorized parties, even in the event of a ransomware attack. The repository allows organizations to set a retention period during which backups remain secure and unaltered.Key Features:Immutability and Retention Locks: Ensures backups are safe from external modifications. Ransomware Protection: Protects backups from being encrypted or deleted by ransomware. Linux-based Security: Utilizes Linux’s built-in security features for enhanced protection. Enhanced Data Availability:
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
The Ingram Micro Technology caravan was built with a modular design in mind. It was originally built to showcase our product portfolio, with its original design focused on IoT devices and integration. Over time, it evolved and was converted into a mobile datacentre to showcase the Whole ecosystem.It now features an 18RU rack inside and has previously featured HPE routing and switching solutions. As technology changes, so does the caravan, and it continues to evolve to showcase different technologies and use cases. My Latest ChangeRecently, it has gone through its most significant change yet, moving away from the Broadcom VMware hypervisor and now showcasing HPE Morpheus VM Essentials (VME) as its primary hypervisor.As part of the migration, I used Veeam Data Platform (VDP) to back up workloads from VMware and restore (transform) them into HPE VME.I was fortunate to start this project just as the production release of VDP 13.1 became available. Migration ExperienceThis didn't come witho
I’m getting the below error after upgrading Veeam servers from v12 to the latest release of v13. It’s a windows based install of Veeam, and it is connected to a (dedicated to Veeam only) AD domain.My user has local administrator permissions, Veeam Backup Administrator permissions, and MFA disabled for testing/troubleshooting purposes. The is happening across each of the Veeam v13 servers I have on the domain.It is only happening for mine and one other engineer’s user accounts, but other engineer’s accounts are not affected. We are all in the same AD groups so permissions are the same.I have tried removing Veeam Backup Administrator permissions from my account, rebooting, and re-adding, to no effect.Has anyone seen this before? Any suggestions for what else to check? In the meantime I have a case open with Veeam support, and hoping they can come up with something.Relevant logs:[19.01.2026 21:07:36.194] <126> Error (1) Veeam.Backup.IdentityService.Shared.CSystemAccountProvid
Hi all,I had a customer who needed a way to obtain Veeam Software Appliance (VAS) updates within a closed OT/dark site/closed environment.However, the challenge was that they lacked Linux experience and would prefer to do everything in native Windows, without using WSL (Windows Subsystem for Linux). If you have no idea what I am talking about, read this section of the Veeam help center: https://helpcenter.veeam.com/docs/vbr/userguide/update_appliance_configure_updates.html?ver=13#setting-up-custom-update-configurationSo my idea was to build/configure two components:1) A PowerShell script that can be run in Windows to download the necessary files from repository.veeam.com to a computer with internet access and then zip the files into a single large Zip file. 2) Create an IIS server website with all update files needed for the VSA. Then we can easily hand-carry the Zip files from the internet-connected Windows computer to the IIS server in the OT/dark site/closed environment with you pre
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
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.