Code: 30983
Summary: The server could not find an appropriate proxy to service the job.
Description: The server was not able to find a proxy based on your proxy selection preference and the proxy setup to service a job. Please review the setup for the proxies and the MCS preference for the proxy selection algorithm.
1. Reboot the vDP Appliance Gracefully:
Even if you've already rebooted, make sure you do it properly via the config GUI or SSH:
/etc/init.d/vdp-configure stop
sleep 10
/etc/init.d/vdp-configure start
Or reboot cleanly from the OS, not just a hard reset.
2. Check Proxy Status:
Login to the vDP configuration interface:
https://<vdp-appliance-IP>:8543/vdp-configure/
* Go to the “Proxies” or “Backup System” tab
* Confirm that at least one proxy is available and healthy
* If proxies are missing, you might need to re-register them or restart services
3. Check MCS Proxy Selection Preference:
From the vDP appliance config UI:
* Go to "MCS Proxy Selection" or related section
* Ensure the Proxy Selection Algorithm is set to “Automatic” or correct availability zone
Also make sure hosts are not in maintenance mode, and proxies are compatible with your backup job (e.g., OS type, resource pool, etc.).
4. Check vCenter Registration and Certificates:
A broken vCenter registration can prevent proxies from being correctly discovered:
* In the config UI → go to “vCenter Registration”
* Re-enter credentials and click “Test Connection”
* If the certificate has changed recently (e.g., after a vCenter upgrade), reaccept it
5. Check Logs for Proxy Registration Errors:
SSH into the vDP appliance and check:
tail -n 100 /opt/vmware/vdp/logs/vdr.log
Look for errors like:
* Proxy unavailable
* Could not find proxy
* MCS failure
This will confirm if proxies are being rejected or failing to register.
6. Ensure Appliance Resources Are Not Overloaded:
Proxies may fail if:
* CPU/Memory is constrained
* The vDP appliance has no access to its underlying datastores
* Too many concurrent jobs are trying to run