NVP-vProxy: VM backups are failing - NSR VMware proxy is not available for datastore using transport mode 'Hotadd' in vCenter
Summary: The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. vProxy backups are failing with errors stating that the vProxy is not available for datastores using transport mode hotadd in the vCenter server. This error means that the vProxy or its ESXi host does not have access to hotadd mount the VM that failed, which resides on the datastore listed in the error message. To resolve this issue, the vProxy must have access to the datastore that the failing VM resides on. There are many ways to accomplish this. The easiest resolution depends on your VMware structure. Ensure that the prerequisites listed are met before deciding which option will be the best fit for your environment. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. The vProxy backups fail with errors stating that the vProxy is not available for the datastore using the hotadd transport. The backup action log and NetWorker Management Console show:
NSR VMware proxy is not available for datastores (Datastore name) using transport mode 'Hotadd' in vCenter 'vCenter FQDN'
Cause
The error message indicates that a registered and online vProxy on the NetWorker server does not have access to the referenced datastore. This can be commonly caused by several reasons:
- The vProxy may not have access to the ESXi Host where the VM being backed up resides.
- The vProxy's ESXi Host may not have access to the datastore where the VM being backed up resides.
- The vProxy may not be properly registered to the NetWorker Server.
- The NetWorker Server and vProxy may not have name resolution of each other working properly.
- The vProxy may not have access to the ESXi Host where the VM being backed up resides.
- The vProxy's ESXi Host may not have access to the datastore where the VM being backed up resides.
- The vProxy may not be properly registered to the NetWorker Server.
- The NetWorker Server and vProxy may not have name resolution of each other working properly.
Resolution
Ensure that the following vProxy pre-requisites have been met for the environment.
1) Validate the vProxy can access the ESXi host, over ports 443 and 902, where the virtual machine resides. These ports are required for backup and recovery operations.
4) Verify that the vProxy is on an ESXi host that has access to the datastore reported in the backup failure.
Once the pre-requisites are properly met for the environment, the following options should help access the virtual machine datastore for the backup workflow.
1) Validate the vProxy can access the ESXi host, over ports 443 and 902, where the virtual machine resides. These ports are required for backup and recovery operations.
- From a vProxy ssh session, use the curl command to validate access: curl -v https://[ESXi_FQDN]:[PORT]
- Go to the vProxy configuration by going to the "Devices" tab in the NMC and select on the VMware vProxies section in the left-hand side menu.
- In the right-hand details pane, right-click to access the "Properties".
- In the NSR VMware Proxy Properties window "Configuration" tab, the VM proxy certificate field should be populated.
- If the certificate is not populated, follow Dell Dell Knowledge Base article to re-register the vProxy. NVP vProxy: How To Unregister/Re-Register a vProxy Appliance?
4) Verify that the vProxy is on an ESXi host that has access to the datastore reported in the backup failure.
a) Log in to the vSphere web client for the vCenter.
b) Go to the vProxy VM under VMs and Templates, and click on the Summary tab.
c) The Related Objects field shows which ESXi host the vProxy Resides on:
b) Go to the vProxy VM under VMs and Templates, and click on the Summary tab.
c) The Related Objects field shows which ESXi host the vProxy Resides on:
d) Go to the Hosts and Clusters tab and select the ESXi host identified in the above step.
e) Click on the Datastores tab:
e) Click on the Datastores tab:
The vProxy only has hotadd access to the VMs which reside on the datastores accessible by the ESXi host the vProxy resides on.
Once the pre-requisites are properly met for the environment, the following options should help access the virtual machine datastore for the backup workflow.
- Deploy an additional vProxy to a cluster that has ESXi hosts with access to the referenced datastore
- Perform a Storage vMotion of the affected virtual machine to a datastore that is accessible by the ESXi host hosting the vProxy
- Update the SAN zoning to ensure the vProxy ESXi host has access to the datastore
- Create a workflow and configure the backup action to use only one vProxy. Ensure the vProxy has the hotadd transport sessions disabled and the NBD transport sessions enabled. If NBD transport is being used as the main backup transport mode, a 10G network is recommended. Performing many backups with NBD mode can cause congestion on the ESXi host management network. Plan your backup network carefully for large-scale NBD installs
Additional Information
For more information about vProxy connectivity, hotadd and NBD transport modes, see the NetWorker VMware Integration Guide for your version of NetWorker: https://www.dell.com/support/home/product-support/product/networker/docs
Affected Products
NetWorkerProducts
NetWorkerArticle Properties
Article Number: 000057075
Article Type: Solution
Last Modified: 26 Sep 2023
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.