Community

When designing a Hyper‑V backup architecture, one of the most important decisions you’ll make is how will backups be moved from a hypervisor and how are they processed. In Veeam Backup & Replication, Hyper‑V backups rely on backup proxies, and unlike vSphere, Hyper‑V proxy behavior comes with some unique considerations that require upfront planning.Hyper‑V supports two types of backup proxies:On‑host proxies Off‑host proxiesAt a high level, these operate similarly to VMware proxies—but the implementation details, limitations, and operational overhead are significantly different. Let’s break them down and discuss when (and when not) to use each. On‑Host Proxy: The Default and Recommended ChoiceFor most environments, the on‑host proxy is the simplest, most reliable, and re

Yesterday, during a conversation with my colleagues at Veeam Brazil, one of them shared a very important link with me related to the Compliance Portal. It’s available inside My Veeam, where partners can download official badges.I will use seals in technical and commercial presentations; I'm sure they will be valuable. Many clients are still unaware of the wide range of certifications that Veeam offers.Take a look here:

I have been approached by the book publishing company (Packt) for my latest release - Mastering Veeam Backup & Replication 13 to see if there are 3–4 people out there that would like a copy.  There are however some conditions for receiving the book -You must read the book and complete an Amazon review of it You need to help spread the word on socials about the book and even a blog post if you canIf there is anyone in the community that is interested and can meet these conditions, drop me a DM with your details for shipping and once I have the 3–4 people I will submit that to Packt to send out your books.

Hello,as in the title, given the software stopped being able to make backups after the April windows update that changed vss and a few other things , is there anyone knowing when the situation may get fixed ?And will be fixed with an update to Agent , or need to wait for a new monthly update from microsoft ? I’m a bit new but other vendors have been I think more vocal publishing info and/or in some cases updates to their software , while I think I didn’t see anything about Agent

Drive D: is a 15k rpm SAS drive, so not at all slow

Hello All, We are currently using Veeam Backup and Replication at my company and we’re using object storage (S3) as our primary backup repository, we are planning to implement a secondary on-prem NAS storage to store full backups every once in a while as an extra safety measure.I’m evaluating NAS options and would like your recommendation for a model that is fully compatible and optimized for VBR. My required capacity for NAS is ~24 TB usable. Specifically:    1.    Recommended NAS vendors/models validated with VBR    2.    Preferred protocol (SMB vs NFS) for performance and stability    3.    Minimum hardware specifications (CPU, RAM, RAID type, network)    4.    Any known limitations or best practices for NAS as a secondary repository Thanks.

Hi, I have a few chained vsphere backup and replication jobs that can be finished in 1 hour or 10 hours or 30 hours, so scheduling them is a bit of a pain in the butt. If the network/raid is already slow at the moment, I don’t want multiple jobs running at the same time, getting more over time, causing vsphere snapshot problems etc.Is it possible to define “Don’t start this job if there is any job running already”?And if not, is it possible to insert pauses between chained jobs, so you could create a loop where 5 jobs are executed one after another, then there’s a 3 hour break, then the first job is started again? ...ideally with a window where no job is allowed to start? Thanks in advance.

On Feb 5, 2026, Microsoft officially announced that EWS in Exchange Online is being deprecated. Starting Oct 1, 2026, Microsoft will begin turning off EWS usage unless it is explicitly extended via a setting. With a deliberate “Not yet!” (aka OrganizationConfig -EwsEnabled $true), EWS is expected to remain usable until Apr 2027—however, this is not a permanent setting, just a temporary extension. So first…. What exactly is EWS? EWS stands for Exchange Web Services and was built almost 20 years ago. For

I speak with customers all the time about Disaster Recovery and if they test. Most of the time, the answer is no. In a recent customer demo, they were looking for just that. How would you simulate a Disaster Recovery with Veeam? This is what I presented to themLet’s be honest—most disaster recovery plans look great on paper. That's if you have a Disaster Recovery Plan available. I ask my customers and most don't have one. What's even worse is they don't test their restores.Diagrams are clean. Runbooks are written. Backups are “successful.”But until you simulate a real disaster, you don’t actually know if any of it works.And the worst time to find out is when production is already down.This is how to simulate a disaster recovery (DR) event step-by-step using Veeam—the same way you’d handle it in the real world, just without the panic. What You’re Trying to ProveA DR test isn’t just “can I restore a VM.”Yo

