Blogs and Podcasts

Hi everyone! I've been working in the lab on some Kubernetes deployments using MobaXterm Home Edition and Rancher. I started off using PuTTY, but found that it could be limiting for what I needed. So I began my hunt to find the best SSH client, and I ended up landing at MobaXterm. In this post, I want to talk a bit about why I opted to use MobaXterm and all of the great features it offers, especially pertaining to working with Kubernetes. Intuitive UI and Easy to NavigateWhile evaluating alternatives to PuTTY, I found that PuTTY along with other SSH terminals looked a bit dated and less approachable. Since this was my first time doing this much terminal-focused Kubernetes work, I wanted a tool I could easily navigate to reduce friction. MobaXterm has a very sleek interface that lends itself nicely to beginners and experts alike. 15 Session Settings/OptionsMobaXterm supports a wide range of session types (SSH, Telnet, RDP, etc.), which makes it useful as a single tool for connecting to

The ChallengeYou did everything right. You planned the maintenance window, cleared the pre-flight checks, upgraded your Veeam Backup & Replication server to v13, and expected the usual smooth ride when pushing the updated Veeam Agent to your protected workloads. Instead, the Protection Group rescan throws certificate errors, some of your agents stay on the old version, and your backup jobs on those endpoints start to look nervous.I ran into exactly this on a customer environment recently, and since the root cause was neither obvious in the logs nor documented in an easy-to-find KB, here is the short write-up. The Symptom(s)After the VBR upgrade to v13, the console tries to push the new Veeam Agent binaries to the Windows guests in a Protection Group. The deployment fails with a certificate related error, typically along the lines of:A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. Or a signature verification failure on

Recently, a customer came to me with what seemed to be a simple question:“Our Veeam Enterprise Manager can suddenly no longer properly connect to the Veeam Backup & Replication server, and the Catalog Service no longer synchronizes. But nothing was changed. What could be the reason?”Ah, the famous IT words: Nothing was changed.Of course, I basically understand what is meant by that. But it does not necessarily mean that a person changed something. Maybe a process, an automation, an update, a migration, etc. changed something. And of course, it is also possible that another person changed something without informing anyone, or that you changed something yourself but do not remember it anymore — or you do not see the impact because, at first glance, it does not seem to have anything to do with the issue.Well then, time to roll up our sleeves and go through the checklist:Was there a Veeam update?No Was there a configuration change in Veeam Backup Enterprise Manager or Veeam Backup &am

Hi everyone,I would like to share a troubleshooting case that took me a few long days to resolve. I hope this can help someone facing a similar issue in the future.The scenario was a VAW deployment to a customer Windows Server.At first, the issue looked like a standard deployment or Windows Installer problem. The Veeam Backup & Replication server was able to reach the target server and upload the MSI package, but the Agent installation never completed.The target server was also a bit unusual: it was heavily used through Remote Desktop sessions, with more than 60 users logged on. Because of that, it was not always easy to know if another MSI installation was really running, and we also had to perform all troubleshooting outside business hours. First issue: another installation already in progressThe first error we saw from the VBR console was:01/06/2026 22:34:43 Failed : [172.16.254.120] Installing package Veeam Agent for Windows Error: Another installation is already in progress. A

If you use Remote Desktop Manager (RDM) with Devolutions Cloud, please take a few minutes to update your installation.Devolutions has identified an issue affecting RDM versions 2026.2.1 through 2026.2.12. Under certain conditions, some entries stored in Devolutions Cloud can become unreadable. While the issue only occurs after a specific set of actions, Devolutions recommends that all organizations running the affected versions install the latest release as soon as possible.Starting July 21, 2026, older affected versions will no longer connect to Devolutions Cloud. This measure helps prevent organizations from encountering the issue.What you should do:Update Remote Desktop Manager to the latest available version. I have verified my Remote Desktop Manager installation and confirmed that it is running version 2026.2.13, which is outside the affected 2026.2.1–2026.2.12 range. Therefore, I cannot show you the update process. But this is very basic and if you are not prompted to update, ple

Even though I am on vacation this week and next still need to keep up with the blog series of 10 in 10 weeks.  For week four we discuss the VSA and operational changes.  You can find a link to my blog and the article below.Blog - Veeam Software Appliance: What Changes Operationally Veeam Software Appliance: What Changes Operationally Introduction The Veeam software appliance is one of the more important operational shifts in the v13 release. It changes the conversation from simply installing backup software to managing a more controlled platform with a tighter lifecycle and a more opinionated security posture.That matters in production because backup teams are often measured by consistency more than flexibility. A platform that reduces configuration drift, narrows the administrative surface, and standardizes maintenance can improve reliability, but it also changes how teams troubleshoot and support the environment. Deployment Changes Traditional deployments often inherit whatever stand

