Discussion Boards

 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  

After months of trying to get upgraded to v12, I finally got Veaam to v13 on Windows 10.   The backup speed is amazing, over 200 MB/s.  It is maxing out the 1 Gbps network.   The two tape drives are running at 76-80 MB/s.   I did have to remove my SCSI tape drive to get to Windows 10.   I will have to replace the motherboard to get to Windows 11.   Today, my 2.5G network upgrade arrives.  It wa $170 for two managed switched for VLANs and 4 NICs.  I ordered two TP-Link Omada 2.5G 5 port managed switches to get VLANs on my Fortinet firewall.  I need them to get more DHCPv6-PD subnets from AT&T fiber.  I am setting up VLANs on DMZ and internal6 for my workstations and servers.  I have four Brostrend 2.5G Ubuntu capable NICs cards.Two for my HP Z840 Hyper-V server.  One for DMZ and one for Internal6 for all my VMs.  One for my workstation and tape server.   By the weekend, I should have everything configured and ready to test network performance on Veaam.  So far no issues with Veeam. 

Receiving error message “invalid system configuration detected”. Checked the logs under C:\ProgramData\Veeam\Setup\Temp\ but not finding anything. The logs end with Vmacheck upgrade.

Hi Veeam Community  I’m unable to run any backups on Veeam Agent for Windows (6.3.1.1074, free edition). While my setup was working previously, I now get the error “Failed to create VSS snapshot” when attempting to run a backup.My destination is an SMB share on a local Windows Server (Server 2022 OS). Other devices on my network (In identical configurations, “Entire Computer”) are able to back up to that share successfully, it’s just this one machine that’s failing.I have tried the following and it only kept the backups successfull without any warnings for 2-3 days and then reoccursRan the following commands:net stop vss net start vss You can also restart these services in services.msc: Volume Shadow Copy Microsoft Software Shadow Copy ProvideWhen running the vssadmin list writers command I see that this writer times out and others show no errorsAny assistance with this issue would be greatly appreciated

While installing Veeam Backup & Replication v13.0.0.4967 from the ISO (Rocky Linux–based appliance), the installer stops mid-way with an “An unknown error has occurred” message from Anaconda.The traceback points to dnf/base.py related to remote package selection or repository fetching.This occurred during the “Downloading packages” stage. Who else has run into this error? Another error, you could run into is this “Appliance Installation Stuck on "Configuring addons" and the following KB addresses what to do correctly.

Instead of backing up the volume, it’s taking multiple copies of the data, one for each snapshot. I think you need to allow specification of which btrfs snapshots/subvolumes not to backup as otherwise you copy the volume multiple times which is really not sensible.

root@charon:/home/amonra# apt-get install blksnap veeamReading package lists... DoneBuilding dependency tree... DoneReading state information... DoneE: Unable to locate package blksnapE: Unable to locate package veeamroot@charon:/home/amonra# So clearly I need to do something before I can install. The manual didn’t say where the repository was.

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.

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

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

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. 

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

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

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 

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", "Java2404_10.10.10.7", "PaperMC_10.10.10.8" ) # List of VMs to back upRemove-Item -Path

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

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.