Unanswered questions

I am in need of some assistance from the community with Veeam Backup & Replication. I upgraded the server to 13.0.1.2067. No errors were thrown during the upgrade, logs don’t show any red flags that stick out; however the service hangs when attempting to access the localhost database server.Here is what I see:When the Veeam console is run, the “Specify backup server” page appears:After the localhost database is selected, the next window appears: The console goes no further than this, and the system doesn’t show any signs of activity. All services show as running on the server:I also tried updating .NET 8 dependencies to newer versions in case these were what may be causing the issue, but there was no change in results. I have attempted to upgrade this application twice with little success. As of now, I may need to revert back to the older version and try again, which may lead me back to here.Has anyone else encountered this when upgrading to 13.0.1.2067? If so, how was it remediate

We  are  unable to access the Veeam Backup Enterprise Manager Web UI, receiving a "localhost refused to connect" error. Initial troubleshooting steps included checking firewall rules and verifying if port 9443 was listening, but the service was not running. We identified that the Veeam Backup Enterprise Manager service was not present or visible on the server.VBR ver is 12.3.2 localhost refused to connect.Try:Checking the connectionChecking the proxy and the firewallERR_CONNECTION_REFUSEDC:\Windows\system32>netsh advfirewall firewall add rule name="veeam.xy.com 9443" dir=in action=allow protocol=TCP localport=9443Ok. Veeam Backup Enterprise Manager' service does not appear in the services.msc. I just joined in the team and don’t know if previous engineer has done anything.EM is local as per logs.Integration] EnterpriseManager: { IsAddedToEM: True, IsEnterpriseManagerLocal: True } (timestamp 2026-04-15 22:36:05) Please advise me how to get the enterprise manager back in action.   

Hallo zusammen,ich habe mal wieder eine Frage zu unserer Veeam-Umgebung.Aktuell betreiben wir die Veeam Service Provider Console (VSPC) sowie unseren Cloud Connect Server (VBR mit VCC) auf demselben System. Das Setup läuft grundsätzlich stabil und die Ressourcen des Servers sind ausreichend.Derzeit bin ich dabei, unser Auto-Reporting weiter auszubauen, sodass möglichst keine manuellen Eingaben mehr notwendig sind. Das Reporting erfolgt über die VSPC.Nun stoße ich allerdings auf folgendes Problem:Ich kann in unserem Cloud Connect VBR die VSPC nicht als Service Provider hinzufügen, da die Verbindung mit dem Hinweis abgelehnt wird, dass keine Verbindung „zu sich selbst“ möglich ist.Daher meine Fragen:Hatte jemand schon ein ähnliches Setup bzw. Problem? Gibt es eine Möglichkeit, das innerhalb eines Servers sauber zu lösen? Oder ist es in diesem Fall zwingend erforderlich, VSPC und VBR/VCC auf getrennte Systeme zu verteilen?Aktuell war ein Split bisher nicht notwendig, da der Server ausreic

PS C:\Windows\system32> Get-Service -Name *Veeam* | Select Name, Status, StartType Name                       Status StartType----                       ------ ---------VeeamAHVSvc               Running AutomaticVeeamAWSSvc               Running AutomaticVeeamAzureSvc             Running AutomaticVeeamBackupCdpSvc         Stopped AutomaticVeeamBackupRESTSvc        Running AutomaticVeeamBackupSvc            Stopped AutomaticVeeamBackupUpdateSvc      Running AutomaticVeeamBrokerSvc            Stopped AutomaticVeeamCatalogSvc           Running AutomaticVeeamCloudSvc             Stopped AutomaticVeeamDataAnalyzerSvc      Stopped AutomaticVeeamDeploySvc            Running AutomaticVeeamDistributionSvc      Running AutomaticVeeamExplorersRecoverySvc Running AutomaticVeeamFilesysVssSvc        Running AutomaticVeeamGCPSvc               Running AutomaticVeeamKastenSvc            Running AutomaticVeeamMountSvc             Running AutomaticVeeamNFSSvc               Running AutomaticVeeamPVESvc

We manage several VBR deployments through Chef using the Veeam powershell module. In testing Veeam 13, we can’t seem to add groups with the Add-VBRUserRoleAssignment command in powershell. Veeam 12 works fine and in Veeam 13 adding local and domain users works fine, just no local or domain groups. We can add the groups manually through the Veeam BnR console just not with the powershell command. We are currently testing on Version 13.0.1.2067 however the previous versions of 13 seem to have the same problem. Has anyone else experienced this issue? 

