Recently active topics

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

🖱️ Your mouse cursor disappears inside the Veeam Backup & Replication console?You are not alone. Some customers since yesterday, several constellations, all on the current 13.1.1.18. Veeam Support sees the same across versions and suspects Edge / WebView2.What worked for us:✅ Update Edge, taskkill /F /IM msedgewebview2.exe and restart the console. Cursor back.If you cannot update or wait yet:🛠️ Registry: HKCU\Software\Microsoft\Avalon.Graphics → DisableHWAcceleration (REG_DWORD) = 1, restart the console. That switches off WPF hardware acceleration for the whole user profile, so test first.🧯 Or work in the Web UI (if possible).Open a support case if it hits you. Volume helps root cause analysis.🔗 R&D Thread: https://forums.veeam.com/viewtopic.php?p=575041 

I'm using Veeam Backup & Replication Community Edition 13.1.1.18 in a home lab with Veeam Agent for Microsoft Windows 13.1.1.700.I'm seeing extremely poor performance with physical Windows Agent jobs configured as:Server -> Managed by backup server -> Veeam backup repositoryThe problem reproduces on multiple physical Windows PCs.The same machines perform normally when configured as:Server -> Managed by agent -> Shared folderThe difference is enormous.Example managed-by-backup-server test:- Destination was a LOCAL NVMe repository on the VBR server- Approximately 49 GB read- Approximately 30 GB transferred- Duration: approximately 4 hours 16 minutes- Average processing rate: approximately 3 MB/s- Veeam reported Network as approximately 99% of the bottleneckThe transfer frequently drops into the hundreds of KB/s or even tens of KB/s, with occasional short bursts of normal/high throughput.I specifically tested a local NVMe repository to eliminate the NAS/SMB repository path

Hi,I’m working with MongoDB backups, and everything was going well until the restoration part.I was able to test all the restore options except: Restoring multiple collections to a point in time Publishing the instance I’m not sure why these two aren’t working. Has anyone faced the same issue before?  

I’m facing an Active Directory security audit, and the account used for the backup job generate a discussion.If i’m correct the account used must me member of builtin\administrator group, and the security team do not like at all that the password is set as never expire.i’ve already implemented that the account cannot be used for interactive login, but it is not considered “enough”So i’m trying to echange my posture without breaking the restore functionality, and i’m evaluating several option:The Veeam Server in in a workgroup and in a segmented network.1) do not do application aware and use only the vmware tools.it seem that the backup of AD is done in a correct wayPS C:\Windows\system32> repadmin /showbackupRepadmin: running command /showbackup against full DC localhostLoc.USN                           Originating DSA  Org.USN  Org.Time/Date        Ver Attribute=======                           =============== ========= =============        === =========DC=DomainDnsZones,DC=intrane

Cześć wszystkim,po części o zdalnym BMR dla Windows wracam do administrowania samym Veeamem. W tej części biorę na warsztat uprawnienia, MFA i zatwierdzanie zmian. Szczególnie w VSA łatwo się tu potknąć: mamy konta w HMC, role w VBR i dwa mechanizmy wymagające udziału drugiej osoby.Najwięcej uwagi poświęcam tutaj kontom i ciągłości dostępu. Dalej zebrałem zmiany dotyczące audytu, Malware Detection i portów. Dodatkowe MFA w Users and Roles oraz usprawnienia opisane w dalszej części to nowości 13.1. Sam Security Officer, recovery token i rozdzielenie ról HMC nie pojawiły się dopiero w tej wersji - opisuję je, bo przy wdrażaniu i aktualizowaniu VSA warto od razu uporządkować również ten obszar.👤 Zmiana uprawnień wymaga ponownego potwierdzenia MFAJeżeli MFA jest włączone, zmiany w Users and Roles serwera VBR wymagają teraz dodatkowego potwierdzenia. Dotyczy to miejsca, w którym nadajemy dostęp do całego środowiska backupowego. Nie należy mylić tego ustawienia z osobną stroną Users and Rol

The Veeam Certified Engineer (VMCE) Certification will retire on Dec. 31st, 2025. The Veeam Certified Security Expert (VMCSE) Certification will be available soon. You can find the details in this link https://www.veeam.com/support/training/veeam-university-pro.html. I have completed the requirements of Veeam Certified Security Expert (VMCSE)! Waiting for the VMCSE exam to be available.   

Today, I built a new Veeam environment using Veeam Backup & Replication 13.1 with oVirt KVM Plugin 13.8.0.395.When deploying the OLVM worker, the worker deployment completed successfully. However, the worker's network was not working afterward:Veeam could not retrieve the worker's IP address information. The worker could not be pinged from the Veeam server. The worker appeared to be deployed successfully in OLVM, but there was no functional network connectivity.To troubleshoot, I downgraded the environment to:Veeam Backup & Replication 13.0.3.63 oVirt KVM Plugin 13.7.3.63After the downgrade, I redeployed the OLVM worker using the same OLVM/network configuration, and everything worked as expected. The worker obtained an IP address, Veeam was able to detect it, and network connectivity was working normally.This makes me suspect there may be a compatibility issue or regression in Veeam 13.1 / oVirt Plugin 13.8.0.395 related to OLVM worker networking. 

