![veeam 11 veeam 11](https://helpcenter.veeam.com/docs/backup/vsphere/images/add_backup_repository_mount_vmware.png)
#Veeam 11 update#
However, a few of the servers still wouldn’t update Veeam components. Then I kicked off the remote deployment of the Veeam components and that resolved the issue for most of them. I noticed that Windows Update was pending with a reboot so I applied the patches on all of the servers that required it. I remoted into the proxy servers that did not upgrade their Veeam components. I thought about why some proxies upgraded and why others did not. I did not see anything helpful in the installer logs. Then about half of the proxies failed to upgrade with a message of “Failed to upgrade the host components. The first screenshot below showed that the necessary components were in the process of upgrading. However, I ran into issues when it came to deploying the upgraded components to the proxy and gateway servers. The major part of the upgrade for the Veeam server itself went well. I upgraded Veeam v10a to v11 P20210525 at another location. After adding more memory to the server, the backup job ran well. Turns out that the Veeam server was not at the required amount of memory. Veeam was even mentioned in the warning’s details.
![veeam 11 veeam 11](https://abload.de/img/veeam-endpoint-loopba8sbsj.png)
The warnings were very transparent and mentioned low memory. The Windows Servers that Veeam was running on had many event ID 2004 warnings in Event Viewer. Skipped arguments Agent failed to process method. The error was “Processing SERVER NAME Error: bad allocation Failed to upload disk. However, the next day had a backup job filled with errors. I upgraded Veeam from v9.5 U4b to v11 P20210525 and it seemingly went well. I have done some Veeam v11 upgrades and would like to share a couple of issues that I have come across. Now is a good time to upgrade to have the latest versions of vSphere and Veeam. Veeam v11 P20210525, released in June, now supports vSphere 7.0 U2. Assuming a backup application will always work with the latest version of vSphere is a common mistake.
#Veeam 11 archive#
It introduced new features, such as continuous data protection and more archive options. Veeam Backup & Replication version 11 has gone GA in February of this year. I’ll be posting to Clearpath’s blog with content related to data center best practices and lessons learned along the way. Proactively engaging and contributing to the VMware community has earned me the vExpert status for the past 4 years. My accreditations include the VMware VCAP-DCV 2020 certification and VCIX-DCV 2020 milestone. About the author: My name is Brian Owen and I work on Clearpath’s managed services team focusing on maintaining our clients’ virtualized environments.