Discussion Boards

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.

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

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

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 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 

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 have a requirement to make monthly backup and store to different tape catridge.Example for January will be store to media pool januari, februari to media pool februari and etc and should use full backup. So January 2026 will be full backup and on January 2027 will overwrite Januari 2026 and make full backup for Januari 2027.I try to make job backup ro running monthly and set the retention to 1 days then for 1st time the job running full like what i expected. Then i try to run in next day for simulate the job running on Januari 2027 then the backup running in incremental and not full backup.Can someone help for my issue here? 

I am currently migrating my backup repository.Previously, I used a Linux Hardened Repository for primary backups, but I have now switched to an ExaGrid backup appliance. The primary backup to the new ExaGrid device has been successfully completed.Now, I want to reuse the backup data stored in the old Linux repository as a secondary target using the Backup CopyBefore: Primary (Linux Repository only)After: Primary (ExaGrid) --> Backup Copy --> Secondary (Linux Repository)However, when I try to select the existing Linux repository and use the "Map Backup" option in the Backup Copy job settings, it fails to recognize the existing backup data. I have already deleted the original backup job from the Linux repository, and the data is currently showing as Disk (Orphaned)The Veeam version is 12.3.2, and the backup source is a vSphere VM. My questions are:Is it impossible to reuse backu

I have backup job to create full backup to the disk then to tape. Total full backup no more than 2TB but why veeam use 2 tape catridge to backup this?Each catridge have 10.9TB and one only one catridge should be enough. 

Fresh install of backup 13 latest version adding a secondary hv host to be backed up (standalone) get the following 20/04/2026 19:03:46 Failed : Infrastructure item save failed Error: No connection could be made because the target machine actively refused it. reinstalled, turned off av, disabled firewall, rebooted all the same - the 3rd HV host is fine

Referencing thi site - https://helpcenter.veeam.com/docs/vbr/userguide/repos_rman.html?zoom_highlight=storeonce+RMAN&ver=13 Why is there a limit of 3,000,000 files per Catalyst Store when using HPE StoreOnce as a backup repository for Veeam Plug-In backups?

We have a Veeam Backup Enterprise Manager that connects to several Veeam B&R servers at our remote sites and child companies. As we’ve been upgrading to V13, the requirement to use HTTPS to connect to the VBR server is causing endless issues. Most of these sites are smaller, and only have one external IP that’s used for something user-facing, such as client VPN. (You know, because default ports are good for end users that wouldn’t know how to specify them.)V12 used Veeam-specific custom ports that we could forward to the VBR servers and there was no issue whatsoever, but the upgrade to V13 has ruined this. It is necessary to be able to specify a custom port for BEM to collect data from VBR servers. We’re not pointing a web browser at this, and backup software is an ideal place for knowledgeable IT staff to use and document custom ports, or even just a single nonstandard port that Veeam uses by default (like is used to with 9392). I don’t know who deci

Hi, Today I have another issue with a hardened repository The VHR is in emergency mode with the message “cannot open access to the console - the root account is locked”I followed the step from this document https://www.veeam.com/kb4663 but unfortunately the root account remains locked. Any further advise? Thanks  

doing a trial version as thinking of switch to the linux hosted server but have run into an issue while testing. While setting up the backup it said preferred method was certificate for authentication for backups which I did and the backup works just fine. Now comes the fun part I cannot restore back to the windows PC, the browse and OK buttons are greyed out. If I choose other location I have to pick SSH for authentication which I am confused about, anyway I can restore the file to the veeam server and copy it back but that's a very ugly way to do things. What am I missing here or failed to setup properly?

Hi,Today I upgrade in my homelab (with NFR license) from Veam 12.3 to 13. I have 3 Proxmox node and three Proxmox backup job, Everything was running fine before the upgrade. Now with 13 I discovered that Proxmox is missing, when I click “add new server” and virtualization platform Proxmox is not there. Proxmox plug in is installed version 13.3.1.7 No idea what has happened with the upgrade. The upgrade process ran without an issue. Any idea? What I already did is uninstall the Veeam Proxmox plug-in and reinstalled installed after a restart of each step.

We have a few clients that have a single physical server and have a service or application that is already using port 443.  So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used and v13 uses it for the Veeam Web Service.  Assuming we can temporarily disable this service/app to get the upgrade to complete, is there a way once v13 is installed to get the Veeam Web Service to use a different port?

Hi All,I’m encountering an error when attempting a restore from VBR version 13.1.2064 (recently upgraded):“ResourceExhausted: Sending message exceeds the maximum configured message size.”Does anyone know if this is a known issue or bug in the newer VBR versions?