Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell EMC Avamar for VMware 19.7 User Guide

Backups fail with No Proxy errors

One or several VM image backups fail with No Proxy errors. Following are the error messages that are seen when backup is triggered:

Figure 1. No proxy error
Policy window

Following is the No Proxy error Activity Monitor shows:

Figure 2. No proxy error on activity monitor

On-demand VMware Image backup fails with the following appear:

Figure 3. On-demand VMware Image backup fails

When you click View Details, you get the following details:

Figure 4. Event details of failed backup

The earlier mentioned issue occurs due to the following three reasons:

Cause 1

There are no Avamar Image Proxy servers that are configured to protect the datastore where the client vmdk files are stored. (This cause usually affects 1 or several VM backup clients.)

The steps to fix this error are:

  1. Open Avamar Administrator in AUI.
  2. Go to Asset Management and click the clients tab.
  3. Find the failing VM with No Proxy and edit it.
  4. Go to the VMware tab and look at the datastore that the VM is hosted on.
  5. Go to the Administration window.
  6. Edit the proxies and check on the datastore that hosts the VM.
  7. Click Ok to save the change.

Cause 2

Interruption to the vCenter connection (This cause usually affects all VM clients).

The steps to fix this error are:

  1. Verify that Avamar can connect to the vCenter.
  2. Go to the Administration window and click on the vCenter root domain.
  3. Click the vCenter client connection object and edit the client.
  4. Verify the Avamar server IP or Hostname is valid.
  5. Verify the vCenter user account that Avamar uses is valid.
  6. Click Ok to verify Avamar connect to vCenter.
NOTE:If the connection to vCenter was interrupted due to vCenter maintenance or network outage, restart the MCS service on the Avamar server. It clears any vCenter connection caching issues.

Cause 3

The VM itself has no Hard Disks (This cause usually affects 1 or a couple of VMs).

The steps to fix this error are:

  1. Open vCenter.
  2. Find the VM that is failing with No Proxy.
  3. Edit the VM settings and verify if there are any Hard Disks.
NOTE:If there are no Hard Disks, check with the VM Administrator and contact VMware support. If a backup of the VM is no longer required, retire the VM object in Avamar.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\