Blogs and Podcasts

Data is at the forefront of what drives organizations today. It drives businesses, powering operations, assisting with decision making and providing a competitive edge. At its core, Veeam Data Platform protects organization’s data, giving it resiliency and the strength to bounce back from disruption. To achieve ultimate resiliency, organizations need to encompass more than just backup, they need to think about recovery, security, intelligence and automation. With this, the monitoring and analytics provided within the Platform, empowers organizations to shift from reactive to proactive data resilience. This latest release continues to innovate, giving customers more options on how they want to consume Veeam.Veeam is all about giving customers choice, giving them the option to self-manage their backup environment, consume it as-a-Service, or utilize a Service Provider to help them manage data protection operations. With the latest news from Veeam, now you can utilize the Veeam

... how to successfully use Windows Server 2025 with Veeam v13 in a workgroupA well-known song by the famous Italian singer Domenico Modugno, called 'Meraviglioso', began like this:È veroCredetemi è accadutoDi notte su di un ponteGuardavo l'acqua scuraCon la dannata vogliaDi fare un tuffo giùIntroductionToday I’m going to tell you a true story.Last Saturday, a former colleague contacted me in order to request my help to resolve a complex situation involving one of his clients. I'm turning into a superhero!SituationThe architecture has been implemented with a Veeam Backup & Replication v13 server and a Veeam ONE server, both of which are operating in Workgroup on Windows Server 2025. The customer does not

Veeam released a new Cumulative Patch for Veeam Backup & Replication 11a: 11.0.1.1261 P20211211Includes a lot of new platform support and a few fixes. See detailed release notes:https://www.veeam.com/kb4245

Are you planning to build Veeam 13 environment on appliances only? Veeam 13 offers backup environment via appliances. VBR and VEM via VSA appliance and proxy with gateway servers via VIA appliance. Hmm, probably you need to consider windows component in backup environment. Of course if you are planning functionality of backup environment like:FLR for Windows Server Application backup  Guest Interaction Proxy (gMSA) Item-level Restore  FLR for Windows ServerIt is needed to define Windows “Mount Server” for repository for usecases:VMware replication job with Re-IP rules

 Upgrading Veeam ONE from version 12 to version 13 introduces significant architectural and security improvements, including changes to authentication and communication methods. Version 13 moves away from legacy protocols such as NTLM and WMI in favor of more secure and modern approaches like Kerberos and gRPC as discussed below.Note: There is a strong business and technical need to upgrade to Veeam ONE v13 in order to leverage Veeam Intelligence, enhanced analytics, and next-generation dashboard capabilities that improve visibility, reporting, and operational decision-making as shown below. For the detailed blogpost, please see 

I think part of the confusion around high availability comes from how universally we try to apply it.Once it works well at the application layer, the instinct is to push the same thinking everywhere else. If something matters, it should be highly available. Reduce downtime, remove single points of failure, make everything seamless.That logic starts to break down when you look at systems that aren’t serving users directly, like backup systems.There’s a discussion in the Veeam community where someone asked a straightforward question: how do you make Veeam for AWS highly available?One of the answers pointed in a different direction. Instead of treating it as something that must always stay up, the focus was on backing up its configuration and, if needed, redeploying a new instance and restoring it.At first, that feels counterintuitive. If everything else is designed for high availability, why not this as well?But it makes more sense once you th

 In this guide, we will discuss the steps to Update Veeam Backup & Replication to Build 13.0.1.2067 due to the following security Vulnerabilities. Veeam Backup & Replication 13.0.1.2067 delivers critical updates focused on strengthening security, improving platform stability, and enhancing integration across backup, cloud, and storage environments.If you have still not patched your VBR yet, you will find this guide very useful: https://techdirectarchive.com/2026/05/19/how-to-patch-vbr-server/

This article is intentionally for one specific scenario: upgrading an existing Windows-based Veeam Backup & Replication installation from v12.x to v13—including the issues that can come up in real-world upgrades.I already wrote a general blog post about patches/upgrades that serves as a guideline for practically all Veeam updates (pre-checks, order of operations, typical pitfalls, rollback strategy, change window, etc.). That guidance is still fully valid.   What about the VSA (Veeam Software/Server Appliance)?If you can/want to move directly to the VSA

