Blogs and Podcasts

The Veeam Software Appliance v13 brings a new level of simplicity, security, and efficiency to modern data-protection workflows. Built on a hardened Linux foundation and designed for fast, consistent deployments, the VSA is an excellent option for organizations seeking a streamlined, appliance-based approach to Veeam Backup & Replication.In this guide, I provide a practical overview of how to configure the Veeam Software Appliance v13 and highlight the main features that make this version stand out. Why VSA v13 Is a Major Step ForwardSecurity by DesignVSA v13 was built with a strong security focus from the very first boot. It includes: A minimal Linux operating system, drastically reducing the attack surface SELinux in strict mode, providing advanced policy enforcement SSH disabled by default, preventing unnecessary access paths With these measures, the appliance starts in a hardened state aligned with modern backup-security best practices.  Straightforward Deployment & Int

My journey with Veeam began in 2020, right in the middle of the pandemic, a time filled with uncertainty, challenges, and a lot of learning. Troubleshooting and analysis weren’t easy at first, but something quickly stood out to me: the Veeam Community.A space where experienced professionals shared knowledge generously and newcomers like me could grow by learning from real-world experiences. I started quietly, absorbing everything I could, and eventually felt the desire to give back. Helping others who faced the same difficulties I once did became a natural part of my routine.One moment that really moved my story forward was when Christian invited me to write posts for his blog. That opportunity boosted my confidence, helped me grow faster, and brought me closer to community members I deeply admired, including the Veeam 100, which slowly became a personal dream.Coming from the outskirts of Belo Horizonte, I’ve always valued every step of my journey. Some people doubted me along the way,

Object First OOTBI (Out-of-the-Box Immutability) is a purpose-built, secure, and immutable backup storage solution engineered specifically for Veeam Backup & Replication. By combining storage performance, immutability, and simplicity, OOTBI helps IT teams achieve reliable data protection while reducing operational overhead.Also, OOTBI eliminates the complexity associated with traditional backup storage by offering an appliance that you can deploy, configure, and integrate with Veeam in minutes. Below are some article relating to Object First OOTBI.Steps to configure Object First OOTBI Appliance | Veeam Community Resource Hub Enable Honeypot on Object First | Veeam Community Resource Hub  Steps to integrate OOTBI with Veeam Backup and Replication and Perform Backup and Restore | Veeam Community Resource Hub Comparing OOTBI by ObjectFirst to VHR | Veeam Community Resource Hub Object First Appliance Setup and Remote Connection Options | Veeam Community Resource HubRole-Based Access Co

Good evening, wonderful community!I'm not very active anymore, but you’ve always stayed close to my heart. To my fellow Windows users: I revisited some code, updated a topic from last year and completely rebuilt it for the 2025 version.I'm talking about: https://community.veeam.com/blogs-and-podcasts-57/direct-to-windows-object-storage-on-premise-with-minio-6055Are you still looking to test direct-to-Object Storage in an on-prem Windows Server environment? Well…This time, I used a simple internal setup, used purely for testing and educational purposes, yet fully on-prem and Windows compatible:Proxmox VE 8.4 Veeam Backup & Replication 12.3.2.3617 MinIO Server Community Edition 2025Note: as before, this setup is intended strictly for internal testing and educational use.Prepare your Object Storage Windows ServerI set up and updated a Windows Server 2025 for MinIO Community, keeping it in a Workgroup.This time, the VM had a single disk with 100GB allocated for both the OS and data.The

Hi folks, as of today, V13.0.1 for Veeam Backup & Replication is generally available! This release also supports Windows Server versions of VBR.In addition, Veeam Recovery Orchestrator (VRO) v13.0.0 and some other products like Veeam ONE v13.0.1 and Veeam Service Provider Console v9.1 have also been released today. So I went into my lab and just started the upgrade procedure from my Veeam Recovery Orchestrator Environment / VRO 7.2.1 → 13.0.0.See the steps below and hopefully no issues… Download the binaries from: Discover the Latest Version of Veeam Solutions. And make sure you have a backup of your current installation 😀 Step-by-step in Screenshots: If nothing special mentioned, it’s in my case a Next, Next, Finish process... Goodbye old icons?                         oops, let’s see… I just copied the mentioned warning in the clipboard: Mostly deprecated features (within VBR), wh

