News, guidelines and various community projects
Recently active
When working with tape environments, tape backup troubleshooting in Veeam is often more complex than it initially appears. Many professionals associate errors directly with faulty media. However, in real-world scenarios, issues often originate from hardware behavior, environmental conditions, or subtle physical problems.In this article, I will share real troubleshooting cases and, more importantly, explain the reasoning behind each analysis. The goal is to demonstrate how to identify the root cause instead of relying only on error messages. Case 1 – Mechanical obstruction during tape movementScenarioBackup jobs started failing during tape movement operations between slots and drives.Observed symptomsFailures during load and unload operations Errors affecting a specific range of slots Intermittent behavior that initially appeared randomExample error:Unexpected slider block, cartridge is not pushed far enough into the slot(ROB_SLIDER_UNEXPECTED_BLOCK_DURING_INSERT) TroubleshootingManual
PostgreSQL is a relational database management system (RDBMS) for storing and managing data. The default installations of Veeam Backup & Replication from v12 uses PostgreSQL. This is due to various reasons as described in the following articles: how to Migrate Veeam Configuration Database to PostgreSQL Server.Steps to move Veeam Configuration Database to PostgreSQL Server | Veeam Community Resource Hub Note: At the time of writing this guide, Veeam still recommended to use Microsoft SQL Server when you backup more than 5000 VMs. There are numerous reasons for upgrading the PostgreSQL Engine used by VBR? I will therefore refer you to the following release note. Determine the PostgreSQL version and BackupBefore proceeding, verify Veeam’s official support for the target PostgreSQL version (system requirements for the compatibility list). At the time of writing this article, Veeam currently supports “local or remote” installation of the following versions of PostgreSQL instance for the
I was planning to upgrade the PostgreSQL database from version 15 to version 17 in a Veeam Backup & Replication environment.Below are the steps I followed to complete the upgrade and restore the Veeam configuration.Steps performed1. Prepare the Veeam environment Upgraded Veeam Backup & Replication to the latest available build. Created a new Veeam configuration backup. Stopped all Veeam services using PowerShell: Get-Service Veeam* | Stop-Service -Force2. Back up the PostgreSQL databaseBefore making any changes, I backed up the PostgreSQL database using pgAdmin.3. Upgrade PostgreSQL Uninstalled PostgreSQL 15. Installed PostgreSQL 17. 4. Restore the Veeam configurationAfter installing PostgreSQL 17, I started the Veeam Backup & Replication Configuration Restore wizard.I selected the configuration backup created earlier and followed the restore wizard to restore the Veeam configuration.5. Start services and validate the environmentAfter completing the configuration rest
===============⚠️ Veeam compatibility note (read before upgrading)This article describes the upgrade procedure to HPE Morpheus VM Essentials 9.1.0. Its publication on the Veeam Community site does not mean Veeam supports this configuration. At the time of writing, Veeam Backup & Replication does not support Morpheus 9.1. Support is expected only after both Veeam Backup & Replication v13.2 and HPE Morpheus 9.1.2 are released and Veeam completes validation. If your environment is protected by Veeam, stay on a supported version and check the official Veeam compatibility documentation before upgrading. This post will be updated once support is confirmed.===============The release of Morpheus 9.1.0 marks one of the most significant updates in the platform’s history. While the release notes list nearly 80 new features and enhancements, the real story isn’t the number. It is how these innovations collectively strengthen virtualization, observability, storage, automation, and cloud-na
We recently upgraded a customer environment to Veeam Backup & Replication 13.1.1.18. The environment used a distributed repository architecture with a combination of Ubuntu Hardened Repositories and repositories deployed using Veeam Hardened Repository ISO v2.The VBR upgrade itself went smoothly, but upgrading the remote components and reconnecting to the repositories presented a few challenges. One of them turned out to be a DNS firewall rule that we had not initially considered.Here are some lessons learned from the upgrade.1. Preparation is keyBefore starting any Veeam Backup & Replication upgrade, I always verify that the configuration backup is available and usable.If something goes wrong during the installation and a full reinstall becomes necessary, having a verified configuration backup makes it much easier to restore the environment to its original state.During the installation, the setup wizard runs a configuration check to validate the existing environment and identi
EnvironmentVBR 13.1.1.18 (incl. patch 20260812), all-in-one backup server on Windows 11 Enterprise (build 26200) Upgraded 2026-10-13 with the full 13.1.1.18 ISO from 13.1 (I believe 13.1.0.411) Config DB on local SQL Express (VEEAMSQL2016). Veeam ONE 13.1 installed on the same machine (test only) Repositories in folders on a local iSCSI volume (Synology LUN) + Azure Blob immutable SymptomSince the upgrade, Rescan of the backup server fails: "Disks and volumes discovery failed Error: No connection could be made because the target machine actively refused it" "Microsoft Windows server discovery failed" (same error)Nothing listens on 6162 although VeeamTransportSvc shows "Running". Installer Service on 6160 works.What the logs show (Svc.VeeamTransport.log, identical in Svc.VeeamFilesysVssIntegration.log and Svc.VeeamNFS.log) Searching server certificate thumbprint in registry New thumbprint found in registry: <thumbprint> Certificates found: 1 Modifying export policy to
🚀 One of the most interesting enhancements in Veeam Data Platform 13.1 may also be one of the most strategic for the long term: Post-Quantum Cryptography.Version 13.1 introduces significant advancements across multiple areas, from support for new hypervisors and enhanced cyber resilience capabilities to improvements across the entire data protection platform.Among all these innovations, one aspect particularly caught my attention: cryptographic resilience.When discussing backup and recovery, we tend to focus on concepts such as immutability, ransomware protection, RPOs, and RTOs. These are all fundamental pillars of a modern data protection strategy.However, there is a less discussed challenge that organizations should start considering today: ensuring that data protected now remains secure years into the future.🔐 The scenario known as "Harvest Now, Decrypt Later" assumes that an attacker can collect encrypted data today and store it for years, waiting for future advances in computin
Status: 19.10.2026Note: Information and links you can find at the end of this postVersion: Veeam Enterprise Manager 12.3.2.4934Introduction:Recently I got an interesting service request from a colleague.It mentioned that in one environment, the job details in Veeam Enterprise Manager showed two different time stamps for the same event: one correct and one wrong.That sounds a little bit confusing at first, but let's get into detail.Problem:On the left side, the time from Veeam Enterprise Manager is shown. On the right side, the time from the Veeam Backup Server is shown.As you can see, there is a time offset of exactly nine hours between these two time stamps. The Veeam Backup Server shows the correct time. Both systems are located in the time zone Europe/Berlin. In general, this offset does not impact the functionality of the backup.Solution:The reason for this time discrepancy is the time zone setting of the PostgreSQL database, which was installed when Enterprise Manager was set up.
Something strange is happening in your infrastructure: Someone wants to enable SSH?Obtain temporary root access?Change security-critical settings without your knowledge? Who you gonna call? Ghostbus... uh, no: the Security Officer of course. With Veeam v13, this new role has been introduced for the Veeam Software Appliance and the Veeam Infrastructure Appliance. However, what may initially sound like the supreme ghost hunter—uh, I mean security chief — for the entire Veeam environment is often misunderstood. The Security Officer neither manages backup jobs nor automatically approves the deletion of backups. Its actual purpose is much more specific: It ensures that particularly critical changes to the appliance cannot be performed by a single person. The Security Officer approves or rejects requested actions. But when do you really need this role? What is the difference between the Security Officer, MFA, and Four-Eyes Authorization? And why is this role particularly relevant for VBR a
AI adoption, cyber risk, regulatory scrutiny, and data growth are changing how organizations protect and manage their information. We want to understand how these trends affect your business and which issues matter most to you. The Veeam Customer Pulse Survey 2026–2027 is an opportunity to share what your organization is experiencing and which issues you believe will have the greatest impact in the year ahead. Your responses will help inform future research, industry insights, and innovation priorities.
Hi everyone,I am currently encountering a recurring issue during our Oracle database backups using the Veeam Plug-in for Oracle RMAN. The backup job fails with the following sequence of errors
If your Veeam Backup files have been damaged due to storage media failure or malware activity, your first and best step is to contact Veeam Technical Support for assistance.I am a Data Recovery specialist and am not affiliated with Veeam. The following information is based on my personal experience recovering data from damaged backup files in a professional DR laboratory, specifically dealing with media failures and ransomware-induced corruption.Terminology used:Header: The first 4KB of the file. SSS0 / SSS1 (Snapshot Slots): Contain archive metadata (parameter groups, Metabank tables with addresses and sizes, and CRC for integrity verification). Metabank: Contains the metadata required to navigate the backup file.The metadata describing data block placement forms tree-like structures that build an abstract object map. This map is then associated with a map of physically stored blocks. This separation of maps is precisely what enables Veeam's deduplication mechanism.Q: The Header (firs
Hello Veeam Community and Product Team,As a Data Recovery specialist, I frequently deal with the aftermath of modern ransomware attacks that partially encrypt backup files, as well as severe storage media failures.To better protect our mutual customers, I would like to ask: is it appropriate to discuss the internal structure of Veeam Backup files in this community? Specifically, I am interested in proposing architectural improvements such as embedding additional recovery context directly into the data block headers. This would enable the extraction of all surviving data even in the event of a 100% metadata (Metabank/Snapshot Slot) loss.Could you clarify if such technical discussions and feature requests regarding file format resilience are welcome here? Or are discussions involving deep binary layout analysis or file structure forensics generally subject to moderation due to EULA restrictions?I am asking to ensure I follow the correct channels for sharing feedback that could genuinely
Happy Friday, Veeam Community! 💚This week’s Recap Show came with a little plot twist. 😄@Rick Vanover was back on the road, and after a few technical hiccups , he ended up flying solo for this episode! So grab a coffee, hit play, and catch up on what’s been happening around the community.Hope you enjoy the video and this week’s playlist!Featured Content via @allynz via @leduardoserrano via @KlausWitt Vanguard Blog Spotlight This week we are pleased to feature @mhmdadl with this post A Practical Look at Kasten K10 SecuritySpecial Department Newsvia @Stephen Seagrave via @Jonty and @GerhardGibbs via @Madi.Cristil Who's New Thank you @safiya for prepping this week’s Who’s New! We are pleased to welcome +95 new members. The coolest usernames are @mdub , @Steve in the bogs , @veeam_operator and @AlexTheTechGuy ! Alfred’s pick is @MrDanTheMan → You have a badge coming your way. Have a great weekend everyone!
Hey everyone, I’m Klaus, a Technical Account Manager at Veeam in Germany.A big part of my role is working strategically with customers around data protection, resilience, and recovery. Disaster recovery concepts are an important part of that work – especially when it comes to understanding which workloads really matter, how they depend on each other, and what needs to come back first when things go wrong. Over time, I noticed that many of these discussions and workshops tend to start in a very similar way: the customer provides an RVTools export, we open a spreadsheet, and sooner or later we end up discussing which VM is actually “critical”. That sounds simple at first, but it rarely is. The final result often lives in that spreadsheet, while a lot of the context behind it does not. Dependencies are difficult to represent properly, assumptions remain in people’s heads, and six months later it can be surprisingly hard to understand why a system ended up in “Gold”, which workloads it dep
Hello Veeam Community and R&D team,As a Data Recovery engineer, I regularly encounter cases of VBK/VIB/VRB archive corruption due to storage failures or ransomware attacks.When dealing with partially encrypted files or read errors, native Veeam tools often simply throw an error and abort, without attempting to extract any surviving data. To address this, I began reverse-engineering the binary structure of Veeam files and am developing custom software for their recovery.During this process, I identified the following key structural groups:Header SnapShotSlot 0 and SnapShotSlot 1 (SSS0, SSS1) Metabanks + DataBlocksThe Header contains basic info and is easy to recover. The SnapShotSlot contains critical data required to begin parsing Metabanks. This block can also be reconstructed, but only after successfully analyzing the Metabanks themselves. Next comes the Metabank table (CRC32, file offset, size). Its loss is fatal, as without it, a parser has no knowledge of the physical location
Happy Friday everyone! 😊@Rick Vanover is still collecting airline miles 😉, but we're back with another catch-up and a few stories worth talking about. This time we're looking at VDC + Grafana monitoring, why one company decided Azure wasn't the cheapest answer after all, and how Veeam 13.1 helped protect nearly 48 TiB of Oracle 10g data.Grab a coffee and spend a few minutes with us ! Featured Content via @Greg.L via @Lars Kristoffersen via @TidusandYuna Vanguard Blog SpotlightThis week we are pleased to feature @Othon Oliveira with this post Workload Mobility and Multi-Hypervisor Support with Veeam Data Platform v13.1Special Department Newsvia @brendan.haglund via @Vpaulcb via @HangTen416 and @Chris.Childerhose via @Tomasz.Magda and @Pawel via @Marcel.K via @Madi.Cristil
please dear Veeam support team, can you confirm if it is currently possible to replicate HPE VM Essentials Morpheus environments with Veeam
hi,i have downgraded to vbr 13.0.3.63 after trying to upgrade to 13.1.x using vbr vm snapshot. i have vbr console installed on jump server and i am using veeam vsa appliance. after the revert, i have also downloaded console from vbr vsa which i am trying to connect but sign in button is unresponsive,i have found som related logs on remote server related to console and launcher<Util.ClientLauncher.log>[22.07.2026 10:33:32] <01> Info Connection was cancelled.[22.07.2026 10:33:32] <06> Error Cannot access a disposed object.[22.07.2026 10:33:32] <06> Error Object name: 'System.Net.HttpListener'.[22.07.2026 10:33:32] <06> Error (System.ObjectDisposedException)[22.07.2026 10:33:32] <06> Error at System.Net.HttpListener.Stop()[22.07.2026 10:33:32] <06> Error at Veeam.Backup.Identity.Client.LoopbackHttpListener.Dispose()[22.07.2026 10:33:32] <06> Error at Veeam.Backup.Identity.Client.AuthorizationCodeFlowExecutor
In this demo I have MCP for Fusion, Everpure Fusion fleets, MCP for vCenter, and MCP for Veeam software as the data protection layer. And I'm gonna walk through a simple scenario on how you can tie these three things together to simulate a recovery action. So let's say [I] work on the help desk or somewhere like that, or in the data protection space, and I get a call, and it's from the app team, and they say that this VM, so called test-vm01, data got corrupted. So you'll notice I just asked where the VM is. I didn't say, "Hey, look on this array. Check in Veeam." I just say, "I got a VM." And it's going to go out there, locate where that VM lives, correlate that with the data protection space, and then tell me my options, just as I asked.So it hasn't done anything yet. It's asking me things to check, right? Hey, do you need files? Do you need a database, right? What type of recovery do you need? Is it the whole VM you're gonna roll back, right? Is the VM still on?I am confronted with
other possible Topic-name: When a PostgreSQL Shows Up That Isn't Yours - A field report on a new AAP warning after the upgrade to 13.1 — including the workaround Veeam Support cleared me to publish. The symptomAfter upgrading a customers environment (doesn’t matter if VBR on Windows or VSA) to 13.1, a previously clean job started completing with a warning: a VM backup of (in this example) an Exchange server with Application-Aware Processing (AAP) enabled. Exchange processing itself was fine. The warning referred to a PostgreSQL instance that isn't really in access of the customer: an embedded component of (in this case) Trellix/McAfee Email Security running on the same guest OS.The customer told me: Vendor-managed, no credentials, no supported way to administer it.So Veeam can't authenticate against it — and flags that with a warning. The same job ran clean on the previous version. What changedSupport's original answer was (and i have the confirmation to do this post about it): With
Veeam 13.1 can back up OpenShift Virtualization VMs from the console your team already uses, without an agent in the guest. Here's the architecture in one diagram: five components, two of them new, and the five steps a backup job takes across them. ComponentsVBR Server — the one giving ordersWhat it is: your existing Veeam Backup & Replication machine, physical or virtual. Job description: holds the configuration, schedules jobs, allocates resources, and coordinates every backup and restore. It also doubles as a general-purpose backup proxy, so it can move data to and from repositories on its own. Where it sits in the diagram: top-left, feeding the plug-in. Mental model: the control tower. It decides what and when; it does not read VM disks.Veeam Plug-in for KubeVirt — the translatorWhat it is: the integration layer between VBR and everything OpenShift Virtualization. Job description: lets the backup server connect to an OpenShift Virtualization cluster and run data protection and
Managing user access through Microsoft Entra ID has become a standard requirement in many environments. With Veeam ONE 13.1, it is now possible to integrate SAML-based authentication and use Entra ID or any other SAML IDP as an external Identity Provider. This step-by-step guide shows the process on how to add Entra ID as an IDP in VeeamOne 13.1. First, we need to create an enterprise application in Entra IDNavigate to https://entra.microsoft.com/ --> Enterprise applications and add a new application Select "create your own application" and specify a name, I chose "VeeamOne SAML" Specify SAML as the single-sign on method Now switch to VeeamOne and go to configuration --> access management and add an identity provider In the Identity Provider Settings: Display name: specify some name for your IDPIDP URL: copy the "App Federation Metadata Url"Entity ID: copy the "Microsoft Entra Identifier" In the Veeam ONE Settings, you need to specify a Client ID, for example "VeeamOne"The S
Hello everyone,I updated a VBR console to v13, but after the update, I was unable to connect to the console and received the following message:“Failed to connect to the backup server: Access to the registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Plugins’ is denied”I noticed that when I launch the console using “Run as administrator,” I can access it without any issues. I checked the Registry Editor, and the permissions are correct.What’s surprising is that I haven’t encountered this error with other customers who have upgraded to v13.I don’t know how to resolve this issue. Do you have any ideas, or have you also experienced this problem?Thanks in advance Bonjour tout le monde,J'ai passé une console VBR en v13, cependant après cette mise à jour je ne parvenais plus à me connecter à la console avec le message suivant:"Failed to connect to the backup server: Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Plugins' is
There are so many data-breach incidents reported by news media day after day in Japan. Ransomware incidents seem to be increasing as well, although we do not hear about them as often as data-breach incidents. Maybe they have become so common and no longer considered newsworthy.Having said that, there was a new incident just reported on October 7th and it appears to be a special case. The first report was about Ibaraki Prefecture municipal office and municipal police websites closure due to IDCF Cloud service outage. The IDCF Cloud is run by Softbank subsidiary IDC Frontier, which then announced that a part of their system was compromised. Later, more details were announced that IDCF Cloud’s East Japan Region 1 was down due to a ransomware attack, which impacted 495 organizations throughout Japan.According to public information on the IDC Frontier website, IDCF Cloud service’s East Japan Region 1 uses VMware ESXi / vCenter, suggesting the ransomware targeted that specific deployment, th
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.