Hi Community! If you use Veeam Backup & Replication to protect Linux environments, you may have encountered the strict requirements of its kernel modules. I recently had an interesting problem with a Oracle Linux 8.9 system running Unbreakable Enterprise Kernel (UEK).SituationThe plan was simple: use the Veeam Agent for Linux (VAL) in managed mode to backup some Folders and a PostgreSQL database. I needed something called "Application-Aware Processing" (AAP) to make sure the database was consistent, so I couldn't use 'nosnap mode' (which doesn't require the kernel module).TaskHere is what the environment looked like: Veeam Agent for Linux (VAL): 6.3.2 OS: Oracle Linux 8.9 Kernel (UEK): 5.15.0-205.149.5.1.el8uek.x86_64 Veeam module status: veeamsnap, 6.3.2.1207: added (via dkms status)IssueWhen starting th

 In this post, I intend to explore key concepts of Agentic AI, outline the risks posed by autonomous agents, and discuss mitigation strategies and emerging global standards that shape responsible agent deployment.This is a fascinating topic that goes beyond the traditional borders of IT cybersecurity.For each concept, threat, and mitigation strategy presented in the text, a practical example will simulate a customer interacting with an airline AI agent to manage a seat.Most of the content below is based on the “State of Agentic AI Security and Governance” and “Agentic AI – Threats and Mitigations” reports from the OWASP GenAI Security Project – Agentic Security Initiative (ASI).You can also get access to this article on my blog: 

AI in Production on OpenShift: Designing for Resilience, Portability, and Control At Red Hat Summit 2026 in Atlanta, Veeam delivered a lightning talk that reframes how platform engineers should think about AI workloads on OpenShift.The core shift: AI placement is no longer a technical decision — it's a business and risk decision."The question is no longer 'Can I run AI here?' — it's 'Where should this workload run, and under whose control?'" This post covers the key architectural principles from that session, the data that backs them up, and a concrete use case that shows what this looks like in practice. Why Placement Matters More Than EverThe assumption that AI lives in the public cloud is already outdated. The actual dis

 Ever wanted to chage your managed server from an IP Adress or DNS (shortname) to FQDN. Then you will find this article very useful. Since the move to version Veeam Backup & Replication (VBR) v13, we have seen that FQDN works more reliably in VBR/VSA due to strict reverse DNS requirements for certificate authentication, SSH, and agent deployment on Linux. IPs skip PTR lookups and often fail validation as demonstrated in this guide “Building VIHR: Ransomware-Proof Re

 In this article, we will discuss how to Leverage Azure Blob Storage as an Object Storage Repo in Veeam. Azure Storage Accounts provide the foundational management layer for storing cloud data in Microsoft Azure. For the entire blogpost, please see https://techdirectarchive.com/2026/05/16/leverage-azure-blob-storage-as-an-object-storage-repo-in-veeam/They create a unique, secure, highly scalable, and globally accessible namespace for your data. Azure Storage Account give you access to Azure’s core storage services. Such as the Blob Storage (object storage), Azure Files (SMB file shares), Queue Storage (messaging), and Table Storage (NoSQL key-value data).

I have been recently reading a great book on German philosophy and hit upon a debate on language that can be easily time travelled to today with all the questions surrounding AI. After all they are not called Large Language Models for nothing.  Yesterday evening when reading about Johann Gottfried (ha that is my first name in German Geoffrey 😁)Herder and Johann Georg Hamman both born in the 17 hundreds it suddenly struck me the debates going on back then have taken on a whole new meaning with LLMS. Do LLMs think? I asked AI about Herder and Hamann’s views:“Philosophers like Herder and Hamann argued that meaning is rooted in embodied, social, historical experience you can't separate words from the life lived around them. On this view, LLMs produce the shape of language without the substance.”This i

Digital Sovereignty  A few weeks ago, I was at the Women in Tech Global Summit in Cape Town, and one topic kept coming up in almost every conversation: digital sovereignty.I went into it expecting the usual conversations—compliance, regulations, cloud regions. And yeah, those came up.But that’s not really what people leaned into.The discussion felt different. It was less about frameworks and more about control.It felt more like a question than a concept: if you don’t control your data and infrastructure, do you really control your future?What made it even more interesting is that this wasn’t just coming from one event. Around the same time, the TDGI Africa Symposium was bringing together p

I recently worked on another project with a major customer where we unfortunately reached the limits of Veeam Backup & Replication’s out-of-the-box features for Scale-Out-Repositories and had to find a workaround. Our ChallengeOur challenge: The customer has over 100 scale-out repositories, each with different permissions depending on the application and operating system. We had to migrate the VBR server to a new Windows Server. However, this also meant that the users created locally on the old server were no longer available. In principle, this wasn’t a problem—we simply recreated the same users on the new server.However, this is where the problem comes in. The SOBR permissions include the old user as “OLDSERVERNAME\USERNAME,” which we then have to replace with “NEWSERVERNAME\USERNAME.” If we didn’t replace these, our Enterprise Plugins would no longer have permissions to write their backups.Unfortunately, there is no function

With Veeam Backup & Replication v13, we’re not only getting a new version number and plenty of new features — we’re also seeing a deliberate clean-up of the product: some capabilities are now deprecated (no longer available for new configurations), while others have been discontinued (removed completely). That’s not unusual for a major release, but in practice it can affect the areas where environments have “organically” grown over many years: job designs, repository settings, restore habits, and legacy workflows that somehow always worked.So this article is not an upgrade how-to. Instead, it focuses specifically on these features: What changes? What did the feature do? Why might you still run into it operationally? And what’s the modern

