VBR 11.0.0.837 & Nutanix AHV 2.1.396

[Didi7]

Hello guys,

I did a fresh install of both software (Community Edition), but unfortunately I cannot add a Nutanix AHV cluster, because this entry is missing. Only VMware vSphere, Microsoft Hyper-V, Microsoft Windows and Linux can be added.

Anybody else with the same behavior or a solution?

Regards,
Didi7

[Mildur]

You have to install the plugin on top of your vbr server.
After that, you are able to add your nutanix cluster.

https://helpcenter.veeam.com/docs/van/u ... tml?ver=21

[Didi7]

What do you mean on top of your vbr server?

I did a fresh OS install Windows Server 2016 and installed the recent Cumulative Updates 03-2021, then I installed VBR 11.0.0.837 and then I installed Nutanix AHV Plugin 2.1.396. Then I configured the infrastructure but I am unable to add a Nutanix AHV cluster.

Is it because of Nutanix Community Edition? In VBR 10.x it works.

Regards,
Didi7

[Mildur]

You have installed „Nutanix AHV Plugin 2.1.396“ on your vbr server. That is correct.
I was missing that information from your first post and I have thought, you forgot to install the plugin.

Nutanix community Edition is supported by veeam.
Community Edition: CE 2019.11.22 or later
https://helpcenter.veeam.com/docs/van/u ... tml?ver=21

If you don‘t see the Nutanix Cluster on this menu, please reboot your vbr server. This way, the plugin will be registered correctly if something is not working in the background.
If that isn‘t working, it‘s best to open a support ticket with veeam support. They can analyze the plugin logs to find the cause about the missing entry.

https://helpcenter.veeam.com/docs/van/u ... tml?ver=21

[Didi7]

Hello Mildur,

thanks for your prompt reply. I was talking about the Community Edition from Veeam B&R, not from Nutanix AHV

Well, even after a reboot, no Nutanix AHV cluster could be added. I removed the software, rebooted the server, reinstalled Nutanix AHV Plugin 2.1.396 and rebooted again, but I still cannnot add a Nutanix AHV cluster.

I did a Nutanix Snapshot on the VM and will restore the server to this Nutanix Snapshot and re-install everything again. Should it still not work, I will let you know again.

To open a support ticket, you need a support id, which is not available in the Community Edition of VBR 11.0.0.837 as far as I know. So how is that done?

Regards,
Didi7

[Mildur]

You can open a support request with community edition.
Support is on best effort.

Here is a small statement about free support from a veeam official: post407365.html?hilit=Community#p407365

Nutanix ahv Backups should work with Veeam Community Edition. Page 6:
https://www.veeam.com/veeam_vbr_one_11_ ... son_ds.pdf

[HannesK]

Hello,
looks like an issue. I remember that worked fine during V10 beta and also looks like it should work in V11 according the license document Mildur mentioned.

I will come back on this.

Thanks,
Hannes

[Didi7]

Ok, i used my Nutanix VM-snapshot to restore the Windows Server 2016 to get back prior Veeam VBR 11.0.0.837 installation. I installed VBR 11.0.0.837, took another Nutanix VM-snapshot and continued with Nutanix AHV 2.1.396, but even after a reboot I am unable to add a Nutanix AHV cluster, so indeed it might be a bug.

Is there any work-around available?

Regards,
Didi7

[Mildur]

You can use veeam Agents to backup your vms, until it‘s resolved.
Let us wait for Hannes response.

[Didi7]

No hurry Mildur,

i could also use VBR 10.0.1.4854 P20201202 with VAN 2.0.558 but this VAN version has other bugs with proxy registration as well

Regards,
Didi7

[HannesK]

