Blogs and Podcasts

Hello,VeeamONE till version 12 was using connection from VeeamONE to VBR on port 2805 to connect to Veeam Agent on VBR.In Veeam ONE 13 connection was exchanged from VBR to VeeamONE on port 2805, even VBR is on version 12.x.We had enabled only connection from central domain, where is located Veeam ONE, to customer domain, where VBR is located.So during adding VBR into Veeam ONE, Veeam Analytics Service (previously Veeam Agent) was installed, but connection timed out. Adding VBR failed due no response from Veeam Analytics Service - status “Failed to install”. Is not possible to download logs to troubleshoot as echo is not providing port number. On helpcenter is described VO → VBR connection only, even for Linux VBR. Once connection from VBR to VO was allowed, data update was successful.Finally, result is installed and Healthy. 

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

Hi Everyone,Earlier today, during the delivery of the Veeam Backup & Replication v12.3: Configure, Manage, and Recover course, I felt compelled to write this article because I've noticed that most students, when they need to create a repository, only think about capacity and forget to consider throughput. Failure to properly configure the required throughput will certainly lead to several problems. Furthermore, the vast majority consider using only RAID 5, without a hot spare disk.In this article, I will make regular updates.https://pulia.com.br/backup-repositories-repositorio-em-bloco-das/ After reading this article, you'll understand that buying an Object First box is the best option to have a repository. Enjoy reading it! have a great week.

 Active Full Backup and Synthetic Full Backup in Veeam essentially serve the same purpose: creating a full backup file containing the data of the entire virtual machine (VM). However, they differ significantly in how they do this and, consequently, their impact on the system.Here are the definitions and differences between these two backup types:What is Active Full Backup?Active Full is the traditional full backup method.Data Source: Reads data directly from the source data store where the virtual machine (VM) is located. Process: Veeam Backup & Replication retrieves all VM data from the source, compresses and deduplicates it, then writes it to the backup repository as a new .vbk (full backup) file. Areas of Influence: Production Environment (Source): The load on the source datastore and VM where the VM is located will be high because all the data needs to be read. Network Resources: Network bandwidth is intensive as all data must be transferred from the source datastore to the ba

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

Hey all, we’ve got a new installment in our RegKey of the Month series up now! This month’s spotlight: the Classified Stripe banner in Veeam Backup & Replication.Why it matters: if you run multiple VBR servers (prod, test, branch, DR, etc.), a visual cue (e.g. “PROD – do not touch”) helps avoid costly mistakes. The post covers: how to implement it via registry keys in Windows deployments how to achieve the exact same result on the Veeam Software Appliance v13 (yes — even though there is no registry in VSA, we map the settings into config files) tooling tips, color code guidance, and gotchas Curious? Read the full deep dive here ➡️ https://integriservices.blogspot.com/2025/09/regkey-of-month-october.htmlVSA v13 ? No problem for Regkey-man ! 

Having updated to Proxmox VE 9.0 below. There is a need to upgrade from  Veeam Plug-in for Proxmox VE build 12.1.3.217 to plug-In build number 12.1.5.17 to support it.The Proxmox VE Plug-in integrates the backup server with the Proxmox VE server and enables worker deployment. From version 12.3.1 and above, you do not have to manually install this plugin.You can download the Plugin for Proxmox VE directly from the referenced link, or navigate to the release Information for Veeam Plug-in for Proxmox VE v12.1.5.17 in the following KB article.To see the current version of the Veeam Backup for Proxmox plugin that you are currently using. Please launch the Control Panel or Windows Settings as you wish. As you can see, we are currently using the version 12.1.3.217 As you can see below, this meets the requirement for the Veeam Plug-in for Proxmox VE build 12.1.3.217 which can be determined via the steps below.You can check the build number in the Veeam Backup & Replication Console’s Main M

Proxmox VE 9 introduces external QCOW2 snapshots on thick-provisioned LVM volumes over SAN (including FC and iSCSI). There is already an updated plugin, that supports not only this version but also those specific snapshots.​@Iams3le already gave insight about the installation of the new plugin: Veeam Plug-in for Proxmox VE v12.1.5.17 update to Support Proxmox VE 9.0 | Veeam Community Resource HubNow, using a shared FC (or iSCSI) SAN is possible just like we did with VMware - while still being able to generate nice Veeam backups of the VMs on the LUNs: Plug-in for Proxmox VE v12.1.5.17 -> shared LVM? - R&D Forums Here's the breakdown:QCOW2 is required for snapshot functionality on SAN LUNs. Snapshots are implemented as external overlays (not internal QCOW2 snapshots). Each snapshot creates a new logical volume to store delta data. This allows rollback and versioning, even on raw block devices like FC LUNs.[TUTORIAL] - Inside Proxmox VE 9 SAN Snapshot Support | Proxmox Support For

  Hello Community! If you’re a Veeam Cloud Service Provider (VCSP), you know the challenges of handling licenses for tenants. The old way of emailing .lic files, waiting for tenants to install them, and then verifying everything worked correctly is time consuming and prone to errors. It may work for a few customers, but as you scale, it quickly becomes unmanageable. This is where the Veeam Service Provider Console (VSPC) changes the game. By integrating VSPC with the Veeam ProPartner Pulse portal, you can manage license distribution, usage reporting, and billing in a centralized, automated way. No more manual file exchanges and licenses are pushed directly into tenant environments with minimal effort. Think of Pulse as the master licensing database and VSPC as the control plane that brings those licenses to life in your tenants’ environments. In this post, I’ll walk through how this works and why it’s a game-changer for service providersHow to connect Veeam VSPC Console to Pro Partner

If you have not upgraded your Promox node yet due to dependencies on Veeam Backup and Replication (VBR). The wait is over as Proxmox Virtual Environment (PVE) 9.0 is now fully supported. It is packed with powerful new capabilities for modern virtualisation and software-defined data centres. Whether you are running a home lab or managing enterprise-scale clusters, this release is a game-changer.Recently, I created some blogposts on how to setup Proxmox VE and also how to Backup and Restore Proxmox VE virtual machines with Veeam.So I had wanted to upgrade to Proxmox 9.0. But because this was not supported by Veeam yet, I ended up protecting the VMs only running on Proxmox 8-3-1.Now, with the release of the new Veeam Plug-in for Proxmox VE v12.1.5.17 It now support for Proxmox Virtual Environment versions 9.0 For what’s New in Proxmox 9.0 and other details not discussed extensively in this guide, please visit the following link. Update Proxmox VETo update Proxmox VE, you can use either th

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

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