Recently active topics

Hello everyone!A quick update for all of you!The waiting has an end!Veeam has officially released Data Platform 13.1 along with all its core components.Don't let the "point release" label fool you—this update is packed with over 70 new features!If you want to dive into the details, you can find all the essential information and documentation right here:🛡️ 𝐕𝐞𝐞𝐚𝐦 𝐁𝐚𝐜𝐤𝐮𝐩 & 𝐑𝐞𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝟏𝟑.𝟏:• What’s New: https://www.veeam.com/veeam_backup_13_1_whats_new_wn.pdf• Release Notes: https://helpcenter.veeam.com/rn/veeam_backup_13_1_release_notes.html📊 𝐕𝐞𝐞𝐚𝐦 𝐎𝐍𝐄 𝟏𝟑.𝟏:• What’s New: https://www.veeam.com/veeam_one_13_1_whats_new_wn.pdf• Release Notes: https://helpcenter.veeam.com/rn/veeam_one_13_1_release_notes.htmlAnd for the service providers under you like me, Version 9.3 of the service provider console has also been released!☁️ 𝐕𝐞𝐞𝐚𝐦 𝐒𝐞𝐫𝐯𝐢𝐜𝐞 𝐏𝐫𝐨𝐯𝐢𝐝𝐞𝐫 𝐂𝐨𝐧𝐬𝐨𝐥𝐞 𝟗.𝟑:• What’s New: https://www.veeam.com/veeam_console_9_3_whats_new_

Hello,We have two Veeam Backup & Replication v12 environments:Veeam Data Platform Essentials Veeam Data Platform FoundationBoth environments are isolated from the Internet, and license updates are performed manually rather than automatically.If we upgrade these environments to Veeam Backup & Replication v13, can we continue using the existing license without importing an updated license file, provided that the current license is still valid and has not expired?The following conditions apply:The current license is still within its validity period. No changes will be made to the edition (Essentials or Foundation). No changes will be made to the number of licensed instances or sockets. The environments will remain offline.Under these conditions, is a license file update required when upgrading from v12 to v13?Thank you.

One month is enough time to prepare for the Microsoft MS-700 Exam properly — if the time gets used deliberately rather than spent on comfortable review of familiar material while avoiding the areas that actually need attention.Most candidates who struggle with this exam do not struggle because one month is insufficient. They struggle because their preparation time distributed unevenly across topics, hands-on practice got deprioritized in favor of reading, and realistic scenario practice arrived too late in the preparation timeline to identify and address gaps while time remained.A structured four-week approach prevents these patterns from developing.Week One — Teams Architecture and Core AdministrationThe first week should build foundational understanding of how Teams works at an architectural level before getting into specific configuration details.Understanding how Teams relates to Microsoft 365 Groups, how SharePoint and Exchange Online underpin Teams functionality, and how the Team

For those who've been waiting for the 1st major update of VDP v13, your wait is over. VDP v13.1 has been released tonight. Veeam v13.1 has some great features, enhancements, and new platform support, like XCP-ng. Check out the Release Notes and What's New docs below:https://helpcenter.veeam.com/rn/veeam_backup_13_1_release_notes.htmlhttps://www.veeam.com/veeam_backup_13_1_whats_new_wn.pdf

When managing backup environments, an error message does not always clearly indicate the actual cause of the problem.In this case, several backup jobs protecting Nutanix AHV virtual machines started failing during the same execution window. Although the failures affected different jobs and VMs, the sessions reported the same error:Failed to perform backup:boost::thread_resource_error: Resource temporarily unavailableFailed to upload disk '72f783a8-b305-481a-b4d7-52e3351ac6c0'Agent failed to process method {DataTransfer.SyncDisk}.At first, the messages related to the disk upload and the DataTransfer.SyncDisk method could suggest a storage, network, or data transfer issue.However, after reviewing the affected sessions and the worker configuration, we identified that the failures were associated with insufficient compute resources available to the workers during a period of high concurrency.In this article, I will explain the environment, the investigation process, the worker configuratio

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

