News, guidelines and various community projects
Recently active
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?
I am driving the recap solo as @Madi.Cristil is activating several matters for some VeeamON Tour and ancillary events. We have a full docket of content this week, you can watch the episode here:Featured Contentvia @Andreas Buhlmann via @Chris.Childerhose via @MarvinMichalski Vanguard Blog Spotlight - Petr BouškaThis week’s Vanguard blog spotlight comes from @Samuraj - with this post Veeam Backup & Replication - Replication Job | SAMURAJ-cz.com → Love doing more around Replication! Special Department Newsvia @NikolaPejkova Be sure to check the Events page on the Community Hub: Events | Veeam Community Resource HubI really liked this blog from the Securiti AI team: When the Cloud Goes Dark: How Securiti and Veeam Helped Customers Maintain Continuity After the recent AWS UAE Outage - SecuritiWho’s NewWe are happy to welcome +222 new members this week to the Veeam Community. The coolest names are @Yemi, @cybertanks, @AnotherRandomTech and @Wim VD. Alfred’s pick is @StevePa
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
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
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:
Hello,A client have a Quantum LTO server connected by DAS cable to a Windows Server that host Veeam Backup Server. Is it possible in this case to migrate VBveeam Backup Server to a VM and keep access to the tape server ?
Hello awesome community! A huge thank you to everyone who participated, shared their votes, and helped make this challenge a success!As promised, the three most-voted articles will each receive a surprise prize. We’ll be reaching out to the winners directly with details on how to claim their prize.And now, the moment we’ve been waiting for…Congratulations to our winners! @lucasmagnum @matheusgiovanini @wolff.mateus Your contributions clearly resonated with the community — well deserved!Thank you again to everyone who took part. Keep sharing, keep contributing, and keep making the Veeam Community awesome! 💚
We have a scenario where the customer has a Tape Library currently connected to Bacula. Due to an issue with Bacula, they are carrying out a reconstruction or recovery process of the existing backups, which they intend to run from Monday to Friday.At the same time, the customer wants to incorporate Veeam Backup & Replication to perform Backup to Tape jobs during the weekends, using the same Tape Library.The question is to determine how feasible and advisable this approach is, considering that both applications would use the same library at different times, and what considerations or limitations should be taken into account to avoid conflicts in the access and control of the tape drives and media.
Hi, I’m having trouble implementing an immutable repository using Red Hat 10 with Veeam version 12.3.2. I installed it a few days ago and it was working fine, but today the Veeam server was shut down to fix an issue with an HBA card. Upon restarting, the machine failed to reconnect to the immutable repository, throwing errors such as: "Unexpected socket shutdown, Failed to rescan repository (...) Error Unexpected socket shutdown, host discovery failed," as well as warnings like: "Refresh linux host failed error: Unexpected socket shutdown, failed to rescan repository (...) Unexpected socket shutdown." I’ve run a number of tests: changing the user password to match what is configured in Veeam, disabling the Red Hat firewall, testing connections on ports 6160 and 6162 in both directions, and re-enabling port 22—yet nothing works. Oh, I almost forgot this warning that appears when rescanning the Linux host: "Unable to collect hardware info: Unexpected socket shutdown." It’s really frustra
Often when looking at Best Practices guides, software documentation, or even during education, I see and hear the answer “It depends.” This is probably my least favorite answer, as someone who likes to understand why something is right or wrong. While it does “depend,” it makes it very tough for people starting out to understand the “why” in many cases. One thing that is not going to be the same for every Veeam user is how the jobs are created. Over the years, Veeam has made some fantastic changes and for most environments, Per-Machine backups are the way to go, the minimal savings you get do not compare to the performance and portability of this mode. Additionally, with this mode you can often add a HUGE amount of VM’s to a job and just forget about it. I know of people who have 1 job. That is the definition of an easy button!Today I want to discuss some reasons that myself and others have gone the other direction to separate jobs. While I keep my jobs as large as I can for the perf
'Why Now' initiative around 13.1 Every time a new version of Veeam is released, the same question comes up:Do I really need to upgrade right now?It’s a fair question.If backups are running, jobs are completing successfully, and restores work, it can be difficult to justify changing an environment that seems to be doing exactly what it was built to do.But I think Veeam Data Platform 13.1 changes that conversation.After spending time working with Veeam 13.1 in the lab, I don't look at this release as simply another collection of new features. The bigger story is how Veeam continues to move from traditional backup and recovery toward a much broader cyber resilience platform.Customers today aren't just asking:“Did my backup complete successfully?”They're asking:“If we're hit with ransomware tonight, how quickly can we recover?”“How do I know the restore point I'm using is clean?”“What happens if Active Directory is compromised?”“Are my backup repositories protected from the attack?”“Have w
It would be nice if you could also upgrade a Cloud Connect server from the Service Provider Console.
I have veeam backup server running in primary site with vcenter integration and backup scheduled and running. Now, I am creating another veeam backup server in DR site, and I want to the same vcenter and esxi to be integrate with DR site veeam backup server. kindly clarify the above approach is correct
Well, another week and another blog as we are at #9 of 10 today. This blog focuses on Universal CDP and its fitment in to v13. Check out the link below and the blog.Universal CDP in v13: Where It Fits Universal CDP in v13: Where It Fits Introduction Continuous data protection gets attention because it promises extremely tight recovery points, but that does not mean it belongs everywhere. Universal CDP in Veeam v13 should be evaluated as a targeted design choice for workloads where small amounts of data loss carry outsized business impact.That framing is important in production. CDP is not a replacement for every backup or replication workflow. It is an additional protection method that changes how teams think about network paths, storage performance, and the operational meaning of recovery success. Match CDP to Real Recovery Needs The strongest CDP use cases are the ones where recovery point objectives are already difficult to meet with conventional periodic jobs. Systems with freque
Greetings. On a Veeam 12.3 install, whether there be an NFS or SBM datastore, and even while trying to hold the [CTRL] key and right-clicking on any datastore, the “Access Permissions...” menu does not show up, nor is there a ribbon icon visible for “Set Access Permissions” option.The logged in user into Veeam is a Veeam Backup Administrator. This option is visible on any other Veeam servers tested.What would be the cause for this effect? Thanks in advance.
Recently, I was involved in a production support case where a Veeam software appliance deployed on physical hardware failed to boot after an unexpected power interruption.The system dropped directly into:“You are in emergency mode. Cannot open access to console, the root account is locked.”At this point, many administrators assume the appliance is corrupted or that Veeam needs to be reinstalled. In this case, the backup administrator had already reinstalled VBR once, and the issue happened again. This is not a Veeam software issue. The problem occurs at the Linux storage layer, specifically with LVM and XFS.The Veeam appliance is built on LVM logical volumes formatted with XFS. During boot, Linux must detect storage, activate LVM volume groups, and mount all filesystems defined in /etc/fstab before any services start.If any of these steps fail, the system enters emergency mode to protect itself. This is a safety mechanism, not a catastrophic failure.Understanding this boot sequence ma
Unprotected DB from the primary node in SQL AG. Other DBs are being backed up successfully on the same primary server.Configured to run transactional logging periodically but one large DB shows as unprotected. The problem started when the old primary node was switched over to a new server and evicted. After the eviction, it started not backing up the DB(error: Transaction logs from some databases were not backed up for the last 8 intervals).Ran image level backup (the parent job), this was successful but transaction logging still not working. However, the error now shows as (error: SQL Server transaction log backup took longer than desired log backup intervalFailed to upload SQL Server transaction log backup for DB to LogShip server: Repository agent is stoppedSQL Server transaction log backup could not be completed within 10 RPO intervals and will not be retried)This was working before and no changes to any of the Veeam servers so this error is not accurate. Confirmed application-awar
Hi everyone,Another week, another little project. 😀I’ve been spending some of my spare time practicing and experimenting with Codex again, and last weekend’s result is AgentBridge. The idea came from something that has bothered me for a while when working with Veeam Agent management in v13 VSA:VBR does a great job managing Agents once a machine is under management — but starting from V13, onboarding Windows machines in non-domain environments is no longer as straightforward as simply pushing via username and password. Linux certification also require SSH-based preparation and manual steps before they can be added cleanly.For one or two machines, that’s fine. But once you start dealing with more hosts, it quickly becomes painful.So I built AgentBridge.It’s a small open-source tool focused specifically on that initial bootstrap and enrollment process.You run AgentBridge as a single application on Windows, Linux, or macOS, open its local Web UI, connect it to your VBR 13.1 server, and us
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.