Automatically add new Hyper-V host to VEEAM

[GabesVirtualWorld]

Hi,
We're trying to automate the deployment for Hyper-V as much as possible. We now have one last manual step where VEEAM sees the new host in SCVMM and we need to configure the host to be used by VEEAM. Is there a way to automate this last step? And would it be best to do this by installing an MSI on the host and connecting to VEEAM, or maybe use powershell to talk to the VEEAM Server and force installation?

[Egor Yakovlev]

Hi!

Add-VBRHvSCVMM PowerShell cmdlet should solve the case.
Make sure SCVMM Admin UI is pre-installed on VBR Server for Veeam to be able to connect to the SCVMM server.

/Thanks!

[GabesVirtualWorld]

Ah thank you, will look into that.

[GabesVirtualWorld]

Is there an easy way to see which hosts are seen by VEEAM but don't have the agent installed? I tried using get-vbrserver and filter on the "IsUnavailable" property, but I'm not sure if that is true when the host is not reachable or true when no agent is installed.

Info : VCDHYP82005.xxxxxxx (Microsoft Hyper-V Server)
ParentId : 414eeac7-6a30-4ac4-9c70-6b625e2f03d8
Id : aee136d4-bd38-492f-bce7-f68dd97544b8
Name : VCDHYP82005.xxxxxxx
Reference : 0a3cf625-648c-4aa8-93f5-5d3fb86aebc4
Description :
IsUnavailable : True
Type : HvServer
ApiVersion : Unknown
PhysHostId : 00000000-0000-0000-0000-000000000000
ProxyServicesCreds : Veeam.Backup.Common.CCredentials

[GabesVirtualWorld]

Hi!

Add-VBRHvSCVMM PowerShell cmdlet should solve the case.
Make sure SCVMM Admin UI is pre-installed on VBR Server for Veeam to be able to connect to the SCVMM server.

/Thanks!

It looks as if Add-VBRHvSCVMM tries to add a SCVMM server and not a Hyper-V host that is part of SCVMM.
When I try Add-VBRHvHost, it adds the Hyper-V host as standalone instead of a host part of SCVMM.

[PetrM]

Hi Gabrie,

Did you try to rescan the existing SCVMM or to use this cmdlet? --Edited by moderator--
UPD 27.09.2021 A newly added Hyper-V host will not be detected during rescan automatically, please refer to our help center.

Also, I'm not sure that I clearly understand the purpose to check agents on Hyper-V hosts. You can just add VMs which are running on virtualization hosts on this step of backup job creation wizard, you don't need to install any additional components manually.

Thanks!

[oleg.feoktistov]

Hi Gabrie,

Actually, Add-VBRHvSCVMM should add VMM host along with dependant Hyper-V hosts thus mirroring the UI behaviour. No need to use different cmdlets to add VMM host and dependant Hyper-V hosts separately. I'd advise to follow Petr's suggestion.

Thanks,
Oleg

[GabesVirtualWorld]

Sorry, somehow I can't get it to work.

I have a running SCVMM with a cluster of 5 Hyper-V 2019 hosts. These show "healthy" in the VEEAM Backup Infrastructure section under the SCVMM server. Now I install the 6th host but I want to automate the VEEAM part so that after installing this host and adding it to the cluster, I just run a script for VEEAM and be done.

So when installation of the hyper-v host is finished, it automatically shows in the VEEAM UI under the SCVMM server, in the Backup Infrastructure. But it shows the host with a red cross. When in this state, if I put a VM on it and try to backup that VM, I get the following error: "Error: Hyper-V Integration Service is not accessible through the network on source host".

What we normally do, manually, is right click the host choose properties and run through the wizard and then it is finished. This is the step I want to automate, since we deploy about 4 hosts weekly.

I tried the rescan-vbr, but that doesn't make a difference:
$newhv = get-vbrserver -type hvserver | where-object {$_.name -eq "newhost"}
Rescan-VBREntity -Entity $newhv

So, how can I use powershell to resolve the red cross on the hosts that show in my backup infrastructure?

Hope I explained it better this time.

[PetrM]

Hi Gabrie,

Yes, the problem is clear, thanks for clarifications! May I ask you to contact our support team and share case ID with us? I don't think it's normal that the host is unavailable and that you get the error about Hyper-V integration service. I believe it's better to understand the root cause of the issue than to develop some scripts to circumvent it.

Thanks!

[GabesVirtualWorld]

Ok, so in perfect scenario I install a new Hyper-V host in SCVMM and it should then become available in VEEAM Backup infrastructure and be immediately available to backup VMs. No manual intervention should be needed?

[GabesVirtualWorld]

Case # 05038496

[PetrM]

Hi Gabrie,

Apology but I gave a wrong statement in my post above: a new host will not be detected automatically during rescan of SCVMM (unlike the rescan of cluster). This limitation is described on our help center, on this page:

If the Hyper-V host is added to a cluster that is managed by SCVMM, right-click the SCVMM server, select Properties and go through the steps of the Edit Hyper-V Server wizard.

You need to go through the wizard in order to deploy our components on the added host. Thus, your request to automate these steps is totally valid. I think we can add this idea to the list of improvements for future releases and implement it as long as we have enough similar requests.

Thanks!

[GabesVirtualWorld]

Thank you for your reply. So:
- Manual intervention is needed
- Currently no way to automate this.

Then we can close this thread and the running case
Thanks for responding so quickly

[oleg.feoktistov]

Hi Gabrie,

Thank you for your feedback on automating this. I believe we need a Set cmdlet for SCVMM server, which would be a programmatic equivalent of going through the wizard again. So, noted it as a feature request.

Best regards,
Oleg