Discussion Boards

We have replaced are our physical servers and are decommissioning the old servers.  I have two servers that were setup and functioning as proxies in Veeam.  When i go to remove the server, i get a message saying the server can’t be removed because it is still associated with backups.  The backups it indicates are blocking are no longer jobs and the only references to those names i can find are in the Orphaned and Exported Disks section, but there is no option in there showing an association to a server or a way to change anything.I have opened a case with support (02943295) and so far they are suggesting that we will need to manually edit the database records to remove this association.I am curious if any one else has had to manually modify database records just to remove old servers from Veeam Backup and Replication?  This does not seem to make sense and is likely just masking the real issue.

Hi all,I had a customer who needed a way to obtain Veeam Software Appliance (VAS) updates within a closed OT/dark site/closed environment.However, the challenge was that they lacked Linux experience and would prefer to do everything in native Windows, without using WSL (Windows Subsystem for Linux). If you have no idea what I am talking about, read this section of the Veeam help center: https://helpcenter.veeam.com/docs/vbr/userguide/update_appliance_configure_updates.html?ver=13#setting-up-custom-update-configurationSo my idea was to build/configure two components:1) A PowerShell script that can be run in Windows to download the necessary files from repository.veeam.com to a computer with internet access and

I have been validating MongoDB full instance restore using Veeam Explorer for MongoDB (VBR v13) and would like to raise a discussion related to file ownership and permissions after restoring.Observed BehaviorWhen restoring a full MongoDB instance to a Linux server, the restored MongoDB data files are owned by the OS user used during the restore process (restore authentication user).As a result:MongoDB service fails to start under the original mongod service account, or The node cannot be cleanly added back to an existing MongoDB replica set Manual post‑restore steps are required (chown / chmod) to revert ownership to the original MongoDB service userThis aligns with current permission requirements documented for MongoDB restore operations, where the restore user m

I would like to consult your suggestions and recommendations for my case. Please refer to the Veeam infrastructure diagram below. There are two Linux Hardened Repositories in the environment. The customer needs to upgrade the operating system from RHEL 9.7 to a supported version, as RHEL 9.7 will reach end of support soon. ConstraintsThe hardware for the Linux Hardened Repositories was purchased in 2023, and the customer intends to continue using it. The license subscription of RHEL will expire in December 2026. The customer is planning to upgrade to Veeam v13. 

Hi i have a PC that was being backed up wit veeam agent for windows free edition not managed by VBRThe PC is runing windows 10 22H2 ,After an agent update started getting the error failed to start service "VeeamEndpointBackupSvc"Tried repairing the agent , i tried removing it and reinstalling it still getting the same error .It seems something with the agent setting is wrong and removing the agent doesn't really clean all the data from the PC , tried even installing older version still the same.Also i am not seeing that service registered in services Any ideas how to purge the data ?  Or Fix this issue ?Thanks

Hello, I have a cluster on my Veeam v13 software appliance I’m looking to configure with CDP, however when i go to install the I/O filter the cluster doesn’t show up. What am I missing. I do have CDP configured on Veeam and another cluster is configured with it. Any ideas? 

I installed the Veeam 12.3.2.3617 on a virtual Windows Server 2025 and this has been a very bad experience.  I started to migrate the repository data to the new server, but it has become very unusable.  Now when I look up the issues on the web with Veeam, other people seem to have similar issues when using server 2025 with the repository on a ReFS file system.  At this point, everything is in limbo, meaning that the server randomly hangs when Veeam runs.  30% of the repository has been moved, but I can’t seem to do anything with the server.  Every time we try to access Veeam repository it just hangs.Does anyone have any suggestions other than scrapping the Veeam backup installation completely?thanksMatt

We have to diable Backup Jobs for Updates and reboots. There is a risk of letting the jobs diabled after reboot! It would be great to disable the Jobs in the GUI for some time only! With API calls we have to diable MFA for this account what can bring a security risk!  