Hey everyone,Let’s kick this off by highlighting that as of this moment, Microsoft SQL Server 2025 has not yet been validated for the Veeam Data Platform, as it was only made GA yesterday the 18th November 2025, so the information I’m providing here is in preparation for the inevitable support when it’s passed through Veeam’s QA.Microsoft have now released Microsoft SQL Server 2025 and in reviewing the changes, I stumbled upon some insights that I thought would be worth highlighting to those still using Microsoft SQL Server to power their Veeam Data Platform installations.Starting with Microsoft SQL Server 2025 Standard Edition, Microsoft are making two key changes that will impact scalability; an increased CPU core count, and increased maximum RAM limits. Now they are:CPU Socket Count: This is unchanged and still a maximum of 4x CPU Sockets. If you’re finding idle cores a lot with your SQL Server instance, make sure this isn’t your limit! CPU Core Count: This is increasing 50% from a

Boosting Resilience in Bare-Metal Active Active Clusters: 4 and 5 Node Control Plane Architecture (4.17 ⬆ Version)  Organizations running active-active deployments across two locations—especially those hosting stateful workloads like OpenShift Virtualization VMs that run only a single instance—depend heavily on the underlying infrastructure to guarantee availability.While traditional virtualization platforms handle this natively, running these workloads on OpenShift bare metal introduces new architectural considerations. The Challenge: What Happens When the Primary Site Fails? ⚠️In typical stretched OpenShift clusters, the control plane is often deployed in a 2+1 or 1+1+1 topology.But if the data center hosting the majority of control-plane nodes goes down: The surviving control-plane node becomes the only source of truth for the cluster. That single node must switch to read-write mode and act as the exclusive etcd copy. If that node fails… recovery becomes catastrophic, especially

I am currently working on my first larger V13 deployment outside of my lab. There are a few stumbling blocks here, because the procedure is slightly different from V12 and the Help Center is unfortunately not yet complete at this point in time (Veeam is working hard to change this quickly and have it complete soon).One of these stumbling blocks was connecting the Veeam VBR V13 server to the Veeam ONE V13 server, which I would like to describe to you in this post. First off, my problem was a user/login issue.Firewall PoliciesIf the servers are located in separate networks, the appropriate firewall policies must always be configured.https://helpcenter.veeam.com/docs/one/userguide/ports.html?ver=13Access to host managementAccess to host management via port “10443” on the VBR server must be available, and the login details for “veeamso” and “veeamadmin” or an other Host Admin and Security Officer must be provided.Creating usersWhen creating users, I made a crucial mistake that cost me a lo

This was my second V100, and it definitely had a rougher story than the first one. Mostly because my previous company — a Veeam VASP partner — basically shut down, and just a month before the event I had started at a new company. I had no clue what I’d be doing there, whether I’d still work with Veeam clients, or if they’d even let me attend.Actually, they told me I’d probably be assigned full-time to a client using a totally different backup system. Not exactly thrilling, but the location was super convenient (close to home), and given the collapse of my old company and how hard it was to find something else, I took the job.Luckily, the new company let me go and assigned me to another client using Veeam — a win, though one I’m paying for dearly 😅. At that point I regretted not flying in on Sunday to attend the Monday workshop I really wanted to join. But since spots were limited, I didn’t feel right reserving one without being sure I could go.sunset on flightI also regretted it becau

This year is my first as a Veeam Legend, and along with that recognition came an invitation to attend the Veeam 100 Summit in Prague. When first hearing I was invited, I experienced two emotions, excitement and trepidation. After all, this would not only be my first time visiting Czechia, it would also be my first time visiting the EU. However, seeing blog posts on the community from previous summits gave me an idea of what to expect. What I did not expect (but was pleasantly surprised about) was how quickly I was adopted into a small group of V100ers. Throughout the sessions I was able to understand their roles within their respective organizations, and their unique challenges, and afterwards when we went for dinner and to explore the city I felt that I was getting to know them as friends more than colleagues.Towards the end of the Summit and during the Dalrymple Toast and Brad Jervis Memorial Award presentation, I was struck by emotion while we remembered Brad and the impact he had o

Let's continue setting up our Proxmox Lab.Previous entry: Download the ISO file from the Proxmox site .I then wrote it to a USB Thumb drive to boot and Install, I use a Mac, so I did it with BalenaEtcher.Now, I will post a few screenshots of the installation process.I did the same steps on the three nodes, just changing the managing IP address and hostname, the rest, the same:Here, IP Adress and hostname!!the other two hosts look the same, different IP address and hostname. The OS installation is super simple, Now, in the next entry, we will get into details with the console, initial configurations and shared CEPH storage.Cheers.https://lfconsulting.org/building-a-lab-with-proxmox-part-2-hypervisors-installation

