Community

I enrolled in a Veeam 13 subscription course, but the lab setup instructions appear to be based on a 2023 recording and an older ESXi licensing model. Because of that, the setup options shown in the course no longer work as presented, which makes it difficult or impossible to complete the home lab as expected. On top of that, I can clearly see the training is v12 = false advertising. The reason for the failure comes when I install VCSA. The error shows the license used in ESXi is invalid however I followed the instructions in the training and the instructor downloaded the same software as I. Conclusion is the material and training is old but sold as some new amazing thing. I contacted support by email, used the chatbot, and reviewed the help section, but I have still not received a response after 78 hours.My concern is not just the delay in support, but that this course is still being sold even though the lab guidance appears outdated. At minimum, this should be clearly disclosed befor

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

I am back with the second of my ten blogs.  The second one is below and can be found at my blog site -Veeam v13 Hardening Checklist for Day One Veeam v13 Hardening Checklist for Day One IntroductionSecurity hardening is easiest when it starts during deployment and not after the platform has already been absorbed into daily operations. Veeam v13 introduces platform changes that make operational consistency and security posture more visible, especially where the software appliance, web-based access, and role design are concerned.For production teams, day-one hardening is less about a perfect checklist and more about eliminating obvious exposure early. Administrative reach, account scope, network paths, and audit visibility should all be reviewed before the environment settles into normal use.Limit Administrative AccessThe first hardening decision is simple: reduce who can reach the platform and from where. Backup infrastructure should sit behind management boundaries that force administr

Unable to install the windows veeam agent remotely from backup server, checked the svc installer logs and can find VeeamDeploymentDlllibrary was not loaded mentioned, checked the C:\Windows\Veeam\Backup and do not find VeeamDeploymentDll here, checked with network and server team and ports are allowed 6160 and 11735.

 Upgrading Veeam ONE from version 12 to version 13 introduces significant architectural and security improvements, including changes to authentication and communication methods. Version 13 moves away from legacy protocols such as NTLM and WMI in favor of more secure and modern approaches like Kerberos and gRPC as discussed below.Note: There is a strong business and technical need to upgrade to Veeam ONE v13 in order to leverage Veeam Intelligence, enhanced analytics, and next-generation dashboard capabilities that improve visibility, reporting, and operational decision-making as shown below. For the detailed blogpost, please see https://techdirectarchive.com/2026/05/26/how-to-upgrade-veeam-one-from-v12-to-v13/The guide highlights the upgrade best practices, and important lessons learned from real-world upgrade scenarios to help ensure a smooth and stable transition to Veeam ONE v13 in your own environment.If you are upgrading an isolated (workgroup-based) environment, this architectura

Has anyone ever seen the following with CDP proxies running Windows Server 2025? There seems to be a constant disconnect, we have no other connectivity issues between site and there is exclusions throughout our Crowdstrike instance.Veeam support have looked at the logs and highlighted the loss of connection, and to refer to our network team but there isn’t anything apparent that would cause an issue.Any help would be appriciated.Many thanks,LGH

