Blogs and Podcasts

I tested the new VSA 13 with SAML implementation and thought I'd share the process in the form of this little step by step guide.  This guide provides instructions to configure Entra ID SAML integration for SSO access to VBR with version 13  As requirements, you need an Entra ID account with one of the following permissions: "Cloud Application Administrator" or "Global Administrator" for creating a new enterprise application.  You also need a working Veeam version 13 installation.   First, configure the Entra ID application:  Access Entra ID (https://entra.microsoft.com) and navigate to Enterprise apps and create a new application.   Search in the gallery for "Microsoft Entra SAML Toolkit" and select the app  You can specify a name, I choose "Veeam 13 SAML" and then click on create  In the newly created application, navigate to Single sign-on and select SAML.   We now need some information from our VBR.  Open "Users and Roles" settings  Navigate to "Identity Provider" and enable SAML a

QNAP QuObjects application is free and certificated for objects with immutability, which means you can use it as object storage within Veeam for a backup repository that supports their immutability feature.QNAT QuObjects Requirements: 1.Log on to the NAS as an administrator.2.Select App Center. 3.Click the Search icon on the App Center page. 4.Enter QuObjects and select the QuObjects and click Install. 5.Click Open after Installation is completed. 6.Ensure turn on Server Connection on the QuObjects S3 Compatible Object Service page and select User Management. 7.Click Add User on the User Management page. 8.Select a user on the Add an Authorized User page and click Add. 9.Click the Add key icon on the User Management page. 10.Ensure QuObjects creates an access key for the user and select Storage Space. 11.Click Create on the Storage Space page. 12.Enter the storage space name in the Folder Name field on the Create Storage Space page, select the user and click Create. 13.Select the new c

This topic is for Lucho ​@JailBreak and others who want to easily install OpenShift virtualization. 🚀 Red Hat simplified OpenShift Virtualization setup with a more intuitive and faster installation experience in the Developer Preview of OpenShift 4.19, coming soon in tech preview, 🌐 making it easier in isolated environments and ⚡ speeding up deployment. The highlights its ⭐ key benefits, the new 🖥️ UI, 🆓 registration-free installs, and a 📘 quick start guide.We’ve made deploying OpenShift Virtualization easier and faster, enabling quicker adoption with: UI-driven configuration: simple guided wizard with best practices. Pre-installed operators: ready from day one. Registry-free installs: work seamlessly in air-gapped environments. Proven Red Hat technology: built on Agent-Based and Assisted Installers. 🤓Now, let’s go through the steps of this updated installation flow. In this example, we’ll demonstrate how to deploy a compact OpenShift cluster in a small test setup using thr

 Importantly, administrators are responsible for enabling and configuring the fencing mechanism after cluster deployment. Without the fencing configuration, node remediation and VM restarts will not happen as expected. In virtualized environments, high availability (HA) is essential to keep workloads running even when a node fails. In OpenShift Virtualization, HA leverages Kubernetes-native mechanisms combined with OpenShift’s self-healing infrastructure.A key element is fencing, the process of isolating a failed node to prevent issues like split-brain—a scenario where nodes lose communication but continue running independently, causing data inconsistencies and conflicts.When a node goes down, restarting virtual machines (VMs) happens in three phases: Failure detection – Identifying that a node has stopped responding. Fencing – Ensuring the failed node is safely isolated with no active workloads. Remediation – Restarting affected VMs on a healthy node. Through this approach, OpenSh

