We can run 2 PowerShell commands which confirm what roles our Veeam Server cannot serve and what components should be deleted, which will update the database as well.
I will present the PowerShell option here as it is faster.
For this you can perform the next action plan:
Step 1: Run a Veeam Configuration Backup> Running Configuration Backups Manually -
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Step 2: Once the Configuration Backup is complete from the Veeam GUI open PowerShell
Step 3: Run the next queries which help identify what roles we should remove, in our current scenario the Hyper-V Integration Role.
Please note that you will have to edit the query and enter your VBR actual Hostname.
Validation of the roles will require the next command:
((get-vbrserver -Name VBRHostname).FindPhysicalHost().GetComponents()) | Where { $_.IsUpToDate -match 'False' }
Removal will require the next command:
((get-vbrserver -Name VBRHostname).FindPhysicalHost().GetComponents()) | ? { $_.Type -eq 'HostComponentTYPE' } | % { $_.Delete() }
Please see here an example:
Let's say the new Veeam server is named "MyVeeamBackupServer" then the PowerShell command will be: ((get-vbrserver -Name MyVeeamBackupServer).FindPhysicalHost().GetComponents()) | Where { $_.IsUpToDate -match 'False' }
The results should show the role which cannot be upgraded, in our case HvIntergration
Then we need to adjust the next command: ((get-vbrserver -Name MyVeeamBackupServer).FindPhysicalHost().GetComponents()) | ? { $_.Type -eq 'HostComponentTYPE' } | % { $_.Delete() }
Please note that the Name has to be adjusted to reflect the Veeam Server Hostname and then the 'TYPE' has to be changed to reflect what role we want to remove, which in the current scenario is the HvIntegration.
So, the PowerShell command for our example will be: ((get-vbrserver -Name MyVeeamBackupServer).FindPhysicalHost().GetComponents()) | ? { $_.Type -eq 'HvIntegration' } | % { $_.Delete() }
If more than one Component should be removed, then you need to run the second command for each of them.
After you run the PowerShell commands, close the Veeam GUI, then power it on and verify if any upgrade components wizard page opens. If it does, then complete the wizard and check the results.
Occasionally a Veeam rescan may be required or a refresh in the GUI (which can be achieved by pressing the "F5" keyboard key. )
Should this not work, revert Veeam to its previous state using the Configuration Restore
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Then raise a case with Veeam support and provide a copy of the Veeam Database as instructed here:
https://www.veeam.com/kb1471#:~:text=Sq ... e%20Backup
To ease the process, confirm the database engine used for the Veeam Database.
