Discussion Boards

Hello.I have three servers: one is EnterpriseManager, the second is VeeamBackup, and the third has the Veeam console installed. When I launch the Veeam console on the backup server, I get the error "failed to load license from backup services." I looked at the logs and see that the client versions match. I see that a connection attempt is being made, but the connection is being closed. I don't understand why. I tried TNC fqdn for the backup server - port 9392, as well as port 9396, and there were no errors..  I changed the names and IP addresses in the logs. I don't think they're needed for analysis. CODElog uploadfiles

Hi,I noticed that I have two running backup jobs since mid May and it appears they are stalled. From the same job I get success emails each day. It appears the backups job were running fine at the scheduled time. Kind of overlap.Maybe the stalled job are leftovers when I upgrade my VBR to 13. I’m not sure. I shutdown the server twice and the stalled jobs reappears. I can right click on it and press stop, but even after hours nothing happens.How can I get rid of the running instances? I enclose two screenshotsThanks,Edy

Hi community! I’m working on an architecture to implement VRO with a Clean Room. I ll be in this kind of topology :  I notice in the prerequisites, this point : “The current release of Veeam Recovery Orchestrator (v 13.0.1) requires at minimum an initial connection to the production vCenter to gather inventory and create restore plans using vSphere tags.Connection to the production VBR is optional and only required to create restore plans based on backup jobs.”The principle of a clean room is to have an environment that is completely decoupled from production, acting as a safe place to store and test backups, and as a trusted source for a clean recovery of workloads, even if the production environments are infected or compromised.Opening network flows to production, even temporarily, seems to go against that principle in my opinion, even if those flows are limited. In my architecture, I have a production vCenter and most likely a dedicated vCenter for the clean room, since standalone E

Hello Community, I'm experiencing an issue when trying to use VM Intelligence in Veeam version 13.0.2.29, both when deployed as a VSA Appliance and when installed on Windows.When accessing the feature, I receive the following error message:"Cannot verify the product license." both Backup servers are connect to the internet. What I find strange is that I am using a valid NFR Premium license with more than 300 days remaining before expiration.I have already verified that the license is correctly installed, and the issue occurs on both deployment types, which makes me think it could be related to a VM Intelligence licensing requirement, online license validation, or possibly a bug in version 13.0.2.29.Has anyone experienced this issue before or knows of any troubleshooting steps or solutions?Any help would be greatly appreciated. Thank you! 

I was wondering if someone could help with an issue I’m having in Veeam agent for windows, I get the following error when trying to restore files from a volume backup stored on a network share. I’m using the agent in free mode.Backup sync failed[computer_name] Failed to connect to installer service[computer_name] Failed to connect to installer service[computer_name] Failed to discover installer serviceA security package specific error occurredConnect failed (RpcBindingSetAuthInfoExW)Please can you help me resolve this?

NetApp ONTAP S3 with Immutability (ONTAP 9.14 and higher) is currently not (or no longer) supported by Veeam. This means that Veeam backups on a NetApp ONTAP S3 bucket with activated Object Lock (Immutability) are currently not considered “immutable” in the sense of Veeam functionality. The main reason is that ONTAP S3 with activated Object Lock no longer fulfills all the requirements that Veeam needs for immutability.  Veeam currently only lists ONTAP S3 as “not immutable” in its own compatibility directory. The use of Immutability is therefore not officially approved NetApp is working on a solution with the support of Veeam (you may be able to get information via the NetApp Partner Manager).  --> This is ONTAP S3 (on ONTAP machines (FAS/AFF), not a NetApp Storage GRID)! Links to this:NetApp ONTAP S3 with immutability - R&D ForumsNetApp ONTAP S3 

What is this type of issue ? Anyone, please explain.   

We’re evaluating replacing out Windows VBR-servers with VSA, and I have set up a pilot machine. We need AD authentication to work for this, and I have joined the VSA to our domain.The main issue we have is that authentication is extremely slow and even if I can get “connected” pretty quick when I log in from the VBR-console, it can then take several minutes just to get past the splash screen. Even once logged in, I can get kicked out with some authentication error and “too many retries”. Also adding the AD-group to the “Veeam Administrator” role took forever and several retries. My strong suspicion is that SSSD used for this, is doing forest-wide queries, and since we are a huge company with many domains and trusts this is what takes time and causes timeouts. We’ve worked around this in other self-managed linux systems by using ldap as provider instead of “ad”, and limiting scope with ldap_serarch_base and filters, but not sure this is an option here, and pretty sure it wouldn’t be sup

Instantly bucket size is increasing. What could be the issue? What is the best practice to follow here? My concern is GCP storage.

Dear Community, What could be the possible issue?  

