Blogs and Podcasts

Often when looking at Best Practices guides, software documentation, or even during education, I see and hear the answer “It depends.” This is probably my least favorite answer, as someone who likes to understand why something is right or wrong. While it does “depend,” it makes it very tough for people starting out to understand the “why” in many cases. One thing that is not going to be the same for every Veeam user is how the jobs are created. Over the years, Veeam has made some fantastic changes and for most environments, Per-Machine backups are the way to go, the minimal savings you get do not compare to the performance and portability of this mode.  Additionally, with this mode you can often add a HUGE amount of VM’s to a job and just forget about it. I know of people who have 1 job. That is the definition of an easy button!Today I want to discuss some reasons that myself and others have gone the other direction to separate jobs.  While I keep my jobs as large as I can for the perf

Well, another week and another blog as we are at #9 of 10 today.  This blog focuses on Universal CDP and its fitment in to v13.  Check out the link below and the blog.Universal CDP in v13: Where It Fits Universal CDP in v13: Where It Fits Introduction Continuous data protection gets attention because it promises extremely tight recovery points, but that does not mean it belongs everywhere. Universal CDP in Veeam v13 should be evaluated as a targeted design choice for workloads where small amounts of data loss carry outsized business impact.That framing is important in production. CDP is not a replacement for every backup or replication workflow. It is an additional protection method that changes how teams think about network paths, storage performance, and the operational meaning of recovery success. Match CDP to Real Recovery Needs The strongest CDP use cases are the ones where recovery point objectives are already difficult to meet with conventional periodic jobs. Systems with freque

Hi everyone! Hope this will be helpful. The idea of the scheme was to imagine everything that could require troubleshooting and put that on the scheme. v13.1 with lots of improvements and new workloads is in progress. Attached you can find both .jpg and .pdf formats, in second one you can put any word in search and find it on the scheme if it exists there. Created in Miro, handmade with lots of user guide research :)

other possible Topic-name: When a PostgreSQL Shows Up That Isn't Yours - A field report on a new AAP warning after the upgrade to 13.1 — including the workaround Veeam Support cleared me to publish.  The symptomAfter upgrading a customers environment (doesn’t matter if VBR on Windows or VSA) to 13.1, a previously clean job started completing with a warning: a VM backup of (in this example) an Exchange server with Application-Aware Processing (AAP) enabled. Exchange processing itself was fine. The warning referred to a PostgreSQL instance that isn't really in access of the customer: an embedded component of (in this case) Trellix/McAfee Email Security running on the same guest OS.The customer told me: Vendor-managed, no credentials, no supported way to administer it.So Veeam can't authenticate against it — and flags that with a warning. The same job ran clean on the previous version.  What changedSupport's original answer was (and i have the confirmation to do this post about it): With

A greeting to allI have deployed a POC of OLVM 4 host Hypervisor version 4.5.4-1.0.31.el8, to replace Vmware infrastructure.I am successfully testing the Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization 4.1. I enclose a fairly comprehensive guide with the ste by steps of configurationWith ISO version 12.1.2.172 the Ovirt KVM plug-in is already installed.for those who do not have latest version of VBR installed download and install the pluginDownload plug inhttps://www.veeam.com/it/products/downloads.html?ad=top-sub-menuVeeam Backup for Oracle Linux Virtualization Manager and Red Hat VirtualizationPerform the following Operations   Architecture OverviewArchitecture Overview - Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization • Virtualization managerVirtualization manager is a Linux-based physical or virtual machine that manages oVirt resources such as VMs, hosts, clusters, storage domains and networks. • Backup serverA backu

Hope everyone managed to view the Global Launch last week, if not and you missed it, here is the on-demand replay: https://www.veeam.com/veeamon-global-launch In addition here is a 40min video with the highlights of the v13 launch last week from product marketing. Demos include High Availability, SAML integration, Data Resiliency Daily Summary report and more.   The latest update from RICKATRON with regards to v13 upgrade is available here:Thanks again 😀