Hi all,Edit 10/09/2026 : it’s now live with 13.1 :) !I've been working on a community side-project, autodeploy-web, and I'd love feedback from people who run Veeam labs.It's a single Docker container (the only host dependency) that bundles three workflows behind one web UI:1. Customise a Veeam Software Appliance ISO — a web form on top of the autodeploy PowerShell script (kickstart/GRUB/MFA/license baked in). No PowerShell or WSL needed on your machine; the form's JSON round-trips with the script. 2. Deploy a whole topology — pick a layout (VSA, VSA + VIA proxy, VSA + hardened repo, HA pairs…), point it at a hypervisor, and it provisions the VMs and wires everything into the VSA over the B&R REST API: adds managed servers, registers proxies, creates hardened repositories, installs the license, builds the HA cluster, and can add S3 / node_exporter / syslog. Two boot modes: pre-customised ISO, or remote kickstart (it injects the GRUB command over the hypervisor console). Back-ends: P

On Tuesday, September 8th, VUG France gathered in person at Scality's offices in Paris for an afternoon full of insights and discussions.This was my first in-person event as a VUG Leader (and Veeam partner), and I was thrilled to meet and connect with some of you!This is also my first post in the WAIT! group. 2026: A pivotal year for Veeam with AI integrationWe covered several strategic topics:VDC, including Veeam Intelligent ResOps for VCD and M365 The transition from VDP to VSA What's new in Veeam 13.1Hypervisors: added support for Sangfor aSV, XCP-ng, XenServer, VergeIO, Platform9, and Red Hat OpenShift Virtualization Application-aware backup via NFS shares Native restoration of an entire AD forest directly from Veeam, an operation that previously required around forty manual steps Significant reduction in the number of required communication ports Automatic updates to stay ahead of security threats without impacting business operations MFA support added to secure VBR connections As

Mardi 8 septembre, le VUG France s'est réuni en présentiel dans les locaux de Scality à Paris pour une après-midi riche en échanges et en découvertes.C'était mon premier événement en présentiel en tant que VUG Leader (et partenaire Veeam), et j'étais ravie de rencontrer et d'échanger avec certains d'entre vous ! 2026, une année charnière pour Veeam avec l'intégration de l'IANous avons abordé plusieurs sujets stratégiques :Le VDC, et notamment le Veeam Intelligent ResOps pour VCD et M365 Le passage de VDP à VSA Les nouveautés de Veeam 13.1Hyperviseurs : ajout du support pour Sangfor aSV, XCP-ng, XenServer, VergeIO, Platform9 et Red Hat OpenShift Virtualization Sauvegarde applicative via partages NFS Restauration native d'une forêt AD complète directement depuis Veeam, une opération qui nécessitait auparavant une quarantaine d'étapes manuelles Réduction significative du nombre de ports de communication nécessaires Mises à jour automatiques pour rester à la pointe de la sécurité sans impa

Bonjour à tous,Je viens tout juste de rejoindre le leadership du VUG Women Allies In Tech, et dans ce cadre, je prépare avec Kira un webinar qui aura lieu en septembre 2026. Pour m'assurer que le sujet corresponde aux attentes de la communauté, je vous propose de voter pour votre préféré parmi ces trois idées : Sujet 1 : Stockage objet & résilience : comment Veeam et Object First protègent vos données contre les cyberattaques ? Sujet 2 : L’immuabilité des données en 2026 : tour d’horizon des solutions Veeam, Object First, Dell Data Domain et autres acteurs du marché. Sujet 3 : Les 5 goulots d’étranglement les plus fréquents dans les infrastructures de sauvegarde et comment les éliminer. Quel sujet vous intéresse le plus ?Répondez simplement en commentaire avec le numéro du sujet (1, 2 ou 3) ou partagez votre avis ! Date du webinar : Septembre 2026 (date exacte à confirmer) Langue: Français En espérant vous y retrouver nombreux et nombreuses 😉Morgan

Bonjour à tous,Je viens tout juste de rejoindre le leadership du VUG Women Allies In Tech, et dans ce cadre, je prépare avec Kira un webinar qui aura lieu en septembre 2026. Pour m'assurer que le sujet corresponde aux attentes de la communauté, je vous propose de voter pour votre préféré parmi ces trois idées : 🔹 Sujet 1 : Stockage objet & résilience : comment Veeam et Object First protègent vos données contre les cyberattaques ?🔹 Sujet 2 : L’immuabilité des données en 2026 : tour d’horizon des solutions Veeam, Object First, Dell Data Domain et autres acteurs du marché.🔹 Sujet 3 : Les 5 goulots d’étranglement les plus fréquents dans les infrastructures de sauvegarde et comment les éliminer. Quel sujet vous intéresse le plus ?Répondez simplement en commentaire avec le numéro du sujet (1, 2 ou 3) ou partagez votre avis ! Date du webinar : Septembre 2026 (date exacte à confirmer) Langue: Français En espérant vous y retrouver nombreux et nombreuses 😉Morgan

