Unanswered questions

Hi All,Unable to install the veeam agent to a windows server, this was working earlier.The service status is as below on the affected VMPS C:\Windows\system32> Get-Service *Veeam* Status   Name               DisplayName------   ----               -----------Running  VeeamDeploySvc     Veeam Installer ServiceStopped  VeeamEndpointBa... Veeam Agent for Microsoft WindowsRunning  VeeamTransportSvc  Veeam Data Mover Service We have killed the msi and veeam services, uninstalled the veeam agents from control panel - cannot find the veeam agent for windows in the control panel though, restarted the server, still the status remains same. Kindly advise.  

We have a Veeam Backup Enterprise Manager that connects to several Veeam B&R servers at our remote sites and child companies. As we’ve been upgrading to V13, the requirement to use HTTPS to connect to the VBR server is causing endless issues. Most of these sites are smaller, and only have one external IP that’s used for something user-facing, such as client VPN. (You know, because default ports are good for end users that wouldn’t know how to specify them.)V12 used Veeam-specific custom ports that we could forward to the VBR servers and there was no issue whatsoever, but the upgrade to V13 has ruined this. It is necessary to be able to specify a custom port for BEM to collect data from VBR servers. We’re not pointing a web browser at this, and backup software is an ideal place for knowledgeable IT staff to use and document custom ports, or even just a single nonstandard port that Veeam uses by default (like is used to with 9392). I don’t know who decided it was a good idea to use t

Please help me with this problemFailed to connect to backup server: Server Veeam Backup Server Certificate certifikate is not trusted

Hi Community.  I am unable to resolve the above referenced issue.  This happened after an update to v13.  After the install, it worked for 2-3 days. I then started to configure my tape infrastructure and when I finished, I was prompted to reboot the server.  Now I can’t get back into the console.  Any help would be greatly appreciated.

I have been having problems with Veeam community edition failing to complete backups and giving the error “Application is shutting down. Unable to retrieve next block transmission command” at different points in long running backups.  This happened for local backups as well as remote system backups (on my network).  This error was from Veeam 12 although 11 was having consistent issues as well.  I tried new backup repo hardware, a new motherboard/USB controller, all the drive/os fixes/scans...there are no 3rd party antivirus scanners, and tried checking for volume snapshot errors.What seems to have fixed it is explicitly blocking all internet traffic (outbound) for the Veeam server executables.  What could my local backups have to do with the internet?  I have a fairly complex set of internet firewall rules with MiTM cert inspection, so I’m not surprised if Veeam gets unexpected certificate errors or failures to reach servers in background processes, but would it affect my local backup

When creating a deployment project under disk capacity it shows number of vCPUs but it should be number of disks. Can someone please test this on their VeeamOne and let me know. 

I'm using Veeam Backup & Replication Community Edition 13.1.1.18 in a home lab with Veeam Agent for Microsoft Windows 13.1.1.700.I'm seeing extremely poor performance with physical Windows Agent jobs configured as:Server -> Managed by backup server -> Veeam backup repositoryThe problem reproduces on multiple physical Windows PCs.The same machines perform normally when configured as:Server -> Managed by agent -> Shared folderThe difference is enormous.Example managed-by-backup-server test:- Destination was a LOCAL NVMe repository on the VBR server- Approximately 49 GB read- Approximately 30 GB transferred- Duration: approximately 4 hours 16 minutes- Average processing rate: approximately 3 MB/s- Veeam reported Network as approximately 99% of the bottleneckThe transfer frequently drops into the hundreds of KB/s or even tens of KB/s, with occasional short bursts of normal/high throughput.I specifically tested a local NVMe repository to eliminate the NAS/SMB repository path

Hi,I’m working with MongoDB backups, and everything was going well until the restoration part.I was able to test all the restore options except: Restoring multiple collections to a point in time Publishing the instance I’m not sure why these two aren’t working. Has anyone faced the same issue before?  

I’m facing an Active Directory security audit, and the account used for the backup job generate a discussion.If i’m correct the account used must me member of builtin\administrator group, and the security team do not like at all that the password is set as never expire.i’ve already implemented that the account cannot be used for interactive login, but it is not considered “enough”So i’m trying to echange my posture without breaking the restore functionality, and i’m evaluating several option:The Veeam Server in in a workgroup and in a segmented network.1) do not do application aware and use only the vmware tools.it seem that the backup of AD is done in a correct wayPS C:\Windows\system32> repadmin /showbackupRepadmin: running command /showbackup against full DC localhostLoc.USN                           Originating DSA  Org.USN  Org.Time/Date        Ver Attribute=======                           =============== ========= =============        === =========DC=DomainDnsZones,DC=intrane

