I have a new installation of Veeam Backup & Recovery and I’m trying to add an Azure Stack cluster. I’ve tried adding it as a Hyper-V virtual infrastructure but this fails with a very generic permissions type error / node is not a cluster error. The account I’m using has domain admin permissions.
I’ve been unable to find any documentation on how this should work. Has anyone experience of this?
Andrew
Best answer by andrew.luck
Got to the bottom of this one and it was a simple authentication issue. There is a difference between specifying domain\username and username@domain. The correct format to use with the installer is domain\username.
+21I am unsure that you can add an HCI cluster from Azure to the Veeam console. Based on the solution architecture diagram from the help site - Solution Architecture - Veeam Backup for Microsoft Azure Guide
Might be something that needs to be asked to Support and possibly the forums - https://forums.veeam.com
+7+21Thanks for sharing that link Cary. I was not sure as I don’t deal with Azure but good to know it is supported for HCI. 😎
+6Thanks for sharing,
Please look at the link below and ensure you meet the requirements.
Yes we’re running Veeam 12 with HCI 22H2.
This article makes a reference to the Hyper-V role being installed. Is that not part of Azure Stack by default?
+21Please look at the link below and ensure you meet the requirements.
Yes we’re running Veeam 12 with HCI 22H2.
This article makes a reference to the Hyper-V role being installed. Is that not part of Azure Stack by default?
I believe it is part of the stack by default but in order for Veeam to connect you need the role installed on a server in the stack. That is if I am reading that correctly. 😋
Please look at the link below and ensure you meet the requirements.
Yes we’re running Veeam 12 with HCI 22H2.
This article makes a reference to the Hyper-V role being installed. Is that not part of Azure Stack by default?
OK, yes. When I checked the installed Windows roles then Hyper-V is ticked on the cluster nodes.
I believe it is part of the stack by default but in order for Veeam to connect you need the role installed on a server in the stack. That is if I am reading that correctly. 😋
OK. When I checked the installed Windows roles Hyper-V is shown with a check mark so that looks OK. Where I’m struggling with this is that the usually excellent Veeam documentation appears to be missing for this feature.
Double checking at the moment that our account is a local admin on the cluster nodes. After that, I think we’ll have to raise a support call.
One other question with https://www.veeam.com/kb4047
My initial reading of the table was that for Azure Stack HCI OS 22H2 (version 20349.x) we require Veeam 12 to be supported. Is this correct, or is v12.1 also OK with this version of Azure Stack?
+21One other question with https://www.veeam.com/kb4047
My initial reading of the table was that for Azure Stack HCI OS 22H2 (version 20349.x) we require Veeam 12 to be supported. Is this correct, or is v12.1 also OK with this version of Azure Stack?
12.1 should work as well and be backward compatible. The minimum version of Veeam is on the left of that chart to support the corresponding version.
+21Please look at the link below and ensure you meet the requirements.
Yes we’re running Veeam 12 with HCI 22H2.
This article makes a reference to the Hyper-V role being installed. Is that not part of Azure Stack by default?
OK, yes. When I checked the installed Windows roles then Hyper-V is ticked on the cluster nodes.
I believe it is part of the stack by default but in order for Veeam to connect you need the role installed on a server in the stack. That is if I am reading that correctly. 😋
OK. When I checked the installed Windows roles Hyper-V is shown with a check mark so that looks OK. Where I’m struggling with this is that the usually excellent Veeam documentation appears to be missing for this feature.
Double checking at the moment that our account is a local admin on the cluster nodes. After that, I think we’ll have to raise a support call.
Yeah, it should work then, but after checking local admin you may be best to raise a support ticket.
+3I assume all the usual things have been checked as well like making sure the right firewall ports are open? If it’s using Kerberos rather than NTLM then you might see errors in the logs on the Azure Stack HCI hosts about SPN records missing, this could be part of the auth issue as well.
+3Forgot to link to the kerberos docs Kerberos Authentication - User Guide for VMware vSphere (veeam.com)
+20Hi
Just following up to see if any of the comments provided was able to help with your question? If so, for others’ benefit with the same question, please mark a comment which best answered your query as ‘Best Answer’.
Thank you.
We still have an open Veeam support call for this.
Looking at Windows Defender firewall on the HCI nodes it appears that Veeam has been previously installed and removed as the rules to allow traffic are already in place.
+20Great! Thank you for the update. Please keep us posted.
+21We still have an open Veeam support call for this.
Looking at Windows Defender firewall on the HCI nodes it appears that Veeam has been previously installed and removed as the rules to allow traffic are already in place.
Thanks for the update. Hopefully support gets the issue resolved soon for you.
Got to the bottom of this one and it was a simple authentication issue. There is a difference between specifying domain\username and username@domain. The correct format to use with the installer is domain\username.
+20Ah, yes. Pretty much throughout Veeam’s User Guide, they share user auth format as that needing to be used for various components. Glad you got it sorted Andrew.
Best!
+21Got to the bottom of this one and it was a simple authentication issue. There is a difference between specifying domain\username and username@domain. The correct format to use with the installer is domain\username.
Yes, Veeam is very picky this way with the username format. Glad to see you got this figured out.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