As many of us know, there is a migration path from Windows to VSA Appliance for VBR.  Recently, this week I migrated another of our sites, but due to forgetting to remove the Windows VBK server from Enterprise Manager after I did the migration I could not enable some licensing checkboxes in the VSA.  I opened a support ticket and worked with them to use PowerShell on the VSA to remove the link to VEM.CAVEAT - Please ensure to have a configuration backup and snapshots of your Veeam infrastructure for rollback, just in case.After doing this, I thought it would make for an interesting blog post to help others with this type of issue, so see the link below to my blog and the blog post itself.  Enjoy.Blog - How to Remove Enterprise Manager Link after VSA Migration from Windows How to Remove Enterprise Manager Link after VSA Migration from Windows Introduction Veeam has a migration strategy for moving your Windows deployment to the new VSA Appliance by following KB4800. During this process w

 Original article: What's New in Veeam 13.1 for HPE Solutions - CloudnRoll #VeeamCommunityChallenge This article summarizes Veeam v13.1 and related release updates specifically relevant to the HPE and Veeam partnership, organized by product area: Veeam Backup & Replication, Veeam ONE, Veeam Recovery Orchestrator, Veeam Service Provider Console, and Veeam Kasten.This article includes the features and integrations that are clearly related to HPE solutions in the supplied release materials.The focus is on new HPE integrations, HPE platform support, and HPE-related feature enhancements that improve protection, recovery, observability, service provider operations, and protection for cloud-native applications.SummaryIn the v13.1 release and related release updates, Veeam significantly expands support for many HPE customers´ scenarios.In Veeam Backup & Replication v13.1, the most notable additions include native support and enhanced usability for HPE Morpheus VM Essentials, as well as

In my last blog post, I covered the basics and requirements of HA in v13.0.1. With a short how-to and a step-by-step guide, I wanted to show how quickly HA can be set up in your own environment and what added value it brings. In my day-to-day work as a Systems Engineer at Veeam, I've also come into contact with HA at many customer sites. Most of the feedback was positive, but unfortunately there were also some issues around stability and node connectivity. That's why I'm even more excited about the release of v13.1, which brings further improvements to this topic. In this article, I want to focus on these improvements: what's changing in the new version, and what else we can expect. For everyone who just wants the summary, here's the TL:DR: TL:DR  Requirements for HA remain unchanged (2x VSA, VDP Premium license, Remote Console) — HA is still exclusive to the Veeam Software Appliance. Cross-subnet deployment: HA nodes no longer need to be in the same subnet. A cluster DNS name now re

Hello everyone!A quick update for all of you!The waiting has an end!Veeam has officially released Data Platform 13.1 along with all its core components.Don't let the "point release" label fool you—this update is packed with over 70 new features!If you want to dive into the details, you can find all the essential information and documentation right here:🛡️ 𝐕𝐞𝐞𝐚𝐦 𝐁𝐚𝐜𝐤𝐮𝐩 & 𝐑𝐞𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝟏𝟑.𝟏:• What’s New: https://www.veeam.com/veeam_backup_13_1_whats_new_wn.pdf• Release Notes: https://helpcenter.veeam.com/rn/veeam_backup_13_1_release_notes.html📊 𝐕𝐞𝐞𝐚𝐦 𝐎𝐍𝐄 𝟏𝟑.𝟏:• What’s New: https://www.veeam.com/veeam_one_13_1_whats_new_wn.pdf• Release Notes: https://helpcenter.veeam.com/rn/veeam_one_13_1_release_notes.htmlAnd for the service providers under you like me, Version 9.3 of the service provider console has also been released!☁️ 𝐕𝐞𝐞𝐚𝐦 𝐒𝐞𝐫𝐯𝐢𝐜𝐞 𝐏𝐫𝐨𝐯𝐢𝐝𝐞𝐫 𝐂𝐨𝐧𝐬𝐨𝐥𝐞 𝟗.𝟑:• What’s New: https://www.veeam.com/veeam_console_9_3_whats_new_

One of the biggest challenges in AWS data protection projects is the time required to provision all the necessary infrastructure. This timeline can vary significantly depending on the customer’s existing environment, cross-team dependencies, and the level of customization required for each deployment.With the goal of accelerating this process and bringing greater consistency across environments, I started developing a CloudFormation-based approach that leverages Infrastructure as Code (IaC) to automate the deployment of the required resources.The solution delivers a fully operational Veeam Data Platform Premium v13 server within a VPC that is completely isolated from the internet. Administrative access is provided exclusively through AWS Systems Manager (SSM) Session Manager, eliminating the need for public IP addresses, bastion hosts, or open inbound ports. All management and operational traffic remains securely within the AWS network.My intention is to share this initiative with the

