Discussion Boards

Hello all,  I’m preparing a new fresh deployment of the infrastructure for Veeam 13. First I’m installing the database with Postgres 17.7.2 and installing Veeam 13 component after (EM in this case) in a different server. I’d like to know if there is any specific requirement I need to follow as I was not able to find much about this specific case (only the recommended configuration for VBR), I guess it’s the same. I also would like to know if you recommend to separate the WAL in an specific disk separated from the DB disk as this machine is going to handle heavy workloads. Thank you in advance!Eric

Just a heads up combined with the questions if others noticed the same:At a customer we have an quite important Windows Failover Cluster (2 VMs) being backed up via managed agents through a protection group. For good reasons the protection group is set to “automatic agent upgrade = no”. After the upgrade of the VBR to V13.0.1.1071 we did rescan the protection group to have it notice the now outdated agents.Instead of just detecting this, the rescan immediately decided to re-install the transport service.This is quite dangerous IMHO as we specifically did not want to trigger any installation tasks without actively starting from the GUI. Did anyone else see this behavior?Thanks,Michael

I’m currently migrating from VMware to Proxmox and have run into an issue with Veeam. Backups from iSCSI only work when the VM machine version is set to 9.1.I wanted to check if you have any visibility into when full support for version 10 is planned, as reverting my VMs to 9.1 significantly reduces the usability and performance of my iSCSI LUN.

Hi VC,I’m wondering if anyone can help, I’m hopeful someone's had this before. We have two SQL servers, one which I am backing up with the Veeam SQL plugin at database level and then restoring to the other using the same plugin through the restore function.When attempting to restore I’m getting the following error:  Any ideas what I can check?Many thanks,LGH

Good day, I have a PVE 9.0.18 in my NUC, using local storage only. Yesterday I updated the VBR and Plugin to the very lastest versions. But..Well, the Proxmox plugin still isn’t working for me… it’s really strange: I configured and tested the worker successfully;I added a Windows VM (same subnet as the VBR, no firewall) to a jobIf I run the credentials test, it fails because the VM is powered off (??)The backup, even crash-consistent, also failsFor the credential test, I guess the error in the log is: “”aiting for file C:\ProgramData\Veeam\Backup\Plugins\PVE\Backup\PVE-Win_c1c3bce9-32d8-419d-b31a-6a63f6c6d2de\8fa94a5b-e558-4d50-bb67-241ff316ecab\PVE-Win.log to be unlocked”for failed backup (hot add mode)“Failed to await the Backup task 444dd208-68ee-498c-aa5a-8282d85b2369: Veeam.Communication.TypeProvider.Invoke.RpcCallException: Failed to perform backup: Failed to prepare disks for backup” 

Can we restore guest file level if the backup source is from tape? Or we must restore entire VM to the disk and then doing the FLR from disk?

Apologies if this is a frequently asked question, I’m very new to the topic of managing backup infrastructure.I’m currently facing the following issue:Server 1 is currently powered off and defective. According to users, there are important files that need to be extracted in some way. Server 1 was not centrally managed and instead had a standalone instance of Veeam Agent to run backups and copy backup files to NAS 1 NAS 1 holds a single full backup of Server 1 and is not managed via Veeam as a repository etc. NAS 1 and Server 1 are physically located at an external location with a very slow internet connection; this was the reason why the standalone agent approach was chosen in the first place Server 2 will host the restored files from the backup in the future and is managed centrallyWhat would be the best way to go about this restore process? My biggest issue is that I know how to restore files from existing centrally manage

Hello Guys, These days Im started to experience a lot of problems with Veeam, every now and then the Veeam Backup and Replication Application and the whole server gets stuck and i could not do anything until i restart it, even some backup jobs started to fail. When i restart it goes fine for a while and then it does it again, and for the jobs a sometimes i see that the service Veeam installer service is stuck so i have to delete it and try the job again and sometimes it works.Did anyone experience this kind of issues lately? I’m having hard time dealing with this and i will be happy with any kind of support.Note:  i started to experience this issue after upgrading to 13 Version.Thank you.

