Avamar: Proxy Deployment Manager Fails With com.vmware.vim25.NotSupported Error

Observed Behavior

• Proxy Deployment Manager (PDM) UI shows no progress after selecting the Create Recommendation button.
• The PDM log records an error containing com.vmware.vim25.NotSupported.

Example log entry:

2021-11-03T12:41:49.843-0600 TRACE [TaskExecutor-36][            util.VcConnection#            close]: Logging out of VC session
2021-11-03T12:41:49.843-0600 TRACE [TaskExecutor-36][ impl.ConnectionManagerService#   releaseSession]: Releasing connection manager session: id=...29d475070b19
2021-11-03T12:41:49.844-0600 ERROR [TaskExecutor-36][        handler.RequestHandler#eGenericException]: Unexpected error com.vmware.vim25.NotSupported
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

Improper vCenter Client Configuration

Root Cause Details

The Proxy Deployment Manager (PDM) expects a genuine vCenter Server as the target for proxy recommendations. In this case, an ESXi host was added to Avamar and labeled as a "vCenter" client. Because PDM’s codebase only supports interactions with vCenter servers, it cannot process the request, resulting in a failure.

• The identified client is an ESXi host, not a vCenter Server.
• PDM does not have logic to handle ESXi hosts presented as vCenter clients.
• This mismatch triggers the VMware API error com.vmware.vim25.NotSupported.

A relevant log excerpt demonstrating the error:

2021-11-03T12:41:49.843-0600 TRACE [TaskExecutor-36][            util.VcConnection#            close]: Logging out of VC session
2021-11-03T12:41:49.843-0600 TRACE [TaskExecutor-36][ impl.ConnectionManagerService#   releaseSession]: Releasing connection manager session: id=...29d475070b19
2021-11-03T12:41:49.844-0600 ERROR [TaskExecutor-36][        handler.RequestHandler#eGenericException]: Unexpected error com.vmware.vim25.NotSupported
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

Manually Deploy an Avamar Proxy in vSphere and Register It.

Prerequisites

• vSphere Client access with sufficient privileges.
• Avamar Proxy OVA file downloaded from the Dell Technologies support portal.
• Network information (IP address, subnet mask, gateway, DNS, NTP server).
• Avamar Administrator credentials.

Step‑by‑Step Procedure

1. Confirm the "vCenter" client type.

Log in to the Avamar Administrator console and verify that the client listed as "vCenter" is an ESXi host. If it is an ESXi host, the Proxy Deployment Manager (PDM) will not function.

2. Deploy the Avamar Proxy OVA.

1. Open the vSphere Client and connect to the ESXi host or vCenter.
2. Select Deploy OVF Template and browse to the downloaded Avamar Proxy OVA.
3. Follow the wizard:
   • Enter a meaningful name for the proxy VM.
   • Select the appropriate datastore.
   • Configure the network mapping to the wanted virtual switch.
4. When prompted for configuration parameters, provide:
   • The Static IP address (or DHCP if preferred)
   • Subnet mask, default gateway, DNS servers
   • NTP server(s) for time synchronization
   • Avamar proxy administrator password
5. Complete the deployment and power on the new VM.

3. Verify proxy VM network connectivity.

# From a workstation on the same network
ping

 

Ensure that the proxy can reach the Avamar server (default port 28000) and the vSphere environment.

4. Register the proxy with Avamar.

1. Log in to the Avamar Administrator web UI.
2. Navigate to System > Proxy Management.
3. Click Add Proxy and enter the proxy’s IP address or FQDN.
4. Provide the proxy administrator credentials set during OVA deployment.
5. Click Register. The system validates connectivity and adds the proxy to the inventory.

5. Confirm successful registration.

# In Avamar Administrator, the proxy should appear with status “Online”

If the proxy shows as "Online," registration succeeded.
 

6. Test the proxy with a backup job.

1. Create a simple backup policy targeting a client that can use the new proxy.
2. Run the backup job and monitor its progress.
3. Verify that the job completes without errors and that the proxy logs show normal operation.

Verification Checklist

• The proxy appears in Avamar Administrator with the status "Online."
• Ping and port checks to the proxy succeed.
• Backup job runs successfully using the new proxy.
• No "com.vmware.vim25.NotSupported" errors appear in the PDM or Avamar logs.

Caution: Deploying a proxy on an ESXi host that is not part of a vCenter will not allow PDM to automate the process. Manual deployment is required.
Warning: Incorrect network settings can cause the proxy to be unreachable, leading to backup failures. Double‑check IP, gateway, DNS, and NTP configuration before powering on the VM.
Note: Ensure that the proxy VM complies with your organization’s security policies (for example, firewall rules, hardening guides) before placing it in production.
Caution: If you encounter any issues during deployment or registration, contact Dell Support for assistance. Do not modify Avamar configuration files manually unless directed by a support engineer.