Problem Description
Backups fail with error code AHV34 when the Druva Proxy is unable to connect to the Nutanix Prism service. This results in immediate failures for Nutanix VM backup jobs.
Cause
This connectivity failure prevents the proxy from performing mandatory API operations. Common causes include:
API Endpoint Unreachable: The Druva Proxy cannot reach Nutanix Prism on the required API endpoint (
https://<prism-host>:9440). This prevents the backup proxy from using the Nutanix v3 API to fetch VM metadata (UUID, disk layouts, network info).Snapshot Operations Blocked: Prism manages VM snapshots. Without API access, the proxy cannot initiate the snapshot workflow required for backups.
DNS Resolution Failures: The proxy cannot resolve the Prism FQDN, preventing it from mapping the hostname to an IP address.
Port 9440 Blocked: Nutanix Prism requires inbound access over TCP port 9440. Traffic may be blocked by firewalls, Network ACLs, routing/VLAN restrictions, or aggressive SSL inspection intercepting HTTPS communication.
Incorrect or Changed Prism Hostname: If the Prism IP or FQDN changes (e.g., cluster migration, DNS updates, certificate changes) and the Druva configuration still references the old hostname, the proxy continues attempting to connect to an invalid endpoint.
Traceback
Failed to get VM by UUID using V3 error: could not connect to Prism. Get "https://<prism-host>:9440/api/nutanix/v3/vms/<vm-uuid>/": dial tcp: lookup <prism-host> on 127.0.0.53:53 no such host
Resolution
Step 1: Verify Connectivity to Prism
From the Druva Backup Proxy server command line, test network connectivity to the Prism endpoint using either of the following commands:
curl -k https://<prism-host>:9440/api/nutanix/v3/vms
OR
telnet <prism-host> 9440
⚠️ Note: If the endpoint is unreachable or connection times out, proceed to Step 2.
Step 2: Validate DNS Resolution
Check whether the Backup Proxy can properly resolve the Prism hostname:
Bash
nslookup <prism-host>
If DNS resolution fails:
Update your environment's DNS server entries to correctly reflect the Prism host.
Temporary Workaround: Add a static host entry mapping the correct IP to the FQDN inside the
/etc/hostsfile on the proxy.
Step 3: Verify Firewall and Network Rules
Ensure that outbound traffic from the Proxy ➔ Prism on TCP port 9440 is explicitly allowed.
Check local firewalls, security groups, and corporate VLAN routing rules.
If your network utilizes SSL decryption/inspection, ensure the Prism IP/FQDN is whitelisted from decryption, as it breaks the secure HTTPS channel used by the proxy.
Engage your network/security team if any blocks are identified.
Step 4: Re-run the Backup Job
Once network connectivity and name resolution are restored:
Navigate to the Druva Management Console.
Retry the failed Nutanix VM backup jobs.
Confirm that the status changes to successful.