Solved

Hi, running my normal weekly backup and came cross this: 7/31/2025 5:08:20 PM :: Error: Cannot process pending I/O request (offset: 453659656192, size: 65536): async reader terminatedCorrupted block processing thread failed unexpectedlyFailed to upload disk. Skipped arguments: [EmulatedDiskSpec>];Agent failed to process method {DataTransfer.SyncDisk}.Exception from server: Cannot process pending I/O request (offset: 453659656192, size: 65536): async reader terminatedUnable to retrieve next block transmission command. Number of already processed blocks: [429608].Failed to download disk '63d26504-899c-457e-bc3d-6e4f5ca89f35'   How can I tell which disk has the error.  I listed all by disks by GUID and none matches 63d26504-899c-457e-bc3d-6e4f5ca89f35 Thank you, Henry

Hello, Thanks,I did a fresh install of VBR on a new machine, using freshly downloaded, latest .iso i did a succesful agent backup of MACH94. Then I tried to agent backup SERVER02 and that failed. “5/28/2024 6:08:33 PM :: Error: The specified path is invalid. Error: in [VctSetCtStorePath] at step [3] Agent failed to process method {VeeamVolumeCt.SetUserStorePath}“  

The storage system is in the SynchronizationFailed state Failed to synchronize storage data: An item with the same key has already been added. Key: 4422-afbb-aass-xdxd….. I would like to try removing and adding the affected storage but not really sure to what extent this would affect the Orchestration Plans. Or could this just be a DB issue?

Hi all,We are currently facing an issue during the installation of CDP (Continuous Data Protection) in our vSphere 8.0.3 environment. Setup: Hosts are updated exclusively using offline ISO images ISO files are internally validated and approved via change control Online depots are completely disabled vLCM is configured with only our custom HPE ISO (VMware-ESXi-8.0.3-24674464-HPE-803.0.0.12.1.0.11-apr2025.iso) vCenter version: 8.0.3 Hosts affected: esxi03.cloud.local (and others) Problem:When attempting to install CDP, remediation fails with the following error: Host 'esxi03.cloud.local' was not processed, the reason: 'Failed to validate the checksum of VIB 'http://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/HPE/vib20/qfle3/QLC_bootbank_qfle3_1.4.51.0-1OEM.700.1.0.15843807.vib', because the computed checksum differs from the expected one stored in metadata. Make sure the specified VIB is NOT corrupted and the expected checksum stored in metadata is correct.'

Does it make sense to use a separate vCenter with one ESXi host for SureBackup, or can SureBackup be configured on the production vCenter, just using a dedicated ESXi host for SureBackup?

Dobrý deň.Do siete budeme mať pripojené dva nove SMB zdielane disky, každy o veľkosti cez 20 TB.Vedeli by ste poradiť s vytvorením/nastavením backupu? Diskusia okolo toho by sa mi hodila :) 

We back up to disk then duplicate to tape for offsite storage. Not quite ready for cloud backups yet. I am wondering if anyone has any experience with Quantum LTO-9 tape drives with Veeam backup. I have quotes for two models. TD-L92BN-AR and TD-L93CN-AR. Thanks.

I have an infrastructure operating on a Nutanix Cluster and Prism Element, and I have integrated it with VEEAM Backup. I possess a socket-based license for VEEAM, and the cluster appears online in VEEAM. There are about 15 VMs in my infra, and I have set up a job to back up all the VMs which are within the cluster, I start the job and observed that it is not utilizing the socket license. Instead, it's recognizing an instance-based approach and only backing up a few VMs, with the rest displaying a license overutilization error. Can any one let me know How Nutanix works with VEEAM, is it a socket based license or instance based license only.

Hi everyone, how are you? I have a customer who has multiple M375 tenants.For example:Main tenant - 200 users Tenant Egge Unit 1 - 50 users Tenant Edge Unit 2 - 50 users We understand the limitations- It's not possible to restore between tenants- It's not possible to distribute licenses between tenants However, we can manage tenants from the same console, as mentioned by​ @MicoolPaul  in the post below. The customer's big question is: If I delete a tenant (this is common in edge units), will I lose all the licenses associated with that tenant? I'm thinking about the possibility: Or can we open a case with Veeam to "unlink" these licenses from the tenant so I can use them in another tenant? Thanks in advance!  