After update to VBR 12.3.2 I am unable to login.The following error:The socket connection was aborted. This could be cause by an error processing your message or a receive timeout being exceeded.  I have restarted all veeam services, specifically veeam backup service.All sql server (veeamxxx_ services have started.However under SQL server config manager the sql server is running but the agent is stopped and I am unable to start that service ( grayed out). TIA

Hi everyone,I'm looking for real-world experiences from anyone who has successfully (or unsuccessfully) tested SQL Server AlwaysOn Availability Groups using SureBackup with custom verification scripts.I tryed to use the predefined SQL script but it failed. My Setup:2-node Windows Server Failover Cluster (WSFC) with SQL Server 2022 AlwaysOn AG configured with synchronous commit Veeam B&R 12.3.2 with Virtual Lab Goal: Validate SQL recoverability without triggering production cluster conflicHas anyone written a PowerShell/ that handles AG verification inside the Virtual Lab (accounting for possible quorum loss)?If you've done this (or tried and hit issues), I'd love to hear about your experience!

Hello dear community !Just a quick update to share a big new release of the M365Simulator tool.M365 Simulator is a free tool that helps you generate realistic Microsoft 365 test data across users, mailboxes, SharePoint, OneDrive, Planner, and Entra ID workloads, and other M365 objects.I’m very happy to share that you can now create even more realistic Microsoft 365 assets in your tenants, with brand-new engines for: Microsoft Planner Outlook Calendar Events Outlook Contacts SharePoint Lists Entra ID Administrative Units / Business Units Entra ID Devices Entra ID Organizational Contacts Sensitive data generation for emails and files, including OneDrive and SharePoint File versioning simulation New Security Audit report (need AI) New M365 Throttling Audit report and now Multi-tenant support! Yes, that is quite a lot of new toys to play with, right!? 😊🥳But wait, there’s more.Some existing engines also went to the gym: Email and file generation engines have been rew

Hi All,I have a VMware environment where backups are performed using Veeam Backup & Replication. The Veeam server is installed on a physical Windows server and also acts as the backup proxy.I would like to understand: In real-world environments, how much performance difference do you typically see between NBD (Network) mode and Direct SAN mode for backup and restore operations? Is the performance improvement significant enough to justify implementing Direct SAN access? How risky is it to present production VMware datastore LUNs to the Veeam server for Direct SAN access? What best practices do you follow to prevent accidental modification or corruption of production datastore LUNs when they are presented to the Veeam server? Looking forward to your suggestions. Thank you

Hi all, I'm planning to deploy the Veeam Software Appliance and wondering — is it generally better to run it on physical hardware or as a virtual machine (e.g. on vSphere)?I know both are supported, but looking for real-world experience on pros/cons of each approach. Things like performance, reliability, and best practice recommendations would be helpful. Thanks in advance!

Hi there,We currently use Veeam CDP and Veeam Replication to replicate our servers from our primary data center to a DR site, and this setup has been working very well in our VMware environment.With our interest in Proxmox growing, I wanted to check whether Veeam has any plans to bring similar capabilities, such as CDP and replication to Proxmox.Is this something that’s on Veeam’s roadmap, or are there any updates on future support for these features? 

Hi all,I am currently involved in an opportunity to deploy over 1,000 VMs and 500 TB of storage to a single GCP region.I went through all the documentation and pulled out some key facts that I think will help you optimise your Veeam Backup for Google Cloud jobs.The first point is that with the default settings, you can have up to:15 Parallel jobs running (global across all regions) 25 concurrent VMs being backed up per jobThis means that the maximum number of concurrent VMs you can back up is 375.Now, this might not sound like a lot, but when you consider that the default worker instance (e2-highcpu-8) can run at a blistering 420 MBps (NTFS disks up to 540 MBps), that comes to 153.8 GBps! This is before going to the e2-highcpu-16, which has a speed of up to 800 MBps, at which point I think the backups would finish before they even start.Of course, this assumes all backups start at the same time; the actual throughput equals the number of concurrent backups. This is based on 420 MBps pe

Hi there, I am still looking to find the solution out there, but it may be much quicker to ask.Scenario is my old VBR server was on VMWare, and a backup of the config was taken.The backup has been recovered on a brand new VBR server, now on HyperV, different server name and IP. The old server is long gone.Restoring the config worked great, but now I cannot pass any ‘four-eyes’ approvals as the users that were on there, do not exist on this new server. I added the users to this new server, using the same usernames, but they do not have access to this new VBR server.If I add the users to the server as admins, that itself kicks off another four eyes approval.So, how do I get around this? Is there a way to disable that feature when dealing with a new box? Thanks in advance!

The case is for Veeam Backup & Replication version 12.The repositories are ExaGrid appliances configured as a scale-out backup repository.Two separate Veeam Backup & Replication instances use different shares on the same ExaGrid appliances.Fast Clone was enabled on both Veeam instances after the ExaGrid firmware was updated to a version that supports Fast Clone.The SOBR placement policy is Data Locality.Fast Clone worked on one Veeam instance during synthetic full backups and initially did not work on the second Veeam instance.We later observed that synthetic full backups on the second Veeam instance used Fast Clone on the second day without running an Active Full backup.Veeam treats a synthetic full backup as a regular full backup that resets the backup chain.Veeam uses Fast Clone for synthetic full backups and other synthetic operations. We understood that  a synthetic full can serve as a chain reset point and enable Fast Clone utilization. However, in our environment, most j

Veeam Enterprise Manageris used for managing VBR servers centrally. Today’s usecase is due migration from V12 to V13Our VBR servers are not part of any domainVEM was migrated to VSANow we have been added VSA VBR on VEM (VSA).Everything was fine and is working Data collection was fine When we decided to add VBR as windows, upgraded from v12. At first time was possible to add (with repeated adding was not possible later add windows VBR)and session were sometimes successful, sometimes failed - because one of VBR failed with data collection. Using VEM for restoring ITEMS we had always errors It was  tricky to find RCA, because VEM sometimes restore back to original location was successful and always failed with alternative location. In logs was visible[22.06.2026 05:26:54.784]    <20>    Info (3)    A connection could not be established within the configured ConnectTimeout. (System.TimeoutException)[22.06.2026 05:26:54.785]    <20>   Error (1)    Unable update EM master key at

Hi all, for those who could not make our last Bootcamp, here is another opportunity to understand more about Veeam’s VDC for Azure offering on 20 March 2025 at 10:00-10:45am. Cosmin Pantea (EMEA Cloud Presales) will present the architecture and give a demo of Veeam Data Cloud for Azure.  To register:https://register.gotowebinar.com/register/8070037561311020123 Thanks

How to Fix a Physical Server Showing Offline in the Infrastructure ViewIf your Physical Server is showing Offline in the Infrastructure view and the backup job continues to fail even after multiple retries, the issue may not be related to the backup software. In many cases, the root cause lies within the operating system.SymptomsYou may notice one or more of the following issues:The physical server appears Offline in the Infrastructure console. Backup jobs fail repeatedly. Unable to start or stop Windows services. Unable to uninstall the antivirus software. Multiple server restarts do not resolve the issue. Adding the backup application paths to the antivirus exclusion list does not help. Unable to uninstall the backup agent manually.If you are experiencing these symptoms, it is a strong indication that the issue should be investigated from the Operating System (OS) side.Troubleshooting Steps1. Check Windows UpdatesThe first step is to verify whether the server is fully updated.Open Wi

​I built another HA cluster this week and grabbed screenshots along the way. The architecture side was covered in my last post, so I am keeping this one short. PrerequisitesTwo Veeam software appliances at the same patch level. Veeam Data Platform Premium. HA is not included in standard licenses. Both appliances on the same subnet. DNS records for the primary node, the secondary node, and the cluster DNS name. A cluster virtual IP address available on the subnet. Connectivity between the two appliances. Appliance admin credentials are available for cluster creation.Enable HA on each nodeOn both appliances, log into the host management console. Go to backup infrastructure, then high availability, and submit the request. Do this on both nodes before building the cluster from the VBR Console.In this example, the HA request is approved on the appliance before the cluster is assembled.Screenshot: host management console showing the high availability request approved.  Create the cluster fro

Sometime last year, ​@ertelle1 created the below blogpost where she stated Veeam Recovery Ochestrator now supports Microsoft Hyper-V “Veeam Recovery Orchestrator 7.2 - Available Now!”With the current opportunity available to some of us as documented below, I have decided to create various articles to reinforce my knowledge.Since the Orchestrator server must be connected to the SCVMM servers or Hyper-V Cluster (which I no longer have in my lab) enviionrment. I will be showing you guys the steps to install System Center Virtual Machine Manager (SCVMM) in this guide, and how to connect SCVMM to VRO in a subsequent article. VMM 2025 supports Windows Server 2025 hosts and Virtual Machines. It works with TLS 1.3, and the dependency on legacy authentication protocols, such as NTLM and CredSSP, has reduced significantly. Also, if you are running System Center 2025. The Service Provider Foundation (SPF) will be discontinued as its capabilities are now built into Azure Arc-enabled System Center

I know this question could lead to more questions like “Why?” - but we have a client who wants to have an on-prem copy of their M365 VDC back-up. How would this be done? What would the egress charges be calculated? 

Hi For those of you that missed the physical event VUG BeLux on 25/06/2026, I will give you a summary of the content of my session... Again it was a pleasure to present this session during our recent VUG, where we explored how modern backup architectures must evolve to address today's cyber threats and the changing virtualization landscape.Of course I would like to talk about my favourite topic 🤣From Backup to Cyber ResilienceFor years, the 3-2-1-1-0 rule has been the gold standard for data protection. It remains the foundation of a resilient backup strategy, providing protection against hardware failures, human error and traditional disaster scenarios.However, ransomware has fundamentally changed the threat model. Attackers no longer focus solely on production systems—they actively target backup infrastructure, compromise credentials, corrupt backup chains and wait for retention periods to expire before launching an attack.This raises an important question:Is a single immutable copy

Simple question, but I don’t think this is possible from reading up about this, there is a great video on migrating, but I think this assumes you still have the old VMWare infrastructure as well as your destination Hyper-V. So, the question is then, can you restore a full backup of a VMWare VM, onto Hyper-V? Assume pre-reqs like removing vmware tools are taken care of, but the actual conversion to Hyper-V can this be done without running your source VMW environment?

Hi,I am trying to restore a file from a Veeam backup for one of our Windows file servers, but it looks like Veeam treating the VM as a linux agent and is asking me to set up a helper appliance. I tested another file server, and it works as usual without requiring one. I have also ran rescan on the hyper-v and the VM is showing up as MS windows server 2019 in the inventory.Do you have any suggestions on what might be causing this? Thank you!