Skip to main content

Unable to Deploy VMware Proxy Using Additional Deployer Tool (Deploy Proxies)– "Error in fetching datacenter mapping by vcid."

Unable to Deploy VMware Proxy Using Additional Deployer Tool (Deploy Proxies)– "Error in fetching datacenter mapping by vcid."

Updated this week

Problem Description:

When attempting to deploy a VMware proxy using the VMware Deployer tool, the following error is encountered:

Cause:

This error typically occurs when existing proxies are in a disconnected or maintenance state and have lingering virtual disks (VMDKs) attached. These disks interfere with the deployer tool’s ability to fetch the datacenter mapping correctly.

Resolution:

Follow the steps below to verify the state of existing proxies and remove unnecessary disks:

Step 1: Verify Proxy State

  • Log in to the Druva Management Console or the vCenter.

  • Check if any existing proxies are disconnected or in maintenance mode.

Step 2: Inspect Disks on Existing Proxies

  1. Log in to vCenter or the ESXi host where the proxy is deployed.

  2. Locate and select the affected Proxy VM.

  3. Right-click and choose Edit Settings.

  4. In the settings window, expand the Hard disk section and review the number of attached disks.

    • The proxy should typically have 4 disks.

    • Any disks beyond disk 4 may be residual from past backup or restore jobs.

Step 3: Manually Unmount Extra VMDK(s) from the Backup Proxy

To safely detach lingering VMDK(s) from the proxy:

  1. Power off the backup proxy virtual machine.

  2. Right-click the proxy VM and select Edit Settings.

  3. Identify the unwanted Hard Disk(s) by checking the Disk File path.

  4. Once verified, click the X mark next to the unwanted disk entry.
    Important: Do NOT select the option “Delete files from datastore”.

  5. Click OK to save and close the configuration window.

Step 4: Retry Proxy Deployment

  • After confirming that unnecessary disks have been unmounted and the proxies are in a healthy state, attempt the proxy deployment again using the VMware Deployer tool.

Did this answer your question?