Community

With my colleague ​@zzsoka  we have developed a procedure the inject needed variables for initial configuration of the Veeam appliances and now we would like to share it with you. When you deploy Linux appliances at scale, cloud‑init is usually the go‑to mechanism for injecting instance‑specific configuration (IP, hostname, NTP, credentials, etc.) at boot time. However, the Veeam Software Appliance used here does not ship with cloud‑init currently, so we need another way to achieve the same result: build one customized ISO and then let vSphere guest variables drive per‑VM configuration.This post walks through how I achieved that using:- a customized Kickstart file,- a customized GRUB configuration,- VMware guestinfo / OVF properties as the source of truth for variables, and- a small shell script that dynamically extracts and uses `vmware-rpctool` (even though open‑vm‑tools is not installed in the installer environment), cleans up after itself, and hands configuration over to the post‑i

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

 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

Additional Details: Issue Description: Our offsite Azure Blob backup job is failing with a REST API 409 Conflict: SnapshotsPresent error when Veeam attempts to delete or clear the metadata lock files located in the .../Metadata/Lock/create.checkpoint/ directory. Steps Performed Before Opening Case & Why: 1. Disabled Azure Blob Soft Delete (In Azure Portal): Disabled Blob and Container Soft Delete and permanent delete for soft deleted items to stop a 7-day duplicate billing loop caused by Azure trapping Veeam's deleted files at premium rates. 2. Enabled Cool Tier Option (In Veeam 12 Console): Edited our repository properties in the Veeam 12 app and checked the box "Use cool blob storage tier" to migrate our data footprint from the premium Hot tier to the cheaper Cool tier, aimed at lowering our permanent monthly storage bill. 3. Inspected Blobs via Azure Portal: Navigated directly to the target metadata folder (try, lock, and declare blobs) to check for active snapshots. The Azure U

SummaryAfter upgrading VBR on Windows from 13.0.1.180 to 13.1.1.18, Veeam Explorer for Microsoft Active Directory can no longer browse AD content from a backup. The same file opens correctly in 13.0.1.x Explorers.Symptoms (13.1.1.18)- The database loads and the object count is correct, but the domain tree collapses within about a second.- With "Advanced Features" enabled, the tree shows only six identical "Integrated DNS" nodes. No Users and Computers, GPOs or Configuration partition.- An LDAP search (&(objectCategory=person)(objectClass=user)) returns no results.Test material- A Windows Server 2022 DC, backed up as a Proxmox VM. I extracted the Windows\NTDS folder from the backup.- esentutl /mh reports Clean Shutdown, Log Required 0-0, with a valid checksum.- The same file mounts with dsamain and is fully readable in ADUC (localhost:10389).What I tested1. Same VBR server VM, restored on a separate host from a backup taken the day before the upgrade (Explorer build 13.0.1.180): 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

 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-native operations across a unified platformMuch of the innovation focuses on improving the virtualization experience for VM Essentials customers. From Host Profiles and advanced migration capabilities to intelligent storage management, GPU virtualization, virtual switching, monitoring, and operational automation, this release delivers meaningful improvements for organizations running business-critical virtualized workloads.Therefore, it´s time to upgrade your HPE Morpheus VM Essentials Manager and the Host Agents.This procedure is aimed at customers using release 9.0.0 or later. If you are using 8.x or earlier, you must first reach 9.0.x, because 9.0.0 is the minimum require

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

SAML single sign-on in Veeam Backup & Replication v13 lets your identity provider handle authentication while Veeam keeps control of authorization. Users sign in with their corporate identity, MFA and Conditional Access policies apply upstream, and Veeam stops being one more place that stores passwords.The setup is simple. The part that trips people up is group mapping, and it comes down to which Microsoft Entra ID license you have.The mental modelKeep this sequence in mind for both setup and troubleshooting:Trust. Veeam trusts Entra ID as the identity provider through exchanged SAML metadata and the signing certificate. Assertion. After the user authenticates, Entra ID sends a signed SAML assertion containing claims about that user. Identity mapping. Veeam matches a claim (the user's UPN or a group claim) to a user or group in Users & Roles. Authorization. Veeam applies the role assigned to that user or group.Entra ID proves who the user is. Veeam decides what they can do.Step

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 

veeam 13 agent not available for wndows 10 32 bit workstation. 

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

Hello, Thanks for the great forum.Lets’ say I have a laptop running VAgent community edition, standalone.On that agent, I create a standalone full backup onto a usb key.The laptop has NOT been connected to my Community Backup and Replication Server.Now, I want to take that standalone full backup from the usb key, plug it into my Veeam Backup and Replication Server and do an instant restore of that full backup.Is that possible.If so, all I need to do is do the import and then do the instant restore?Is there more steps involved?I could not find the answer in Importing Veeam Agent BackupsRestoring Veeam Agent Backup to Hyper-V VMThanks Much, David

Hi,i am using Community Edition of Backup and Replication.  In special i have been using a script to start Veeam ZIP to get a standalone full Backup. This has been working flawless for quite a while.There has been Issues with Powershell in the past, so i have to start the batch explizit with the “new” powershell version. But this was about a year ago.So i got a running Version of Backup an Replication (13.0.2.29) then i upgraded to 13.1.1.18 and Veeam ZIP stopped working with the following Error Message:  Error: Unable to cast object of type 'Veeam.Backup.Core.CFreeVmBackupTarget' to type 'Veeam.Backup.Core.CVmBackupTarget'.I searched the Internet and have been finding very few users with the same problem. One of them provided two solutions: Revert back to functional version, or contact Support and get a hotfix to makle changes on DLL.i do not want to revert back, because i think this is a greate Problem which has to be adressed by the support generally.I filed a case by the Veeam Supp

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,I’m running Veeam Backup & Replication 13.1.1.18 with the Community Edition (free, no paid license and no active maintenance contract). I’m trying to add a Veeam Infrastructure Appliance (VIA) as a Hardened Repository, installed from the latest ISO available, and I’m stuck.SetupVBR 13.1.1.18, Community Edition VIA installed from the most recent ISO Versions shown on the VIA: Veeam Deployment Service: 13.1.1.18 Veeam Updater: 13.1.202.0 Veeam Host Management Console: 13.1.1.9 Problem 1: Add Linux Server wizard fails at the “Apply” stepAfter accepting the server certificate, the wizard gets through “Starting infrastructure item update process”, “Resolving server certificate” and “Configuring the identity service connection information”. It then fails with:Software updates require an active maintenance contract.Failed to save Linux server: Software updates require an active maintenance contract.Problem 2: SSH elevation fails when using single-use credentialsWhen I retry using