I am new with veeam and i build up a software appliance V13 on proxmox VE 9.1.4The appliance is running well and i can also use the veeam console from another PC to connect.The console i installed from the community iso last version.But now i have the problem with License of community version.Where can i find the license File for the community version of veeam?Downöoad or use of online licensing?Must i send a mail to become from veeam  the license file for community version.Without the license file for community version i can not test and learn more about veeam.Do you have a link for me to solve the problem?I hope you have a answer for a new beginner on veeam.

I’m getting the below error after upgrading Veeam servers from v12 to the latest release of v13. It’s a windows based install of Veeam, and it is connected to a (dedicated to Veeam only) AD domain.My user has local administrator permissions, Veeam Backup Administrator permissions, and MFA disabled for testing/troubleshooting purposes. The is happening across each of the Veeam v13 servers I have on the domain.It is only happening for mine and one other engineer’s user accounts, but other engineer’s accounts are not affected. We are all in the same AD groups so permissions are the same.I have tried removing Veeam Backup Administrator permissions from my account, rebooting, and re-adding, to no effect.Has anyone seen this before? Any suggestions for what else to check? In the meantime I have a case open with Veeam support, and hoping they can come up with something.

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

Hello, everyone!! Today is a special day. I passed the VMCE exam. I want to thank the group for the tips and questions; they were fundamental for me. 💚🤗

I have a veeam V13 appliance under Proxmox VE 9.1I want use a smb share under Qnap NAS. The QNAP is not in a domain.The shares are working on windows PC and servers with the credentials.The same creditentials i use for connect to the share under the veeam console V13But when i want to use it as repository SMB share. I become this  Have anybody a solution to solve this. 

