Discussion Boards

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

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

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 figure out your next steps, it gives you practical guidance that fits whatever you’re working with.You can access Veeam Intelligence within your product and within Veeam tec

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 

Hi everyone,just wanted to share something we hit recently after deploying Veeam B&R v13 in a Hyper-V environment.The issueAfter the upgrade, Application-Aware Processing stopped working.Symptoms:No Hyper-V production checkpoints Multiple VMs affected Happening across different customersWhat we checkedWe went through all the usual stuff:Firewall → OK Permissions → OK VSS → OK Integration services → OKEverything looked fine… but still no AAP.The causeAfter a long search, we found a post from mazvazzeg that pointed us in the right direction.Turns out it’s a wrong registry value for the Hyper-V VSS service (vmicvss).Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmicvssWrong value in ImagePath: %systemroot%\system32\svchost.exe -k VeeamHvVssGroupstemNetworkRestrictedRedirectionGuard -pThis basically prevents the service from starting.The fixChange it to: %SystemRoot%\System32\svchost.exe -k VeeamHvVssGroup -pAfter that:Service starts correctly AAP works again Production ch

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 backup copy, but not all backup files are copied to another repository.Thanks and regards.

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 After (v13): ❌ Scripts only work when executed by a Backup Administrator ❌ Direct impact on monitoring (scripts no longer return data) Error MessageWhen attempting to run PowerShell commands using a non‑administrator

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.

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

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 backup data created by a regular "Backup Job" for a "Backup Copy Job" via the Map Backup feature? Is there an

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?

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  

 In my Azure Local node the backup job always error for only one node with below error (node 03).If i scan the hyper-v cluster then all nodes is up to date. But after the job is run then this 03 node always back to  

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.

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?

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 decided it was a good idea to use t

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?

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 hang issues in a variety of applications, including Veeam Agent for Windows Community Edition. 

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.

Hello Expert,I am looking for advice on the best way to protect our Veeam VBR/DB. Our environment is currently set up as follows:Veeam VBR Server: Running as a VM on VMware.Database Server: Running as a separate, dedicated VM (MS SQL).Current Backup: We are currently including both the VBR VM and the DB VM in a standard VMware snapshot-based backup job.Is this considered a "good" or "supported" configuration? I am concerned about:Stun/Freeze: Will the VMware snapshot "stun" cause the VBR server to lose its connection to the remote database during jobs?Consistency: Does a standard VM backup ensure the VBR server and the separate DB VM stay in sync if a restore is needed?Circular Dependency: If our VMware cluster goes down, we lose our backup server.Should I exclude these VMs from our regular backup jobs and rely solely on the Configuration Backup tool, or is there a benefit to using Veeam Agent for these specific servers instead?

I enabled MFA for login and if I login from veeam server then I asked to enter the MFA every I open the console.If i login from veeam console from my laptop then i’m only asked to enter the MFA when 1st time connect to the server. After that even i already reboot my laptop then i never asked to enter the MFA again.

After moving from v12 to v13 we have started seeing:Backup copy RPO violation: [server] was not copied within 165 days 23 hours 6 minutesThese seem to occur at semi-regular intervals to VM’s residing on a Proxmox server, maybe every14 days. What is odd is regular backups and offsite copies run daily and without error, even these jobsreporting RPO violations. Just in case, when these errors popup we run an active full and a copy. Werun tests to ensure they are working and can be restored.Any ideas why the error is occurring?