Recently active topics

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

Pierwsze fizyczne spotkanie VUG Poland połączone z warsztatami mamy za sobą! Dziękuję Wam za tak liczne przybycie i świetną atmosferę przez wspólne 6 godzin.Wielkie podziękowania dla Object First: Waltera Berendsa za warsztaty i Kristiny Clark za organizację miejsca i gadżetów oraz dla Oktawiana Majkuta, który zadbał, żeby niczego nam nie zabrakło. 😎 Dziękuję też całemu zespołowi Veeam Polska - Tomkowi Turkowi, Mariuszowi Rybusińskiemu, Marcinowi Dudziakowi i Tomkowi Krajewskiemu za wsparcie, dużo pozytywnej energii, a także sporą dawkę wiedzy.👉 Teraz Wasza kolej: czy taka formuła (cały dzień z warsztatami) Wam pasuje, czy wolicie krótsze spotkania popołudniowe? Jakie tematy chcielibyście zobaczyć następnym razem? Dajcie znać w komentarzach lub ankiecie poniżej, a wkrótce wrócimy z terminem kolejnego spotkania!   

🚀 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. 

E’ con piacere che comunichiamo il primo evento congiunto del Veeam User Group Italia e del VMware User Group Italia !L’evento si svolgerà a Napoli il 2 dicembre prossimo presso NH Hotel Panorama.Prossimamente daremo ulteriori dettagli e la pagina di iscrizione.Apriamo quindi la “call for papers” di questo evento per coloro che vorranno presentare un argomento inerente Veeam e VMware/Broadcom o un case study particolare.La durata della presentazione potrà essere al massimo 30 minuti.Le richieste dovranno pervenire entro il 13 novrembre prossimo per essere valutate all’indirizzo email: cfpvug@gruppo-e.tech con oggetto: “Candidatura VUG”Vi aspettiamo ! 

