SOLVED: Veeam Fails on Server 2016 Cluster

If you Veeam backups are failing when connected to a new or upgraded Server 2016 cluster, you likely need to set a disk parameter to fix it.  Veeam has a KBase article on this but it skips some simple steps and does not tell you where to perform the changes… so we do, right here:

Note that this will only work if you have upgraded the functional level of your cluster to Server 2016 which you can verify with the PowerShell command get-cluster | fl *

If you see version 9, you are good to go.  If you see version 8, you need to make sure you have no 2012R2 (or holder) hosts still in your cluster then upgrade it using PowerShell command Update-ClusterFunctionalLevel .    See the screen shot to the right.

On one of your Server 2016 Cluster Machines:

1. Create the folder: C:\Clusterstorage\Volume1\Hyper-V\Shared
2. In PowerShell (as an admin) run the following three commands:
   Get-ClusterResource "Virtual Machine Cluster WMI" | Get-ClusterParameter ConfigStoreRootPath
$path = "C:\ClusterStorage\Volume1\Hyper-V\Shared"
Get-ClusterResource "Virtual Machine Cluster WMI" | Set-ClusterParameter -Name ConfigStoreRootPath -Value $path