Hi there,After the first part of this topic, now is time to jump into the good stuff, the main thing here is to be notified every time something changes or goes "wrong".Lets follow u the screenshots, from Setup, to Notifications setup, to finally monitor a couple servers and services.As I said before, this is basic "alive" monitoring, not statistics and deep monitoring, there are other cool tools for that, the topic here is first line, quick and easy! lets go:This is my Uptime-Kuma Dashboard, after install, lets go to Settings, click on your name up right, and click settings, under Settings, we will find an easy and clear menu to config the tool, f

Hi Everyone, Last Tuesday I was lucky enough to attend VeeamON in NYC. This time I had to be on the best Burke behavior since I would be at the bar. Before you are shocked, this was the experts bar so no worries about Geoff’s infamously bad bartending skills for those who might have heard about them.I flew into Kennedy airport on an extra early flight to make sure that nothing went wrong. Flights and airports are not immutable unlike good backups so you never know when they will hit you with Delayware or even worse Cancelware! Flying in over the city I saw down below the Verrazzano bridge and it occurred to me that I had never seen it up close. I packed light (Vanguard Backpack!) so took the subway to Bay Ridge station in Brooklyn. Since joining marketing I have changed from the introvert, photo shy personality to a more extravert nature and I am always thinking of that perfect marketing shot (which can then be lowered somewhat in quality by my selfie!).

If the backup jobs fail and show an error message is “Unable to allocate processing resources. Error: Unable to find Hyper-V hosts where VM 'xxxx-xxxx-xxxx-xxxx-xxxx' is registered: Failed to connect to Hyper-V Integration Service on host, port 6163”. I tried to review the settings, and all of them look fine, but the backup jobs failed always. I have run into these issues sometimes, it’s easy to solve, you just need to reboot the Veeam management server or restart the Veeam services of the Veeam management server.

While upgrading to Veeam Backup for Microsoft 365 8.4, you might notice the following message: Connection to PostgreSQL is not encrypted. Enable TLS in PostgreSQL for secure communication.  VB365 checks whether the connection to the PostgreSQL database uses TLS.If TLS is not explicitly enabled, the warning is shown regardless of whether PostgreSQL is local or remote. If the PostgreSQL database is locally hosted on the vb365 server itself, this traffic does not leave the host. But if you have multiple proxies, those proxies also connect to the database, and this traffic leaves the network. So in those scenarios, it might be good to have this traffic encrypted. I will describe here how you can enable this traffic to be encrypted. Step

 I ran into a situation recently where one of our VSPC servers stopped working after a Windows patch update. The portal was dead. I went ahead and upgraded to VSPC 9.2 and that brought everything back online. Except the April license usage report never got generated. It was stuck. I could not finalize it or submit it. If you are using VCSP /w rental licensing, you know that the report has to go to Veeam every month. A missing one is not something you can just ignore (Not for lack of trying 😊). I opened a support case and Veeam Support gave me a procedure to regenerate the report. It worked. I am documenting it here because I could not find this written up anywhere and I know other providers might encounter something similar. Step 1. Back up the VSPC SQL database.Take a fresh backup of the VSPC database first. Veeam covers this in KB1471. If the SQL work later goes bad you want something clean to restore. Step 2. Update the configuration o

 VBR v13 defaults to PostgreSQL for new installs, so for a lot of environments the question is no longer “Should we care about PostgreSQL?” It is “When do we move, and what do we need to fix after we do?”If you are still running SQL Express, the answer is usually sooner than later. If you are running a licensed SQL Server only because VBR needs it, there is a good chance you are carrying cost and patching overhead you no longer need. And if you already migrated but the console feels slower than it used to, that is usually not because PostgreSQL is a bad fit. It is because the default PostgreSQL settings are conservative and generic, while VBR is not.This is the part people miss. The migration itself is usually the easy piece. The performance conversation starts after the restore, not before it. First question: do you actually need to migrate now? Not every environment needs to sprint in

TL;DROn May 14, 2026, the PostgreSQL Global Development Group released security updates for all supported branches (18.4, 17.10, 16.14, 15.18, 14.23), fixing 11 CVEs, several rated CVSS 8.8. If you run VBR on Windows with PostgreSQL as your configuration database, you are affected. Veeam does not auto-update PostgreSQL. You have to do it yourself! Here is what you need to know and what to do about it. Why this matters for VBRSince VBR v12, PostgreSQL has been the default (and recommended) configuration database. VBR v13 GA ships with PostgreSQL 17.6, and the latest cumulative update (13.0.1.2067) bumps it to 17.9.1. Both versions are below the patched 17.10 and therefore vulnerable to all 11 CVEs disclosed on May 14 (PostgreSQL release announcement).If you are still on