We recently had a customer environment running Veeam Backup & Replication (VBR) 12 on a Windows server that was approaching end-of-life. The existing setup also included a local Windows repository for short-term retention and an HPE StoreOnce repository used for long-term retention.With both the VBR server and the StoreOnce platform approaching their lifecycle limits, we needed to plan a migration that would:Replace the aging VBR server Maintain the existing Veeam configuration and backup jobs Preserve all existing backup data Replace the legacy short-term repository Move the long-term backup data away from StoreOnce Improve the security posture with immutable backup storage Continue using the customer's existing socket-based Veeam licensingThe goal was not simply to build a new Veeam server, but to move the customer to a more modern and secure backup platform without losing access to the existing backup history. The Existing EnvironmentThe starting point consisted of:Veeam Backup

Welcome to My First Technical Blog PostOver the past several years, I have had the opportunity to work with a wide range of Veeam technologies, including Veeam Backup & Replication, Veeam Backup for Microsoft 365, Veeam ONE, and the Veeam Service Provider Console (VSPC). Throughout these projects, I repeatedly encountered features that are incredibly powerful, yet often overlooked in day-to-day operations.One such feature is API Proxying via Veeam Service Provider Console (VSPC).In this article, I would like to share practical experience, technical insights, and real-world use cases around this capability. My goal is to demonstrate how service providers can simplify automation, reduce complexity, and leverage existing infrastructure more efficiently.If you have worked with VSPC API Proxying yourself, I would be happy to exchange ideas and experiences.Let's dive in! 👉What is VSPC API Proxying?Most Veeam users know the Veeam Service Provider Console as a centralized management platf

This week we are on to blog #8 in my v13 series.  Check out the link below on my blog site and the blog article.Blog - v13 HA in One Lab Session v13 HA in One Lab Session Introduction High availability only matters when something fails. In a backup platform, that means the design should preserve management access and backup service continuity well enough that the environment remains useful during a component outage.Veeam v13 places new attention on HA as part of broader platform resilience. For production teams, a short lab session should focus on one practical question: when a node or service becomes unavailable, what keeps working, what pauses, and what dependencies become the real bottleneck? Identify the Dependency Chain Before any failover test begins, the environment should be mapped in simple terms. Storage, identity, networking, DNS, certificates, and any shared services all influence whether the backup platform is truly resilient or just appears redundant on a diagram.This is

If you’ve ever had to deal with the pain that comes after deploying the Veeam Virtual Appliance (VSA) v13 with the following error message as discussed in the KB4648. Then I have got you covered.As you can see, below is the error message (Authentication failed). You will get when you use the “veeamso” or the “veeamadmin” account to login In this guide, I have detailed the steps to Fix Authentication failed: Invalid credential after installing VSA. The fix requires downloading a small Linux Live ISO such as the Ubuntu Live Server or Debian Live from this link. You could also use the ISO with the generic image with (Unabhängig davon, welche ISO verwendet wurde).download,, upload and attach as CD/DVD. To fix this, boot from a Linux live ISO and mount the Veeam appliance disk to access and edit the /etc/sssd/sssd.conf file. To proceed, hit the Enter button on your keyboard.Feel free to have the right settings that works for your environment entered. You can see the image below for similar