At the beginning of the year, we faced a critical scenario with one of our clients: a ransomware attack directly compromised the company's main file server. The impact on operations was immediate, as multiple departments depended on these spreadsheets and shared files in real time to keep daily processes running.When a crisis of this magnitude happens, the initial instinct of any technical team is to start restoring data as quickly as possible. However, without organization, the work ends up being duplicated, files may become recontaminated, and the time until full recovery only increases. I have been through this before.In this specific scenario, we had two teams working together: our team and the client's internal team. To avoid conflicts in priorities or misaligned actions between the teams that could compromise the restoration window, incident governance was our first step before executing any command.Below, I share the practical workflow that we aligned on to organize the situatio

I'm running the latest version of Windows 25H2 version, and Veeam version 13.0.3.1220.  I installed Veeam Agent for Microsoft Windows Free version, and created the USB Recovery Media. I then did a test Bare Metal Restore.  I immediately get the error: Authentication failed, see inner exception.If I use old Recovery media created on an different PC, that is running an older Windows version with an older version of Veeam, the restore process works just fine. I don’t get the Authentication error. I found a post on Reddit, where everyone was having this same problem. One poster said he opened a support ticket with Veeam, and they acknowledged the problem. But I can’t find any information on what Veeam is doing about this very significant bug. Does anyone have an update on this bug? Is Veeam planning a fix, and where can I find a timeline? I’m not updating my Veeam version on the older PC, as I don’t want to introduce the bug on that PC. Thank you.

Hi, We are protecting a virtual machine in OCP, backup failed on export phase showing the below:status:  endTime: "2026-07-28T11:38:02Z"  error:    cause: '{"cause":{"cause":{"message":"Failure in exporting restorepoint"},"fields":[{"name":"FailedSubPhases","value":[{"Err":{"cause":{"cause":{"cause":{"cause":{"cause":{"cause":{"cause":{"cause":{"cause":{"cause":{"message":"rpc      error: code = DeadlineExceeded desc = context deadline exceeded"},"fields":[{"name":"snapshotID","value":"k10-csi-snap-d9lxt6q44c8s2sqw"},{"name":"sourceDeviceFile","value":"/mnt/sourceDevice/kanister-pvc-pnwzb"},{"name":"volumeID","value":"test112-vm-186544-mm2tf"}],"file":"kasten.io/api/datamover/client/backup_service.go:71","function":"kasten.io/api/datamover/client.(*backupServiceImpl).Upload","linenumber":71,"message":"failed      to receive upload response"},"fields":[{"name":"pod","value":"block-mode-upload-t8rqz"},{"name":"snapshotID","value":"k10-csi-snap-d9lxt6q44c8s2sqw"},{"name":"sourceDeviceFile

Hi all,Before I start this post I humbly request that if you like this project and want me to continue to develop this and other projects, to please share, give it a star on GitHub. It really helps with the motivation. I’ve been wanting an easy way to monitor logs from Veeam products in real-time.https://github.com/shapedthought/logwatchBinary download:https://github.com/shapedthought/logwatch/releasesSo I’ve put together just that, logwatch can monitoring all the files in a folder for changes and you can also recursively monitor all the files in sub-directories. If you enable ssh on your VSA v13 (do carefully!), you can then run the following to get all the first level directories:ssh -n user@server "tail -f /var/log/VeeamBackup/*.log" | logwatch --stdinTo monitor recursively:ssh -n user@server "while true; do find /var/log/VeeamBackup -type f -name '*.log' -print0 | xargs -0 -r tail -n0 -F 2>/dev/null; sleep 1; done" | logwatch --stdin -PYou can also use this with the cloud produc

During a recent implementation, I ran into one of those problems that looks simple after you find the cause, but takes much longer to understand while you are still in the middle of it.The request was to configure Application-Aware Processing for a Linux VM running Oracle and protect its archived redo logs every five minutes.The VM backup was working.Oracle was detected by Veeam.The redo log job was showing success.The problem was that it was transferring exactly 0 B.In this article, I will share the full troubleshooting process, including a few parallel issues we found along the way. They were not all responsible for the 0 B behavior, but they still had to be corrected before the environment could be considered healthy. The environmentThe environment included:VBR 12.3; VMware vSphere; Red Hat Enterprise Linux 8; Oracle Database; Application-Aware Processing; archived redo log backups every five minutes; key-based Linux authentication; an Oracle account with SYSDBA privileges; a VM wit