Hi VRO heroes!…how do you work within a Recovery Plan when it comes to a parallel processing, for example 5 VMs simultaneously?  For example: in this specific plan (built on based with Tags), there are some Domain Controllers in it. Within a DataLab Plan i can add the option for Prepare DC for DataLab (preparing services, exiting DSRM and so on). Within a Recovery Plan, this is not available. But in the case of a Desaster, and these DCs within the Recovery Plan are the only available DCs - they has to be started first.With a parallel processing and no available option for a Pause-Step, other VMs will be booted, even the Domain Service are not yet available.For sure, i can start those DCs within a separate Recovery Plan first or a better solution: have a DC also running and available at the DR-Site…What do you think about it, or how do you handle this?  thanks and best, Markus

Hello,I have situation were I have to export fully Entra ID backup from Veeam, how to do that?There are hypothetical examples with powershell, but I have to export the full backup for authorities. # Hypothetical example$session = Open-VEXEntraIDSession -BackupId "your-backup-id"Export-VEXEntraObject -Session $session -ObjectType "User" -TargetFolder "C:\Exports" 

I am going to be performing an upgrade of Veeam 8.1.1 to 8.1.2. Is there a way to backup VBO config before I do this, or is it not necessary? My plan is to just launch the upgrade and install it over the top of the existing install, reapply the license if needed, and hope that all my backup jobs and settings are still there. Is there anything I’m missing? I see in some instructions that I will need to configure the PostgreSQl and NATS again, so that may take some figuring out.  When I click on Upgrade in Veeam it says I am up to date, so that is why I downloaded 8.1.2 to install over the top of existing install.

just moved veeam to a new server. All is good and working but backups are successful with warnings…“failed to collect malware metadata from the backup proxy for the disk XXXXXX”Any ideas? ports 2500-3300 are open so not sure the next steps to resolve unless I look at the logs… thanks

Hi allWe have multiple installations of Veeam and some of them have all roles on the same server (Backup, Proxy, Mount and so on), some roles are distributed on others servers. Some installations have PostgreSQL and some have MSSQL. Has anyone a idea how to get the installed roles on a server (registry, folders) so we can choose which service to monitor on which server. Additionally is there an overview of which service belong to which role? Thanks,Dario

Hello, when making a backup copy the following error comes up: Failed to perform post-processing: Agent invoke failed with non retryable error.  Failed to delete 'vm-1042.281cD2024-08-02T222720_EFBF.vbk' per retention policy      However the backup does not exist in our cloud storage.The backups from the 7 day retention are present but differently named. Anybody know a solution?

Good Day.Premise of the infrastructureSERVER A: 192.168.1.10 (Windows Server 2022 Std)SERVER B: 192.168.1.4 (Windows Server 2022 Std)Veeam Backup & Replication is installed on Server B.I added both servers under Infrastructure > Managed Servers in Veeam.When I start a replication job from Server B, I receive the following error:    Error: Target proxy 192.168.1.4 requires Veeam components upgrade. Here are all the troubleshooting steps I tried, with no success:    Disabled Windows Firewall on both servers    Forced a components rescan from Veeam on Server B    Uninstalled Veeam and manually deleted all Veeam folders    Reinstalled Veeam    Removed version VeeamBackup&Replication_12.3.2.3617    Reinstalled version VeeamBackup&Replication_12.3.1.1139

I need to add an additional 35 licenses to Veeam for 365 and I have acquired the .lic file. The Update button in the Veeam License Information window does not allow me to add licenses, nor does it detect additional licenses. I was going to try just clicking the Install button and browsing to the file, but I am concerned it may overwrite the existing license file and not just add licenses to it. Can anyone confirm this is the correct method? Or should I be adding these licenses with another method? The email with my license file did not have instructions, only a link for support if I need assistance. 