I am looking for advice on the best way to migrate my legacy backups from an older tape environment to a newer one. Here is my current setup:Source: A Veeam Backup & Replication server with an LTO-5 drive attached.Target: A separate Veeam Backup & Replication server with an LTO-8 drive attached.Since LTO-8 drives cannot physically read LTO-5 tapes, I know I cannot simply move the tapes to the new library. I need to move the data from the LTO-5 media to the LTO-8 media.What is the most efficient and reliable workflow for this migration?Should I restore the backups to a temporary staging repository (Disk) first and then run a "File to Tape" job on the new server?Is there a way to automate this process within Veeam without having a massive amount of interim disk space?Are there any specific considerations for the Veeam Catalog when moving data between two separate VBR servers? 

I have A DC that is being backed up, the backups complete successfully, but when I try to test it with surebackup it errors out with “Results: unable to perform Domain Controller restore from a crash-consistent backup. Be sure application-aware processing is enabled in the backup job settings”For the backup job on the server I have “Enable Application Aware Processing” ticked under guest processing. Is there some place else I need to look? I’ve tried unchecking the application aware processing, saving the job, and the re-checking it and saving then re-running the backup, but the surebackup still fails with the same error message.   

I have backup job with forever forward incremenal and the retention set to 7 days.I also have backup copy to Azure Blob where immutable set to 30 days.When we use forever forward incremental then full backup will be merged with last increment, then how this work in immutable storage?If the immutable set to 30 days then full backup only for 1st day and rest 29 days is incremental and no full backup merged every day?

I am trying to update Veeam Community Edition to the current version as recommended by KB4743.  Unfortunately, each time I attempt to run the upgrade I get a "Modify" option instead of "Upgrade".   I have check the Veeam KBs as well as looked though the Veeam Community for an answer - any help on this would be appreciated.  

Hi teamI was wondering if anyone has noticed some strange behavior when configuring network during ISO installer workflow?I have done two installs now. When I go into the network portion and I select the connection toggle, it stays in the connecting state and eventually disconnects.For one repo, one nic actually connected.From a switch perspective, all is up and connectedI made the changes as per documentationInstalling from Veeam Hardened Repository ISO - Veeam Backup & Replication User Guide for VMware vSphereFor the repo that manages to connect to one nic, I configured LACP as per document but only with one nic. This got the repo on the network and I manually added added the second nic the bond from the CLI.The second repo, in the network workflow, the two nic are discovered but are not connecting.I ended up configuring one nic as an ethernet link. Then I created the LACP bond from the CLI and added the links manually. This worked.So not sure why I am seeing this strange behavio

Hello Community, We have two DC’s and running Veeam 13 for Backup and Replication of VMware Virtual Infrastructure. In previous versions we have backup server VM running in the secondary DC and replicated to the primary DC. In case of loss of secondary DC, we can recover the VM on the Primary DC by simply powering it ON and then recovering any other VMs. However with Veeam 13 we have observed that the Veeam policy doe snot allow the Veeam Server to be replicated. What should be the recovery steps for the Veeam backup server (we have deployed the Veeam software appliance)?My thoughts:Deploy a new Veeam backup server appliance with same network IP as the previous server. Import the config backup Rescan all the backup components.Is this the right approach or should we deploy the server appliance with a different IP and import the previous backup config? BR,Sudhir 

Network Mapping in Veeam Orchestrator  Recover Locations can not be deleted.Checking if any of you guys have experience this. I can delete the network mappings. However if I go back, the network mappings reappear. The only way I can make the mappings go away is to delete the Recover Location and re-add the Recovery Location. Is this normal behavior on VRO v13? 

Hi, I’m considering supporting cross-platform recovery on a large production scale /w CC. I’m aware of the limitations presented with this. I’m really interested in hearing about experiences with recovering Prox backups into VM or Hyper-V and accounting for driver removal/install. What was your experience? Were you able to automate the workflow?  What was more problematic, Windows or Linux? What about boot loaders/Grub & Kernel drivers?  Thanks!

Please help, We are trying to backup large number of laptops, ± 400 using 1 proxy server to backup to S3 type of storage. We are experiencing performance issues. Laptops are using wi fi to connect to the cooperate network. We used a CSV file to configure protection group and our backup are scheduled during working hours. Please advise on the way forward for the best practice or recommendations. 

I have a migration from Veeam on Windows to Veeam on Linux, and I need to make sure there are no problems after the migration

