Community

Hi,I created a full system backup with veeam agent for windows on a dell laptop with Win 11 installed. I boot from Veeam recovery media to a new laptop, select the backup from external usb drive, select bare metal recovery and whatever i do (Entire, volume, manual) i receive the same error message: Restore failed: The stub received bad data

We recently had a customer environment running Veeam Backup & Replication (VBR) 12 on a Windows server that was approaching end-of-life. The existing setup also included a local Windows repository for short-term retention and an HPE StoreOnce repository used for long-term retention.With both the VBR server and the StoreOnce platform approaching their lifecycle limits, we needed to plan a migration that would:Replace the aging VBR server Maintain the existing Veeam configuration and backup jobs Preserve all existing backup data Replace the legacy short-term repository Move the long-term backup data away from StoreOnce Improve the security posture with immutable backup storage Continue using the customer's existing socket-based Veeam licensingThe goal was not simply to build a new Veeam server, but to move the customer to a more modern and secure backup platform without losing access to the existing backup history. The Existing EnvironmentThe starting point consisted of:Veeam Backup

Welcome to My First Technical Blog PostOver the past several years, I have had the opportunity to work with a wide range of Veeam technologies, including Veeam Backup & Replication, Veeam Backup for Microsoft 365, Veeam ONE, and the Veeam Service Provider Console (VSPC). Throughout these projects, I repeatedly encountered features that are incredibly powerful, yet often overlooked in day-to-day operations.One such feature is API Proxying via Veeam Service Provider Console (VSPC).In this article, I would like to share practical experience, technical insights, and real-world use cases around this capability. My goal is to demonstrate how service providers can simplify automation, reduce complexity, and leverage existing infrastructure more efficiently.If you have worked with VSPC API Proxying yourself, I would be happy to exchange ideas and experiences.Let's dive in! 👉What is VSPC API Proxying?Most Veeam users know the Veeam Service Provider Console as a centralized management platf

I am in need of some assistance from the community with Veeam Backup & Replication. I upgraded the server to 13.0.1.2067. No errors were thrown during the upgrade, logs don’t show any red flags that stick out; however the service hangs when attempting to access the localhost database server.Here is what I see:When the Veeam console is run, the “Specify backup server” page appears:After the localhost database is selected, the next window appears: The console goes no further than this, and the system doesn’t show any signs of activity. All services show as running on the server:I also tried updating .NET 8 dependencies to newer versions in case these were what may be causing the issue, but there was no change in results. I have attempted to upgrade this application twice with little success. As of now, I may need to revert back to the older version and try again, which may lead me back to here.Has anyone else encountered this when upgrading to 13.0.1.2067? If so, how was it remediate

This week we are on to blog #8 in my v13 series.  Check out the link below on my blog site and the blog article.Blog - v13 HA in One Lab Session v13 HA in One Lab Session Introduction High availability only matters when something fails. In a backup platform, that means the design should preserve management access and backup service continuity well enough that the environment remains useful during a component outage.Veeam v13 places new attention on HA as part of broader platform resilience. For production teams, a short lab session should focus on one practical question: when a node or service becomes unavailable, what keeps working, what pauses, and what dependencies become the real bottleneck? Identify the Dependency Chain Before any failover test begins, the environment should be mapped in simple terms. Storage, identity, networking, DNS, certificates, and any shared services all influence whether the backup platform is truly resilient or just appears redundant on a diagram.This is

