Can't deploy VEEAM Proxy

[lazman]

Hi,
i can't depoloy VEEAM proxy.
The vm is created, but is then deleted before reaching 100%.

I made the update suggested by LCM to the version:
AHV: el7.nutanix.20201105.30281
AOS 6.1.1
Is this the problem or are they properly supported?

[ronnmartin61]

Take a look at post374097.html#p374097. There are instructions for making a VBR registry change to allow the proxy VM to persist on failure so that you can troubleshoot. Most likely it's a name resolution issue...

[jorgedlcruz]

As Ronn mentioned,
Most likely will be DNS resolution somewhere, take a look on that forum post with great insights into all things DNS. Basically:

• Create a new DNS entry for your future Veeam AHV proxy, like ahvproxy001.jorgedelacruz.es on your DNS Server, with PTR and all
• Make sure AHV, CVM, and in general all Nutanix components can resolve all Veeam Components. Including this new entry you added, ping will timeout but at least should resolve
• Make sure the Veeam Components can resolve all Nutanix AHV, CVM, etc.

If not suing a proper valid DNS Servers, then on that forum post you might find a lot of manual workarounds like adding entries into the hosts files, etc. I wrote a guide step by step with the previous VAN version, in case it helps somehow.

Let us know!

[lazman]

So can you confirm that there are no compatibility problems?
With each VMware update, VEEAM was left behind and had to wait months. Is the situation better with Nutanix?
I checked, there is no DNS problem and the PTR records are correct.
The Windows VEEAM server is in a different VLAN than the Nutanix servers (but there is routing), while the VEEAM proxy is in the same VLAN as Nutanix.

[lazman]

I get this error during deploy AHV proxy VM: Discovering objects on cluster : Backup REST error: HTTP StatusCode:'BadRequest', Description:'"Unable to connect to AHV cluster FQDN cluster:9440"

[chris.childerhose]

This message seems that it could be permissions-related possibly. Have you tried using the IP address instead of FQDN to test it out?

[lazman]

Yes I tried.
The proxy deployment reaches about 75%, the Ubuntu VM starts, completes the operations and then reboots.
After the reboot, the deployment stops and the VM is removed.
I can't understand where the problem lies.
In a few days we will have a technician and we will see with him,
the cluster is not yet in production.
The technician had installed the VEEAM server and the proxy and everything was working.

Then it stopped working and the proxy appliance said it was no longer able to connect to the cluster.
I thought the problem was caused by creating a new SSL certificate for Prism.
So I removed the Nutanix cluster from VEEAM and its AHV-Proxy.
But now I have this problem.

[chris.childerhose]

Interesting. Looking forward to the results as I have never worked with Nutanix.