Skip to main content
Possible Causes of VMWARE backup proxy deployment failure

Possible Causes of VMWARE backup proxy deployment failure

Updated over a week ago

Problem description

VMWARE Manual backup proxy deployment Fails

Cause

VMware account has limited permissions

Traceback

Check Deploy Proxy Logs

  • Location: /var/log/Phoenix/deploy_proxy.log

  • Look for error messages related to permission denials.

Example Log Snippet:

[2022-05-06 10:15:05,179] [ERROR] Failed to Upgrade proxy VM to NVMe compatible version: (vim.fault.NoPermission) { dynamicType = <unset>, dynamicProperty = (vmodl.DynamicProperty) [], msg = 'Permission to perform this operation was denied.',

This error clearly indicates that the VMware account used does not have the required permission to perform an operation—such as VM upgrade or modification.

Resolution

Option 1: Use the vCenter Administrator Account

  • Log in using a vCenter Administrator account that has full privileges across the vCenter Server and associated resources.

  • Redeploy the proxy using this account to avoid permission-related issues.

Option 2: Assign Required Permissions to Existing User

  • If using a custom or non-admin account, ensure that the user has all the required permissions necessary for proxy deployment and operations.

  • Refer to the Druva documentation for minimum required permissions

See also

Did this answer your question?