We are no longer able to use the "Update All" function on our Veeam Hardened Repository, as it fails with an error related to the GPG key.To clarify, we do not have a Host Management Web UI or a Veeam Appliance deployment. Our environment consists of Veeam Backup & Replication with a Linux Hardened Repository only.Username veeamsvc  Cannot access log file directorytar -czf ~/veeamlog-$(date +%Y%m%d-%H%M%S).tar.gz /var/log/VeeamBackup/tar: Removing leading `/' from member namestar: /var/log/VeeamBackup: Cannot open: Permission deniedtar: Exiting with failure status due to previous errors  Could you please advise on how to resolve the GPG key error in this configuration?  

While trying to export.BAK file while using Veeam Explorer, it gives the following message what could be the issue. This same error appear by using instant recovery, recovering to the same location and alternate location, in addition to restore DB file to the same location and alternate location. DB Unable to attach database. | Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. | The statement has been terminated. 

Version 13.0.1I am backing up to LTO 4 tape drives.   I have one job that backs up drive M: and N: backups.   One backup I get this error on drive M: and the next time on drive N:.   5/31/2026 7:27:36 AM Warning : Failed to create a VSS snapshot for M: Details: Writer 'MSMQ Writer (MSMQ)' is failed at 'VSS_WS_FAILED_AT_PREPARE_BACKUP'. The writer's timeout expired between the Freeze and Thaw events. --tr:Failed to verify writers state. --tr:Failed to create VSS snapshot. --tr:Failed to perform pre-backup tasks. (0:00:15)I changed the VSS timeout to 20 minutesI ran chkdsk and analyze and optimize on both drives.  No errors.   Windows 10 does it weekly.   More than 50% available on both drives.   I have rebooted the tape server.   I restarted the services.   The jobs are not big.  M: is around 50GB.   N: is 350GB.   I never had this issue on 11A. Still get these errors.  

when adding minIO object storage  which is deployed on local server to vbr , it throws error of certificate reterival failed from minio..note:vbr is deployed using JeOS and is applinace based,minIO uses 2083 port for its api endpoint.do any one encounter this error and have wayout!

I'm experimenting with the VHR 2.0.09 ISO. It works perfectly for me. I'm using a virtual machine for VHR where I have two disks added, one for the OS and one for the repository. I'm trying to extend the repository. What would be the recommended steps to extend the disk, or is it not possible?

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

Scenario, a customer has a complex environment where their DC doesn’t have groups for servers, Laptops, Different users in different regions. Customer want to backup servers and endpoint but the laptop backup has different requirement. Let’s say Executive backup must backup the entire PC and other users you select a specific folder.  If you deploy backup protection group using CSV files, there is a lot of manual requirements if changes happen to that environment.  The question is how to use AD to create separate requirement even thou the DC is complex.

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?

Hello Team,I am using Veeam Agent / Veeam Backup and Replication for backup storage on a NAS.I noticed that in my backup repository folder, Veeam creates:.VBK full backup files multiple .VIB incremental backup files .VBM metadata filesMy question is:Why are there multiple .VBK files stored in the same backup folder?Are these incremental restore points expected behavior?Also:Will Veeam automatically delete old .VBK and .VIB files according to the retention policy? Is it safe to manually delete multiple or older .VBK files from the repository folder if storage becomes low? How does Veeam manage the backup chain cleanup process?I want to better understand how Veeam handles incremental backup retention and storage management.Thank you. 

Hello, On new V13 VSA installation, I would like to backup some VMs (inside domain) with AAIP enabled.When I try it as I did with V12, it doesn’t work. My VSA is not in a domain.I saw for authentication only Kerberos or certificates can be used (from Veeam deployment kit) because NTLM is removed.Does that mean I need to add my VBR server to the production domain if I don’t want to use Veeam deployment kit on all my Windows VMs ?  I don’t find a way for my backup to work with AAIP enabled while I’m using domain\user account with correct privileges.I have this error : 29/05/2026 14:33:16 Failed : Failed to connect via Administrative share.Host: [COMPUTER.domain.com]. (Failed to connect to the guest OS. [Failed to connect to guest agent. Errors: 'Samba failed with error: NT_STATUS_NO_SUCH_DOMAIN [stderr: Kinit for administrateur@DOMAIN to access COMPUTER.domain.comfailed: Cannot find KDC for requested realm;Could not connect to server COMPUTER.domain.com;Connection failed: NT_STATUS_NO_SU

We are facing an issue where SentinelOne is blocking our Veeam Mount Server, even when the operation is happening on the same server (VBR Windows).These errors occurred after attempting a File Level Restore (FLR):   We tested using Interoperability mode, but the error persisted. We then tested using Performance mode, and the restore was successfully mounted.  Has anyone experienced this behavior before or found a workaround?