I'm getting in my own way right now.I've set up an organization in Veeam M365. I want to edit it, but when I go to the connection settings, I'm asked for the application ID and a certificate.Which certificate should I select here? Veeam only suggests three options:1. Self-Service Patch Certificate2. Restful API3. (without friendly name) I didn’t have to specify a certificate during setup; I just followed the wizard.How can i choose the correct certificate?Maybe I'm just being stupid today. 

Fresh install of backup 13 latest version adding a secondary hv host to be backed up (standalone) get the following 20/04/2026 19:03:46 Failed : Infrastructure item save failed Error: No connection could be made because the target machine actively refused it. reinstalled, turned off av, disabled firewall, rebooted all the same - the 3rd HV host is fine

Hi since upgrading my PVe to version 9.1 and the VBR to 13, the backup performance have degraded a lot. We have 1 worker per pve host, storage is Ceph. Did someone encounter this issue?

Hi,I am going over DR scenarios and have a query on improving our procedure.We have two sitesPrimary site Hosts all production servers (5x physical & 30ish virtual) Hosts the VSA virtual server Primary & immutable storage repositories Secondary DR Site Off-site storage repository 2x spare physical servers for use in DR scenarioBoth sites connected via VPN. Everything on Hyper-V Now my query - lets say the primary site is destroyed. We want to restore everything to the secondary site.First step I can’t login to Veeam console because it was hosted in the primary site. Therefore current procedure is to setup a new instance of VSA and import a backup of the config. Not a difficult task but it takes time which I’d rather not have to spend during an emergency scenario.Is there a better way? Does it make sense to replicate our VSA virtual machine to the secondary site? Maybe high availability? Or should we be hosting the VSA virtual machine at the secondary DR site with a proxy server

Currently you can only restrict the Server-Scope for File-Restore not for the whole application. So whenever you want to give an user any role more privledged than “Restore-Operator”, you cannot fully restrict the scope of servers he see in the Jobs or Server Tab...

After upgrading to Veeam 13 on Windows, I am unable to login with UI console. Access throw WEB conole works. 

Hi All,As I checked the release notes for the Veeam Agent for Linux that supported most of Oracle Linux 8 versions but when I tried to install the agent I’ve got this error below :2/18/2024 3:24:09 PM Failed [172.17.2.207] Failed to install veeam-6.1.0.1498-1.el8.x86_64.rpm, veeam-libs-6.1.0.1498-1.x86_64.rpm and veeamsnap-6.1.0.1498-1.noarch.rpm packages: error: open of kernel-uek-devel-5.15.0-3.60.5.1.el8uek.x86_64 failed: No such file or directory Failed to invoke rpc command  0:08:012/18/2024 3:32:10 PM Failed [172.17.2.207] Failed to install Veeam Agent for Linux: error: open of kernel-uek-devel-5.15.0-3.60.5.1.el8uek.x86_64 failed: No such file or directory Failed to invoke rpc command  Can somebody let me know why I’ve got this as what I am looking for is using Oracle RMAN backup via Veeam Backup and Replication using Agent and Oracle Plugin Appreciate your help Thanks

Is Surebackups Virtual Lab on the to do list to work with Proxmox?

Hi teamI am tasked with implementing new repositories and I have to move backups and backup copy created by AHV. It seems that moving AHV backups is not supported with VEEAM move feature.I wonder what the best options are here and what I need to be aware off?The existing repo are configured to not use per machine-machine backup files.The old repos will be decommissioned once all data has been migratedMuch appreciated 

Hi everyone,I’ve been running tests on K10 DR and immutability features for the past 3 weeks. Despite trying many different configurations, I can’t seem to recover a fully functional restore point after restoring Kasten via K10 DR... specifically when I simulate an “unintended deletion of the restore point” before performing the Kasten restoration.Here’s my use case:Create the location profile (with immutability enabled) Enable K10 DR Run a backup policy (In my test, I’m using an etcd-backup policy based on the official Kasten Blueprint: https://docs.kasten.io/latest/kanister/etcd/ocp/install) Run the K10 DR policy Delete all existing restore points from the Kasten UI Completely destroy Kasten Reinstall Kasten Create the location profile pointing to the same S3 Bucket Restore Kasten via "Kasten Restore" (K10 DR) Launch the ETCD restore using the Restore Point, which is now visible again in the Kasten UI after executing "Kasten Restore"(N.B.: Kasten version used in my tests: v8.5.5) Obs