Let me explain the customer environment first.Customer has 3 Dell Poweredge servers (will name them pe1, pe2, pe3) and 1 Dell Powervault server. Customer uses pe1 and pe2 and has deployed 2 windows machines on them with hyperv on them respectively, pe1 has hyperv1 and pe2 has hyperv2. Customer has taken the storage of these hypervs from the Del Powervault server so that they have a large size. Customer has deployed a windows server on pe3 where veeam has been installed and the backup repository is on that pe3. Now, we added the 2 hyperv on veeam by adding them as standalone hyperv, hyperv 1 has 6 windows VMs under it and hyperv2 has 5 windows VMs under it.One of the windows VMs is showing a used capacity of 50 GB. Now this windows machine is a file server, has 2 partitions, the C partition where the 50 GB is used , and another Partition, the D partition that has almost 3 TB of files on them.On Veeam i only see the 50 GB used. If i run a backup schedule in or

Hello, I try to restore some email for specific user let say user1@mydomain.com but i have error :When restore using user1@mydomain.comNone of the required roles (Global Administrator, Exchange Administrator) is assigned to the user : user1@mydomain.com When restore using administrator accountFailed to open mailbox : user1@mydomain.com. Failed to Access mailbox. The specific object was not found in the store. Default folder root not found. Anyone know why?

[Post updated on January 23rd]As a Solution Engineer, I never demo or validate a solution in production, and I shouldn’t. MS Dev tenants are the standard: isolated, safe, and disposable.On paper, they’re ideal: all M365 services are provisioned, licensed, and ready.In reality, they’re empty shells. Blank mailboxes. Empty SharePoint sites. Silent Teams. No data, no history, no behavior. And without behavior, I can’t properly demonstrate, test, or stress a solution.That’s the real issue: I don’t need just a tenant, I need a living environment. One that reflects real-world structures, volumes, permissions, and inconsistencies. Without that, demos feel artificial, performance tests are misleading, and edge cases only appear in production.I started by building scripts to automate content creation in M365. It worked, up to a point.As soon as I needed randomness in the assets, multiple item types, and all their specific behaviors, the setup bec

This is the second time my Veeam 13 console cannot connect and shows the error below.The first time I faced this issue, I reinstalled VBR and it worked normally. However, now that I am facing it for the second time, I feel there might be a bug in this version.After checking the Veeam services, I found that there are three services that cannot start:Veeam Backup Server RESTful API Service Veeam Explorers Recovery Service Veeam Web ServiceHas anyone else experienced the same issue?   

Many vendors talk about "ransomware resilience".In real production environments, what are you actually doing with Veeam?Immutable repositories? Air-gapped? Object Lock?What failed in real attacks?Looking forward to your experiences and honest feedback.This could be valuable for everyone designing resilient backup environments.

Hi AllI’m currently assisting a client with a Veeam ONE deployment and they would like to send alarm notifications directly to Telegram in addition to the standard email alerts.Has anyone successfully implemented this type of integration? What method did you use? Was it done specifically with Veeam ONE or through Veeam Backup & Replication events? Has anyone tested or confirmed that it still works with Veeam 13? From what I have found it is possible, by default Veeam ONE natively supports email and SNMP notifications, with other integrations typically handled through scripts or external tools.I’m trying to confirm real-world experiences and any recommended approaches before implementing it for the client.Any guidance, scripts, or best-practice recommendations would be appreciated.

The error that I am getting is Outdated being agents, please upgrade or remove the following theme Agents from the production configuration. Shared-FS01 Veeam agent for windows 3.0.1.1039. And we got rid of that file share. But for some reason Veeam is still seeing it as a stale agent. I went back to the beam backup and replication console went to infrastructure physical. I found it an unmanaged, but it wouldn't allow me to delete it. So I tried creating a temp protection group. And the era I got was remote deployment and management is available for license agents only. Please change your backup service settings to allow manage agents to consume the license then perform a protection. Rescan. Then I went back to unmanaged and it disappeared.Sorry, I know to this whole Veeam thing. I have been tasked with it and I have very little experience with Veeam. Thanks.