Hallo Community, Ich habe zwei ESX-Hosts mit VmWare (ohne vCenter). Auf denen laufen insgesamt 19 VMs. Mein Problem: 2 von den 19 VMs können von Veeam nicht gesichert werden. Die anderen 17 werden in dem gleichen Backup-Job mit den gleichen Einstellungen gesichert. Ich habe den Veeam Server und auch die zu sichernden Server neugestartet. Leider ohne Erfolg. Den Virenscanner habe ich auf dem Veeam Server versuchsweise auch deaktiviert. Der Veeam Server kann die beiden Server z.B. per Ping erreichen. Gestern habe ich das Update auf Version 13.1.0 installiert. Same Text in english:(Hello Communitiy, I have two ESX-Hosts with VmWare (no vCenter). 19 VMs running on this two Hosts. My Problem is two of 19 VMs cannot be saved by veeam. The other 17 VMs will be saved in the same Backup-Job with the same properties. i have restart the Veeam server and the both target Servers. I deactived the anti-virus for testing but nothing changed. The Veeam server can reach the both VMs with for example pin

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 

The new Veeam security bulletin is all the buzz lately with multiple CVE’s - https://www.veeam.com/kb4649 and I’m sure you’re all aware of this by now.However, what comes with this 12.2 update is a bit of a compatibility challenge. Cloud Connect Veeam 12.2 no longer supports customers running anything older than 12.0 as a Cloud Connect tenant. Previously, Veeam 12.1 supported tenants running anything newer than Veeam 10a.Now you probably have a conundrum. Do you know all the different Veeam versions tenants are running that are backing up or replicating to your environments? Even if you could upgrade today, how many customers are you going to break? While this won’t tell you exactly which tenants have the older versions, you can at least see *which* versions are hitting your environment with this one powershell script (run it from your VCC server).Get-CimInstance -Query "SELECT * FROM CloudTenantVersionInfo" -Namespace "ROOT\VeeamBS" | Select ProductVersionGood luck out there!PS: Of co

Back in 2023/24 we setup a DR site with a Ubuntu 24.04.3 LTS to act as our immutable repo for backup copy jobs. I believe this may be out of date now, and the VIA is all the range. The backups on the Ubuntu 24.04.3 LTS copy sit on a separate storage shelf to the OS, is it possible that if we were to migrate to VIA we can retain the backup files or is it a go no go situation?I’ve seen the migration process for Windows Repos to VIA and you can retain backup files, but we’re postponing that for now, we’d rather get all the other components in order.Just wondering if anyone’s managed to do Ubuntu > VIA and keep backups files?Cheers.

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

bonjour comment peut on créer un media recovery sur une version datacenter 2022 ? merci

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

Včera to bol naozaj skvelý večer!Ďalšie stretnutie VUG Slovakia v Košiciach je za nami a opäť ukázalo, akú úžasnú komunitu máme. A tú komunitu tvoríte práve vy všetci, ktorí prídete, diskutujete, zdieľate svoje skúsenosti a venujete jej svoj čas.Ďakujeme každému, kto bol s nami! 💚🎤 Pavol Vanacky nám priniesol veľmi zaujímavú a praktickú tému o využití AI pri vytváraní eventov v ticketovacích nástrojoch.🪟 Ja som sa tentokrát venoval téme Windows v modernej Veeam infraštruktúre a pozreli sme sa na špecifické situácie, v ktorých má Windows vo Veeam prostredí stále svoje miesto.Svoje riešenia a ich spoluprácu s Veeam nám predstavili aj naši partneri a sponzori.Veľké poďakovanie patrí Košice IT Valley za partnerstvo a HPE, Object First, Deutsche Telekom IT Solutions Slovakia a Virtuozzo za podporu, bez ktorej by sa tento večer nemohol uskutočniť. 🙏Osobitné ďakujeme patrí aj Karoline Basak, Nikole Pejkovej, Simone Haiderovej, Borisovi Mittelmannovi a Martinovi Baňasovi z Veeamu za podpor

VUG Canada held another successful event at Spirithouse on October 13, 2026 sponsored by Object First. We had the first live presentation by the two Geese from Between Two Geese, Tyler Jurgens and Matt Crape about some of the features of v13.1 and a sneak peak at some new features coming to 13.2 as well as a fascinating overview by Geoff Burke from Object First about Absolute Immutability. In between these presentations, we were led by the amazing staff at Spirithouse in making three cocktails, a Negroni, a Paper Plane, and an Espresso Martini. Everyone had a great time making these and networking while tasting them.The Two Geese, Tyler Jurgens and Matt Crape Geoff Burke from Object FirstCocktail Making BeginsThe Rare and Exotic Rickatron in the wildCheers!Paper Planes

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

Hello everyone, On October 6, I hosted my very first webinar in French. I recently joined the leadership team of the Veeam User Group WAIT, and Kira Bezhanova joined me for the event. Thank you to her, and thank you to everyone who took the time to join us. 🙏 The topic: understanding why a backup is slow.My starting point is simple. We often look for the answer in the wrong place.A Veeam job consists of a chain of four links:→ The source→ The proxy→ The network→ The target Only the slowest one matters. Once identified, we finally know where to take action.I shared the method I use in the field to achieve this. It’s a topic that doesn’t get much discussion, yet optimizing backup time changes everything: infrastructure costs, RPO, RTO. Weren’t able to attend? The replay is available here 👇▶️ https://lnkd.in/emWGCYnb And you which link gives you the most trouble?

Bonjour à tous,Le 6 octobre, j'ai animé mon tout premier webinar.Je suis récemment arrivée au Leadership du Veeam User Group WAIT et Kira Bezhanova m'a accompagnée pour l'occasion.Merci à elle, et merci à toutes celles et ceux qui ont pris le temps d'être là. 🙏Le sujet : comprendre pourquoi une sauvegarde est lente.Mon point de départ est simple. On cherche souvent la réponse au mauvais endroit.Un job Veeam, c'est une chaîne de quatre maillons :→ La source→ Le proxy→ Le réseau→ La cibleSeul le plus lent compte. Une fois identifié, on sait enfin où agir.Je vous ai partagé la méthode que j'utilise sur le terrain pour y parvenir.C'est un sujet dont on parle peu, et pourtant l'optimisation du temps de sauvegarde change tout : coûts d'infrastructure, RPO, RTO.Vous n'avez pas pu y assister ? Le replay est disponible ici 👇▶️ https://lnkd.in/emWGCYnbEt vous, quel maillon vous donne le plus de fil à retordre ?