Resolving SQL Backup Error - Code 0x80040e14 (Dispatch error #3092) / failed: 112(There is not enough space on the disk.) IssueBackup operation fails with the following error:Failed to perform internal backup                                                               Code = 0x80040e14Code meaning = Dispatch error #3092/ failed: 112(There is not enough space on the disk.)Source = Microsoft SQL Server Native Client 11.0 Root CauseThis error typically occurs due to insufficient space for temporary transaction log (T-log) files during SQL backup operations. Resolution Steps1. Verify Transaction Log File SizeContact the SQL DB Team to check the size of the transaction log file. Confirm the required space for temporary log storage. 2. Check Drive AvailabilityIf lacks sufficient space, proceed to request a new temporary disk. 3. Request Disk AdditionAdd a new temporary disk to the server. Disk size should be based on SQL DB Team's recommendation plus 10 GB buffer. 4. Configure SqlTempLogPa

Earlier this year, I kicked off a series on HPE storage platforms and their integrations with Veeam Backup & Replication. We started with the HPE Alletra Storage MP B10000 and then looked at Veeam Ready – Appliance Hardened storage servers as secure backup repositories. I paused the series for a while to let some important HPE announcements catch up with the story I was telling and to complete more hands-on validation. Now is the right time to pick things back up with the HPE Alletra Storage MP X10000, the next natural step in the conversation. This blog is not a deep dive into every feature of the X10000 — instead, it’s about where it fits into a Veeam-powered backup architecture, why it matters, and how it supports cyber resilience at enterprise scale. The X10000 is HPE’s flagship object storage platform, built to manage unstructured data at scale with an all-flash, disaggregated architecture. Independent scaling of capacity and performance, powered by NVMe drives and 100 Gb Ethe

Hello Everyone,We are using Veeam Data Cloud for Microsoft 365 Flex with a license for 250 users.During the initial setup, we tested with 1 user to validate the configuration. After confirming everything was working properly, we deleted this backup job and created a new policy to protect the actual 250 production users.However, we are still seeing the backup for the original test user, and the license usage shows 251 users consumed, even though our license count is 250.I have a few questions regarding this situation: How can we delete or revoke this test user so that it no longer consumes a license? If we keep the test user without removing it, will this impact production users (e.g., only 249 users protected)? Is there any automatic cleanup or retention process that eventually removes old test accounts from the license count, or must it always be handled manually? Any guidance on how to properly handle this case would be greatly appreciated.Thanks in advance for your support. 

Hey Everyone, wanted to share a few things with the community about Virtualisation or Virtual Machines on Kubernetes, in the field and with the overall Hypervisor Hunger Games all options are on the table it seems. I have made my feelings quite clear around vSphere being the best hypervisor and ultimately today still the best ecosystem but this is not stopping the exploration of alternatives. ​@Geoff Burke and I did a live stream at the end of August touching on a project called Kubevirt, this is the mechanism to run Virtual Machines on Kubernetes, either as an alternative hypervisor and / or alongside your containers. This is also what we find being used in the enterprise products such as Red Hat OpenShift and SUSE Harvester. Every month me and Geoff jump on the live stream and cover something cloudy, DevOpsy or just something interesting.   From this episode and the release of the Veeam Software Appliance, I had an idea lets show the apples to oranges comparison here between say some

Hey Folks, I wanted to share my discovery of Veeam v13 beta with you. ​@Michael Melter  made an excellent post on the installation.I had undertaken the same work so I'm sharing my version with you. On my side, in this first post I go a bit further by presenting the Host Management part. I wish you a good read! 1. Veeam Software ApplianceOne of the flagship announcements at VeeamON was the release of the Linux appliance version - yes, Veeam Backup & Replication is switching to Linux. (The Windows version is not deprecated for now, so don't worry).Objective: we want a product that performs backups without having to worry about maintaining operating systems.In this first article, we will cover the installation process of this new appliance, based on Rocky Linux, and the use of management consoles.⚠️Reminder: We are testing a beta version here. Some features are still missing, incomplete, or might not even make it to the final version.Deployment: In this Beta version, to deploy V13 as

HPE and Veeam jointly validated HPE Alletra Storage MP X10000 as an S3-compatible, immutable backup repository for Veeam Kasten v8. The team confirmed successful backup and restore behavior, Object Lock immutability enforcement, and post-retention cleanup. CSI-assisted local snapshot restore testing was performed with HPE CSI Driver 2.5.2. Reference Architecture (at a glance)  Kubernetes cluster running Kasten K10 v8  Repository configuration: HPE Alletra MP X10000 S3 endpoint with Object Lock (immutability) enabled  Policies: App-aware backups with defined retention and periodic export plus restore validation  CSI for local snapshot flows: HPE CSI Driver 2.5.2  What HPE Validated HPE configured the repository settings in Kasten to use the HPE Alletra MP X10000 S3 endpoint with Object Lock enabled, then ran immutable backups governed by policy-based retention. HPE performed restores from the repository and observed expected behavior end to end. After the retention window elapsed, th

Hands-On with Scale Computing  At Veeam on, Scale hinted to me they were at the event for a reason. As we are a large user of Veeam, this excited me as there is no chance of my installing VM’s I can’t backup. Things have progressed quickly in this area since and I’ll be testing these features out in the near future. Hypervisors have been such a hot topic this past year, with lots of discussion around cost, complexity, and future direction. I have been testing all options as the future is still unknown and there are a lot of new options available. Scale demoed how you could run a highly available cluster on just a few Intel NUCs, compact, inexpensive hardware that still delivers solid performance. That got me thinking: could this work in my environment too? I wanted to see firsthand how their platform performs, and I was especially curious about their Fleet Manager Platform, which makes it easier to manage multiple clusters from a single dashboard. Fleet Manager DashboardThe Dashboard i

 Hello Community ! Subscriptions to Veeam Universy PRO, new learning platform for professionals, are now open.Special thanks to ​@Federica !  Currently, these courses are available, with two more to be added over the course of the next year:  This type of subscription is very advantageous and economical as it allows 4 people from the same company to access the courses.For more information, please visit https://veeamuniversity-pro.com/  