Hey everyone! 🎉I know many of you have been waiting for this, and I am really happy to finally share with the Veeam Community that VMCE+ is officially live Woo-hoo!!! 🎉 🎉 🎉VMCE+ is the first certification aligned to v13 and a real step up from VMCE. It goes beyond backup and recovery fundamentals to validate advanced skills across the full Veeam Data Platform. If you have been working with Veeam at an advanced level, this one is built for you.What you need to get certifiedTo earn VMCE+, you complete three trainings:Veeam Backup & Replication: Configure, Manage, and Recover (VBR) Veeam Data Platform: Monitor, Manage, Analyze (Veeam ONE) Veeam Data Platform: Scale, Automate, Secure (Veeam Orchestrator)The courses are available through the Veeam University PRO eLearning subscription, with instructor-led options available only for the Backup & Replication course. There may be an option to have the Veeam ONE and Veeam Orchestrator training instructor-led as well, but there is st

 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

 Secure backups have always been important. But over the last few years, the requirements have shifted from “Yes, we should have backups — and ideally a second backup copy in another location and on another medium” to “Hopefully the backup still exists, is reachable, and really cannot be deleted.”Ransomware, compromised admin accounts, supply-chain attacks, and targeted attacks against backup infrastructures have made one thing very clear: a backup is only truly useful if, in the worst-case scenario, it is reliably available, usable, and uncompromised.Terms like WORM, immutability, Hardened Repository, Linux Repository, Veeam Infrastructure Appliance, single-use credentials, certificate-based authentication, Governance Mode, Single Disk, and Multi-Disk installation appear very quickly. But what is actually behind these terms, and what do I need for my use case?With Veeam Backup & Replication 13.1, the topic and the available options have been significantly improved and expanded. Bu

Hey all,Back from a bit of a blogging hiatus to remind people of two things:That Entra ID got new capabilities in v13 & v13.1 That you have to reauthorise the application to enable them.It’s a really simple process, so I thought I’d just quickly show everyone how it’s done!Alt Text: Screenshot of the inventory view within VBR, selecting my Entra ID Organisation.Step 1: Within the Veeam Backup & Replication Console, go to Inventory, and then ‘Microsoft Entra ID’. Select your organisation, then choose Edit Tenant.Alt Text: View of the protected object types, with the new object types missing.Step 2: Proceed to the ‘Protection Scope’ section, you’ll see here every ‘Essential’ type of object protected (as the type name suggests, these cannot be removed). You may also see some ‘Optional’ type of objects protected here. This depends on which VBR version you onboarded your tenant, and whether you’ve remembered/known to do this in the past.Alt Text: Showing the menu presenting the obje

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

When I first heard of the new Application Backup Repository that was just released in 13.1, my mind was full of ideas! I firstly documented what the Application Backup Repository (ABR) was and how to get up and running. https://vzilla.co.uk/vzilla-blog/the-veeam-application-backup-repository-13-1One of the first use cases, was based on us being asked by the Homelab community about Proxmox LXC container backup, we have accelerated how we protect and recovery Proxmox VMs but the business requests for LXC has been mild, so I thought how could we use this new feature to help. https://vzilla.co.uk/vzilla-blog/veeam-application-backup-repository-proxmox-lxcThe other idea I had was a much bigger problem to solve, Veeam have been great at protecting databases over the years, we have enterprise plug ins for most of the common databases we see across your estates as well as the public cloud managed databases and services. But what about all those others…. What about databases running in containe

One of the things I enjoy about designing Veeam environments is that the best architecture on paper is not always the best architecture for the people who have to operate it every day.This project was a smaller Veeam Backup & Replication v13 environment. The system administrators were very comfortable with Windows Server. Linux was another story. They had limited Linux experience and were hesitant to own a Linux-based system after implementation.That became part of the architecture decision. We could have introduced Linux simply because it gives us attractive security options, but doing that would also introduce another operating system the team would need to patch, monitor, troubleshoot, and secure. In a larger organization with dedicated Linux resources, that conversation is different. Here, operational capability mattered.So the question became: how secure can we make a Windows-based Veeam v13 deployment while keeping it manageable for the administrators who will own it?Figure 1

I took advantage of my holidays to step away from screens for a while. Unfortunately, the contest has now come to an end but I still wanted to share my experience with the community.So, what will you find in my toolbox? Well, before answering that, I think it's essential to cover a few other points first because being ready for a disaster is about more than just technology. Experience Is Your Best AllyI fully agree with what others have already mentioned: experience is your ally. The more you dig into topics and use your tools on a regular basis, the more comfortable you become and the day a problem hits, you'll be far more confident in how you approach it.Take the different restore options Veeam provides as an example: it is absolutely essential to test each of them so you understand *when* to use them. Knowing how and when to leverage Instant Recovery, for instance, can save you precious minutes when every second counts.You Need a Big-Picture View of the InfrastructureYou need a holi

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