Hello community,After upgrading a Veeam Backup & Replication environment from version 12 to version 13, we started experiencing some unexpected behavior related to remote script execution, user permissions, and MFA. I’d like to check if anyone else has faced a similar situation. EnvironmentVeeam Backup & Replication recently upgraded from v12 to v13 Monitoring solution relies on PowerShell scripts executed remotely Use of Operator role / custom non‑Administrator users Scripts used for status collection and integration with external monitoring tools Issue 1 – Remote Script ExecutionAfter the upgrade to Veeam v13, scripts no longer work when executed remotely unless the user is a Veeam Backup Administrator.Before (v12): ✅ Scripts worked with Operator or custom roles Af

A couple weeks ago I had the opportunity to attend and present at the Atlantic Security Conference (ATLSECCON) in Halifax, Nova Scotia. Established in 2011, this information security conference focuses on fostering innovation, strengthening collaboration and building resilience. The conference agenda centers on everything security related; challenges, complexity and emerging threats. This was not my first time attending ATLSECCON, I have had different working roles at the event throughout the years, meaning I’ve worked booth operations, I’ve presented at the event, and I probably have coordinated just the sponsorship opportunity in the past. I am unsure of the exact number of times I have attended, but I can say I look forward to this event every year, and it only gets better over time! After I got back, I was thinking about all the se

Anyone can help me to understand about this picture?When the tape retention is over then backup day 1 will be removed and this mean 1st full backup wlll be removed. Then how we can restore the VM to the Monday? Isn’t restoring the incremental need the last full backup? 

Hi Team,Currently we are facing an issue.We have multiple full backup file for NAS backup, with condition:Backup file 1 on repository A --> inactive backup chain.Backup file 2 on repository A --> actively running.Our goal is to move all backup files (1 & 2) to another repository, because we have concern about capacity on repository A almost full.Our customers do not want to lose all the backup data stored in Repository A.My question is:Is there a way to move or copy all backup files 1 and 2 from repository A to repository B without having to disable the existing backup job that is currently running? This is because when we copy the backups, it disables the existing backup job. Our customers’ file shares are very large (ranging from tens to hundreds of TB), so backups take several days to complete, and we don’t want to lose any RPO during the daily incremental.We already use back

Migrating between sites is rarely straightforward, especially when you don't have access to the virtual infrastructure to create a replication job between sites. In this post I'll walk through a real-world migration from another provider to our own Virtual Private Cloud on VMware vCloud Director.  This will not be a build guide, but more of a high level overview of how it was accomplished and some of my findings, positive and negative. Project Background Our customer had expressed a desire to offboard from their previous service provider and onto our platform. They did not want to approach the provider before migrating, and suspected that the provider would not cooperate with setting up replication jobs to another service provider.They asked us to come up with a solution that had a low Recovery Point Objective to minimize interruption to public facing services. Key Constraints:The customer did not have access to the

DCOM timeout on {740FE937-01F7-4482-AA62-C83F0AD3D6D0}, package Microsoft.WidgetsPlatformRuntime 1.6.14.0, VSS writer enumeration hang.In the last two weeks, running Veeam Windows Agent CE on my laptop and office computer were hanging for hours showing “Preparing for backup”. I was also unable to cancel these jobs, requiring reboots.The problem here is likely a post April 15 update of Microsoft.WidgetsPlatformRuntime 1.6.14.0.Removing this package in an elevated Powershell withGet-AppxPackage *WidgetsPlatformRuntime* | Remove-AppxPackage And possibly a reboot, repairs the issue and allows backups to proceed to “Creating VSS snapshot”.You can test if you have this issue by verifying the following hangs without producing output:vssadmin list writersIt is possible that any Windows 11 machine with this widget’s runtime version will have VSS ha

Backup and recovery move fast and the stakes are high. Additionally, every environment has its own mix of platforms, workloads, policies, and pressure points. For example, one team may be protecting a handful of critical virtual machines (VMs). Another may be juggling physical servers, cloud workloads, and strict retention requirements across multiple sites. That’s exactly why we at Veeam offer so many ways to protect and recover your data.However, this flexibility comes with choices, and you don’t have to choose on your own.Veeam Intelligence an AI-powered assistant layer embedded within Veeam products and technical documentation that’s designed to help you quickly find the right path for your environment. Whether you’re setting up a new deployment, reviewing best practices, comparing feature options, or trying to

