VBR 11.0.0.837 & Nutanix AHV 2.1.396

[Helferlein]

So but when I raise a support case there will be a an unofficial fix for this?

[Mildur]

With VBR community edition, you will not be able to get or even install hotfixes.
A paid license is necessary for that, or veeam will not run after installing the hotfix.

[Helferlein]

Well we have Enterprise Edition VUL licenses... don't worry...
Just want to know if there is a fix when I open a case...

[HannesK]

if you have paid licenses, then the bug does not exist. It's only a community edition issue.

if you have issues with the paid edition, please open a case, yes.

[Algent]

It seems that bug did not got resolved yet?

I just installed the Nutanix AHV Plugin ontop of the newest B&R Server Version and I cannot see that Nutanix Plugin to add in the Add Server.

Had this issue two weeks ago when upgrading to veeam 11
Make sure the "Veeam AHV Service" is running with same user as Veeam Backup Service then restart both. Same things for other plugins like AWS.

Personally I'm at the next step aka: upgraded from 9.5 to 11 and it still constantly fail to cleanup volume groups at the end which make the backups show up as failed even if maybe they are ok.

[Helferlein]

Thank you @Algent!

That did the trick! The AHV Service needs to be run with the same user as the Veeam Backup Service.
Did not realize this that this is documented somewhere in the Veeam documentation... Perhaps I did overread it if it is

[Algent]

You are welcome,

I think it's an issue bound to happen if you use an external sql server since you have to use another account to run the service for that (unless I missed an obvious way of setting sql credentials another way, with we could). In my case I figured it was because it's an old VM that isn't super clean but if it can be replicated on fresh install then the plugins setup are missing a step to set service user.

As for how I got to it it's actually in the setup logs in tmp and I could have found it by myself... but I didn't. It's the support who helped me find the issue with this.
In case you run into it too: had some trouble adding ahv clusters with dns, made proxy vm deployment fail until I re-added cluster with their ip instead of name.

[HannesK]

Hello,
thanks for pointing out the user name solution. I will check that.

In general: all services should run as local system. There is no need to change the defaults. SQL credentials for remote servers can be provided during setup. Or there is the database configuration tool

Best regards,
Hannes

[HannesK]

Hello,
yes, strong recommendation from our QA: always use LOCAL SYSTEM.

Best regards,
Hannes