Blogs and Podcasts

 The release of Morpheus 9.1.0 marks one of the most significant updates in the platform’s history. While the release notes list nearly 80 new features and enhancements, the real story isn’t the number. It is how these innovations collectively strengthen virtualization, observability, storage, automation, and cloud-native operations across a unified platformMuch of the innovation focuses on improving the virtualization experience for VM Essentials customers. From Host Profiles and advanced migration capabilities to intelligent storage management, GPU virtualization, virtual switching, monitoring, and operational automation, this release delivers meaningful improvements for organizations running business-critical virtualized workloads.Therefore, it´s time to upgrade your HPE Morpheus VM Essentials Manager and the Host Agents.This procedure is aimed at customers using release 9.0.0 or later. If you are using 8.x or earlier, you must first reach 9.0.x, because 9.0.0 is the minimum require

Hey everyone, I’m Klaus, a Technical Account Manager at Veeam in Germany.A big part of my role is working strategically with customers around data protection, resilience, and recovery. Disaster recovery concepts are an important part of that work – especially when it comes to understanding which workloads really matter, how they depend on each other, and what needs to come back first when things go wrong. Over time, I noticed that many of these discussions and workshops tend to start in a very similar way: the customer provides an RVTools export, we open a spreadsheet, and sooner or later we end up discussing which VM is actually “critical”. That sounds simple at first, but it rarely is. The final result often lives in that spreadsheet, while a lot of the context behind it does not. Dependencies are difficult to represent properly, assumptions remain in people’s heads, and six months later it can be surprisingly hard to understand why a system ended up in “Gold”, which workloads it dep

  Something strange is happening in your infrastructure: Someone wants to enable SSH?Obtain temporary root access?Change security-critical settings without your knowledge? Who you gonna call? Ghostbus... uh, no: the Security Officer of course. With Veeam v13, this new role has been introduced for the Veeam Software Appliance and the Veeam Infrastructure Appliance. However, what may initially sound like the supreme ghost hunter—uh, I mean security chief — for the entire Veeam environment is often misunderstood. The Security Officer neither manages backup jobs nor automatically approves the deletion of backups. Its actual purpose is much more specific: It ensures that particularly critical changes to the appliance cannot be performed by a single person. The Security Officer approves or rejects requested actions. But when do you really need this role? What is the difference between the Security Officer, MFA, and Four-Eyes Authorization? And why is this role particularly relevant for VBR a

