Loading...
Loading...
Affected Versions: All Reporting engine upgrade failed ServerDR backup skips Reporting Engine Other Potential Symptoms: Guest OS file retrieval fails. Agent version validation fails. Connection timeout errors are reported. ESXi host responds to ICMP ping requests but TCP port 443 communication fails. Network connectivity tests to the ESXi host show port 443 is inaccessible from the PPDM. Server disaster recovery backup failure Server disaster recovery (DR) backup requests are skipped with the following error message: "The reporting engine cannot process server disaster recovery backup requests during upgrade. Recommended Actions: Wait for the reporting engine upgrade to complete, then retry the backup." The following log entries are observed: "result" : { "issues" : [ { "message" : "The reporting engine is being upgraded. The server disaster recovery backup request was skipped.", "details" : "The reporting engine cannot process server disaster recovery backup requests during upgrade.", "responseAction" : "Wait for the reporting engine upgrade to complete, then retry the backup.", "messageArgs" : [ ], "messageId" : "NR0021", "raiseAlert" : false, "extendedReason" : "The Reporting Node is being upgraded. This Reporting Server DR request will be skipped." } ] } PPDM's internal log is unable to validate the Report engine's version. Therefore unable to upgrade. Error in log InfrastructureNodeSessions-<node_id>.log Log Location: /opt/emc/vmdirect/runtime/logs/visd ERROR: [ReportingNode] vProxy: vProxy: utilization: Unable to retrieve contents of file '/tmp/vmware-admin_850-2768414368/vpvmware313.out' from VM '[HOSTNAME]' (vm-1234): Get "https://[ESXI_HOSTNAME]:443/guestFile?id=39&token=<redacted>": dial tcp ESXI_IP:443: connect: connection timed out ERROR: [ReportingNode] vProxy: vProxy: Unable to retrieve contents of file '/tmp/vmware-admin_850-2768414368/vpvmware43.out' from VM '[HOSTNAME]' (vm-661422): Get "https://192.168.x.x:443/guestFile?id=39&token=<redacted> [192.168.x.x]": dial tcp ESXI_IP:443: connect: connection timed out ERROR: [ReportingNode] vProxy: vProxy: Cannot identify upload path in agent output. INFO: [ReportingNode] vProxy: vProxy: Unknown version is present on VM '[HOSTNAME]' (vm-1234) ERROR: [ReportingNode] vProxy: vProxy: Unable to perform vProxy Agent operation 'utilization' on VM '[HOSTNAME]' (vm-1234).
This issue occurs when PowerProtect Data Manager (PPDM) cannot establish TCP communication with the Reporting Engine ESXi host. As part of the guest file indexing and agent validation workflow, PPDM must communicate with the ESXi host over TCP port 443. Although basic network connectivity, such as ICMP ping, may be successful, PPDM can still fail if TCP port 443 communication is unavailable. This can occur due to firewall restrictions, network routing issues, incorrect DNS resolution, packet filtering, security appliances, or any other network condition that prevents successful TCP communication between PPDM components and the ESXi host. When connectivity on TCP port 443 cannot be established, PPDM is unable to retrieve guest operating system information or validate the agent version on the protected host, resulting in connection timeout or communication failure errors.
Verify end-to-end network connectivity between the PowerProtect Data Manager (PPDM) appliance and the affected ESXi host(s). Since virtual machines may be migrated between hosts within the cluster, validate connectivity to all ESXi hosts that could process backup operations. Confirm the following: TCP port 443 is open and reachable from the PPDM appliance to each ESXi host. Firewall policies permit communication between PPDM and ESXi hosts. Network routing between the systems is functioning correctly with no connectivity interruptions. DNS resolution is accurate for all PPDM, vCenter, and ESXi hostnames involved in the backup workflow. No security appliances, proxy devices, intrusion prevention systems (IPS), or network security policies are blocking or inspecting HTTPS traffic in a manner that disrupts communication. Use ping, nslookup and curl to validate TCP port 443 connectivity from the PPDM Appliance to the ESXi host. Example: nslookup ESXI_HOSTNAME nslookup ESXI_IPping ESXI_HOSTNAME PING ESXI_IPcurl -kv ESXI_HOSTNAME:443 curl -kv ESXI_IP:443
Click on a version to see all relevant bugs