Blogs and Podcasts

An Introduction to RDMA for S3 One of the biggest challenges customers and partners bring to me is how to get their backups written to object storage faster. That challenge is only magnified when they’re pushing hundreds of terabytes of backup data into their object storage repositories every day. In most cases the bottleneck isn’t the disks, especially if the object storage is backed by SSD/flash. The culprit is most likely the TCP/IP network stack used to move data from the backup server to the object storage target. Every object written over HTTPS pays a TCP/IP penalty in CPU cycles, memory copies, and latency, and those penalties really become apparent when high volumes of backup data are being transferred during the backup window.When we started our object storage journey with Veeam Backup & Replication (VBR) v9.5.4 back in early 2019, we expected object storage to become the predominant platform for secondary storage and it has. Adoption of object storage repositories has cli

 When working with tape environments, tape backup troubleshooting in Veeam is often more complex than it initially appears. Many professionals associate errors directly with faulty media. However, in real-world scenarios, issues often originate from hardware behavior, environmental conditions, or subtle physical problems.In this article, I will share real troubleshooting cases and, more importantly, explain the reasoning behind each analysis. The goal is to demonstrate how to identify the root cause instead of relying only on error messages. Case 1 – Mechanical obstruction during tape movementScenarioBackup jobs started failing during tape movement operations between slots and drives.Observed symptomsFailures during load and unload operations Errors affecting a specific range of slots Intermittent behavior that initially appeared randomExample error:Unexpected slider block, cartridge is not pushed far enough into the slot(ROB_SLIDER_UNEXPECTED_BLOCK_DURING_INSERT) TroubleshootingManual

🖱️ 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 

Hi all,I had a customer who needed a way to obtain Veeam Software Appliance (VAS) updates within a closed OT/dark site/closed environment.However, the challenge was that they lacked Linux experience and would prefer to do everything in native Windows, without using WSL (Windows Subsystem for Linux). If you have no idea what I am talking about, read this section of the Veeam help center: https://helpcenter.veeam.com/docs/vbr/userguide/update_appliance_configure_updates.html?ver=13#setting-up-custom-update-configurationSo my idea was to build/configure two components:1) A PowerShell script that can be run in Windows to download the necessary files from repository.veeam.com to a computer with internet access and then zip the files into a single large Zip file. 2) Create an IIS server website with all update files needed for the VSA. Then we can easily hand-carry the Zip files from the internet-connected Windows computer to the IIS server in the OT/dark site/closed environment with you pre

 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