For those who joined my online and VeeamON sessions on migrating from VMware to Hyper-V or Proxmox, I promised I would share my cleanup scripts. It took longer than planned to prepare them, but they are now ready.Online session HERE unfortunately there is no video of the VeeamON session that was migrating to Proxmox.When you use Veeam to migrate a Windows virtual machine, the work is not done when the job finishes. Your migrated VM is now running on a new platform, but it still contains old drivers and devices from VMware.These leftovers can cause instability, performance issues, or future driver conflicts. This post explains how to use my PowerShell scripts to safely clean the VM after your migration, making it ready for the new platform.Get the Scripts on GitHub All the tools discussed here are available in my public GitHub repository. You can clone or download them to get started.My GitHub: My GitHub Repository Before You Begin: A Safety Checklist Before running any scripts, take th

Today while I was working in the Veeam Windows Console for v13 I hit a strange error when copying a job error message to the clipboard.  It let me paste but the error noted is just a minor annoyance.  I have reported this and you can read it below and on my blog.  Once confirmed I will update things on the community and my blog post.Veeam Console – Possible BUG – Copying to Clipboard Veeam Console – Possible BUG – Copying to Clipboard I have been using Veeam v13 more frequently lately, particularly the VSA and the Windows Console application. Today, I encountered an unusual issue with the Console application while copying an error message from a job to the clipboard for investigation. The message below appeared, but I was still able to paste the clipboard contents regardless.Copy to Clipboard Error (Potential Bug?)I have posted this in the Veeam 100 thread (not everyone will see this, as it is a special section of the Forums) as a possible bug, which you can see here if you have access

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

​ Oracle Retention for RMAN and Veeam Plugin Backup   When it comes to RMAN, Veeam acts as a storage location utilized by the Oracle SBT interface. Therefore, it is RMAN retention settings that are utilized to manage the backups generated when using the Veeam Plugin backup protection.Typical retention for application aware backup will focus on the most recent restore points and mark backups to be pruned per familiar Veeam retention policies and retention methods.With Oracle, an incremental strategy employs a combination of incremental level 0, incremental level 1 and incremental level 1 with cumulative incremental or stand alone full. Each of these backup types dictate what data RMAN will identify and capture to create backup sets.Data captured during any one of these types can be manipulated as desired by the user. Typically, an incremental level 0 backup will capture all files necessary to restore and recover a database including the Initialization or SPFILE, Control File, all databa

The Veeam SAP HANA Plugin is an SAP-certified backup tool that connects directly to SAP HANA through the Backint interface and lets you store transaction-consistent database backups and log files in Veeam backup repositories. It acts as an intermediary between the SAP HANA server and Veeam, compresses the backups, transfers them to the Veeam repository via Data Mover, and allows backup and restore operations using native SAP tools such as SAP HANA Studio, Cockpit, and HDBSQL.As the plug-in only establishes the interface to Veeam, all further configuration is carried out via SAP, and SAP administrators are free to configure this as they wish.Installing the plugin is quite simple, but there are a few things to consider beforehand. Preparations / Basic InformationOS and HANA VersionThe OS and SAP HANA version must be compatible with the currently used Veeam version.https://helpcenter.veeam.com/docs/backup/plugins/system_requirements_saphana_64.html?ver=120 Firewall RulesFirewall rules mus

With the release of Veeam Software Appliance and JeOS, deployment processes have become significantly more streamlined. In Europe, the prevalence of multiple languages naturally results in a variety of keyboard layouts, such as Azerty for French users, Qwertz for German users, and a Danish variant of Qwerty to accommodate specific characters like Å, Æ, and Ø. However, the rapid installation process does not provide the opportunity to configure keyboard settings during setup.There is, however, an effective solution. JeOS is an optimised and secure edition of Rocky Linux, and its installation is managed through an automated kickstart script. Settings such as keyboard layout, timezone, timesource, and network configuration are all specified within this script. To ensure every installation includes your preferred configurations, you can update or remaster the ISO and integrate these settings directly. For this purpose, I have developed a custom script, ksmod.py, which is available at https