Fique por dentro das novidades da Veeam!A Veeam disponibilizou o ProPartner Network Launch Resource Center, um espaço concentrando os principais anúncios, lançamentos, atualizações de programas, soluções e recursos apresentados ao ecossistema de parceiros.🔗 Acesse: https://propartner.veeam.com/propartner-network-launch-resource-center/ 

A Hands-On Look at the Next Generation of Cyber ResilienceEvery time I get access to a new Veeam BETA release, I have the same routine. I spin it up in the lab, build out a realistic customer environment, and start testing. While new platform support and performance improvements are always exciting, the first area I wanted to explore in Veeam Backup & Replication 13.1 BETA was security.Over the past few years, customer conversations have changed. We still talk about backup jobs, recovery times, and storage, but today almost every discussion includes ransomware, Zero Trust, immutability, and cyber resilience. Customers want to know one thing:"If we get attacked, can we recover?"After spending time with Veeam 13.1 BETA in our CIC lab, it's clear that security continues to be one of the biggest areas of investment. This release doesn't rely on a single feature to stop threats—it layers multiple technologies together to help organizations detect suspicious activity, protect backup data

In alto vedete il banner del prossimo webinar il cui argomento è sorto dai numerosi interrogativi che stanno animando il mondo dei sistemisti e responsabili di backup.Con l’avvento dell’AI nella piattaforma di Veeam vogliamo capire come cambierà il nostro ruolo, le nostre funzioni, le nuove possibilità di utilizzo e tutto quelle domande che abbiamo e di cui cercheremo di discuterne insieme con l’aiuto di ​@DChiavari Danilo Chiavari - Veeam Sr. Presales Manager – Italy & Turkey.Al webinar parteciperanno anche:Andrea Mauro – Veeam VanguardAlessandro Tinivelli – Veeam LegendPaolo Valsecchi – Veeam VanguardMarco Sorrentino – Veeam Vanguard Link per registrarsi:  Vi aspettiamo e se volete fare domande ci sarà la possibilità di farle !

 With the July 2026 security updates, Microsoft will permanently disable the legacy RC4 encryption algorithm in Kerberos authentication, requiring the use of modern encryption standards such as AES128 and AES256.I do not anticipate any significant impact on systems that are properly maintained, but I strongly recommend carrying out a proactive assessment to identify any systems that still use the RC4 algorithm.Potential RisksLegacy applications, older servers, hardware appliances, or service accounts configured only for RC4 authentication may fail to authenticate after Domain Controllers are updated.How to Verify Your EnvironmentMicrosoft provides tools to detect accounts and services still using RC4:Microsoft Learn: Detect and remediate Kerberos RC4 usageDetect and Remediate RC4 Usage in Kerberos | Microsoft LearnHow to manage Kerberos KDC usage of RC4 for service account ticket issuance changes related to CVE-2026-20833 | Microsoft Support Audit RC4 usageDetail about RC4 usage is sto

After about 18 months of many XCP-ng users making their voices heard on the Veeam Forums requesting Veeam to add Backup support, Veeam listened and has finally granted our request!...at least from a preliminary standpoint.  As a member of the Veeam100 Community, I was one of several approached about a month ago to perform an early Veeam XCP-ng Plugin BETA test, so I'm quite thrilled Veeam took feedback from us early BETA testers and modified the Plugin code to create a viable working Backup product for Public BETA testing. I was given the ok by Veeam to share my testing and thoughts on this Public BETA, thus this article 👌🏻In this post I'll share with the Community how to get the XCP-ng Veeam Plugin installed and configured so you can start backing up your XCP-ng VMs. For those who aren't entirely familiar with XCP-ng, I created a couple of posts talking about the XCP-ng hypervisor and its history, how to install it, and then how to get your new XO/XCP-ng environment configured and r

All Veeam jobs are started failing (VMware Snapshot/Agent/Offload) suddenly with error Job cannot be started timeout 901 sec. we are on 12.3.2 version. Any suggestions or guidance is highly appreciated.Its started working fine post restart of services.

