
The services can be turned on and off individually. All integration services except Hyper-V Guest Service Interface are on by default on Windows guest operating systems. This is not just for Veeam but for all migration projects, that will save your time by avoids potential issues and rollback in urgency.Each service you want to use must be enabled in both the host and guest in order to function. Just keep in mind to always check the compatibility matrix for hardware/software and system requirements before apply updates or upgrades. Finally after this latest upgrade, the backup finished with a success ! Conclusion From the Inventory just apply the « Upgrade » task. The host indicate than an upgrade is required for the Veeam Agent. Once the server updated, I tried to launch a new backup task on my Agent… Result the same error message… I missed one step ! ( ) in the resolved issues part give us the answer : « Microsoft Windows 11 and Microsoft Windows 10 21H2 support as guest OS, Hyper-V hosts (as a target for Instant Recovery and SureBackup), for installation of Veeam Backup & Replication components, and for agent-based backup with Veeam Agent for Microsoft Windows 5.0.2 (included in P20211211) ». A quick review of the release notes for Veeam Backup & Replication 11a Cumulative Patches. Interesting, we don’t have the latest Cumulative Patches on this VBR. Weird… What could go wrong ? Let’s take a look to the Veeam Backup & Replication Version : Build 11.

This is the lastest version for Veeam Agent for Windows ( )Ī quick look to the system requirements indicate that both version are compatible. Let’s take a look at the Windows & Veeam Agent versions: The message seems clear the computer has been updated on a new Windows Version not supported by the Veeam Agent installed. The host rescan gave me a first clue « Microsoft Windows version installed on this machine is not officially supported by Veeam yet ». « Processing **** Error : Failed to process **** : BIOS UUID has been modified, pleace rescan the host » The investigation It’s was not the case so I had to investigate. Today I want to share with you the resolution of a Veeam Error I had to deal with and why it’s important to apply updates and check the compatibility matrix.Ī coworker sent me this error message from a Veeam Agent managed by Veeam Backup & Replication and asked me if I had come across it before.