it's a bug, yes - but I don't have a date yet, when it will be fixed (that's why I did not come back yet).

I will update once I have a timeframe when it will be fixed.

[Didi7]

Ok HannesK, good to know. Vacations are over now for me but as there is no workaround available currently, the product is useless atm.

I must wait until it's fixed now.

[Didi7]

Upgrading to VBR 11.0.0.837 P20210324 prior to installing Nutanix AHV 2.1.396 doesn't work either btw.

Regards,
Didi7

[HannesK]

Hello,
yes, as I said, it's an open bug bug.

Please understand that free product bugs have lower priority for bug-fixing than other products. With a valid license, everything works fine.

Best regards,
Hannes

[Didi7]

HannesK,

you say that activating a VBR 11 license into VBR 11.0.0.837 prior to installing Nutanix AHV 2.1.396 resolves the bug?

Well, I have enough valid licences for VBR 11, so this would fix the issue? Are you serious?

Regards,
Didi7

[HannesK]

yes sure. You asked specifically about community edition

licensed versions work fine.

Just install a valid license and it will work.

[Didi7]

Yes, indeed. I asked specifically about the community edition of VBR (not the community edition of Nutanix AHV).

I will give it a try.

[HannesK]

hmm, we have Veeam Universal Licensing (VUL) since some time. So there is no difference between VMware / Hyper-V / Nutanix / Windows / Linux / AIX / Solaris / X TB NAS data... a license covers everything.

[Didi7]

Indeed, as long as a valid license is installed in VBR 11.0.0.837 you can not even add servers based on...

VMware vSphere
Microsoft Hyper-V
Microsoft Windows
Linux

... you can also add servers based on ...

Veeam Backup for AWS
Veeam Backup for Microsoft Azure
Nutanix AHV cluster

As soon as you remove the valid license and return to the Community Edition of VBR, the last 3 entries (including Nutanix AHV cluster) are removed again.

Community Edition is no longer welcome at Veeam

[Mildur]

Are you using Community Edition for your customers or is it for internal use?

[Didi7]

Internal use!

We have a lot of valid production licenses in use as well. In some environments we use Community Edition of VBR.

[Mildur]

I have asked, because Community edition would not be allowed to use for offering services to a customer.
If it were for customers, you'd have to purchase licenses and your problem would be resolved.

https://www.veeam.com/eula.html

You may not use the Free and Community Licenses to provide services to third parties (including support services for existing installations) or to process third party data.

[Didi7]

Well, i wouldn't say resolved. If all customers would use a valid license for their VBR installation, I would never had to open this thread, as is just works since the initial release but if you just use the Community Edition, you are lost atm and are forced to use VBR 10 instead

[HannesK]

chances are good, that the fix makes it into the next cumulative update (some weeks to go)

[Didi7]

Good to know HannesK, but there are still bugs installing or deploying the linux proxy appliance. The appliance gets deployed, is up and running with the configured IPs, but registering the proxy appliance fails and the wizard comes up with errors, similar to those in ...

nutanix-ahv-f51/failed-to-deploy-ahv-pr ... 67378.html

Of course this happens with the licensed version.

So far, v1.0, v2.0 and v2.1 of the Proxy Appliance deployment causes problems.

It would be nice, if these bugs would be finally fixed as well. It doesn't work flawlessly.

Regards,
Didi7

[HannesK]

Hello,
in the post you linked everything worked as documented / expected as far as I see. The release notes mention DNS requirements.

To get bugs fixed, the easiest way is to ask support for a bug number (posting on the forums is not necessary). The only reason this here worked out is because I installed community edition, re-produced it and created a support case for you

Best regards,
Hannes

[Didi7]

Good job HannesK.

Well, you know ... I do spend a lot of free spare time myself to report those bugs, as I have enough other tasks to spend time on during regular work beside backup software in general, as we not only use Veeam.

As soon as I have more time, I will document the problems deploying AHV Proxy appliance in a seperate thread again. It's definitely not bug-free, allthough we have proper working DNS in that environment and the Proxy appliance gets correct DNS configuration in the wizard right before deployment.

For this reason there are some websites trying to solve the problems with deployment of VBR AHV Proxy appliance, which I miss a little bit here at Veeam knowledgebase ...

https://vinception.fr/veeam-how-to-reso ... appliance/
http://www.ms4u.info/2020/03/failed-to- ... m-vbr.html

But there are different bugs as well.

Regards,
Didi7