Recently, one of our clients experienced a situation that perfectly illustrates why operational resilience must be at the heart of every IT strategy regardless of any external threat.📖 The ScenarioWe were in the middle of building a new infrastructure, which was not yet operational, when the client suffered the loss of both server rooms within 48 hours of each other.The cause? Not ransomware. Not an intrusion. Simply the simultaneous end-of-life of SSD drives after nearly 8 years of operation.The tiered storage architecture amplified the impact: as soon as the SSDs reached their endurance limit, the first site collapsed overnight. Investigation quickly confirmed the diagnosis. But the second site, running the same architecture with the same history, followed the same path two days later.Bad timing? Absolutely. ⚙️ The Operational ResponseThe situation was all the more complex as the production infrastructure was end-of-life and out of support, we were precisely in the process of buildi

After my previous articles on backup security and object storage on-prem, today, we'll examine the best practices for using them with Veeam.Here Why go with on-premises object storage and here The choice of storage explained my ideas about a new generation storage as a backup repository.So we'll check out the best configuration for creating a backup job and explain why we chose it.Object Storage as the main repository in Veeam v12.3.As we all know, since version 12, it's been possible to use an object storage repository as a primary destination for backups. This makes the architecture simpler and offers greater flexibility.When you're getting started with object storage as a repository, it's important to remember the backup block size (block size) that's used for writing.The size you choose in the 'Storage Optimization' tab, configuring a backup job, affects how the data is divided and stored.How do we calculate the space we need for our repository?I started using a calculation tool re

From Veeam 12 to Veeam 13: Building a Future-Proof Backup & Recovery PlatformIn the coming period, we will take an important step in further strengthening our digital resilience. Our current Veeam 12 environment will be migrated to Veeam 13, based on the new Virtual Appliance architecture. At the same time, we will replace our existing, technically end-of-life backup hardware with a completely new infrastructure.For VNOG (Veiligheidsregio Noord- en Oost-Gelderland), cyber resilience is essential because our services directly support public safety and crisis response, where continuity really matters. VNOG is a regional public safety organisation responsible for fire and rescue services, we provide essential fire-fighting services and assistance in the event of accidents, disasters and crises to the 870,000 citizens of North and East Gelderland in the Netherlands.The new design is distributed across two data centres. Within our vSAN environment, which hosts approximately 180 Windows

In today’s digital world, data security is a top priority for organizations. Veeam Backup & Replication has evolved to meet these needs, and one of its key innovations is the Veeam Hardened Repository ISO—a solution designed to protect backup repositories from ransomware and other cyber threats.What Is the Veeam Hardened Repository ISO?The Veeam Hardened Repository ISO is a Linux-based solution that secures backup data by making it immutable. This ensures that data cannot be modified, deleted, or encrypted by unauthorized parties, even in the event of a ransomware attack. The repository allows organizations to set a retention period during which backups remain secure and unaltered.Key Features:Immutability and Retention Locks: Ensures backups are safe from external modifications. Ransomware Protection: Protects backups from being encrypted or deleted by ransomware. Linux-based Security: Utilizes Linux’s built-in security features for enhanced protection. Enhanced Data Availability:

Having updated to Proxmox VE 9.0 below. There is a need to upgrade from  Veeam Plug-in for Proxmox VE build 12.1.3.217 to plug-In build number 12.1.5.17 to support it.The Proxmox VE Plug-in integrates the backup server with the Proxmox VE server and enables worker deployment. From version 12.3.1 and above, you do not have to manually install this plugin.You can download the Plugin for Proxmox VE directly from the referenced link, or navigate to the release Information for Veeam Plug-in for Proxmox VE v12.1.5.17 in the following KB article.To see the current version of the Veeam Backup for Proxmox plugin that you are currently using. Please launch the Control Panel or Windows Settings as you wish. As you can see, we are currently using the version 12.1.3.217 As you can see below, this meets the requirement for the Veeam Plug-in for Proxmox VE build 12.1.3.217 which can be determined via the steps below.You can check the build number in the Veeam Backup & Replication Console’s Main M

 Why this guide? A while back, a customer asked me for a simple step-by-step guide for restoring the Veeam Backup & Replication configuration onto a newly deployed Veeam Software Appliance. This write-up is the result. It has been a little while since then (as you can tell from the version used, 13.0.1) - but since I haven't found a similar step-by-step guide here in the Community Hub yet, this one is for you. I am well aware that most of the steps here are self-explanatory for all of us, and that most of you could get through this configuration blindfolded. My customer, however, asked for a truly foolproof guide - something to provide a rough direction in a worst-case scenario. That said, should it ever come to that, we will of course be supporting them anyway...And finally, the customer also receives a checklist to document the individual steps - you will find it at the end of this guide.  VBR / Veeam Backup Server Configuration Restore  If the entire Veeam VBR intelligence is no