Hi,i am using Community Edition of Backup and Replication.  In special i have been using a script to start Veeam ZIP to get a standalone full Backup. This has been working flawless for quite a while.There has been Issues with Powershell in the past, so i have to start the batch explizit with the “new” powershell version. But this was about a year ago.So i got a running Version of Backup an Replication (13.0.2.29) then i upgraded to 13.1.1.18 and Veeam ZIP stopped working with the following Error Message:  Error: Unable to cast object of type 'Veeam.Backup.Core.CFreeVmBackupTarget' to type 'Veeam.Backup.Core.CVmBackupTarget'.I searched the Internet and have been finding very few users with the same problem. One of them provided two solutions: Revert back to functional version, or contact Support and get a hotfix to makle changes on DLL.i do not want to revert back, because i think this is a greate Problem which has to be adressed by the support generally.I filed a case by the Veeam Supp

Today, I built a new Veeam environment using Veeam Backup & Replication 13.1 with oVirt KVM Plugin 13.8.0.395.When deploying the OLVM worker, the worker deployment completed successfully. However, the worker's network was not working afterward:Veeam could not retrieve the worker's IP address information. The worker could not be pinged from the Veeam server. The worker appeared to be deployed successfully in OLVM, but there was no functional network connectivity.To troubleshoot, I downgraded the environment to:Veeam Backup & Replication 13.0.3.63 oVirt KVM Plugin 13.7.3.63After the downgrade, I redeployed the OLVM worker using the same OLVM/network configuration, and everything worked as expected. The worker obtained an IP address, Veeam was able to detect it, and network connectivity was working normally.This makes me suspect there may be a compatibility issue or regression in Veeam 13.1 / oVirt Plugin 13.8.0.395 related to OLVM worker networking. 

Bonjour à tous,Je viens tout juste de rejoindre le leadership du VUG Women Allies In Tech, et dans ce cadre, je prépare avec Kira un webinar qui aura lieu en septembre 2026. Pour m'assurer que le sujet corresponde aux attentes de la communauté, je vous propose de voter pour votre préféré parmi ces trois idées : Sujet 1 : Stockage objet & résilience : comment Veeam et Object First protègent vos données contre les cyberattaques ? Sujet 2 : L’immuabilité des données en 2026 : tour d’horizon des solutions Veeam, Object First, Dell Data Domain et autres acteurs du marché. Sujet 3 : Les 5 goulots d’étranglement les plus fréquents dans les infrastructures de sauvegarde et comment les éliminer. Quel sujet vous intéresse le plus ?Répondez simplement en commentaire avec le numéro du sujet (1, 2 ou 3) ou partagez votre avis ! Date du webinar : Septembre 2026 (date exacte à confirmer) Langue: Français En espérant vous y retrouver nombreux et nombreuses 😉Morgan

Bonjour à tous,Je viens tout juste de rejoindre le leadership du VUG Women Allies In Tech, et dans ce cadre, je prépare avec Kira un webinar qui aura lieu en septembre 2026. Pour m'assurer que le sujet corresponde aux attentes de la communauté, je vous propose de voter pour votre préféré parmi ces trois idées : 🔹 Sujet 1 : Stockage objet & résilience : comment Veeam et Object First protègent vos données contre les cyberattaques ?🔹 Sujet 2 : L’immuabilité des données en 2026 : tour d’horizon des solutions Veeam, Object First, Dell Data Domain et autres acteurs du marché.🔹 Sujet 3 : Les 5 goulots d’étranglement les plus fréquents dans les infrastructures de sauvegarde et comment les éliminer. Quel sujet vous intéresse le plus ?Répondez simplement en commentaire avec le numéro du sujet (1, 2 ou 3) ou partagez votre avis ! Date du webinar : Septembre 2026 (date exacte à confirmer) Langue: Français En espérant vous y retrouver nombreux et nombreuses 😉Morgan

Hi everyone,I am surprised that I could not find anything regarding this topic.Here is the situation :I have no issue adding a vCenter server in the console.But when Veeam does the volume discovery, I get the warning in the title. In the screenshot it show up for two hosts actually.The ESXi hosts belong to the same datacenter under that same vCenter.Weirdly, as you can see in the screenshot, the next steps is successful.I tried to edit the vCenter object to see if it would prompt me to accept an untrusted certificate, but nothing appears.Also I tried to edit the properties of the ESXi objects but still no prompt to accept certificates.Does anyone have an idea about what is happening and how to fix this issue ?Best regards

Hi Everyone, I installed Veeam 13.1 on Windows Server 2022 without joining an AD domain and in an environment without internet access. I used IP addresses when adding the PVE9.2, but when I deployed the workers, the installation failed with the error “Veeam Updater is unavailable.” Later, I set up DNS forward and reverse lookups for the PVE and worker IPs, but the same error persisted. I unchecked the “Check for updates online” option for the workers.Does Veeam require an internet connection for the worker to install packages? Translated with DeepL.com (free version)

Hello everyone,I used the sizing tool to estimate the number of API calls for Veeam Backup for AWS.However, when I specify the following conditions, the calculated API call count is shown as 0:Immutable: Disabled Retention period: 7 daysIf I enable Immutable or set the retention period to 8 days or more, a non-zero API call count is displayed.Is this expected behavior, or is there a limitation when using a 7-day retention period? ​​​​​ 

