Discussion Boards

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.

I am trying to deploy Veeam Data Platform v13 on my windows server however i am getting the error “License is not valid for this product” when attaching the license to it before the deployment. Deployment cant proceed like the previous versions with no license.The foundation license was purchased late September before V13 was released so I suspected that was the case, I went into the license portal and generated a new license for V13 however the same error occurred. I have the windows defender the Kaspersky antivirus disabled to avoid having any error in deploying the license however I am stuck here.

When i tried to restore my database using veeam explorer for oracle from a backup created using application aware processing i got :Failed to resolve path : /h01/oracle/agent/agent_13.4.0.0.0.  

If we use forward forever incremental backup on the tape, can we disable the full backup schedule? 

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.

Hi Community,Has anyone successfully reverted Veeam ONE from version 13 to version 12? Are there recommended steps or considerations to avoid issues during the downgrade? Any official guidance or lessons learned would be greatly appreciated.

What could be the issue? Failed to send certificate, but certificate is required for remote agent management Error:

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

Hi All,Can you backup normal vms in Red Hat Openshift with VBR or do you need to use Veeam Kasten?Thanks,Benny

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 

Hello Community,I would like to check if anyone has practical experience or official guidance regarding the following scenario.Has anyone successfully presented a LUN from a Dell Unity array via Fibre Channel to either: Veeam Backup Appliance v13, or Veeam Hardened Repository (JeOS) with the intention of using that LUN as: a backup repository, or an additional backup disk for the repository? My main concern is related to the fact that both the Veeam Software Appliance and VHR (JeOS) are locked down by default for security and immutability purposes. I could not find clear documentation or a community thread that explicitly discusses: Whether FC-based block storage is supported in this scenario Any 

we are veeamawsbackup                   7.1.0.8                                 amd64        Veeam Backup for AWS. we want to upgrade veeamaws 10. can some one please provide the procedure for the same.

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

Good day Running Veeam Community v12 with a VMWare environment. I am running a backup of 3 VMs. Since I installed Veeam I cannot do a backup copy of a job for one of my servers. The 2 other servers that I run a backup copy and send it in a remote location works but that server I always get this error: Processing [server name] Error: Times out waiting for NFS async IO block callback. Timeout: 180000 msec Failed to download disk 'filenameofserver-flat.vmdk'. Shared memory connection was closed. Failed to upload disk 'filenameofserver-flat.vmdk' Agent failed to process method {DataTransfer.SyncDisk}.Some restore points were not processed The local backup works but I cannot get the backup copy to workI created a different backup job for this server alone but I also get that error. The option I was thinking to do is to do a backup job just for this but i’d like to figure out why only that server on the sam