SAML single sign-on in Veeam Backup & Replication v13 lets your identity provider handle authentication while Veeam keeps control of authorization. Users sign in with their corporate identity, MFA and Conditional Access policies apply upstream, and Veeam stops being one more place that stores passwords.The setup is simple. The part that trips people up is group mapping, and it comes down to which Microsoft Entra ID license you have.The mental modelKeep this sequence in mind for both setup and troubleshooting:Trust. Veeam trusts Entra ID as the identity provider through exchanged SAML metadata and the signing certificate. Assertion. After the user authenticates, Entra ID sends a signed SAML assertion containing claims about that user. Identity mapping. Veeam matches a claim (the user's UPN or a group claim) to a user or group in Users & Roles. Authorization. Veeam applies the role assigned to that user or group.Entra ID proves who the user is. Veeam decides what they can do.Step

 In this demo I have MCP for Fusion, Everpure Fusion fleets, MCP for vCenter, and MCP for Veeam software as the data protection layer. And I'm gonna walk through a simple scenario on how you can tie these three things together to simulate a recovery action. So let's say [I] work on the help desk or somewhere like that, or in the data protection space, and I get a call, and it's from the app team, and they say that this VM, so called test-vm01, data got corrupted. So you'll notice I just asked where the VM is. I didn't say, "Hey, look on this array. Check in Veeam." I just say, "I got a VM." And it's going to go out there, locate where that VM lives, correlate that with the data protection space, and then tell me my options, just as I asked.So it hasn't done anything yet. It's asking me things to check, right? Hey, do you need files? Do you need a database, right? What type of recovery do you need? Is it the whole VM you're gonna roll back, right? Is the VM still on?I am confronted with

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

Veeam 13.1 can back up OpenShift Virtualization VMs from the console your team already uses, without an agent in the guest. Here's the architecture in one diagram: five components, two of them new, and the five steps a backup job takes across them.  ComponentsVBR Server — the one giving ordersWhat it is: your existing Veeam Backup & Replication machine, physical or virtual. Job description: holds the configuration, schedules jobs, allocates resources, and coordinates every backup and restore. It also doubles as a general-purpose backup proxy, so it can move data to and from repositories on its own. Where it sits in the diagram: top-left, feeding the plug-in. Mental model: the control tower. It decides what and when; it does not read VM disks.Veeam Plug-in for KubeVirt — the translatorWhat it is: the integration layer between VBR and everything OpenShift Virtualization. Job description: lets the backup server connect to an OpenShift Virtualization cluster and run data protection and

Managing user access through Microsoft Entra ID has become a standard requirement in many environments. With Veeam ONE 13.1, it is now possible to integrate SAML-based authentication and use Entra ID or any other SAML IDP as an external Identity Provider. This step-by-step guide shows the process on how to add Entra ID as an IDP in VeeamOne 13.1. First, we need to create an enterprise application in Entra IDNavigate to https://entra.microsoft.com/ --> Enterprise applications and add a new application  Select "create your own application" and specify a name, I chose "VeeamOne SAML"  Specify SAML as the single-sign on method  Now switch to VeeamOne and go to configuration --> access management and add an identity provider  In the Identity Provider Settings: Display name: specify some name for your IDPIDP URL: copy the "App Federation Metadata Url"Entity ID: copy the "Microsoft Entra Identifier"  In the Veeam ONE Settings, you need to specify a Client ID, for example "VeeamOne"The S

There are so many data-breach incidents reported by news media day after day in Japan. Ransomware incidents seem to be increasing as well, although we do not hear about them as often as data-breach incidents. Maybe they have become so common and no longer considered newsworthy.Having said that, there was a new incident just reported on October 7th and it appears to be a special case. The first report was about Ibaraki Prefecture municipal office and municipal police websites closure due to IDCF Cloud service outage. The IDCF Cloud is run by Softbank subsidiary IDC Frontier, which then announced that a part of their system was compromised. Later, more details were announced that IDCF Cloud’s East Japan Region 1 was down due to a ransomware attack, which impacted 495 organizations throughout Japan.According to public information on the IDC Frontier website, IDCF Cloud service’s East Japan Region 1 uses VMware ESXi / vCenter, suggesting the ransomware targeted that specific deployment, th

During a recent Veeam Agent for Windows deployment project, we found an interesting issue involving VSS, SQL Writer, and old SQL Server references left behind after an incomplete removal or previous intervention.The scenario looked simple at first: a new backup project using VBR, Windows servers, and workstations protected by Veeam Agent. The agent deployment was successful, the jobs were configured, and everything was going according to plan.However, two specific servers started failing during the snapshot stage.At first, it looked like another common VSS issue. But after a deeper investigation, we found that the root cause was related to old SQL Server references pointing to files that no longer existed on the server. The environmentThe environment included: VBR; Veeam Agent for Windows; Windows Server 2025; Servers with SQL-related components; Jobs configured for protection through Veeam Agent. An important detail in this scenario is that the job was not initially configured

This week will take a small break from Wasabi related things and check out replication for Proxmox VE.  Check out blog #6 below.Blog - Veeam 13.1 and Proxmox VE – Native Replication is Here Veeam 13.1 and Proxmox VE – Native Replication is Here The post-Broadcom VMware licensing situation has driven a real migration toward alternative hypervisors, and Proxmox VE has been one of the biggest beneficiaries. Veeam has clearly been watching these trends, because version 13.1 delivers something Proxmox users have been waiting for: native VM replication.This is not just a backup story anymore. Proxmox is now a first-class citizen in Veeam’s disaster recovery capabilities. What’s New for Proxmox in 13.1?  Veeam already had Proxmox VE support for backup and recovery. Version 13.1 extends this with: Native VM replication — create Proxmox VM replicas for near-instant failover Instant Recovery — spin up VMs directly from backup storage without waiting for a full restore Unified management — ma

Every environment has a system that everyone knows is old, but nobody can simply turn off.During a new Veeam Data Platform 13 deployment, I reached one of those systems: an Oracle 10g database running in a Solaris zone. It held almost 48 TiB of data and supported core applications and services used across a worldwide company.The customer knew it needed to be modernized. They also estimated that replacing or migrating the applications and databases around it would cost millions of dollars. That project wasn’t going to happen before we needed a reliable backup.The backup job wouldn’t completeMy initial plan was to protect the Oracle workload as part of the new Veeam deployment. The jobs failed, so I started troubleshooting them like any other failed backup.Eventually, the support requirements gave me the answer. The Veeam Plug-In for Oracle RMAN supports Oracle Database 11g Release 2 and newer; Oracle 10g isn’t listed. Solaris 10 is listed as a supported operating system for the standalo

Today was release the Veeam Backup & Replication. The process of upgrading or updating a Veeam Software Appliance (VSA) is straightforward and performed via the web interface. One of the advantages of using the VSA is that you do not need to manually manage packages and dependencies within the operating system, as the appliance itself handles the update lifecycle.Despite how easy it is, I will show you here how to perform the upgrade procedure. Navigation and Checking for Updates Access the Host Management Console interface of your Veeam Software Appliance. In the left-hand menu, click the Updates button.This screen will show available updates; you can select the Veeam Backup & Replication option and click the Install Updates Now button. Configuration Check and Details Now we need to check some details and look if it have any compatability issues:Installation Process The wizard will take over and automatically begin downloading and applying the packages. A progress bar displayi

Hello Veeam community! 😊VDC recently added a new capability to send events from the Control Plane and Microsoft 365 to SIEM platforms (with Entra ID coming soon as well).Today, it supports Splunk and CrowdStrike, but there is also a 3rd connector that opens the door to many more possibilities: the Generic Webhook connector. 🤩And of course… that gave some ideas, right? As a big Grafana fan, I started wondering: could we use this webhook to send VDC events into Grafana and build a dedicated dashboard?So, et voilà guys… I built it in my lab. 😄I used my usual monitoring stack: Telegraf → InfluxDB → GrafanaThe full setup, configuration, and all the steps are available in my latest blog article: https://home.point4.fr/monitoring-vdc-using-grafana/And just to give you a small preview, here is what the final dashboard looks like.Of course, I’m also sharing the Grafana JSON dashboard file, so you don’t have to start from scratch. 😉Hope you enjoy it!❤️ to this community. 

IntroductionCloud is not always the most cost-effective solution for every workload.We recently worked with a customer who was experiencing increasing costs in Microsoft Azure. The customer was running approximately 40 virtual machines (VMs) in Azure, and as the environment continued to grow, so did the monthly operational costs.The primary goal of the project was straightforward:Reduce the customer's infrastructure costs without compromising availability, security, backup, or future scalability.After evaluating several alternatives, we concluded that moving the workloads from Azure to a dedicated on-premises environment hosted in our data center provided the best long-term financial outcome.Evaluating the OptionsWe looked at several possible solutions: Continue hosting the environment in Azure Host the infrastructure with a third-party provider Rent rack space in a data center, including power and cooling Deploy the infrastructure at the customer's own location After comparing t

 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 overrides file.Open this file on your VSPC serve

 Heads up: this plug-in is upcoming and not GA. What's shown is a pre-release build and may change before it ships. If you want to get ahead of it, reach out to your Everpure team.I recorded a quick walkthrough of the upcoming Everpure (formerly Pure Storage) plug-in for Veeam Backup & Replication 13.1. It does two things: it supports 13.1 on both Windows and the Linux-based Veeam Software Appliance (VSA), and it takes advantage of the Fusion fleet-wide management built into every Everpure array. I focused on the VSA.What's in the demo:Install on the VSA. In Host Management, go to Logs and Services > Components and add the plug-in bundle. A Windows executable covers Windows installs. Hardened by design. The VSA's Security Officer role keeps separation of duties. Pair that with SafeMode and MFA on the array for layered security. Backup from storage snapshots, on by default. As long as your proxies can reach the storage over iSCSI, NFS or Fibre Channel, jobs process VMs with stora

There is something satisfying about getting a new piece of hardware into the lab.You can read documentation, look at architecture diagrams, and talk about specifications all day, but I always prefer getting my hands on the actual hardware. Unbox it, rack it, cable it, configure it, integrate it, and then see how it performs.Recently, I had the opportunity to add a new Dell PowerProtect Data Domain DD3410 to our lab. The goal was simple: Take the DD3410 from the shipping box to a working Veeam Backup & Replication 13.1 repository.In this blog, I’ll walk through the process I used:Unboxing and installing the DD3410 Initial hardware and iDRAC setup Configuring DD OS Configuring networking Preparing storage Enabling DD Boost Creating the Veeam storage unit and account Adding the DD3410 to Veeam Backup & Replication 13.1 Creating and running the first backup job A few configuration and performance considerations I found along the wayThis isn't intended to replace the Dell or Veeam d