With the Veeam Software Appliance and the Veeam Infrastructure Appliance, update distribution is fundamentally changing. The Veeam Appliances automatically install certain updates to ensure security and operational continuity. This represents a massive increase in security and compliance. What is updated?Operating system and security updates are installed centrally and automatically, cannot be deselected, and are mandatory for both appliances. Security updates for Veeam Backup & Replication are also installed automatically and without user intervention to ensure security.Both appliances can also optionally install feature and bug fix updates automatically, provided this is enabled in the configuration. Major updates (e.g., V14.0), minor releases (e.g., 13.x), and private fixes are optional by default.Here is a simplified overview:Mandatory updatesVeeam cumulative & security updates (e.g., 13.0.x) Operating system security updatesOptional updatesMinor product updates (e.g., 13.x

Status: 23.09.2026Note: Information and links you can find at the end of this postIntroduction:The storage integration in Veeam Backup & Replication allows integrating various vendors of storage systems like NetApp or HPE into Veeam to take advantage of the snapshot mechanism directly from the array to perform backup and restore operations.But how is all of this implemented? What do you need to keep in mind? And how is it configured?With version 13 of Veeam Backup & Replication, the Veeam Universal Storage API (US API) is introduced.That means the integrations are no longer developed directly by Veeam, but they offer a framework that storage vendors can use to integrate their storage solutions into Veeam Backup and Replication.At this point it is important to mention that the new US API-based plugins do not automatically replace everything from the built-in integration.Currently the new US API plugin is only intended for block or file storage for VMware Sphere; NAS filer backup

When I published my previous article about NFS repository performance, one of the key observations was that NFS mounts could become a bottleneck due to a limited number of network connections being used between the backup infrastructure and the storage system.At the time, a common recommendation was to manually tune Linux NFS mount options, especially the nconnect parameter, to improve throughput.Recently, I discovered an interesting configuration option within Veeam Backup & Replication that deserves attention. A Hidden Registry SettingVeeam appears to support custom NFS mount parameters through the following registry value: Key:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and ReplicationValue Name:NfsLinuxMountOptionsType:REG_MULTI_SZ Example: nconnect=300 When configured, the resulting mount may look similar to:172.0.0.30:/data /mnt/repository nfs rw,soft,vers=4.1,nconnect=300  Now all Linux Gateway Servers will use this option …. 

✦ All of this seem over your head? Ask Claude to help. The GitHub repo ships a ready-made prompt that lets Claude Code ask for your addresses, set up SSH, install the proxy and the Pis, and guide you through the Veeam console: Deploy it with Claude Code →There is no Veeam Agent for ARM. There is, however, a way to give the stock Linux agent a frozen, point-in-time image of a Pi's SD card and let it do what it does best. Here is the full build, end to end, almost entirely from the VBR web console.This started as a weekend puzzle and turned into something I would actually run. I have a couple of Raspberry Pi 4s doing real work: one is a fixed ADS-B flight-tracking ground station, the other rides along in an aircraft. They are cheap, they run for months untouched, and when an SD card finally dies you discover how much configuration lived on it. That is exactly the kind of "small but annoying to rebuild" workload people have scattered across labs, shops and edge sites: signage players, sen

IntroductionThis week I upgraded our internal lab/PoC environment from Veeam 12.3.2 to 13.1. I'd like to share my experience with this upgrade — what worked well, what you should prepare for, and a few things that aren't immediately obvious from the release notes.Here's an overview of our lab/PoC environment:Enterprise Manager (Windows Server 2022) Backup Server (Windows Server 2022) ONE Monitoring (Windows Server 2022) 2x Backup Repositorys, Performance Tier (Windows Server 2022 / HPE ProLiant DL380 Gen10) 2x Backup Repositorys, Performance Tier, used for Backup Copy (Ubuntu Server 24.04 LTS / HPE ProLiant DL380 Gen10)On the virtualization side, we run a full VMware Cloud Foundation 5.1 stack, including the Enterprise Manager integration (Veeam plugin) in VMware Cloud Director.Storage integration is not currently in use, and neither are Veeam backup agents — so this is a pure virtualization backup environment.This setup essentially mirrors our production environments, which made it a

For my fourth blog in my new series which covers both Veeam and Wasabi, I wanted to look at setting up Veeam with Wasabi to go over some of the basics.Blog - Getting Started with Veeam and Wasabi – Step by Step Getting Started with Veeam and Wasabi – Step by Step Wasabi is one of the most popular object storage targets for Veeam deployments, and for good reason — no egress fees, predictable pricing, S3-compatible API, and Veeam Ready certification. If you are not already using Wasabi as part of your backup strategy, this guide will walk you through getting it set up. Why Wasabi for Veeam?Before diving into the configuration, let’s quickly cover why Wasabi is worth considering: Veeam Ready certified — validated for both Object Storage and Object Storage with Immutability No egress fees — restoring your data does not cost you extra (looking at you, AWS) No API call fees above a reasonable threshold S3-compatible — works natively with Veeam’s object storage repository type Object

I have a lot of jobs that are getting a new naming convention. The old way to do this was remove from the job from the configuration, modify the folder name on the repository, rename the job, rescan the Repo, then map the back files to the job.   I found there is an updated way to do this and is a welcome feature to save time. To go one step further, it is not recommended to use the remove/rescan method due to the fact the files get new identifiers that cause the restore points to be seen as new data by all tape and cloud storage offload jobs.  To test it, lets create a new job.In my case it’s called “___TEST_NAME_CHANGE” to keep it at the top of my screen.  Next, after running a job, we will click “Disk” on the left to make sure there is a backup on the Repository. It’s similar, but it’s not quite the same screen. 😉  Now, return to the Backup page, right click your Backup job, click edit, and lets rename it.   On the Backup Job page you can see it’s been renamed.   On the Disk page w

During a recent check on a Veeam Backup & Replication server, I noticed that the folder below had grown to several gigabytes:C:\ProgramData\Veeam\Backup\System\CheckpointRemovalThis can become a problem, especially during Veeam upgrades, where the installer often requires more and more free disk space to complete successfully. What is in this folder?The log files stored in this location are related to offload activities.Unfortunately, Veeam does not currently apply any log retention to this folder, so its size can continue to increase over time. Can these files be deleted?Yes, according to Veeam Support, it is possible to manually delete folders older than 14 days from this directory.That means you can safely clean up old content and recover disk space when needed. Why this mattersIf this folder grows unchecked, it may:consume several GB of disk space, create unnecessary pressure on the system volume, and potentially cause issues when performing Veeam upgrades.A quick cleanup may s

One of our recent projects focused on modernizing a customer's data protection strategy, replacing a legacy environment with a resilient and recovery-ready architecture.A key success factor was the ability to reuse the existing physical backup server and LTO tape library from the legacy solution, avoiding additional infrastructure investments and making the project financially viable. This approach enabled the customer to modernize its backup platform while protecting previous investments and accelerating adoption. The ChallengeThe customer was operating with a legacy Arcserve backup solution that presented several operational and business risks.The environment faced a high risk of data loss and limited confidence in backup recoverability. Critical workloads lacked adequate backup coverage, creating protection gaps across the infrastructure. Operational management had become increasingly complex due to manual processes, limited visibility, and the challenges associated with maintaining

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

For anyone in the community preparing for the CISSP exam, there’s a free group mock exam taking place tomorrow, Saturday, September 19, at 3:00 PM Eastern Time. You can take the full practice exam, get domain-by-domain results, and compare notes with other participants afterward.No subscription is required for the event.Registration: CISSP Mock Exam Day

Why You Should Integrate Veeam with CrowdStrike Bridging the Gap Between Detection and RecoveryI'm in the process of integrating Veeam with CrowdStrike in my lab, which will be available for customer demos. In this first article, I'll talk about "Why you should integrate," and in the next, we'll walk through the configuration steps for the integration.Most organizations today are investing heavily in security tools to detect threats faster than ever. At the same time, they rely on backups to recover when things go wrong.But here’s the uncomfortable truth:Detection and recovery are still often completely disconnected.That gap is exactly why integrating Veeam with CrowdStrike is becoming a critical part of modern cyber resilience strategies. The Problem: Fast Detection, Slow DecisionsCrowdStrike is incredibly effective at identifying:ransomware behavior lateral movement credential abuse suspicious processesIn many cases, it detects threats within minutes.But once an alert fires, the ques

Recently I faced an interesting issue with a Hyper-V VM backup in Veeam. One specific VM suddenly started failing during checkpoint creation, while all the other VMs in the environment continued to be protected normally.What made the case more interesting was that there was nothing obviously wrong with the affected VM. It was powered on, the operating system was accessible and the applications were working normally. From a production perspective, everything looked fine.However, every backup attempt failed with the following error:Failed to create VM recovery checkpoint (mode: Crash consistent)Checkpoint operation for 'SRV-IA-CONATA' failed.Checkpoint operation for 'SRV-IA-CONATA' was cancelled.'SRV-IA-CONATA' could not initiate a checkpoint operation:Incorrect function. (0x80070001).Error code: '32768'.Retrying snapshot creation attempt(Failed to create production checkpoint.)Unable to allocate processing resources.Error: Failed to create production checkpoint. Finding the real problem

For my third blog in my new series which covers both Veeam and Wasabi, I wanted to look at something new in Wasabi called “Covert Copy”.   It is very interesting technology and you can read about it below.Blog #3 - Wasabi Covert Copy – The Invisible Air Gap Your Backups Need Wasabi Covert Copy – The Invisible Air Gap Your Backups Need Ransomware attackers have gotten sophisticated. They do not just encrypt your production data anymore — they go after your backups first. If an attacker can find and destroy your backups, your recovery options disappear. That is the threat Wasabi designed Covert Copy to solve, and it is one of the most interesting data protection features to land in cloud storage in a while. What is Covert Copy? Wasabi Covert Copy is a feature of Wasabi Hot Cloud Storage that creates a locked, hidden copy of a selected S3 bucket. The copy is completely invisible to anyone accessing your Wasabi account through normal means — including authenticated users and, critically, a

In Japan, when Anthropic announced Claude Mythos in April, there was an enormous urgency in the Japanese government and the news was everywhere on the media. Finance Minister Satsuki Katayama called it “clear and present danger”. Prime Minister Sanae Takaichi commented that “finding vulnerabilities is a race against time” when she directed her team to “come up with concrete measures and implement them”.Three months have passed since then and nobody seems to talk about Claude Mythos on Japanese media anymore. I searched for related news to update myself. On August 27th a couple of major newspapers reported that Japan’s three megabanks finally gained access to Mythos and started evaluating how to use it. That is how the newspaper article is written, if I translate directly. TV and other media didn’t actively report on it, as far as I am aware.I also searched on English media. There were a lot more updates available, including the info about Project Glasswing. The ones that caught my eye