Skip to main content

Hi,

I have upgraded Veeam backup and Replication from V12.0 to V12.2.

When I logon to console it ask me to upgrade Veeam VSS Hardware snapshot provider.

If I try to upgreade it give me this error:

Product: Veeam VSS Hardware Provider -- Minimum supported OS version for Veeam VSS Hardware Provider is Microsoft Server 2012 (64-bit only).

 

How can I resolve this issue?

 

thanks

Fabio

What server and OS is it trying to upgrade?  The message is clear on what is supported.  Not sure what else you are looking for here.


Hi Chris,

 

the message is not clear because OS is Windows 11 23H2 and not other windows server version.

 

Where can i find a exustive log of the error?

 

thanks 

Fabio


Hi there, your thread title say it’s on Windows 11?

are you running your VBR on of of these supported versions: https://helpcenter.veeam.com/rn/veeam_agent_windows_6_2_release_notes.html ?

 


Then that should work as that is a supported OS.  You can check the logs here - C:\ProgramData\Veeam\Backup\foldername

This could also potentially be a bug so you might want to open a Support ticket as well to ask.  They can check the logs quicker for you.


Hi there, your thread title say it’s on Windows 11?

are you running your VBR on of of these supported versions: https://helpcenter.veeam.com/rn/veeam_agent_windows_6_2_release_notes.html ?

 

He is as it is 23H2 as noted.

 
 
 

Hi,

 

Yes VBR is running on a supported version:

  • Microsoft Windows 11 (from versions 21H2 to version 23H2)

If you check this page - System Requirements - User Guide for VMware vSphere (veeam.com)

Under the Software section there is .Net, etc. requirements - are any of these outdated or need updating?

It would be faster to get a Support ticket opened for this as we are not Support here and it is just users within a community.  We can only offer suggestions.

 
 
 

Sorry, was a bit to late with my response (regarding the used OS version), as I am typing currently on my mobile. Chris is always fast as light 😊.
As he mentioned, if all requirements are met, contacting the support in that case, would be a good option. 
Cheers, Markus


I found the detail log under C:\ProgramData\Veeam\Backup

 

I attached it.

 

If you notice something strange. please tell me.

 

otherwise I will open a ticket.

 

Thanks


@fabiodna - again this community is not support.   You need to open a support ticket from the main veeam.com website.  They can analyze the logs for you and determine the issue.


@fabiodna as mentioned in VeeamVssHwSnapshotProviderSvc.msi with VeeamVssProviderSvc does not work on Win10. | Veeam Community Resource Hub you have also fixed it with the query 😀


Same problem when upgrading my backup server from 12.1 to 12.2, which is running on a Windows 10 system. I have a ticket open (07409274). This was opened on 9/8. It’s a Community case, so I have no idea how long I’ll have to wait for some help.

 


Same problem when upgrading my backup server from 12.1 to 12.2, which is running on a Windows 10 system. I have a ticket open (07409274). This was opened on 9/8. It’s a Community case, so I have no idea how long I’ll have to wait for some help.

 

I know you have a case but did you follow the other thread above?


Yes, I looked at the other thread, thank you.

The solution presented may make sense to more advanced users, but then, those people may not be using a Community edition and seeking help in Community Support. I looked for the mentioned pgadmin on my system and don’t see it.

Now, if you have some detailed instructions on how to fix this issue, I’d love to hear them...


Yes, I looked at the other thread, thank you.

The solution presented may make sense to more advanced users, but then, those people may not be using a Community edition and seeking help in Community Support. I looked for the mentioned pgadmin on my system and don’t see it.

Now, if you have some detailed instructions on how to fix this issue, I’d love to hear them...

Well this is the Veeam Community but we are not support for the CE edition of Veeam that is still the standard support channel.  I think the direction of the support case is going to be the best way forward unless someone has detailed instructions to post here.


A note to everyone, do not use the SQL queries listed earlier. The UUIDs for the delete statement are unique to each installation, and you may end up causing interruptions in your backups if you run the query. If you already ran the query, simply go through the properties of your managed servers and click “finish”, it should reinstall any components the query accidentally removed.

 

The issue is that the Veeam Hardware VSS Provider is installed on desktop editions of windows, which is not supported by Windows Desktop version. Our requirement for this is listed in the user guide and this KB article.

 

These never should have been installed in the first place (it was not expected behavior in previous versions), and there is now a stale-entry in the Veeam Configuration Database where Veeam thinks the VSS Hardware Provider is installed even if you uninstall it.

 

If you have this issue and an active support contract, please open a Support case regarding the issue. Support can assist with removing the stale entry (do not use the previous query linked earlier, those UUIDs will be specific per each environment, so the query will not work as written)

If you do not have support contract, at your own risk, you can remove the Hardware VSS Provider safely with the following script:

Steps:

  1. Make a fresh Configuration Database Backup.
    1. Optional but good safety: Take a native backup of the database: https://www.veeam.com/kb1471
  2. Copy the script below to a text file, and save it as a .ps1 file, e.g., host-components-remover.ps1
  3. Ensure the script is being run from the Veeam Backup and Replication Server itself.
  4. Run the script from an Administrative Powershell session as Administrator with Backup Administrator Privileges in Veeam
  5. Select the host you’re getting the error on from the UI which pops up (remember, only Windows Desktop Edition is affected)
  6. Afterwards, you’ll be asked which components you want to remove, select the Hardware VSS Provider
  7. Let the script remove the hardware VSS provider component from the database.
  8. Close and open the console again, you should stop being bothered about it.

Script: Before running, do not skip step 0! You must make a backup of the Configuration Database prior to running this script

$answers = "Yes","No"
$Servers = Get-VBRServer
$badServer = $Servers | Select id, name, type | Out-GridView -Title "Select the host with incorrect Components and click 'Okay'" -PassThru
$realBadServer = $Servers | Where-Object {$_.id -eq $badServer.id}
$rbsComponents = $realBadServer.FindPhysicalHost().GetComponents()
$rbscToDelete = $rbsComponents| Select id, type, version | Out-GridView -Title "Select which components to remove and click 'Okay'" -PassThru


While($null -eq $rbscToDelete){
Write-Host "No component was selected. Please ensure you select a component from the list by clicking on it and ensuring it is highlighted. Please select a component to remove once more."
$qq = Read-Host -Prompt "Stop the script now? (Write 'Yes') or Try selecting Components again? (write 'No')"
While($qq -notin $answers){
$qq = Read-Host -Prompt "Answer 'Yes' or 'No'"
}
If($qq -eq "Yes"){Exit}
$rbscToDelete = $rbsComponents| Select id, type, version | Out-GridView -Title "Select which components to remove and click 'Okay'" -PassThru
}


Write-Host "About to remove component $($rbscToDelete.Type) from host $($realBadServer.name). Proceed?"
$Response = Read-Host -Prompt "Answer 'Yes' or 'No'"
While($Response -notin $answers){
$Response = Read-Host -Prompt "Answer 'Yes' or 'No'"
}
If($Response -eq "Yes"){
Write-Host "Removing component $($rbscToDelete.Type) from host $($realBadServer.name) and exiting"
($rbsComponents | Where-Object {$_.id -eq $rbscToDelete.id}).Delete()
} else {
Write-Host "Doing nothing, ending the script"
}

 

 


ddomask,

Beauty. Your script worked like a charm! Thanks for the awesome solution that is simple enough for any of us users to use.

Veeam,

Shame on you for dropping un update on everyone that is broken like this…

 

Roy


Comment