Hallo Experten. Ich habe ein Problem mit Veeam Bare-Metal Desaster Recovery (12.3.2) betreffend SUSE Linux Leap 15.6 auf einem HPE Proliant Gen9 Server.Bei einer Sicherung mit dem aktuellen Veeam Linux Agent 6 und einer Wiederherstellung mit dem Veeam Recovery Image 6.3.2.1207_x86_64 tritt folgender Effekt auf:Eine Desaster Recoveri im “Legacy Mode” funktioniert einwandfrei und wie in der Anleitung beschrieben.Wird allerdings ein Server im UEFI Modus gesichert, stertet er nach dem Recovery mit einen “grub”  Prompt.Laut den Anleitungen muss der Bootloader wieder hergestellt werden. Hat hier jemand Erfahrungen und kann sie mir (mögl- einfach ;-) ) erklären?Schöne GrüßeMarcus

In the past, we sent the backup logs by e-mail. The settings for sending emails were set under Email Settings --> SMTP server (basic authentication); Port 587; Connect using SSL. Authentication was via credentials. From one day to the next, this dispatch no longer worked. When I now try to save the configuration, I get the message: ‘Unable to connect to SMTP server because of invalid credentials or connection settings’. I tested a Thunderbird on the same device with the same smtp settings and it worked there. Any idea why Veeam can't manage SMTP authentication right now?

Hi Community,I'm trying to implement a Veeam backup strategy for unstructured data stored on a file share (SMB or NFS). The goal is to: Back up the file share to a local repository, and Offload or copy the same data to Azure Blob Storage for offsite/cloud retention. I understand that Scale-Out Backup Repository (SOBR) is not supported for NAS backup jobs, so I’m looking for an alternative way to achieve dual-target backup for unstructured data.Has anyone here set up such a workflow?Would you recommend scripting the offload, using a post-job action, or integrating a third-party sync tool? Any best practices would be highly appreciated.

Hello Dear Community,Is it correct that with the Veeam Windows Agent free edition I can only create one job?I already have one job to USB disk attached to the computer I want to create another job to a VBR server which is icensePlease confirm even the VBR is license, the Windows Agent free edition is strictly limited to one job?Thanks,Edy

I upgrade my VBR then when try to upgrade the component for my hyper-v i got error the destination file already exists.How we can solve this? 

Hello,i would like to know if regkey for updating automatically thread hunter is workingKey Location: HKLM\ SOFTWARE\Veeam\Veeam Threat Hunter\Value Name: VTHInternetProxyValue Type: String Value (REG_SZ)Value Data: <proxy>:<port> could you please advise how to check easily that is working update of signatures? thank you

I’m trying to do my first backup with the Windows Agent, but it fails several hours in.After the first failure, I ran chkdsk on the target, and no errors were found; the second attempt failed in the same way. I have 2 drives in the system: It recorded success for the first one.I tried to open a case for this, but no luck so far.7/6/2025 12:14:22 AM :: Error: Shared memory connection was closed. Failed to upload disk. Skipped arguments: [EmulatedDiskSpec>]; Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The requested operation could not be completed due to a file system limitation Failed to write data to the file [E:\VeeamBackup\greatful\Job greatful\Job greatful2025-07-05T172307.vbk].Failed to download disk '251db751-6938-460c-8b6d-c34dc909537e'  7/6/2025 10:08:23 PM :: Error: Shared memory connection was closed. Failed to upload disk. Skipped arguments: [EmulatedDiskSpec>]; Agent failed to process method {DataTransfer.SyncDisk}. Exception from ser

Hi all,We have recently moved from VMWare to Hyper-V.We use Veeam B&R V12 and have encrypted offsite backups going to a remote backups repository via a site-to-site VPN connection to a third party. On VMWare, we used VMs as backups proxies and included only those VM addresses in the site to site VPN.When we moved to Hyper-V, because of the on-host backups proxy architecture, we needed to add the Hyper-V host IPs into the VPN profile.  On any given day, I’m happy that the remote team follow best practice in terms of security but I’m not willing to expect that to always be the case.  I’m really not comfortable having our host IPs being directly accessible from a third party location, when they have control over the remote IP scheme.Is there any way to introduce a VM as a backups proxy as per the VMWare architecture to remove the Hyper-V host from the VPN?If not, is there any reason why I can’t just block all inbound access from the third party IPs?  I would expect that all activity i