15.01.2026 10:42:19.819]    <45> [000P]   Error (3)       at Veeam.Backup.VssProvider.CVssControl.WaitIndexComplete(IIndexingSession indexingSession, IStopSessionSync sessControl)[15.01.2026 10:42:19.819]    <45> [000P]   Error (3)       at Veeam.Backup.VssProvider.CVssControl.Index(IStopSessionSync sessControl, Guid jobId, String[] includeFolders, String[] excludeFolders, String outputDir)[15.01.2026 10:42:19.819]    <45> [000P]   Error (3)    Failed to call RPC function 'Vss.IndexGetState': Error code: 0x80004005. Failed to invoke func [IndexGetState]: Unspecified error. Could not copy host file [C:\Windows\TEMP\ifd4615.tmp] to guest [C:\Users\SXXXX\AppData\Local\Temp\31acb312-7db4-4fb0-bee8-f9e3ab42bc00]. Could not check if guest [vm-1716606] file [C:\Users\SVCACC~2\AppData\Local\Temp\31acb312-7db4-4fb0-bee8-f9e3ab42bc00] exists. Could not get item info [C:\Users\SXXXXX\AppData\Local\Temp\31acb312-7db4-4fb0-bee8-f9e3ab42bc00] in the guest [vm-1716606

Using Veeam Backup and Repliaction 12, and running a file backup, receiving the following error, “Error: Failed to connect to agent: ‘VeeamServerName’, EP ‘VeeamServer IP Address:2502’. The message received was  unexpected or badly formatted.

Backup made simple. Backup becomes child’s play with new Backup Agent — a fully managed, offsite backup solution built for Bare Metal servers based on Veeam Service Provider Console.In just minutes, you can automate daily incremental backups, and start to monitor everything from a centralized dashboard.⚡ Setup in under 10 minutes, and let daily automated backups run🔐 Incremental, encrypted and immutable retention💰 Free licence for the Agent — pay only for Object Storage (0,007 €/GiB/month exl. tax)Be safe with the simple, reliable, and predictable backup layer that doesn’t bloat your budget. https://www.ovhcloud.com/en-ie/storage-solutions/backup-agent/  Please reach out to me if you want to discuss more about this new product! I need feedback to drive and build our strategy ar

The database simply freezes and Veeam needs to be restarted. We discovered that disabling Offload for the current Service Provider completely stops the problem from occurring. VBR RAM/CPU resources remain without overload.The database loses communication, and as a solution, we need to restart the postgres service. Veeam Version 12.3.2.4165 PostgreSQL Version 15.14-1 We have implemented these changes so far: Set-VBRPSQLDatabaseServerLimitshttps://helpcenter.veeam.com/archive/backup/120/powershell/set-vbrpsqldatabaseserverlimits.html AV & Firewall

We have a few clients that have a single physical server and have a service or application that is already using port 443.  So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used and v13 uses it for the Veeam Web Service.  Assuming we can temporarily disable this service/app to get the upgrade to complete, is there a way once v13 is installed to get the Veeam Web Service to use a different port?

Hi All, Job type on Prod is forever forward incremental on Disk -  ReFS formatDR has a repo in XFS formatI’m setting up a new Veeam environment and using Cloud Connect to copy backups from Prod site to DR (single tenant / one client).On the Cloud Connect side, the XFS repository is assigned 100TB and the actual storage usage is only around 56TB.However, the Backup Copy Jobs keep reporting that the cloud repository quota is filling up / quota exceeded, even though there should be plenty of space available.As a workaround, I increased the tenant quota on cloud connect server from 100TB to 150TB, and after that the copy jobs started working normally again and has used like 130TB. But this doesn’t make sense because: The physical repo capacity is still 100TB Actual used space is sti

What happened to the Status column when viewing a backup job’s statistics?  After upgrading to version 13, I no longer see this column.  If a backup object fails, the job shows failed however you have to view each backup object in the job to see which one failed.  Prior to v.13, the status column would show which object failed. Was this intended in v.13 or am I missing it somewhere?  

I get this errors on one of my clients VBR. Fails when running the copy job to our Qnap NAS running Quts Hero, Immutable setup with Quobjects. When it fails we don’t have several copy jobs running at the same time.Any ideas of what i can try next to solve this?  

Good day, everyone,I am seeking assistance in identifying the best method for migrating to new hardware.Current Environment:DC-A to DC-B bi-directional Veeam replication Old HP servers running Veeam Old HP StoreOnce appliances used as Catalyst repositoriesNew Hardware:New HP servers and HPE StoreOnce appliances procuredRequirements:Build two sets of new Veeam/HPE StoreOnce environments at DC-A Migrate old DC-A Veeam/HPE StoreOnce to new DC-A Veeam/HPE StoreOnce Migrate old DC-B Veeam/HPE StoreOnce to new DC-B Veeam/HPE StoreOnce Establish bi-directional Veeam replication between the new environments Decommission old Veeam/HPE StoreOnce hardware once backup and restore jobs are validatedBased on my previous experience with Veeam/Data Domain migrations, I have outlined the following proposed mi

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 netwo

Hello! I am attempting to set up SureBackup to test backups of VMs from my Hyper-V environment in a way that mimics production and simulates interactions of VMs in separate, routed subnets, but I am running into issues setting up the isolated network’s NICs on the proxy appliance. It is unclear if I’m misunderstanding the setup documentation or if I am running into a limitation caused by the logical network of my Hyper-V cluster.My Hyper-V hosts have a single logical switch for VM traffic with all VLANs trunked to it from the physical switch that the hosts are connected to. Each VLAN has a unique subnet of varying size, mostly /24 but there are some /23 and /27 networks.I am trying to create a Virtual Lab in advanced single-host mode with an isolated network for each subnet containing a VM being tested, with the proxy appliance acting as the router for each subnet.The two subnets I am testing with are:192.168.124.0/23 (VLAN 124) 192.168.196.

Hi All,My customer would like to continue to use an external USB hard drive as a backup repository on the new DELL physical VSA server they have stood up. It’s look as though it’s not supported in this release, but they would like confirmation that it’s on the roadmap for future releases.Any ideas? Thanks!