It was a real pleasure to receive a copy of this new edition directly from the author, Chris Childerhose, who is joined this time by another well-known expert in the industry, Rick Vanover, Vice President of Product Strategy at Veeam.As regular visitors of the Veeam Community Hub well know, where Chris is an incredibly active figure always ready to support users, his dedication and expertise are fully reflected on every page of this manual.Although I haven't finished reading the book yet (I only have the last three chapters left) I can already say with confidence that it is an outstanding resource. From the first pages, the depth of the technical content, the practical approach, and the attention to detail clearly demonstrate the extensive experience of the authors.This book is designed to support system administrators, IT professionals, and consultants in mastering the platform through a balanced combination of solid technical foundations and a hands-on approach. With a clear structur

 Excited to share a new project with the Veeam community: MoovIf you run Veeam and you're staring down a move off VMware, you already know the awkward part: the backups are right there, your target hypervisor is ready, but getting the workloads across is still slow, manual, and one VM at a time.Moov closes that gap. It uses your Veeam Backup & Replication restore points as the source and brings VMs up directly on KVM platforms, Proxmox VE, oVirt / OLVM / RHV, and HPE VM Essentials, without ever touching the source vSphere environment during the migration.It's open to the community on GitHub (VeeamHub), currently in beta.https://github.com/VeeamHub/moovWhy another migration tool? Full-restore workflows work, but at scale is complex: extended downtime windows, manual VirtIO driver injection, and moving machines serially while you make some manual tasks. Moov was built for the fleet case, hundreds of VMs, in waves, with the boring parts automated.Three ideas drive it:- Veeam is the si

The StartThis series of blogs, which I will try update weekly, is about me getting to understand Kubernetes and is for someone like me coming from a level of zero dot 1, a true beginner. If you have been working with containers and know something about it, you will most probably be bored with these blogs although you might also learn something new. Luckily in this Veeam Community we have some very high-level resources that I am sure will deliver some interesting insights, and ​@Geoff Burke  has kindly agreed to moderate my journey before I take you down the wrong rabbit hole too far.Please comment and discuss freely so everybody can learn what seems to me at present a confusing technology, but don’t try proving your prowess - this is for us that do not know to learn by taking baby steps helped along the way by you.I will be writing down my understanding while doing some basic courses, reading what AI has to say about what I still don’t understand – and spending my evenings watching You

I noticed that every REST API request, including the access token request (POST /api/oauth2/token), requires the x-api-version header (for example 1.3-rev1).So I wanted to check if is there any REST API endpoint that returns the supported x-api-version (or REST API revision) without requiring the x-api-version header?

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

Recap: Veeam BeLux User Group Meeting June 25th) 🇧🇪🇱🇺 The Veeam Belgium & Luxembourg community gathered for an incredible half day of networking, technical deep dives, and collaboration.Whether you joined us to sharpen your data protection skills or simply to talk shop with fellow IT professionals, it was fantastic seeing our local community vibe together. Here is a quick look back at how it went.💡 Event Highlights & Insights Between the interactive presentations and the casual chats, the day was packed with value, we talked about the more than 70 changes, improvements and new features in the upcoming V13.1 release and building resilient Veeam architectures across hypervisor.s  Knowledge Sharing at Its Best: We had a wealth of interesting discussions and deep insights passing between end-customers and partners alike. From real-world architectural strategies to the latest recovery best practices, everyone walked away with something new. The Perfect Mix of Faces: It was wo

Hello everyone,I'm reaching out today because we're experiencing performance issues with our Veeam backups. More specifically, I find that both the incremental backup duration and the Synthetic Full backup duration are extremely long.Here's a quick overview of our current physical infrastructure:Veeam Backup Server running as a virtual machine (connected at 10 Gbps) - 13.0.2.29 Backup Repository: Synology RS2418+ (Intel Atom C3538, 4 GB RAM, no SSD cache, connected at 10 Gbps) Disks: Disk 1: WDC WD80EFAX-68KNBN0 Disk 2: WDC WD80EFAX-68KNBN0 Disk 3: WDC WD80EFAX-68KNBN0 Disk 4: WDC WD80EFAX-68KNBN0 Disk 5: WDC WD80EFPX-68C4ZN0 (recently added, hence the different model) For every backup job, the bottleneck consistently shows "Target".Backup configurationWe currently have two backup jobs:Job 1Selected production servers Incremental backups: Monday to Friday, starting at 7:00 PM Synthetic Full: Saturday (same start time, as it's not possible to schedule a Synthetic Full earlier than t