Community

This is a tough situation I’ve been fighting for a week. Our windows server (2016) on which veeam Backup & Replication 12 was running on broke and we were unable to make it boot again.After much trying, I setup a new Windows Server (2025) and installed Veeam 12 on it. Before installation I installed MSSQL, imported the database from the old server and used that as an existing DB during installation. We don’t have a .bco Backup.This worked pretty well, all our backups were recognized, our configuration was still there, etc. I managed to restore the connection to our VMWare by re-entering the connection password. Now we have a Linux Backup Proxy. I reset the credentials and a connection can be established, but I am getting these errors now (from Util.VolumesHostDiscover.log): [31.07.2026 15:52:41.908]    <24>   Error (3)    Failed to unprotect data: the actual generation 1be493dd-f053-4957-86cf-06d604afcbdd does not match the expected generation ad168c2e-58e4-49d5-aa58-747ee032

Hi all,Me again, I’ve been wanting to create a scanning tool to get detailed information about file systems to aid in the design of Veeam unstructured backups for a while. I created this tool a few years ago but I thought I’d dust it off and with the help of Claude make it something that the community can use. As always I’ve written it in Rust as it provides fast, multi-threaded scanning.https://github.com/shapedthought/fast-walkIt provides file system information in the following files:results-20260801-160000.csv           totals per extensionresults-20260801-160000-age.csv       totals per age bandresults-20260801-160000-size.csv      totals per size bandresults-20260801-160000-hotspots.csv  directories holding the most small filesresults-20260801-160000-largest.csv   the largest files foundIt also provides the information in the terminal:It also allows you to compare scans to get an idea of change rate over time:I’m looking for testing and feedback on different file systems of which

Veeam has officially introduced Veeam Data Cloud Vault Archive, a new capability designed for long-term backup retention (“cold data”) that helps organizations reduce storage costs while maintaining security and compliance.Key Highlights💰 Lower Storage CostsStores infrequently accessed backups in a cost-effective Archive storage tier. Ideal for long-term retention (5, 7, 10+ years).🔒 Enhanced SecurityImmutable backup storage. End-to-end encryption. Protection against ransomware and accidental or malicious deletion.📋 ComplianceHelps organizations meet regulatory and corporate retention requirements. Simplifies long-term data retention for audits and compliance.⚙️ Simplified ManagementFully managed by Veeam. No need to manually configure Azure Archive Storage or lifecycle policies. Seamlessly integrated with Veeam Data Cloud Vault.📦 Best Use CasesLong-term backup retention. Cold data that is rarely accessed but must be preserved. Organizations looking to reduce cloud storage costs wi

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

I am back this week with blog #6 on the v13 series.  This one takes a look at RBAC in v13.  You can check it out below and on my blog site via the link.Blog - Veeam v13 RBAC: A Simple Operational View Veeam v13 RBAC: A Simple Operational View Introduction Role-based access control becomes more valuable as backup environments grow beyond one or two trusted administrators. In production, the purpose of RBAC is not just to reduce risk on paper. It is to let teams delegate routine work safely while preserving control over the settings that define recoverability.That distinction matters because backup access is often granted too broadly for convenience. When everyone can modify jobs, repositories, and restore actions, the environment becomes harder to audit and easier to disrupt by accident. Map Roles to Responsibilities An effective RBAC model starts with real work, not job titles. Backup operators may need to review failed jobs and rerun tasks, while restore administrators may need access

I wanted to post this for everyone who uses VB365 and PGBouncer with Postgres with the recent upgrade 8.1.2.180.When trying to run this upgrade I ran in to an issue with the following error which was caused by connecting to Postgres via the PBBouncer 6432 port.  I had to stop services, modify the XML files back to 5432 (default PG port) and then run the upgrade.  Once complete I could then revert back to 6432 for PGBouncer and start up the services again.Error seen during upgrade -    

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.

Hello, I’d like to ask about an issue I’m facing.Recently, I configured Veeam Backup & Restore version 13 to back up my Windows SQL Server. The database backup completed successfully, but when I attempted to restore it on a per‑table basis, I noticed that this cannot be done via the plug‑ins. The interface looks like this:Restore interface for MSSQL Server using Plug‑InsAfter that, I checked the Veeam guide and noticed that if I want to perform a per‑table restore, I first need to configure a staging server in Veeam Explorer for MSSQL. However, when I try to add the staging server, I encounter the following error messages:Staging Server cant be added to ControllerDoes anyone know how to fix this? Any suggestions would be greatly appreciated.

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

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

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

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

 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

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?

When designing a Hyper‑V backup architecture, one of the most important decisions you’ll make is how will backups be moved from a hypervisor and how are they processed. In Veeam Backup & Replication, Hyper‑V backups rely on backup proxies, and unlike vSphere, Hyper‑V proxy behavior comes with some unique considerations that require upfront planning.Hyper‑V supports two types of backup proxies:On‑host proxies Off‑host proxiesAt a high level, these operate similarly to VMware proxies—but the implementation details, limitations, and operational overhead are significantly different. Let’s break them down and discuss when (and when not) to use each. On‑Host Proxy: The Default and Recommended ChoiceFor most environments, the on‑host proxy is the simplest, most reliable, and recommended backup transport mode.When a Hyper‑V host is added as a managed server in Veeam Backup & Replication, the on‑host proxy is automatically deployed to it. Each Hyper‑V host runs its own proxy, leveraging

When disaster happens in my virtual environment, there is no one single tool I have implemented, configured, or created to help me get my environment back up and running. There are 3 must-have "tools" I want to help me during such crises → first and foremost my Business Continuity/Disaster Recovery Plan (BCDR); second, Veeam's Instant VM Recovery (IR); and third, Veeam Immutability.When an unwanted or unwelcomed situation arises, each of the above listed tools provides me with the following:Having a BCDR Plan gives me a sense of direction and clarity I need to begin tackling the disruption When the recovery process starts, Veeam Instant VM Recovery provides me with speed and confidence to meet my Recoery Time Objective (RTO) Service Level Agreements (SLAs) And with Veeam Immutability configured, I have assurance and trust in knowing the data I'm recovering hasn't been tampered with; and I'd couple this with using Veeam's Scan Backup feature using Veeam Threat Hunter for added ease of m

In modern backup environments, the protection ecosystem must ALWAYS be designed assuming that the primary infrastructure will be compromised. This is done so we can guarantee operational continuity and the ability to respond to an isolated problem or an entire disaster in the production environment. With this in mind, I have separated three components that cannot be neglected when designing or reviewing your backup and data protection environment. 1. Immutability Nowadays, it is no longer enough to guarantee just a single layer of immutable backup. As soon as an attacker obtains administrative credentials for a backup system, the first thing they will try to do is delete local backups or force the expiration of retentions. After that, they will do the exact same thing to the second copies of your data or your cloud backups.In the past, it was very common to see backup environments with local disk backups and tape backups. In a scenario like that, only the tape backup could be considere

Backup job finished with Failed, Job details: Job cannot be started. Timeout 904 sec, Job has failed unexpectedlyEven the scheduled config backup job did not progress , veeam version 12.3.2All the veeam services are running fine. Kindly advise

Hello Community.I was asked by Packt Publishing if there are any influencers out there with a blog/vlog that would be interested in doing a book giveaway for a physical copy and e-book (PDF)?If you are, reach out to me via DM and I can also see for the person who does the giveaway about getting a copy of the book as well.Look forward to hearing back as I am trying to work on some traction with the book sales.Cheers - Chris