So it's very simple, our backup server (infrastructure appliance) had a proxy server configured for access to Internet (in order to fetch updates etc.)Everything good in 13.0.In 13.1 it seems to be trying to use internet proxy to connect to anything http(s), even “localhost”. Goes without saying that Backup server doesn't even properly start (system services can't connect to local identity service bc that sends them to internet proxy).After defining proxy exceptions for localhost etc., connections to data movers still fail, again because those connections attempt to go through internet proxy.Case is open with support. Reverted to 13.0. Careful!

If you’ve ever had to deal with the pain that comes after deploying the Veeam Virtual Appliance (VSA) v13 with the following error message as discussed in the KB4648. Then I have got you covered.As you can see, below is the error message (Authentication failed). You will get when you use the “veeamso” or the “veeamadmin” account to login In this guide, I have detailed the steps to Fix Authentication failed: Invalid credential after installing VSA. The fix requires downloading a small Linux Live ISO such as the Ubuntu Live Server or Debian Live from this link. You could also use the ISO with the generic image with (Unabhängig davon, welche ISO verwendet wurde).download,, upload and attach as CD/DVD. To fix this, boot from a Linux live ISO and mount the Veeam appliance disk to access and edit the /etc/sssd/sssd.conf file. To proceed, hit the Enter button on your keyboard.Feel free to have the right settings that works for your environment entered. You can see the image below for similar

Hey everyone! 🎉I know many of you have been waiting for this, and I am really happy to finally share with the Veeam Community that VMCE+ is officially live Woo-hoo!!! 🎉 🎉 🎉VMCE+ is the first certification aligned to v13 and a real step up from VMCE. It goes beyond backup and recovery fundamentals to validate advanced skills across the full Veeam Data Platform. If you have been working with Veeam at an advanced level, this one is built for you.What you need to get certifiedTo earn VMCE+, you complete three trainings:Veeam Backup & Replication: Configure, Manage, and Recover (VBR) Veeam Data Platform: Monitor, Manage, Analyze (Veeam ONE) Veeam Data Platform: Scale, Automate, Secure (Veeam Orchestrator)The courses are available through the Veeam University PRO eLearning subscription, with instructor-led options available only for the Backup & Replication course. There may be an option to have the Veeam ONE and Veeam Orchestrator training instructor-led as well, but there is st

We are reviewing our Veeam Backup for Microsoft Azure design to optimise Azure storage costs while maintaining best practices. Currently, our Azure VM backups are stored in GRS storage accounts, with daily backups (31-day retention), monthly backups, yearly backups in a separate GRS repository, and hourly snapshots. We also have a 125TB Veeam Data Vault subscription and use Backup Copy Jobs to maintain an immutable offsite copy of all backups. Given that we already have a secondary immutable copy in Veeam Data Vault, we are questioning whether GRS is still providing sufficient additional value to justify the extra cost compared to LRS.We are considering creating new LRS-based repositories and directing future backups there while leaving existing backups in the current GRS repositories until they age out naturally. Is this the recommended approach, and would restores continue to work from the existing GRS repositories during the transition? Also, if we retain GRS, can someone explain th

Hi everyone, During the execution of a backup in Veeam Backup & Replication version 13.0.1.29 , integrated with Prism Central  pc.2024.3.1.14 the snapshot creates a recovery point, and this recovery point has a retention period of 60 days.I cannot find where this 60-day retention period is configured. I checked the backup job, but I cannot find any information or setting related to this retention.  where this retention is configured? does anybody know?  

Hey all,Back from a bit of a blogging hiatus to remind people of two things:That Entra ID got new capabilities in v13 & v13.1 That you have to reauthorise the application to enable them.It’s a really simple process, so I thought I’d just quickly show everyone how it’s done!Alt Text: Screenshot of the inventory view within VBR, selecting my Entra ID Organisation.Step 1: Within the Veeam Backup & Replication Console, go to Inventory, and then ‘Microsoft Entra ID’. Select your organisation, then choose Edit Tenant.Alt Text: View of the protected object types, with the new object types missing.Step 2: Proceed to the ‘Protection Scope’ section, you’ll see here every ‘Essential’ type of object protected (as the type name suggests, these cannot be removed). You may also see some ‘Optional’ type of objects protected here. This depends on which VBR version you onboarded your tenant, and whether you’ve remembered/known to do this in the past.Alt Text: Showing the menu presenting the obje

This article is intentionally for one specific scenario: upgrading an existing Windows-based Veeam Backup & Replication installation from v12.x to v13—including the issues that can come up in real-world upgrades.I already wrote a general blog post about patches/upgrades that serves as a guideline for practically all Veeam updates (pre-checks, order of operations, typical pitfalls, rollback strategy, change window, etc.). That guidance is still fully valid.   What about the VSA (Veeam Software/Server Appliance)?If you can/want to move directly to the VSA, the best approach is usually a greenfield installation: deploy a new VSA and rebuild your jobs step by step according to current best practices. This is not only the cleanest migration path, but also a great opportunity to remove legacy baggage and review/update your configuration in detail — aligned with best practices and your specific use cases.There is also a migration path from Windows (e.g., 12.3) to VSA 13.0.1, but it comes

When I first heard of the new Application Backup Repository that was just released in 13.1, my mind was full of ideas! I firstly documented what the Application Backup Repository (ABR) was and how to get up and running. https://vzilla.co.uk/vzilla-blog/the-veeam-application-backup-repository-13-1One of the first use cases, was based on us being asked by the Homelab community about Proxmox LXC container backup, we have accelerated how we protect and recovery Proxmox VMs but the business requests for LXC has been mild, so I thought how could we use this new feature to help. https://vzilla.co.uk/vzilla-blog/veeam-application-backup-repository-proxmox-lxcThe other idea I had was a much bigger problem to solve, Veeam have been great at protecting databases over the years, we have enterprise plug ins for most of the common databases we see across your estates as well as the public cloud managed databases and services. But what about all those others…. What about databases running in containe

Hi, We are thrilled to announce the general availability of AsBuiltReport.Veeam.VBR 1.0.0 — a comprehensive PowerShell module that generates professional as-built documentation reports for Veeam Backup & Replication (VBR) infrastructure. What is AsBuiltReport.Veeam.VBR?AsBuiltReport.Veeam.VBR is a specialized report generator that plugs into the AsBuiltReport framework to automatically document your VBR environment. It produces multi-format reports (HTML, Word, Text) that capture the complete state of your backup infrastructure—from backup jobs and repositories to proxies, tape libraries integration, cloud gateways, and more. Key FeaturesReport Sections — Comprehensive coverage of all VBR components including backup repositories, jobs, proxies, WAN accelerators, tape integration, and cloud connectivity Diagram Types — Visual representations of your infrastructure, including backup-to-repository flows, proxy routing, and tape library topology Flexible InfoLevel Configuration — Contr

One of the things I enjoy about designing Veeam environments is that the best architecture on paper is not always the best architecture for the people who have to operate it every day.This project was a smaller Veeam Backup & Replication v13 environment. The system administrators were very comfortable with Windows Server. Linux was another story. They had limited Linux experience and were hesitant to own a Linux-based system after implementation.That became part of the architecture decision. We could have introduced Linux simply because it gives us attractive security options, but doing that would also introduce another operating system the team would need to patch, monitor, troubleshoot, and secure. In a larger organization with dedicated Linux resources, that conversation is different. Here, operational capability mattered.So the question became: how secure can we make a Windows-based Veeam v13 deployment while keeping it manageable for the administrators who will own it?Figure 1

Hi everyone,I’m testing the Malware Detection capabilities in Veeam Backup & Replication v12.1 (or latest) and wanted to check if this behavior is expected.Here is what I did step-by-step: Enabled Inline Entropy Analysis under the main menu's Malware Detection settings. Placed .onion links and ransomware notes inside a test VM. Enabled the Malware Detection option within the Backup Job settings as well. Executed the Backup Job. The job completed successfully without throwing any warnings, alerts, or failures.However, when I ran a SureBackup job on the same VM, it successfully flagged and detected both the onion links and the ransomware notes.Is Inline Entropy Analysis intended to catch file-based artifacts like text notes during the live backup process, or is deep artifact/file scanning primarily deferred to SureBackup/YARA scans?Any insights on how these two detection layers interact would be appreciated!Veeam version: 13.1

We manage several VBR deployments through Chef using the Veeam powershell module. In testing Veeam 13, we can’t seem to add groups with the Add-VBRUserRoleAssignment command in powershell. Veeam 12 works fine and in Veeam 13 adding local and domain users works fine, just no local or domain groups. We can add the groups manually through the Veeam BnR console just not with the powershell command. We are currently testing on Version 13.0.1.2067 however the previous versions of 13 seem to have the same problem. Has anyone else experienced this issue? 

I'm doing a full VM restore in Veeam to an HPE VM Essentials host, and I want to understand how the disk provisioning gets decided. Is there a way to force the restored disks to come back as thin-provisioned, or does Veeam just inherit whatever the target VME datastore or storage policy dictates?Trying to work out whether I have any control over this at restore time or if it's entirely determined by the destination.

I took advantage of my holidays to step away from screens for a while. Unfortunately, the contest has now come to an end but I still wanted to share my experience with the community.So, what will you find in my toolbox? Well, before answering that, I think it's essential to cover a few other points first because being ready for a disaster is about more than just technology. Experience Is Your Best AllyI fully agree with what others have already mentioned: experience is your ally. The more you dig into topics and use your tools on a regular basis, the more comfortable you become and the day a problem hits, you'll be far more confident in how you approach it.Take the different restore options Veeam provides as an example: it is absolutely essential to test each of them so you understand *when* to use them. Knowing how and when to leverage Instant Recovery, for instance, can save you precious minutes when every second counts.You Need a Big-Picture View of the InfrastructureYou need a holi

1. Our environment:Veeam Backup & Replication (Advanced edition), HPE MSL3040 tape library, LTO-9 SAS HH drives, Windows Server 2025. Source data lives on a NAS file share (accessed via SMB/NFS). Processed data gets written to tape via a File to Tape job.2. Our requirement — tape verification:We need our verification to cover two layers:Read-after-write — checking tape parity and block integrity as blocks are written by the tape drive head, to ensure physical tape sectors have no write errors.Content integrity — after writing, reading back the raw file structures from tape, generating a cryptographic MD5 checksum of that data, and matching it against the original source file's MD5 to confirm the two are identical.Ideally this would be something we can run as part of an automated job rather than a manual step.3. Why this matters:Once a file is archived to tape, the source copy gets deleted from the NAS share to reclaim space. That means tape becomes the only copy — there's no going

The Application Backup RepositoryVeeam Backup & Replication v13.1 introduced the Application Backup Repository (ABR). It runs on the Veeam Infrastructure Appliance in Hardened Repository mode and turns local storage into a pool of virtual volumes, each one exposed as its own NFS target.The interesting part is what the writing side has to know: nothing. An application, a script, or a device simply writes to an NFS share. Veeam takes care of snapshots, immutability, and access control underneath.No agent, no plug-in, no awareness of Veeam at all.  That makes ABR a good home for everything that never fitted into a backup job. Which brings us to how you should lay it out.One Repository Per SourceIt is tempting to create one big ABR and point everything at it. Do not. Permissions and the snapshot schedule are configured per repository. That makes the repository your boundary for who may write, for who may read, and for how long data is kept. A single shared repository means one set of N

Hello everyone!This is my first contribution to the Veeam Community Hub!In the long term, I plan to start my own blog to share my thoughts and technical perspectives from my daily work, but while it is in the making, let's move on with my thoughts on the topic „how to structure jobs.“This post will cover Veeam Backup & Replication in the first place, but in the future I will also cover Veeam Microsoft 365.In my daily work, I have seen a lot of variations, like “naming schemes“ (please imagine this in very large quotation marks), like "Backup Job 1“ or „Server Backup x with Database.“Basically naming jobs like this, of course, works, but in the daily work you have to search for what this job is exactly, and when the description is the default one, you don't know anything.To prevent this situation, and because I really like to organize things:)Over time, I have developed a specific naming scheme for jobs in Veeam Backup and Replication, such as Backup to Disk or Backup Copy Jobs.This

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!