Discussion Boards

I’m testing several On-Prem S3 Object Backups ( Backing up Object Storage in 12.1) no matter which of the 4 systems I try I get the attached error. All of the systems have “buckets” that Veeam 12.1 has written to, and they have data in them, and are set as repo’s in VBR that I am using for this test. Suggestions? Error is attached - I get it on all of them. 

I am having trouble accessing the remaining 3 workstations I don't know where they are I only have 4 workstations here. I am here at the VBR.

I have VBR installed in Site-B to backup VM under hyper-v and vmware in Site-A.Connection from Site-B to Site-A using ipsec vpn site to site with 2 internet link for redundant.The VPN have same policy for both connections. When the link use primary link then the VBR can backup the VM but if the primary link and connection switched to the backup link then i got error only for Vmware when using backup proxy.I try to ping from the backup proxy in Site-A then the proxy is able to reach HS-W2019.This error mean the backup proxy is not able to connect to the HS-W2K19 on port 2503? Error: Failed to connect to the endpoint [HS-W2K19:2503]. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 

Hi, I have a protection group of 8 windows machines.  The machines were added to the protection group using their host names.  The machines get their ip from a DHCP server.  I see that one of the machines, originally with ip 192.168.1.151, is not 192.168.1.155 and is not being backed up.  Is there a way to update the protection group for the new ip?  Unfortunately, I cannot revert back to the original ip because that ip is now being used by another machine (that’s not part of the protection group).

Hello Everyone,We are using Veeam Data Cloud for Microsoft 365 Flex with a license for 250 users.During the initial setup, we tested with 1 user to validate the configuration. After confirming everything was working properly, we deleted this backup job and created a new policy to protect the actual 250 production users.However, we are still seeing the backup for the original test user, and the license usage shows 251 users consumed, even though our license count is 250.I have a few questions regarding this situation: How can we delete or revoke this test user so that it no longer consumes a license? If we keep the test user without removing it, will this impact production users (e.g., only 249 users protected)? Is there any automatic cleanup or retention process that eventually removes old test accounts from the license count, or must it always be handled manually? Any guidance on how to properly handle this case would be greatly appreciated.Thanks in advance for your support. 

Object First storage is used in our main data center.Regional backups are first stored locally, then copied to Object First at the main site using a forever incremental job (using Scale Out repo and Object First configured as capacity tier)Now If full backup data needs to be sent to AWS (e.g., when decommissioning a regional application server), it can be done from the main site through a secondary copy—without using the regional office’s primary copy.

I have recently installed the Scale Computing plugin into our Veeam B&R 12.3.2 server. If we are currently using Microsoft Agent Backups, is there a migration path to moving to direct VM guest backups via the Scale plugin? If not, can I utilize VM guest backups via Scale plugins for 'new' guest servers and also back up pre-existing servers using the Microsoft Agent method?

I always having this issue when perform the backup or replication, the virtual machine will create the snapshot and once finish will delete the snapshot. When this activity happen the VM will like stun and loss ping. How can we perform resolve this? 

Build new windows (2022) server for Veeam B7R 12.3.2.4165 and imported the config from older server.Since then every backup job has a warning “Sending e-mail report Details: Failed to wait mutex VeeamMailServiceAzureToken: timeout 00:01:00 sec exceeded”  Opening options takes sometimes 10 min or more, but when it does I can send test mails successfully.After saving the first backups work with email, after a day its the same error.When opening options sometimes this message appears: I don't know what's wrong here server has plenty of power.Grtz.Bart P.s. old server did not have this problem. 

Hello Veeam Community,I’m performing a restore process in Veeam Backup for Google Cloud and encountered an issue after the data restoration phase. Here are the key log details:  The disk restore completed successfully, but the instance restore failed due to snapshot creation error. Question:Has anyone faced this issue in GCP restores? What could cause snapshot creation to fail after disk restoration? Any recommended troubleshooting steps or permissions to check? 

Hi.If someone had completed the training of Veeam Backup & Replication v12.3: Configure, Manage, and Recover (VMCE), Can they just attempt the exam for the same or they can also attempt the exam for VMCE 13 as well or they have to attend the VMCE 13 training to attend the v13 exam. TIA

My recent discovery so it could help someone not to loose time. And maybe if there is a solution I’ll be most thankful.So with Proxmox version 9 you need to set Machine type to version 9.2 instead of Default as it defaults to 10 and that causes Veeam backup to fail.  That will insure that your backup will be sucesful and restore will work too. I have issue, where I am migrating servers from Hyper-v to Proxmox and usual and most painless solution was to use Veeam Backup&Restore as intermediary as we are already using it.But in this case restore to proxmox fails as when VM is created is created with default version for machine type and this defaults to 10 and this results in: Failed to prepare disks for restore. (If anybody knows how to convince the process to default to 9.2 Mychine type I’ll buy you a beer).I tested this on 12.3 and on veeam appliance 13 with the same result. I can restore VM, that was originally backed from Proxmox as it will bring it’s machine type version along.

I was trying to upgrade the Veeam Enterprise Manager to v12.3.2.4165, I noticed the version is showing 12.3.2.3617 on the Upgrade page.I view detailed information about Enterprise Manager and its components, the Veeam Backup Enterprise Manager Service build: 12.3.2.4165Veeam Catalog Data Service build:12.3.2.3617Web Site Information Build: 12.3.2.3617bugs?