​In the first part of this three part blogpost we’ve discussed why to use gMSAs to achieve application consistency before backing up our workloads with Veeam Backup and Replication (VBR).In this part I will show you, how easy it can be implemented with VBR and how the process differs from the official manual.  (1) Ensure your forest schema is updated to (at least) Windows 2012 (Version 56+)First, check your version of the forest schema and increase it, if needed, beforehand. You might well go all the way up to the maximum possible level for your most legacy domain controller. Check for compatibility with other domain related services like Exchange servers etc. first, to make sure you don’t break other things. (2) Make sure you have created a KDS root keyThe KDS root key is a crucial component of the Microsoft Group Key Distribution Service (KdsSvc). It is used to generate group keys that are distributed within an Active Directory environment. This root key is essential for creating gro

After four years away from Veeam (now a Pure Storage Principal Technologist), v13 represents the evolution I always hoped to see. This isn't just another release. v13 is Veeam's comprehensive answer to modern infrastructure challenges. Key Transformations:Web UI Revolution: Complete backup management in-browser, eliminating dedicated management workstations Security-First Foundation: STIG-compliant hardened Linux with enforced MFA and dual admin model from deployment Hybrid Infrastructure Ready: Modern foundation while maintaining full backward compatibility Appliance Simplicity: OVA deployment with wizard-driven hardening, without being stuck In The Box.The Linux foundation isn't just OS modernization it is in reality an infrastructure alignment; strongly catering to security-conscious hybrid environments. Having seen customer challenges from both the backup and storage sides, v13 addresses every major adoption barrier I encountered as a SE.Bottom Line: This is Veeam's strategic reset

A previous post (https://community.veeam.com/blogs-and-podcasts-57/veeamsoftwareappliance-on-fedora-42-11241) covered how to set up the software appliance on a Fedora 42 host, including network configuration for direct bridging. This post provides information on setting up a Veeam Hardened Repository.While this documentation is intended for lab use, it may also be relevant for SMB customers seeking guidance on configuring an all-in-one appliance. Security considerations were not a primary focus, so additional safety measures may be necessary. For instance, it may be advisable not to bridge the host itself to prevent external access after installation.First, install virt-install to quickly set up new virtual machines.sudo dnf install virt-install -yIf you want the disks on another drive set (eg /dev/sdb mounted to /mnt/backup), we can create a subdirectory for the user on it and add as a pool. sudo mkdir /mnt/backup/$USERsudo chown $USER:$USER /mnt/backup/$USERmkdir /mnt/backup/$USER/da

Recently I installed Fedora 42 using Gnome Boxes, which serves as a lightweight graphical interface for KVM/QEMU, comparable to VMware Workstation.Since Gnome Boxes functions primarily as a front-end for KVM, it is possible to leverage virsh for automation purposes, making it particularly suitable for laboratory environments. For graphical access, users may utilize either virt-viewer or the Boxes GUI.These commands are generally compatible with other KVM-based platforms such as Proxmox, although networking configurations may vary. This setup is recommended for home lab use; it should not be deployed in production environments unless its appropriateness has been thoroughly evaluated, and you know exactly what you are doing Setting up networkFirst, set up a bridged network. This step is optional, and much of the configuration can be skipped if it is not performed. With this setup, VBR will be accessible on the network (think VBR HA for example)Use nmcli to display your current network ad

Greetings, friends! I want to share with you the new Grafana Dashboard for Veeam Backup & Replication, no Enterprise Manager is needed, and it uses 100% VBR API.Small note: For those familiar with the data protection scene, you might recall that we’ve already got a Grafana Dashboard dedicated to the Veeam Enterprise Manager API since 2020. Grafana Dashboard for Veeam Backup & Replication API 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, protected workloads, jobs, etc.Dashboard – SummaryJob Historical Information – The very first graph. The most important one in my opinion. Grouped by 24 hours, get to know the status of your policies per day, on a range in time. Job Historical Information Table – Very similar to the previous panel, but this time with more details about job name, status, date, etc. Job Historical Information Duration – Very simil

 Extracted from the original blog at wcithipster.com on Nov 25 Written By Zane AllynAs a Veeam Vanguard and a longtime backup enthusiast with more than six years of experience working at Veeam. Today, I’m beyond excited to share an early look at Veeam Backup & Replication v13. This release introduces two major enhancements: a fully Linux-based backup server and an HTTPS-based web console. These updates are not just features; they’re milestones that reflect years of community feedback.This sneak peek is based on alpha code, so things may change before the final release. That said, there’s plenty here to get excited about. Let’s get into it.A Fully Linux-Based Backup Server: No Windows NeededOne of the most significant changes in v13 is the move to a fully Linux-based backup server. For years, Veeam relied on Windows to power its core services. With v13, that dependency is gone. Instead, you’ll deploy the server using an OVA file, making the process faster, more secure, and platform-