Community

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 distribution of AI/ML workloads today:65% on-prem, colocation, specialist GPU clouds, or network operatorsAnd placement has real operational consequences: The driver behind this is a shift toward AI sovereignty — and it goes well beyond data residency.Sovereign AI: Cont

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 Software A

How can I get VAW to power the computer on (from shutdown, not from sleep or hibernate)?I set the backup to turn the system on at 01:30 and run the backup, but it actually started when I switched the computer on later in the morning.Is there some Windows registry, or BIOS setting that is needed?Thanks, David 

Hi ALL,I am running VBR11 and VBAz 4.0, recently all my AzureVM backup started failing. I still have over 3months of license validity.I can no longer connect to the VBA from my VBR console only can access from the browser.We are getting the following error; "Client secret has expired. Use a valid client secret or renew the application on the Service Account Type tab.This was done however the issue still persists.My Infra is still running older systems so upgrade was not an option hence no support available.Any thoughts?

... 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 have a domain, and therefore no Active Directory from which vulnerabilities could be inherited. They don't have a DNS server, so I've configured hosts files on both servers.Having verified that static IP addresses were configured as part of the same VLAN and that firewalls on the V

Hi All, I really hope someone can help! I have Veeam Backup for Microsoft 365 which is now running in community edition. I had two backup jobs, S3 to Wasabi and they have been deleted. I can see the repositories contain large amounts of data but when I attempt to restore files utilising the Veeam M365 console it only shows one restore point date.Previous backup jobs (excluding the deleted backup jobs) I had created and ran a backup copy from the existing backup job from Wasabi to a newly created Azure storage account and this appears to have worked. As I no longer have the backup jobs, what are my options of being able to restore these backups once I no longer have access to Wasabi? Thank you,Scott

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 Instant Recovery of  Microsoft Windows workloads Instant Disk Recovery for Microsoft Windows workloads Application item restore Secure restore for workloads with ReFS volumes Scan Backup for workloads with ReFS volumes SureBackup Guest OS file restore for Microsoft Windows workloads with ReFS volumes, or from workloads with data deduplication enabled for some volumes  Guest Interaction Proxy Based on KB you can use:appli

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 think about what problem you’re actually trying

 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, the best approach is usually a greenfield installation: deploy a new VSA and rebuild your jobs step by step according to current best practices. This is not only the cleanest migration path, but also a great opportunity to remove legacy baggage and review/update your configuration in detail — aligned with best practices and your specific use cases.There is also a migration path from Windows (e.g., 12.3) to VSA 13.0.1, but it comes

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 the backup job from the VBR server, the task fails, returning this sequence of errors:Failed to create volume snapshot Failed to take volume snapshot Failed to perform managed b

Hello everyone,I need some help with an issue and hope I won’t have to contact support.  I’m seeing several failures on a file backup with the following error message:Failed to perform repair backup Error: Agent: Failed to process method {NasMaster.TransformMeta}: The process cannot access the file because it is being used by another process.Error: Agent: Failed to process method {NasMaster.TransformMeta}: The process cannot access the file because it is being used by another process.Processing finished with errors  I checked the logs, and the only thing that stands out are warnings like:Masks are not applicable for the server pathSo I understand that my exclusions cannot be taken into account. I can’t seem to find a solution; I ran a Backup health check which returned the error:Failed to perform repairing backup Error: Agent: Failed to process method {NasMaster.TransformMeta}: The process cannot access the file because it is being used by another process. I don’t understand how to ide

 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: Agentic AI Security: Managing the Autonomous Risk - CloudnRollContext of the New Agentic Era ChallengesAgentic AI represents the next evolution of artificial intelligence, building on foundational components such as Large Language Models (LLMs) and Retrieval-Au

Hello!I look through logs, and see this texttransport mode: [hotadd], max sectors to read/write: [8192], async I/O: [unsupported]The backup operation ends successfully, but why could possibly async I/O be unsupported for hotadd? I've changed VBR VM (it's a Default Proxy) SCSI Controller type to VMware Paravirtual and it didn't help and sincerely I'm out of options to guess. Can you suggest me a direction to dig?

 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).Types of storage accountsAs mentioned above, Azure Storage offers several types of storage accounts. Each type supports different features and has its own pricing model. To learn more about blob storage, please take a look at this Microsoft Learn article. This matrix below outlines the different Azure storage account tiers. It shows th

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 is opposed by the Functionalists: The most well known modern one being Alan Turing who broke the German enigma code in WW2:“if a machine is behaviourally indistinguishable from a thinking huma

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 policymakers and technologists to talk about very similar topics—how to reduce dependence on externally defined models, how to build data protection and AI frameworks that actually reflect local needs, and how Africa positions itself as a real participant in shaping the global digital landscape.So it d

Hi,we have Veeam Backup and Replication v13, Community Edition, Build 2067 on Microsoft Windows Server 2019 with Hyper-V.When I try to add a Veeam Data Cloud Vault from the Austria East Region I get the following error:The error occurs during authorization of the backup server after I login using Microsoft, including MFA and after I answer the question if I want to stay signed in (Yes or No has the same effect).If I add the same VDCV Repo on another installation of Veeam (different customer, paid version) it works.I installed the Veeam Console on the only VM of the server and I got the same error.AI suggested to check the version of a specific DLL, which is 2067.I installed a trial license, same error.I disabled all security filtering on the firewall temporarily and checked the logs.Any ideas, how this can be fixed? Thanks a lot for your help!Thomas

Greetings from Puerto Rico,The AsBuiltReport for Backup for Microsoft 365 has received significant community contributions and now supports documentation for version 8.4. This update represents a major milestone in the ongoing development of this reporting tool.In addition to these enhancements, we updated the diagram to incorporate Veeam's latest infrastructure icons, providing a more modern and visually consistent representation of your backup environment. We also added a new chart to visualize backup repository space utilization, along with improvements to several existing charts, offering better insights into your backup infrastructure performance and resource allocation. I'm grateful for the community's continued support and contributions, which make this tool better every single day! Sample ReportNew Features and changes:## [0.4.0] - 2026-05-20### Added- Add Dependabot support- Support for Veeam Backup for Microsoft 365 v8.4 (upgraded from v8.3) @acgdickie- Support for PowerShell

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 path forward? I’ll go through each deprecated and discontinued feature, outline the impact, and share practical recommendations—so you don’t find out only when creating a new job or during an actual recovery that: „Wait… this isn’t available anymor

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, from appearance to proxy, etc. Im going to deep dive into the Notifications menu:Click on Setup Notification Now, let's check it out, in the main menu, at the very bottom, we have the option to monitor TLS certificates and Domains expiracy, this is awesome! Im super happy Im not missing a cert renovation anymore, and no entries into my calenda