Because of the new v11-feature of immutable backups on XFS filesystem, I am looking for real-world experiences with XFS as Repository.I just read through this forum entry:https://forums.veeam.com/veeam-backup-replication-f2/v10-xfs-all-there-is-to-know-t65222-30.htmland the closing experience of user ferrus:https://forums.veeam.com/veeam-backup-replication-f2/v10-xfs-all-there-is-to-know-t65222-30.html#p388579 Sounds very good to me so far. I can remember first implementations of ReFS Block Cloning. Lets say, it does not work that fine at the beginning.Would you share some of your experiences with XFS as Veeam Repository? I would be interested in:stability  performance (over time) needs for troubleshooting administrative effortThanks!

Hi all,looking for real-world guidance on NIC sizing for a Linux Hardened Repository.Context (VBR 12.x or 13.x ; Linux appliance vs Windows?): Repository: Linux Hardened Repo (XFS, immutability). Repo server NIC options: either 2×10/25GbE or 4×10/25GbE. Backup server/proxies can also be 2×10/25GbE or 4×10/25GbE. Primary storage for the VMware workloads will be either 32G FC (Direct SAN from proxies) or 10/25GbE iSCSI. Single site, LAN backups (no WAN in the data path). Goal: Max throughput and resilience without adding complexity that doesn’t pay off.Has anyone measured a meaningful improvement going from 2×25GbE to 4×25GbE on a single Linux repo?What actually worked (or didn’t) in your environments —  “wish-I-knew” lessons appreciated :-) 

Hey everyone,As we prepare for the upcoming update that introduces support for Veeam v13 on Windows, I wanted to ask:What migration strategy are you planning to adopt and why ?Will you simply upgrade your existing Veeam Windows server to v13? Or do you plan to migrate to v13 and then transition to the Veeam Software Appliance?So far, I haven't found any official discussion about the migration process from Windows to Linux. Ideally, I'm looking for a solution that allows me to back up and restore my settings during this migration. Personally, for all new projects, I’m planning to propose the new Linux-based appliance, even though some aspects still require optimization and improvement. In cases where migration is possible, I would tend to recommend switching to the appliance for smaller infrastructures as well — mainly to benefit from the native hardening layer and eliminate Windows licensing costs. Smaller companies often have limited time to dedicate to cybersecurity.For larger infras

Hi all,the in place upgrade of Veeam ONE 12.3.x to 13.x doesn’t work. The MSI packet for the monitor client won’t be found. The path to the MSI file is shown as “1” and giving the correct path to the mounted ISO ends in an error message that the MSI doesn’t fit to the system (Windows 10 22H2).What can I do? At the moment I do not plan to update my Windows machine. My way is to go away from Windows in the next months.Kind Regards

You might have found the same information when you upgrade the previous version of Veeam Backup and Replication server to v12.3.2.4165.The version shows 12.3.2.3617, not 12.3.2.4165.After the upgrade is complete, verify the Veeam Backup & Replication version from the Veeam Backup & Replication console (Help | About). It shows the correct version information. 

Hello everyone!Veeam 12.3.2.3617, Community Edition, Workstation Backup by veeam agentI’m having an issue with one of my home PCs. When I try to back it up, an error appears.29.09.2025 21:31:17 :: Error: Unable to resend traffic block '15863' because traffic history doesn't contain this block. History low block id '15869'.Failed to upload disk. Skipped arguments: [EmulatedDiskSpec>];Agent failed to process method {DataTransfer.SyncDisk}.Exception from server: There is no traffic block '15863' on the source side.Unable to retrieve next block transmission command. Number of already processed blocks: [25496].Failed to download disk 'bdd448f6-e7b0-4f2b-93b3-6eb675ad51c3'   Backups of two other PCs to the same storage complete without any problems. What could be causing this behavior?I tried replacing the target HDD — it didn’t help; the error can also appear when backing up the SSD (the drive’s health is normal, no errors).I tried different backup types (volume, file-level, entire PC) —

Hi everyone,Im going to update Veeam from 12.3.2.3617 to 12.3.2.4165. How much storage should I keep free to upgrade it?Regards.

Here’s one to find out who has the largest backup in the forums. Currently my largest server I backup is 45.1TB.  The largest one I had backing up was 115TB.  It took a while but worked fine.  I’ve been working on splitting it up in to multiple file servers to allow more concurrent streams to our backup/tape jobs. 

Hi everyone, So we just made the switch from Symantec Backup Exec to Veeam a couple months ago, and so far I'm very happy. With Backup Exec however, you had the option to permanently retain backups, which seems to be missing from Veeam. For Windows Agent backups, Veeam forces you to choose a retention period for a maximum of 730 days or restore points. Problem is, this customer requires permanent retention with the ability to restore data from 10 or 20 years ago, if possible.  What are my options here with Veeam? Isn't there a way to disable the retention policy or retain data beyond 730 days? And believe me, I've looked at all of Veeam's program options and haven't been able to find anything to this effect. We can't be the only company with a permanent retention requirement. Thanks for your help!Kurt

We have received an update alert for recent CVE for KB ID 4771, to install a patch. What we want to understand is not in any guide, is - Is this patch just for our Windows VBR server…? Are there any pre reqs. Going through the setup of the .exe from the ISO there are no checks and no reboot required, this was tested installed on a non Veeam server which may not give the correct results…?Thanks in advance Tony

I’m running Veeam B&R v12. Veeam is the only backup software I’ve used that doesn’t have the option to backup a single server from a Backup Job. It’s all or nothing.

Seeking field experience for a Veeam repository on HPE Alletra 4120 (Linux Hardened repo) does SSD cache drives deliver measurable gains (ingest/synthetic/merge) compared to simply adding spindles?