NVP-vProxy: Backups Fail With 'The VM Backup Request Is Not Valid'
Summary: NetWorker VMware Protection (NVP) vProxy backups fail with "The VM backup request is not valid" after repeated retry attempts. The NetWorker server reports that the Data Domain (DD) has reached its maximum read stream count. The DD read stream exhaustion prevents new backup sessions from being established on the NetWorker storage node. ...
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 integration is configured with the vProxy Appliance. The backups have been running successfully for some time, and they started intermittently failing with "
Example of one VM failure from the VMware Protection Policy backup action log:
The VM backup request is not valid." The backup action log shows it keeps retrying for a direct save to the NetWorker Storage node for an hour before it fails with the message.
Example of one VM failure from the VMware Protection Policy backup action log:
MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrvproxy_save NSR notice Action backup vmware-vproxy 'backup' has initialized as 'vproxysave job' with job id 2370140 ... MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrvproxy_save NSR notice Saving the backup data in the pool 'Prod VM'. MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrvproxy_save NSR notice Received the media management binding information on the host '[NETWORKER_STORAGE_NODE]'. MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrvproxy_save NSR notice Connected to the nsrmmd process on the host '[NETWORKER_STORAGE_NODE]'. MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrvproxy_save NSR warning Unable to set up the direct save with server '[NETWORKER_STORAGE_NODE]': retry needed. ... MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrvproxy_save NSR error Unable to process VM '[VM_NAME]': Request timed out before session established. ... MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrvproxy_save NSR warning Unable to set up the direct save with server '[NETWORKER_STORAGE_NODE]': The VM backup request is not valid.. MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrvproxy_save NSR critical [VM_NAME]: Cannot start session with NetWorker server '[NETWORKER_STORAGE_NODE]': The VM backup request is not valid.. ... MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrvproxy_save NSR notice Action backup vmware-vproxy 'backup' with job id 2370140 is exiting with status 'failed', exit code 1The
deamon.raw shows that at the start of the workflow the NetWorker Server was generating warnings indicating the Data Domain reached the read stream count limit. During the VMware Protection Policy execution, the NetWorker Server daemon.raw shows:
MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrd NSR info Protection Policy Notice: Starting workflow '[POLICY_NAME]/[WORKFLOW_NAME]'
MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrd NSR info Protection Policy Notice: Starting action 'backup' for workflow '[POLICY_NAME]/[WORKFLOW_NAME]'
MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrd NSR warning current_read_stream (89) reach max_read_stream 50 for DDR '[DATA_DOMAIN]'.
MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrd NSR warning current_read_stream (90) reach max_read_stream 50 for DDR '[DATA_DOMAIN]'.
MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrd NSR warning current_read_stream (90) reach max_read_stream 50 for DDR '[DATA_DOMAIN]'.
...
MM/DD/YYYY HH:MM:SS [NETWORKER_SERVER] nsrd NSR info policy notice: action backup failed
See article NetWorker: How to use nsr_render_log
Cause
The NetWorker storage node or the target DD is overloaded during the workflow execution. The DD enforces a maximum read stream count. When the current stream count exceeds this limit, the DD cannot accept new sessions. The vProxy backup process requires a direct save session on the storage node. The storage node cannot establish the session because the DD reports the stream limit is reached. The backup retries for approximately one hour before timing out. This typically occurs when multiple backup workflows run simultaneously against the same DD. Traditional client backups and VMware protection workflows compete for the same DD read streams.
Resolution
- Stagger backup schedules. Adjust the protection policy schedules to distribute the load throughout the day. Separate traditional client workflows from VMware protection workflows.
- Review the DD stream utilization. Monitor the DD read stream count during peak backup windows. Identify which workflows overlap and consume the most streams.
- Reduce concurrent backup sessions. Lower the parallelism settings on backup policies that target the same DD. This reduces the number of simultaneous streams.
- Distribute workloads across storage nodes. If multiple storage nodes are available, distribute VMware and traditional client backups across different storage nodes.
- Verify the DD stream limits. Review the DD license and configuration for maximum read stream count. Confirm the limit matches the environment requirements.
Article Properties
Article Number: 000053641
Article Type: Solution
Last Modified: 04 Sept 2026
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.