Recently active topics

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

V13.1 New Feature! - The environment described in this architecture is one main datacenter containing 5 PB of NAS data. The NAS environment contains 50 shares and 2 billion files hosted on two filers that has a max throughput of 400,000 IOPs each. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will be targeting the Veeam Hardened Repository. Backup copies with GFS retention points will be to sent Veeam Data Cloud Archive The general-purpose proxies and cache repositories will be collocated on the same server hardware.

V13.1 New Feature! - The environment described in this architecture is one main datacenter containing 1 PB of NAS data. The NAS environment contains 10 shares and 400 million files hosted on a filer that has a max throughput of 400,000 IOPs. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will be targeting the Veeam Hardened Repository. Backup copies with GFS retention points will be to sent Veeam Data Cloud Archive.

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

please dear Veeam support team, can you confirm if it is currently possible to replicate HPE VM Essentials Morpheus environments with Veeam

Is VBR support to backup and restore to Tencent Cloud?

Zdravíme přátele Veeamu 💚,na konec roku opět plánujeme naše tradiční fyzické setkání VUG CZ komunity. Protože bez střechy nad hlavou to nejde, hledáme partnera/sponzora, který nám prostory poskytne.Plánujeme to podobně jako předchozí akce. 📅 Termín zhruba v listopadu, v odpoledních hodinách. 👥 Kapacitu potřebujeme pro cca 50 účastníků (klidně i víc, pokud to prostory umožní). 📍Hledáme prostory, kde se dá v klidu sedět a sledovat prezentace.Pokud máte tip na vhodné prostory, nebo byste sami rádi byli letošním hostitelem, ozvěte se. 🚀 Hostitel dostane prostor na reklamu/prezentaci firmy a zároveň možnost slotu pro vlastní přednášku na akci. Je to skvělá příležitost, jak se dostat do povědomí celé Veeam/IT komunity v Česku. Zároveň dobrý pocit podpořit komunitu. 🤝Díky moc předem za tipy a nabídky!Antonín StrnadDavid ŠevčíkPetr Bouška

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

Всем привет,Наш файл резервной копии Veeam Agent был частично зашифрован программой-вымогателем. Процесс шифрования был прерван, и затронута только первая часть файла (1 МБ).Подробности: - Файл: dm-1c2 - 192.168.10.x.vbk, ~630 ГБ - Ошибка при монтировании: "Не удалось создать резервную копию источника монтирования. Версия хранилища [...] не поддерживается для доступа только для чтения" — заголовок некорректен. - vbkview завершается с ошибкой "недопустимое максимальное количество банков слота снимка". - Шифрование резервной копии (пароль репозитория) НЕ было включено. - Файл метаданных .vbm полностью цел и доступен для чтения (XML, версия 2626). - Критические идентификаторы: Идентификатор резервной копии = 508d4cc8-d124-4053-b6fb-b4a5190445c6, Идентификатор задания = d0d61837-77e6-4b8b-8319-fc6a449901db, Имя задания = dm-1c2, Тип задания = 12000 (Агент Veeam). - Шестнадцатеричный анализ подтверждает: все данные, начиная со смещения 1 048 576, целы — нули, стандартные индексные структуры

Over the last two weeks, several Saudi customers protecting GCP workloads have hit the same wall: backup policies fail because the worker instance can’t be created. After working through it with Google’s regional team and our R&D, the cause and the fix are clear.What’s happeningGoogle has confirmed it is no longer expanding Gen2 capacity (E2, N2, N2D) in me-central2. These machine types aren’t being decommissioned, but available capacity will keep shrinking, and it varies by zone and over time. Google’s growth in the region is on Gen4 (N4/C4) with Hyperdisk.That matters because the default worker profile is Gen2. Out of the box, the primary profile is e2-highcpu-8, the secondary is e2-highcpu-2, and the archiving profile is e2-standard-4. So a default deployment in Dammam keeps trying to launch the machine types that are hardest to get. veeamThe errors you’ll seeFailed to create a new worker. Failed to perform the operation: The zone'projects/<project>/zones/me-central2-c' do

V13.1 New Feature - The environment described in this architecture is one main datacenter containing 500 TB of NAS data. The NAS environment contains 5 shares and 200 million files hosted on a filer that has a max throughput of 400,000 IOPs. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will be targeting the Veeam Data Cloud Vault Archive The general-purpose proxies and cache repositories will be collocated on the same server hardware.

 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

You’ve equipped yourself with the introductory knowledge and skills to implement Structure & Strategy concepts! Remember to continue exploring advanced features, test your setup regularly, and leverage the best practices shared in this course to maintain a reliable and efficient workflow. Continue to module 2

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

For those that could not attend or want to watch the recording from our VUG Canada event that took place yesterday - October 8, 2026 you can find it below. 

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

Hi folks, back on the community forum. couldn’t use my old login so it took a while to enter here. however with the suffix of “exa” I managed to get on my new credentials.>So yes… for those who have been sleeping under a stone for the last two-three months there was a disruption in the space (to talk star-wars-language)… In a nuttshell, I’m no longer at Veeam, but recently joined exagrid that allows me to work with my former peers, clients, partners and so on.Keep me posted for Vmug!andeuhm… I might need your support on getting me elected as a vanguard soon when elections are open ;) now that Veeamclick is not being done by me as an MVP, I can do it as a Vanguard ;-) ps: you need backupstorage, or have an issue with current prices that goes completely crazy… don’t hesitate to drop me an email smarivoet@exagrid.com… I might be working at the right company to fix that issue ;)

We remote into the Veeam server to do our choirs, but since we upgraded to 13.1 we have a problem. We can’t use PowerShell 5 since because of the requirements of Veeam. Remoting into the Veeam server using a PowerShell.7 configuration fails with “ParentContainsErrorRecordException: Exception calling "ImportByDll" with "1" argument(s): "Dependency resolution failed for component C:\ProgramFiles\Veeam\Backup and Replication\Console\Veeam.Backup.PowerShell.dll with error code -2147450750. Detailed error:Hostpolicy must be initialized and corehost_main must have been called before callingcorehost_resolve_component_dependencies. “If I do a $psversiontable in the session it says PSVersion=7.6.3What I do:Enter-PSSession -computername veamserver -ConfigurationName “PowerShell.7” -Credential $mycredimport-module Veeam.Backup.PowerShell

During a recent Veeam Agent for Windows deployment project, we found an interesting issue involving VSS, SQL Writer, and old SQL Server references left behind after an incomplete removal or previous intervention.The scenario looked simple at first: a new backup project using VBR, Windows servers, and workstations protected by Veeam Agent. The agent deployment was successful, the jobs were configured, and everything was going according to plan.However, two specific servers started failing during the snapshot stage.At first, it looked like another common VSS issue. But after a deeper investigation, we found that the root cause was related to old SQL Server references pointing to files that no longer existed on the server. The environmentThe environment included: VBR; Veeam Agent for Windows; Windows Server 2025; Servers with SQL-related components; Jobs configured for protection through Veeam Agent. An important detail in this scenario is that the job was not initially configured