Skip to main content
commvault.com commvault.com

Good day all

 

I have an issue with a Hyper-V cluster.
I have 6 nodes that are all VSA’s.

Three of the nodes were upgraded to Windows Server 2016. The remaining three are on Windows 2012 and are pending an upgrade.

Since the upgrade it seems that the hosts in the cluster do no communicate with each other during a VM backup.
If I use the upgraded nodes as the only VSA’s then I have on issue.
Is this issue due to different OS versions? I’ve checked the account permissions on the cluster and the nodes and they’re all correct.

 

The error is see is the normal authentication one usually associated to a permission issue.

Error Code: r91:50] Description: Unable to connect to virtual machine host hCORE01] as user ]xxx]. Please ensure that the access node is able to communicate with the host and that the user account and password are correct. Source:core05, Process: vsbkp 

 

Core01-03 are Server 2016 

Core04-06 are Server 2012

 

Would the OS discrepancy be something within Commvault or something at a Hyper-V cluster level?

 

Thanks all,
Mauro

From MS, the pre-requisite is to have same OS version in the cluster.

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn505754(v=ws.11)?redirectedfrom=MSDN

https://social.technet.microsoft.com/Forums/windowsserver/en-US/f3e94f13-f28a-4c21-926a-1b90c0e7d6cc/create-cluster-with-2-different-operating-systems?forum=winserverClustering

Each of the Windows comes with different versions of WMI. WMI calls are used to communicate with the nodes. 

Thanks so much for the information. I came across the same information after typing the question. Much appreciated.

 

Reply


Terms & ConditionsCookie settings