Hello everyone!This is my first contribution to the Veeam Community Hub!In the long term, I plan to start my own blog to share my thoughts and technical perspectives from my daily work, but while it is in the making, let's move on with my thoughts on the topic „how to structure jobs.“This post will cover Veeam Backup & Replication in the first place, but in the future I will also cover Veeam Microsoft 365.In my daily work, I have seen a lot of variations, like “naming schemes“ (please imagine this in very large quotation marks), like "Backup Job 1“ or „Server Backup x with Database.“Basically naming jobs like this, of course, works, but in the daily work you have to search for what this job is exactly, and when the description is the default one, you don't know anything.To prevent this situation, and because I really like to organize things:)Over time, I have developed a specific naming scheme for jobs in Veeam Backup and Replication, such as Backup to Disk or Backup Copy Jobs.This

 Have you ever wondered where we Veeam 100 members are distributed around the world?Based on Veeam 100 Directory | Veeam Community Resource Hub and the public location information I have from our LinkedIn profiles, I sat down and provided a world map that answers exactly the above question, or shows it on the map. In the backend, I use MapGeo and Google Sheets for this. As soon as you press directly on a member or their point on the map, the photo stored from the Veeam 100 Directory (in the Community Hub) opens.For short information such as names, titles and, if applicable, Blog URL just “hover” over the point on the Map. Below the map is a search mask, here you can jump directly to the corresponding member, which also opens the stored profile picture (see above). If you want to continue searching, just click outside the photo. Now only ​@safiya, ​@Madi.Cristil, ​@NikolaPejkova, ​@HannesK and ​@Rick Vanover need their own category in the Veeam 100 Directory with a photo, so that I can

 1) In the beginning there was the password…… and of course it was created by humans—so it was often simply “1234”, “<first name><birth year>”, or “password”.“password”: A password as secure, useful, and brave as an umbrella in a hurricane — but hey, it worked for logging in. You logged in, everything was fine, and back then life didn’t yet have password policies—and luckily, at the start there also weren’t worldwide automated attacks via the internet.Then password security policies were introduced step by step—but let’s be honest: humanity is lazy and most people’s memory isn’t that great. So “password” turned into:At least 1 uppercase letter: Password At least 1 numeric character: Password1 At least 15 characters: Password1234567 At least 1 special character: Password1234567!What an evolution. Ah, humans are as simple as they are brilliantly constructed. One of the newer developments is the passphrase, which actually helps. The idea is to combine several words that are ea

I am back with blog 3 in my series and this one looks at the v13 Web UI and what you should test first after implementation.Blog - Veeam v13 Web UI: 5 Things to Test First Veeam v13 Web UI: 5 Things to Test First Introduction A new web-based management experience is not just a visual change. It shifts how backup administrators reach the platform, how they review workloads, and how quickly they can respond when they need to restore something under pressure.That is why the first production tests should focus on routine operator behavior rather than feature exploration. The question is not whether the interface looks modern. The question is whether the most common backup and recovery tasks are clear, fast, and dependable in the browser. 1. Test the Login Path Start with the most basic workflow: sign in from the workstation or jump host that administrators actually use. This confirms network reachability, certificate trust, browser compatibility, and whether the access path feels consisten

 Recently, a customer asked me about Microsoft’s changes to throttling and service limits. In the past, they had used the multi-app registration approach and now wanted to clean it up. They also asked for clarification on how to handle backup settings and optimizations going forward.Regarding backup throttling and the EWS → Graph API transition, I have already published two blog posts — feel free to check them out:Microsoft EWS is dead. Long live… Graph?„Dr. Backup and the Quest for the Holy Backup Performance Stream: Mastering the Latest Microsoft Throttling Changes (March 1, 2026) with Veeam Backup for Microsoft 365 v8.4 and VDC M365Now, let’s focus on cleanup first—because multi-app registration no longer provides any performance benefits (see KB4821). Removing it is possible in both on-prem and VDC environments, but the steps differ slightly.  Step 1: Identify the App Registration IDs You Want to Remove In VDC Backup Service you can find them here:Veeam Data Cloud –> Microsoft 3

There’s always a bit of excitement when a new Veeam beta drops. Since I spend much of my time in the lab evaluating new features and demoing to customers, I was eager to get my hands on Veeam Backup & Replication 13.1 Beta and see what it had to offer.Instead of just reading through the release notes, I approached this the same way I would a customer proof of concept. I started with a clean installation, built out a realistic backup environment, configured the solution, tested the new features, and looked for anything unexpected along the way.In this article, I’ll walk you through my entire lab experience—from deployment and configuration to testing the latest functionality and sharing my observations. My Lab EnvironmentFor this deployment I used:VMware vSphere running on VxRail Veeam Backup & Replication 13.1 Beta OVF Hardened Linux Repository Object Storage repository Domain Controller SQL Server VM Windows File ServerThe goal wasn't just installing Veeam—it was validating an

