Clearpath Insights: Managed Services | Cloud Services | IT Solutions

Veeam v11 Upgrade: Memory Management & Remote Component Errors

About the author: My name is Brian Owen and I work on Clearpath’s managed services team focusing on maintaining our clients’ virtualized environments. My accreditations include the VMware VCAP-DCV 2020 certification and VCIX-DCV 2020 milestone. Proactively engaging and contributing to the VMware community has earned me the vExpert status for the past 4 years. I’ll be posting to Clearpath’s blog with content related to data center best practices and lessons learned along the way.

Veeam Backup & Replication version 11 has gone GA in February of this year. It introduced new features, such as continuous data protection and more archive options. Assuming a backup application will always work with the latest version of vSphere is a common mistake. Veeam v11 P20210525, released in June, now supports vSphere 7.0 U2. Now is a good time to upgrade to have the latest versions of vSphere and Veeam. I have done some Veeam v11 upgrades and would like to share a couple of issues that I have come across.

I upgraded Veeam from v9.5 U4b to v11 P20210525 and it seemingly went well. However, the next day had a backup job filled with errors. The error was “Processing SERVER NAME Error: bad allocation Failed to upload disk. Skipped arguments [>]; Agent failed to process method {DataTransfer.SyncDisk}.

Veeam upgrade v9.5 U4b to v11 P20210525 error

The Windows Servers that Veeam was running on had many event ID 2004 warnings in Event Viewer. The warnings were very transparent and mentioned low memory. Veeam was even mentioned in the warning’s details. Turns out that the Veeam server was not at the required amount of memory. After adding more memory to the server, the backup job ran well.

Veeam Event Viewer

I upgraded Veeam v10a to v11 P20210525 at another location. The major part of the upgrade for the Veeam server itself went well. However, I ran into issues when it came to deploying the upgraded components to the proxy and gateway servers. The first screenshot below showed that the necessary components were in the process of upgrading. Then about half of the proxies failed to upgrade with a message of “Failed to upgrade the host components. Error: ‘Upgrade completed with errors. See Installer Logs’.

Veeam Installer Logs

Veeam Components Update

I did not see anything helpful in the installer logs. I thought about why some proxies upgraded and why others did not. I remoted into the proxy servers that did not upgrade their Veeam components. I noticed that Windows Update was pending with a reboot so I applied the patches on all of the servers that required it. Then I kicked off the remote deployment of the Veeam components and that resolved the issue for most of them.

However, a few of the servers still wouldn’t update Veeam components. I contacted Veeam support and they had another idea. I uninstalled all Veeam components from each proxy server that was having the issue. Then I pushed the Veeam components to the proxy servers as a new install. The proxy configuration was still on the Veeam server so no configurations were lost. That worked for the remaining proxy servers.

Thanks for taking the time to read my blog on what I learned when upgrading Veeam to v11. Clearpath can help with all types of Veeam deployments: on-premises, Veeam Cloud Connect with our managed backup and disaster recovery offerings, and in the public cloud. If you have any questions you can reach out to me at

Contact Clearpath’s Veeam Account Management Team


Our engineers customize
IT solutions for your business

The best hardware, software and cloud computing solutions are nothing without expert design and implementation.

Our team becomes your team. We take the time to understand your business needs first, and tailor high performance systems specifically for you.

Learn more
Live Chat Support Software