BackgroundRecovery tokens are available for agent and plugin backups. They allow for easy and secure access to backups within repositories from a remote system, without the need to allow access to the full repository via credentials. To keep things easy, Veeam decided to have a fixed timeout for these tokens of 24h once created. This is usually sufficient for most recovery cases. So, the token is delivered to the workload owner and he can recover his - and only his - workload within these 24h.Creating Recovery Token - Veeam Agent Management GuideCreating Recovery Token - Veeam Plug-ins for Enterprise Applications ChallengeWe recently faced the challenge to recover a large SAP-HANA system of more than 10TB database size. From the repository used (a Dell DataDomain in our case) the recovery took more then 24h. Therefore, the recovery will fail, as the token times out during the recovery. SolutionThere is no way to have VBR create longer valid tokens from the GUI. But there are PowerShell

Greetings community, it was so good seeing you last week. We've discussed during the sessions, and after about the strict DISA STIG password complexity, and password rotation, there is a forum on the public VBR when using hundreds of appliances. Since then I couldn’t sleep properly as I imaged myself changing dozens of appliances with the 2 default accounts. So I’ve built an script of course.TLDR Automate rotation of local OS accounts on VSA, Hardened Repos, and VIA nodes through Host Management API only. Handles OTP, does self change for veeamadmin, proper self flow for Security Officer, writes CSV for your vault. GitHub Code on GitHub: https://github.com/jorgedlcruz/veeam-appliance-password-rotate Important NOT OFFICIALLY SUPPORTED. Use at your own risk. Protect your env files. Move CSV to your password manager then delete local copy. Test in a lab first. What you get API only. No SSH into nodes. OTP prompt or TOTP secret. Self rotation for veeamadmin (uid 2000) using /v2/users

Hey everyone, I started a blog series for my obsession topic “Object Storage” and created 4 blog posts on “everything you need to know to size and architect for Object Storage”. My last and final one was around Benchmarking, which you can find here. Part 4/4 https://www.virtualhome.blog/2025/11/04/veeam-object-storage-benchmarking-part-4/This last part of the series concentrates on how to benchmark object storage systems and how to benchmark “Veeam I/O patterns” + “Object Lock Retention” settings. Feel free to have a look and give feedback :) This blog post was originally created to collect all my experience in a series with Object Storage.Here is a little sneak peak: https://www.virtualhome.blog/wp-content/uploads/2025/11/Benchmark-Testing.mp4?_=1The other parts of the blog you can find here: Sizing and Architecting for Object Storage with Veeam – Part 1 Sizing and Architecting for Object Storage with Veeam – Part 2 Sizing and Architecting for Object Storage with Veeam – Part 3 Sizing

The walkthrough of the official #VMCA 2022 practice exam question 02 is ready. 

The walkthrough of the official #VMCA 2022 practice exam question 28 is ready.Did you have to check the scenario document? Which section did you locate the information inside? 

The walkthrough of the official #VMCA 2022 practice exam question 07 is ready. 

The walkthrough of the official #VMCA 2022 practice exam question 01 is ready. 

Everything shown here is included in all OpenShift subscriptions.As enterprises shift from VMware to OpenShift Virtualization, one of the most common questions is: how do networking concepts map across? This post walks through key visual mappings to help make that connection.Figure 1: Virtual Machine Networking in OpenShiftThis diagram shows how VMs in OpenShift can connect to: OpenShift SDN (for pods and services), or External networks via Multus and nmstate. Supported interface types include: Linux Bridge VLAN Bond Ethernet This architecture is fully supported and replicates VMware flexibility at the node level. Figure 2: Core VMware to OpenShift Mapping Here we map: VM Network ➝ NetworkAttachmentDefinition (NAD) Virtual Machine ➝ OpenShift VirtualMachine resource Physical NIC ➝ Configured via NodeNetworkConfigurationPolicy (NNCP) Think of NAD as the way you attach your VM to a Port Group. Figure 3 & 4: OVS-Bridges and NADs OVS bridges are equivalent to Distributed Sw

Hi Hello everyone,I am here to share with you my experience configuring VBR for the Azure Local environment, a step-by-step guide to configuration.Link:KB4047: Veeam Support for Azure Stack HCIRenaming Azure Stack HCI to Azure Local - Azure Local | Microsoft LearnAzure Local solution overview - Azure Local | Microsoft LearnPrerequisites:Veeam Backup & Replication v11a or later (v12 or later recommended). Azure Stack HCI\ Azure Local registered in Azure. PowerShell and Azure modules installed. Administrative access to Veeam Server and the HCI environment. Azure Arc enabled (optional but recommended).Ensure PowerShellGet is updated (recommended)Install-Module -Name PowerShellGet -Force -AllowClobberSet-ExecutionPolicy RemoteSigned -Scope CurrentUserInstall the Az moduleInstall-Module -Name Az -Scope AllUsers -Repository PSGallery -ForceUpdate-Module -Name Az -ForceDuring the process of adding the Azure Local cluster dedicated to the HyperV environment, you will receive the following