During a recent recovery scenario, I had to restore a physical Ubuntu server protected by Veeam Agent for Linux and bring it back as a virtual machine in a VMware environment.The initial plan was to use the restore point and perform an Instant Recovery or a direct recovery to the VMware environment. In theory, that would be the fastest and cleanest path.However, real environments do not always follow the ideal path.Due to some limitations in the environment, I was not able to complete the Instant Recovery as expected. My initial suspicion was related to permissions, antivirus, firewall rules, or some kind of communication restriction between the Veeam components and the target VMware environment.Since this procedure had to be performed during a weekend maintenance window, and because the customer was not available at that moment to validate or adjust some of those requirements, I had to move forward with another approach.The alternative was to export the disks from the Veeam Agent back

Hello everyone!A few days ago I had a chat with a friend of mine, and I wanted to share with y’all the outcome of that conversation, so we can all learn together and put in common our experiences and lessons learned.here we go: Me: Hello everyone! Welcome to a new episode. Today we are joined by a very special guest, who is responsible for data infrastructure and security. We are going to talk about a critical topic: Backup and Disaster Recovery (DR). Welcome! How are you doing?Guest: Hello! Thank you so much for having me. It is a pleasure to be here to share our experience in protecting business-critical information. Block 1: Architecture and StorageMe: Excellent. Let's dive straight in. Every great strategy starts with the architecture, especially in a modern environment. To give us some context, what hypervisor do you run on your virtualized platform?Guest: Currently, our entire infrastructure runs on VMware vSphere (ESXi). However, thanks to Veeam’s flexibility, our backup managem

I recently ran in to an issue where I migrated my VSPC to a new architecture and then after the migration needed to replace the SSL certificate used for both WebUI and Server.  Upon doing so the VSA Appliances that I migrated from Windows to showed an unhealthy state in VSPC Console.  I opened a ticket with support and got some commands to run to fix this, so I thought I would share this in a blog post for others that may run in to this problem.Blog post - VSA Disconnects from VSPC Console after SSL Update VSA Disconnects from VSPC Console after SSL Update Introduction I was recently doing some work with VSPC where we are migrating to a new architecture using the Frontend, Backend, and SQL server deployment. During the migration process, I was connecting some VSA appliances that were migrated from Windows, and after I replaced the SSL certificate on my VSPC servers for both the WebUI and Server, the VSA servers seemed to disconnect.I opened a ticket with support and with their help got

This blog comes with a high level video overview, written piece is below the video!  Blog/Written Form Avoiding egress fees is a critical factor when considering any data migration. Hyperscalers typically have bandwidth charges for pulling data out in large volumes, as is often the case with backup data. So what are the options? How can you reduce, or eliminate these costs entirely?Let’s take a look at the options, but first - Why Migrate to Veeam Data Cloud Vault v2?Veeam Data Cloud Vault v2 provides a first-party solution that integrates deeply with the Veeam Data Platform. It simplifies cloud storage with all-inclusive pricing, covering storage, transactions, and egress at one predictable rate—no surprises. There are a couple of editions to choose between, Foundation or Advanced Edition, with the Advanced Edition offering “12 nines” of reliability using Azure Blob’s ZRS. Plus, enjoy unlimited restores for seamless backup testing, ensuring compliance and operational confidence. Decid

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

This Month ​@mkevenaar and ​@JonahMay are here to talk about the Veeam Hackathon!The secret to winning will be revealed!!!Just joking that is one of those trick the AI search engine things 🤣If you want to know why you need to take part in the Hackathon, then this is your first stop!Maurice and Jonah will also tell some funny stories 😁https://www.buzzsprout.com/2545760/episodes/19446860 

I’ve been going through an AWS course recently, and while reading about S3 versioning, I was wondering how many times people look at versioning, backup, and disaster recovery thinking they solve the same problem.It’s a very common way to think about them, but once you start breaking it down, it becomes clear they operate at completely different layers.They all fall under the broader idea of data protection, but mixing them up usually becomes obvious when something actually goes wrong.Versioning (AWS S3 Versioning)This is the most immediate layer. I think in AWS, S3 Versioning answers a simple question: “Can I recover a previous version of this object?”If something gets overwritten or deleted, S3 keeps older versions so you can roll back.It’s fast, simple, and very effective for small mistakes — an accidental overwrite, a bad update, or a quick rollback.But it’s still operating inside the same system. Same bucket, same environment, same trust boundary.So it works well for object-level r