Hello, Is there some Visio / Draw IO sample about common Veeam architecture ? I’m not “good” to create them and I guess there are some provided by veeam :)  Thanks for your help

OS is Linux Mint Mate 22.  Been running VAL v.6 successfully for some time, now looking to update to v.13.  File downloaded, only option seems to be .iso for which I use Balena Etcher.  BE says, problem with this file, and cannot continue.  Ran the download three times, BE tells me the same thing with each of the downloaded files.Previous Veeam downloads were .deb files, used for ubuntu/debian systems.  Could be there isn’t or won’t be such for v.13.  Anyone know whether v.12 is available?

I was running the Community Edition ver. 8.2.0.2202 on my Windows Server 2025 when a notice appeared to install the latest update for Veeam Backup for Microsoft 365 8.3.    (Community Edition)I did that upgrade but it jacked up my system. I got an "Installation Failure" with no useful information in the log. After much searching, I found this https://forums.veeam.com/veeam-backup-for-microsoft-365-f47/unable-to-install-vbo365-on-a-fresh-windows-11-system-t101611.htmlI used some of the suggestions there and I finally got 8.3.0.2201 installed.But now I get the "No connection could be made b/c the target machine refused it." I briefly saw something about a installation issue with multi-homed server

Hello. I have installed the newly released version 13 of the software appliance. I also have a Synology DS923+ NAS. Both devices are separate and are not added to any domain. Could you please advise me on the safest way to connect this NAS to the newly released appliance? I tried to connect to the SMB share, but I am getting Kerberos errors. I have version 12 installed on Windows Server, and the connection works there. Now I am testing the appliance and encountering connection problems. Thank you in advance for your help.

Dear Veeam team,I am trying to uninstall VBR 13 but get stuck the issue below. I have checked both services: Veeam Backup Update Service and Veeam Backup Service. There is no Veeam Backup Service anymore.Please advise me for this case 

I’m unable to connect VSPC to Cloud Connect. When I try to add the Cloud Connect server from Configuration → Catalog → Veeam Cloud Connect, it fails with “Failed to connect to the deployment service.” I’ve already tried disabling Windows Firewall and antivirus, but the issue persists. I can install the agent manually on the Cloud Connect server without any errors; however, after installation, the server only appears under Discovery in VSPC and does not show up under Catalog → Cloud Connect → Veeam Cloud Connect Integration. Both servers are on the same subnet with no firewall in between.  

Backup for vmsrv0 on hyper v host1 worked always before, but for hyper v host1 i forgot that i turned off vmsrv0 vm LOL, so veeam was backing up a turned off vm. I went into host1 and switched from vmsrv0 to vmsrv1 running the same/replica (OS-Suse Linux Enterprise 12), did not continue backup chain, i just created a new backup to drive. Now i get vmsrv1 Processing vmsrv1 Error: Error: The requested operation could not be completed due to a file system limitation Asynchronous request operation has failed. [requestsize = 1056768] [offset = 240544063488] Failed to download disk 'drive_1_backup.vhdx'. Reconnectable protocol device was closed. Failed to upload disk 'shadowSpec>' Agent failed to process method {DataTransfer.SyncDisk}. Hard disk 2 (4 TB) Error: The requested operation could not be completed due to a file system limitation Asynchronous request operation has failed. [requestsize = 1056768] [offset = 240544063488] Failed to download disk 'drive_1_backup.vhdx'. Reconnectab

I am using /api/query?type=’BackupJobSession’ to retrieve all backup job sessions. Does anybody know if this query will retrieve sessions for ‘Backup to Tape’ jobs as well? I don’t have the ability to setup such jobs in my lab and I can not test it. Alternatively is there a different query to retrieve sessions for such jobs?