Greetings friends! I have seen this question popping up since VSA was released. How do we monitor VSA, or any other hardened appliance? There is a clear announcement about support for things like this, bear this in mind before you continue. Grafana Dashboard for Veeam Software Appliance (Unofficial + unsupported)When you finish this article, if you follow all the steps, you should have something similar to this. It might be different according to your environment, number of days you select, etc.Dashboard – SummaryUptime and Latest Data Collection – Two main widgets that will show us if everything is alright. Appliance Information Table – Another great set of information, including Hostname, version, RAM, etc. SWAP is dynamic, if you have anything more than 0% colors will change. CPU Usage – Always good to keep a good track of the CPU usage, the query is granular and shows the effort and pressure per Core RAM Usage – Bit simple, just showing the % of RAM used. Query can be modified to s

Introduction In the first two parts of this series, we explored the why and how of using Group Managed Service Accounts (gMSAs) with Veeam Backup & Replication (VBR). If you missed them, check out:Part 1 – Why Use gMSAs with VBR Part 2 – How to Configure gMSAs with VBRThis third and final installment dives into security implications, introduces Dedicated Managed Service Accounts (dMSAs), explains the threat of Kerberoasting, and previews what's new with gMSA in Windows Server 2025.  1. Security Considerations: gMSAs in the Real World a) Overprivileged AccountsAvoid assigning excessive permissions like Domain Admin to gMSAs.Best Practices:Apply least privilege Use role-specific gMSAs (e.g. Exchange, SQL, File-Servers, but NOT DCs! - see below) Audit regularlyb) Password Retrieval AbuseOnly authorized systems can retrieve gMSA passwords. Compromised systems pose a risk.Mitigation:Harden GIP and other retrieval systems no other services on the GIP restrict network access (e.g. switch

🚀 Exciting news for Service Providers!Veeam Service Provider Console (VSPC) v9 just dropped, and it comes packed with some really cool new features. Over the past few days, I’ve been digging into one in particular—REST API proxying—and wanted to share what I’ve discovered, plus a small demo script that shows just how powerful this feature can be. So, what’s REST API proxying?Simply put, VSPC can now use a single API token to authenticate itself and then proxy requests to all your remotely managed Veeam products. That means you can manage everything from one central console without juggling multiple keys or credentials. A note on securityBecause a single API key can reach all your servers, it’s super important to keep it safe. Treat it like gold. 😄 When you create an API key, you can also enable “read-only access.” This applies not only to calls against VSPC itself but also to all proxied requests to your Veeam servers. If you’re just pulling information (like in my demo), enabling re

Hello everyone, I am sharing the migration of the Enterprise Manager database from Microsoft SQL to PostgreSQL.https://www.veeam.com/kb4409Part 1: Back up the Current Veeam Backup Enterprise Manager Database    Open an Administrative Command Prompt cmdcd  "C:\Program Files\Veeam\Backup and Replication\Enterprise Manager"Using the Enterprise Manager Database Migration Utility, create a Backup of the current Veeam Backup Enterprise Manager database.https://helpcenter.veeam.com/docs/backup/em/em_db_migration.html?ver=120Veeam.EM.DB.Migration.exe /file:"C:\Temp\BEMConf.emco" /backupemdatabase /encryptionpassword:1l0v3KB5 /encryptionhint:bestpasseverPart 2: Restore the Enterprise Manager Database Backup to PostgreSQL    Using the Enterprise Manager Database Migration Utility, restore the backup created in Step 3 to the destination PostgreSQL server.Veeam.EM.DB.Migration.exe /file:"C:\Temp\BEMConf.emco" /restoreemdatabase /encryptionpassword:1l0v3KB5 /servername:localhost /initialcatalog:Vee

​I’ve been using Veeam with IBM storage snapshots for quite a while now, and it’s been excellent. The integration works smoothly and gives you a lot of flexibility in how you want to configure things. One option is to let Veeam handle the snapshot orchestration and leave snapshots behind for a set amount of time. The other is to use IBM’s Safeguarded Copy feature, which gives you immutable snapshots controlled directly by the SAN. Because this is policy based and includes SAN Replication Policies, I opted for this option to have my production data in a second site, with Safeguarded copies there as well.Each snapshot can be browsed in Veeam, where you can see the virtual machines inside, and even use them for SureBackup jobs or lab environments that mirror production. Having snapshots that are only a few minutes behind production means your test or DEV environments are never out of sync. The ability to snapshot a PB of data ever hour is also quite impressive as a 1 hour backup window is