Recently active topics

Title: Worker VM is deleted immediately – Cloud‑Init never runs – Proxmox Plug‑In Worker Bug?Description:I am using Veeam Backup & Replication 13.x together with the Veeam Proxmox VE Plug‑In (version 3.x). The Worker Test always fails. The worker VM is created, receives a static IP (e.g. 192.168.0.28), but is deleted again after a few seconds — before Cloud‑Init or SSH ever start.Symptoms: Worker VM is created successfully Static IP is injected by the Veeam Proxmox Proxy VM boots for a few seconds Cloud‑Init does not execute SSH never comes up Veeam aborts the worker initialization VM is deleted immediately Hookscript never runs (no stop event) No logs appear on Proxmox because the VM is removed too early Storage situation:My worker storage is an LVM‑Thin pool (Data01):Codelvmthin: Data01 thinpool Data01 vgname Data01 content rootdir,images nodes pve02This storage type does not support ISO images or snippets. Cloud‑Init ISO cannot be created properly on

 CYBERSECURITY & BACKUP INFRASTRUCTURE  •  STEP-BY-STEP GUIDE  Hardening Veeam Backup & Replication on Windows: A CIS-Compliant Walkthrough Acknowledgments & Project Inspiration This guide and implementation walkthrough are inspired by the open-source hardening framework developed by Lukas Klostermann. A special thanks goes to ​@lukas.k  for creating and sharing the excellent veeam-win-hardening-script on GitHub (https://github.com/lukas-kl/veeam-win-hardening-script). His work provides an invaluable foundation for automating CIS-compliant security baselines tailored specifically for Veeam infrastructure on Windows.  Backup infrastructure is one of the primary targets for modern ransomware attacks. Securing your Veeam Backup & Replication environment against unauthorized access and lateral movement is no longer optional—it is a critical security imperative. In this guide, we dive into automating Windows baseline security and Veeam-specific hardening using CIS (Center

Hardening with Microsoft Security Compliance Baseline 2025 & CIS Standards for Veeam Infrastructure  References: Configure Security Baselines for Windows Server 2025 | Microsoft Learn Windows Server 2025, security baseline | Microsoft Community Hub osconfig/security at main · microsoft/osconfig · GitHub 1. Overview & Architecture Creating a baseline Golden Image for Windows Server 2025 ensures consistency, security, and rapid deployment across your infrastructure. This guide provides a complete, production-ready workflow to build, harden, and generalize a Windows Server 2025 template specifically optimized for enterprise environments and Veeam Backup & Replication workloads. 2. VMware Virtual Machine Prerequisites Configure the VMware Template Virtual Machine with the following specifications: Parameter Recommended Configuration Operating System Windows Server 2025 Standard (64-bit) Firmware UEFI Firmware Security Features Secure Boot Enabled Virtual Hardware

The goal of this step is to give you a high-level understanding of the core fundamental components of Veeam Backup & Replication. We will also guide you through some general backup strategy considerations and infrastructure deployment requirements. Veeam Backup and Replication is a comprehensive solution that allows you to back up and restore your data residing in hybrid and multi-cloud environments:Cloud: AWS | Azure | Google | IBM Virtual: VMware | Hyper-V | Azure Local | Nutanix AHV | Proxmox VE | HyperCore | oLVM |RHV Physical: Windows | Linux | MacOS | Unix | NAS Applications: Microsoft | Oracle | SAP Hana | PostgreSQL | MongoDB Backup JobVeeam Backup & Replication does not install agent software inside the VM guest OS to retrieve VM data. To back up VMs, it leverages VMware vSphere snapshot capabilities. When you back up a VM, Veeam Backup & Replication requests VMware vSphere to create a VM snapshot. The VM snapshot can be thought of as a point-in-time copy of a VM t

Account and Roles LicensingAccount and RolesLog in or create your My Account login if it's your first time.My Account is a central place to access your Veeam® products, license keys, Veeam Support, technical documents and much more! You can also use this same login to access resources on Veeam.com, Veeam University and Veeam Community.Once you have access to My Account, you will be able to:Obtain your licensing: Select License Management > Production to manage and obtain your Veeam licensing (License Administrator only). The License Administrator can download the license key directly from My Account and the other users can request the license key to be sent via e-mail to the primary license administrator.Download products: Select Products to access and download your product(s). When accessing the Products tab, a list of products appears based on the licenses owned. If you cannot see a product that you are looking for on that page, you can access “All Veeam Products”.Assign a License

The failure that wasn't a failure Every backup admin knows the drills for a dead array: a controller dies, a BBU gives up, a broken drive corrupts a stripe, you rebuilt, restore and move on. What almost broke us at two independent customer sites was none of those. It was worse, because nothing was actually “dead”.  The symptom: not down, just uselessly slow Two of our customers are running fully independent 2-node HCI clusters using a 3rd party HCI solution inside VMware VMs on ESX 8. As usual, the storage-VMs are consuming all the local storage on the nodes and - while mirroring via LAN - give it back to both hosts via iSCSI. Many HCI vendors go down this path.Both clusters ran flawlessly and fast for 7+ (!) years with roughly 40 VMs on top of each cluster.Goal was, to have them distributed and fully redundant between two fire zones on the campus.But suddenly and within two weeks, those two customers independently reported major outages for their systems to us. The systems never went

Hi Veeam Experts,I am trying to install the Veeam Software Appliance on a bare-metal server.The installer detects the disks and creates the partitions during the Rocky Linux setup, but it stops at the Installation Summary with a “Kickstart insufficient” error and doesn’t proceed further.I have tried both GUI and CLI installations, but the installation is not proceeding further.Could you please advise on troubleshooting steps? Regards,Dhanapal

Watched video over Veeam Sire - Clean Room we have just covered a network refresh, Core - Edge Switch - AP but wanted to make use of old HP Switch 2920 with 10gb Gbic to rear this will be my clean room with referb of Arcserve UDP Server refresh install Windows Server 2025. Been looking at options on Firewall OPNsense Connection to both LAN that is Production - Clean Room to opt for Lenovo m720q with riser attached 2 x 10gb ports will configure 10gb Prod - 10gb Clean has any one created firewall rules for such connection or used firewall device to cover on / off question as my build as TrueNAS with NFS share this needs access over both connections. Any solutions to what members have done with such solution. Education secondary 6th form school

​@Rick Vanover  and I are back with another Community Recap, and we have quite the mix this week!Who are you gonna call when it comes to the new Security Officer? What happens when Enterprise Manager seems to have its own sense of time? Where did that SAML group claim go? And if you’ve been wondering what Veeam iResOps actually is, we’ve got you covered there too.Plenty of great community content to get through, a few things to learn, and, as always, some thoughts from Rick and me along the way.Come catch up with us! Featured Contentvia ​@Andreas Buhlmann via ​@fabian.papenfuss via ​@Chris.McDonald Vanguard Blog SpotlightThis week VBS comes from ​@zamaan.ali , and he’s taking a newly launched Veeam concept, iResOps, and trying to explain it in a really simple way. We know we can recover. But do we know exactly what we need to recover? I think that’s where the conversation around iResOps gets really exciting!Special Department News: On Demand VeeamON Virtual Event 2026 until December 18

Good News for Veeam Products:KB4953: PHP2Shell Vulnerability (CVE-2026-109618/CVE-2026-109619)https://www.veeam.com/kb4953

We are a vmware shop, being priced out.  Many factors pushing us toward Hyper-V.I understand that in the early days ReFS was bug-ridden in multiple aspects.Going forward with Windows 2025 CORE Hyper-V, with VM’s of Windows2022, RHEL 9, and a few linux-based OVA deployments, what is the community recommendation for the format of the iSCSI LUNs that the VM’s run from?  there will be sizes from a couple hundred GB to all the way to 6TB, and in a special case 20TB.Our Veeam Repos are XFS, so not a factor here.Thank you kindly

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

Bonjour à tous,Ce matin je devais préparer un job de sauvegarde d’un VCHA chez un client.J’ai constaté que Veeam ne peut pas sauvegarder nativement et correctement un cluster VCHA en raison de plusieurs contraintes techniques imposées par VMware :Prendre un snapshot sur un nœud Passive ou Witness peut déclencher un failover ou un état incohérent, or Veeam utilise des snapshots pour les sauvegardes image-based VMware recommande de ne sauvegarder que le nœud Active et d’exclure les nœuds Passive et Witness, or Veeam ne peut pas distinguer automatiquement le nœud actifPour pouvoir sauvegarder un VCHA il faut pouvoir exclure le noeud passif lors du lancement du job.Pour ce faire je lance deux script, un script qui s’exécute avant le job et un script qui s’exécute après le job.En espérant que cette technique pourra aider certains d’entre vous.Morgan. ________________________________________________________________________Script avant le job: ########################################## PRE-JO

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

Hi team,Thank you for building and maintaining the Veeam Calculators.I'm reaching out because a partner re-ran a NAS sizing with the exact same inputs as before and got noticeably different results after the recent update. They need to explain the difference internally before requesting additional resources, so I'd like to understand what changed in the logic.Inputs (identical in both runs)- Source: 40 TB, 4 shares, 1M files, 5% daily change rate- Backup window: 8 hours, retention: 60 dailies (no GFS)- Immutability: enabled, 60 days, block generation 10 days- Storage: Block Storage, compress by 10%- Growth rate: 0%, forecast: 0 years- New in the latest run (Advanced, defaults): network speed 40 Gbps, array max IOPS 400,000, array count 1Previous result- Repository: 264.4 TB- Proxy: 2 cores / 4 GB- Cache repository: 2 cores / 12 GB, cache space 1.0 GB- Repository compute: 2 cores / 8 GB Current result- Repository: 144 TB- Proxy: 1x 8 cores / 16 GB- Cache repository: 6 cores / 16 GB, cac

Just a heads-up folks, there are new critical vulnerabilities affecting PHP:   CVE-2026-109618 CVE-2026-109619 Product PHP core PHP core Severity Critical, CVSS v4 9.2 Critical, CVSS v4 9.2 Impact reported Remote Code Execution Remote Code Execution Authentication Reported as unauthenticated Reported as unauthenticated Affected versions Reports indicate PHP 5.4+ Reports indicate PHP 5.4+ Name Collectively referred to as PHP2Shell Collectively referred to as PHP2Shell  Initial reports suggest these vulnerabilities have the potential for unauthenticated RCE. If a public facing site can’t be patched, it should be taken offline. Still very sparse but should know once there is additional information.https://cert.europa.eu/publications/security-advisories/2026-018 https://www.ncsc.gov.uk/news/critical-security-issue-affecting-php https://www.bbc.co.uk/news/articles/cmly0lg3w5x2o https://www.php.net/archive/2026.php#2026-10-20-1

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

Buongiorno a tutti: nella console di VEEAM BACKUP & REPLICATION 13 abbiamo un JOB che è rimasto appeso da 43 giorni e quando proviamo  a cancellarlo restituisce il seguente errore:    A qualcuno è già capitato?Come possiamo risolvere?Grazie

 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