Upgrading Hyper-V intergrations (9.5 u4a)

[leo.white]

I upgraded my Veeam environment last week to the newest version. Only issue i have is veeam says my Main backup server is out of date on the hyper-v integrations. Only problem is the main backup server is a virtual machine. So it will not let me update that component or let me remove that component. Anyone else have this issue?

Error it throws "Failed to upgrade host components. Error:'This server is not a hyper-v host'

[wishr]

Hi Leo,

Please reach out to our support team for a comprehensive investigation. Thank you.

BR,
Fedor

[Mike Resseler]

One thing you can do is run the hyper-v integrations component manually on that server. Please find VeeamHvIntegration.msi and VeeamTransport.msi in C:\Program Files\Veeam\Backup and Replication\Backup\Packages on your backup server and run those. (Start with the Integration.msi first before you do Transport and see if the second one is still necessary. Not sure about that to be honest)

Thanks
Mike

[Linking Informatica]

Error it throws "Failed to upgrade host components. Error:'This server is not a hyper-v host'

Hi Leo, did you manage to solve the problem? We are a reseller using an NFR for testing so we cannot open a ticket with the support...

[Vitaliy S.]

Linking Informatica, did you try following the suggestion from Mike to resolve it?

[Linking Informatica]

Yes, same error: how can I install the HyperV integration since the software is installed onto a virtual machine?

[Vitaliy S.]

I have reviewed OP's case number, the solution was to remove an internal ID (unique in each installation) via SQL script of the backup component reporting this problem. VeeamHvIntegration.msi should not and cannot be installed in a VM, that's why you see this error. Since you cannot open a support ticket, then I'm afraid a complete re-install is a way to go.

[Linking Informatica]

Well, I do understand you point of view... but since you do know the solution it would be kind to share it...
Thank you and Best Regards

[Vitaliy S.]

I'd love to share it, but it is not possible to do over forums since the solution requires reviewing the database of your Veeam B&R server. Based on the results, someone has to write a correct SQL script to clean up duplicated/wrong IDs. Copy-pasting the script from OP's case would not help as each script is unique to every Veeam B&R server.

[StyleTec]

So for everyone who is looking for a solution. Following did the trick for me.

First of all, manually update all correctly recognized components, like vPowerNFS.

Then open a SQL Server Management Studio, connecting to the Veeam database and open up the table "HostComponents" in edit mode. Searching for the wrong component - most likely this is the one with a lower version number and something like "HvIntegration" under options column - and deleting the entire row.

[frankive]

Thanks Styletec!
That did the trick for my server too.

[ochm]

So for everyone who is looking for a solution. Following did the trick for me.

First of all, manually update all correctly recognized components, like vPowerNFS.

Then open a SQL Server Management Studio, connecting to the Veeam database and open up the table "HostComponents" in edit mode. Searching for the wrong component - most likely this is the one with a lower version number and something like "HvIntegration" under options column - and deleting the entire row.

Perfect, it helped me too in upgrade from 9.5.4 to 11
Thank You.

[arorris]

So for everyone who is looking for a solution. Following did the trick for me.

First of all, manually update all correctly recognized components, like vPowerNFS.

Then open a SQL Server Management Studio, connecting to the Veeam database and open up the table "HostComponents" in edit mode. Searching for the wrong component - most likely this is the one with a lower version number and something like "HvIntegration" under options column - and deleting the entire row.

I made an account just to post that this workaround, still works - I upgraded from 11 to 12 with this modification.

Thank you StyleTec.

[Luciano.Glla]

Hello,
Thanks for helping with this error,
I'm updating the version from 11.xx to 12.xx, and I'm having the same error, and I'm not able to locate the table via SQL Server Management Studio, if possible can you get a screenshot, with the path of the table?
Thanks,

[keksbert]

I am also interested in a solution for v12 installations. I have to deal with the problem with each minor patch and would like to finally resolve this. Until now I have installed the Hyper-V role on the server and removed it after patching.

[HannesK]

I have to deal with the problem with each minor patch and would like to finally resolve this

did you ever open a case to get that problem solved from Veeam side? If yes, can you please post the case numbers so that we can check?

[gnarlynorris]

So for everyone who is looking for a solution. Following did the trick for me.

First of all, manually update all correctly recognized components, like vPowerNFS.

Then open a SQL Server Management Studio, connecting to the Veeam database and open up the table "HostComponents" in edit mode. Searching for the wrong component - most likely this is the one with a lower version number and something like "HvIntegration" under options column - and deleting the entire row.

Thank you. This was the solution for me as well. Upgraded from 11 to 12

[sayler]

So for everyone who is looking for a solution. Following did the trick for me.

First of all, manually update all correctly recognized components, like vPowerNFS.

Then open a SQL Server Management Studio, connecting to the Veeam database and open up the table "HostComponents" in edit mode. Searching for the wrong component - most likely this is the one with a lower version number and something like "HvIntegration" under options column - and deleting the entire row.

This still works, thanks very much.