Hi guys my name is Ayanda i am new here so i wanted you to explain how do i reach a point where i will be rewarded badge 

Veeam Data Cloud (VDC) is Veeam’s cloud-delivered backup platform designed to simplify how partners deliver backup services. It removes the need to manage the underlying infrastructure while providing protection for Microsoft 365, Entra ID, Microsoft Azure workloads, Salesforce, and secure storage through Veeam Data Cloud Vault.If you’re a VCSP partner looking to explore VDC, getting started is fairly straightforward.The primary license administrator of the VCSP partner account (with an active rental agreement) can register the business for Veeam Data Cloud through VCSP Pulse.Steps to access Veeam Data Cloud in VCSP Pulse Log in to the ProPartner Portal and navigate to VCSP Pulse. In the top menu, go to Licenses and Subscriptions. Click Veeam Data Cloud Subscriptions. If your organisation hasn’t yet accepted the updated VCSP Terms & Conditions for Veeam Data Cloud, you’ll see a banner message indicating that the terms must be accepted before proceeding.To resolve this: Click th

Hey all,Hopefully you have seen the registration banner in this area for the next user group we are hosting in Manchester on the 24th September. We have some great sessions covering hypervisor migrations, how to better protect your Veeam environments, real world lessons from deployments on a budget and lunch!Check out the registration page here https://go.veeam.com/event-veeam-user-group-uk.html, hope to see you there 😁Cheers,Ian

Hi everyone,I am surprised that I could not find anything regarding this topic.Here is the situation :I have no issue adding a vCenter server in the console.But when Veeam does the volume discovery, I get the warning in the title. In the screenshot it show up for two hosts actually.The ESXi hosts belong to the same datacenter under that same vCenter.Weirdly, as you can see in the screenshot, the next steps is successful.I tried to edit the vCenter object to see if it would prompt me to accept an untrusted certificate, but nothing appears.Also I tried to edit the properties of the ESXi objects but still no prompt to accept certificates.Does anyone have an idea about what is happening and how to fix this issue ?Best regards

I’m really pleased that one of my feature requests got implemented by Veeam.Out in the field with customers, or in our own demo lab, we keep running into stumbling blocks or things we’d wish worked differently. Veeam’s R&D Forum is where you can submit feature requests like that. Veeam employees look at them directly there, evaluate them, and work on them. My feature requestI submitted a feature request in the Veeam R&D Forum: an option to skip the update check when adding Managed Servers (Veeam appliances).Feature request – Veeam Managed Servers – Option to skip update check The problemWhen you add a new Veeam Infrastructure Appliance as a Managed Server in V13, the appliance checks whether updates are available for it. On a standard installation with internet access, you barely notice this.On a dark site, or when internet access and firewall rules haven’t been configured yet, it’s a different story. For dark sites you should use a local offline repo, and in other environments

Hi Everyone, I installed Veeam 13.1 on Windows Server 2022 without joining an AD domain and in an environment without internet access. I used IP addresses when adding the PVE9.2, but when I deployed the workers, the installation failed with the error “Veeam Updater is unavailable.” Later, I set up DNS forward and reverse lookups for the PVE and worker IPs, but the same error persisted. I unchecked the “Check for updates online” option for the workers.Does Veeam require an internet connection for the worker to install packages? Translated with DeepL.com (free version)

1 października MS wyłącza EWS dla Exchange’a online. Będzie to miało też wpływ na backupy robione przez VDC M365 i VBO! Poniżej jest artykuł KB, który opisuje całą sytuację i jak się na to przygotować. Jak to mówią słowianie - SPREAD THE WORD! Link: https://www.veeam.com/kb4820

VMs Living Inside Kubernetes: What Veeam v13.1's New KubeVirt Proxy Is and Why You Should CareIf you come from the traditional virtualization world, the first time you heard about "running virtual machines inside Kubernetes" it probably sounded like an architect's joke. Wasn't Kubernetes supposed to replace VMs? And now VMs run on top of Kubernetes?Well, yes. And not only does it work: it's becoming one of the most popular landing spots for organizations rethinking their virtualization platform. With the announcement of the KubeVirt Proxy in Veeam Backup & Replication v13.1, Veeam just made an important move on that board. In this post I'll walk you through what KubeVirt is, what exactly Veeam announced, and why it matters even if you don't have a single Kubernetes cluster in your data center today.First things first: what is KubeVirt?KubeVirt is an open source project (originally created by Red Hat and donated to the CNCF) that lets you run traditional virtual machines as first-cl