Hello, I have some File Backup and Proxmox VE Backup jobs configured in Veeam Backup & Replication. However, one of them shows an "Outdated data mover" error. When I go to Backup Infrastructure, rescan the Linux Server, and run the backup job, the error disappears and the backup runs normally.However, after a few minutes, the data mover error reappears, and the scheduled backups fail. In other words, every day I have to rescan the server to update the data mover service and perform the backup manually.I have already tried uninstalling and reinstalling the Veeam Transport service directly on the server, I deleted the /opt/veeam folder and then rescanned the server in Veeam to reinstall the agent, but the problem persists.I'm using Veeam Backup e Replication version 13, but this error started occurring when I was using version 12.The server in question is running Debian 12.I have two other servers, one also with Debian 12 and another with Debian 13, where the file backup jobs ru

I recently deployed the Veeam Plug-in for HPE Morpheus VM Essentials version 13 (RTM) on my Veeam Backup lab server, which is running v13.0.1. Once tested, I'll have it available to demonstrate to my customers. Veeam has introduced a dedicated plug‑in that enables image‑level backup and restore for virtual machines running on HPE VM Essentials. This integration brings VM Essentials into the same unified protection workflow as VMware, Hyper‑V, and other supported hypervisors. The plug‑in is not bundled with the main Veeam Backup & Replication installer, so it must be added separately. What the Veeam Plug‑in for HPE VM Essentials DoesThe plug‑in extends Veeam Backup & Replication to understand and interact with HPE VM Essentials resources. Without it, Veeam cannot discover or protect VM Essentials servers or workers. Once installed, the plug‑in enables:Discovery of HPE VM Essentials hosts Ba

I have Veeam 13 installed , I removed it and tried to install it again ,I mounted the ISO and click setup , then got the below error message  So any suggestions as seems still detect previous setup while i completely cleanup it 

 You open the Add Server wizard in Veeam Backup and Replication. You pick Microsoft Hyper-V. The next screen gives you three choices. Microsoft System Center Virtual Machine Manager. Microsoft Hyper-V cluster. Microsoft Hyper-V server (standalone).Here is the part that catches people at times. SCVMM is the first option listed in the wizard. If you do not have SCVMM in your environment and you click Next without changing the selection, VBR throws this error: "Veeam Backup & Replication server does not have Virtual Machine Manager Administrator Console installed." That is KB4351. It is not a bug. You picked the wrong type.Each option changes how VBR discovers your VMs, tracks Live Migration, deploys components, and handles backup proxy behavior. This post covers what each option does, what it requires, and when to use it. It also covers how the same choice applies in Veeam ONE.What VBR Deploys on Every Hyper-V HostRegardless of which type you

We manage several VBR deployments through Chef using the Veeam powershell module. In testing Veeam 13, we can’t seem to add groups with the Add-VBRUserRoleAssignment command in powershell. Veeam 12 works fine and in Veeam 13 adding local and domain users works fine, just no local or domain groups. We can add the groups manually through the Veeam BnR console just not with the powershell command. We are currently testing on Version 13.0.1.2067 however the previous versions of 13 seem to have the same problem. Has anyone else experienced this issue? 

I have to replace a SCSI tape drive with SAS to upgrade to Veeam 12.   I have to replace the OS on the Veeam server to upgrade to 13. I am still on Veeam 11.  I have HP Z840 workstation that is on Windows 10 Hyper-V.   I am moving VMs from VMWare 6 to this workstation.   I have so far installed our children’s minecraft servers on Ubuntu 24.04 as virtual machines.    I setup for file level backups.   I want to backup each VM in E:\Hyper-V separately.   Each VM has its own folder and VM structure in this directory.   E:\VMBackups has a script that removes and replaces each of these VMs.# Import the Hyper-V moduleImport-Module Hyper-V# Define parameters$BackupDriveLetter = "E" # Change to your backup drive$VMHost = "localhost" # Change if backing up from a different host$VMNames = @("Bedrock2404_10.10.10.3", "Bedrock2404_10.10.10.4", "Bedrock2404_10.10.10.5", "Java2404_10.10.10.6",

I recently had an issue after updating both my VBR v12 Servers to the latest patch v12.3.2.4465. As most of you know, Veeam released a Vulnerability KB back on 12 March. See below:https://www.veeam.com/kb4830From this page, there is a link to direct you to VDP v12.3 Release information:https://www.veeam.com/kb4696 , which provides the download to the latest VDP v12 Patch. A few weeks ago, I downloaded the small patch and updated both my VBR servers. All good. But, with this patch, there is a bug. And let me be more specific here, a non-functional disruption bug. (i.e. more cosmetic than anything; Jobs are unaffected)IssueThe bug is on how VBR detects the latest update/release information. Even after I installed the P