After a failed Veeam backup, a Hyper-V VM (ADCC130HP01) was left with multiple nested Veeam Recovery Checkpoints that cannot be removed.Current situation:4 Recovery Checkpoints are chained together. The oldest Recovery Checkpoint dates back to 06/08/2026. The VM is still running normally. The VM disks currently point to the base VHDX files. Multiple AVHDX files still exist on disk.When attempting to delete the checkpoints from Hyper-V Manager, I receive the following error:"Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Virtual machine failed to generate VHD tree."When attempting removal via PowerShell, I receive:"Cannot delete a checkpoint subtree that contains a recovery checkpoint."I have already tried:Deleting checkpoints from Hyper-V Manager. Deleting checkpoints using PowerShell. Attempting manual merge operations.Has anyone experienced a similar issue and successfully removed these orphaned/chained Veeam Recovery Checkpoints without rebuilding the VM or risking dat

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

Hi. We followed the Veeam documentation to install the IBM AIX agent in "pre-installed agent" mode, but we later realized it could also work within an "individual computer" protection group. We believe the latter approach is better because the pre-installed agent method requires manually triggering synchronization on the AIX host or waiting up to six hours for it to occur. I found a Veeam article explaining how to migrate between protection group types, which I’ve included at the end of this message.The agent—version 13—has just been installed; we used the XML file provided by the Veeam console, and the connection was successful. Since we prefer the "individual computer" method, and I believe moving it avoids the need to revert to standalone mode (allowing everything to be managed from the console), could you please confirm that this procedure works as expected? I’d like to proceed with this change.Here is the link:https://helpcenter.veeam.com/docs/vbr/userguide/agents_protected_comput

Hello Community,which approach do you use/recommend in order to gather all of the required information needed for the Veeam Calculator Object Storage/VDC Vault Sizing ?Although I have a clear understanding of all of the required information needed for the Veeam Calculator, I am curious to check what are the recommendations in order to gather all of the required information from an existing VBR instance, such as a script/tool-based approach, manual information gathering and so on.Any help will be greatly appreciated.Thanks!Massimiliano

I just want to confirm if my understanding is correct.Lets say my veeam managed oracle rman plugin backup has this configuration:control_file_record set to 30 days.rman retention is set to 30daysveeam retention is set to 30 days.I also send the veeam backup to that offsite location, with retention period of 1 year.If I want to restore my database to 1 year ago, and rman and veeam repository already deleted the metadata, so is this the step:copy the backup from offsite back to repository (.vab, .vasm, .vacm) (should I replace the .vacm?) rescan the repository, then it will show under DISK (IMPORTED), will I be able to restore the control file to 1 yr ago now? Or do I need to run --remap backup first ? will the RMAN channel for  this old backup files be different from the current one?thanks

Hi All, I want to use Veeam 13.1.0.411 for Windows.When I try to add the Veeam Infrastructure Appliance as a handheld repository, it fails. 

​​​Exagrid Repo’sVeeamOne reports all backups that’s hosted on Exagrid as not immutable although the Exagrid is immutable with time lock enabled. Is there any way to setup the threat center to report all backups on Exagrid as immutable? ExaGrid’s unique approach is called AI-Powered Retention Time-Lock for Ransomware Recovery (RTL). It prevents the threat actors/hackers from deleting the backups and allows for backup retention points to be purged. The result is a strong data protection and recovery solution at a very low cost of storage.

2025-11-06 Subject: VBR 12.3.2.4165 Installation Failure Version provider was not found in suite context on Windows 11 Pro ARM ParallelsHello,I am attempting a fresh installation of Veeam Backup & Replication Community Edition (ISO: 12.3.2.4165) on a newly created virtual machine, but the Veeam Setup Engine consistently fails with the error: An error has occurred: Version provider was not found in suite context.Environment Details: My host is a MacBook Air running macOS Tahoe 26.1 and I am using Parallels Desktop 26 for Mac. The guest operating system is Windows 11 Pro, Version 25H2. The system type is a 64-bit operating system with an ARM-based processor. The ARM architecture may be a factor in the installer's execution checks.Troubleshooting Steps Completed:I have tried running Setup.exe as administrator, unblocked the ISO file in its Properties, and also extracted the entire ISO contents to a local folder and tried the setup again.I have confirmed that .NET Framework 4.8.1 or la

Hey, Folks!  Just got my trial license and downloaded the Linux kernel for Veeam Infrastructure ApplianceVersion: 13.1.1.18It finds all of my hard drives and starts the installation process.  After creating a few file structures, it stops and gives me:Dasbus.error.DBusError:Process reported exit cod 5: device-mapper:reload ioctl on (253:0) failure.   Failed to activate new LV datavol/veeamrepo.Thoughts on what might be happening here?  This was a Dell Windows 2025 server with 8 10TB HD’s and 128Gb of RAM. 2 Xeon processors.  Booting and choosing to wipe drives.