Additional Troubleshooting(All versions):
- Manual Hotadd - http://www.veeam.com/kb1184
- Hotadd Requirements - http://www.veeam.com/kb1054
- Deploy an additional standalone proxy to isolate failures to a single specified proxy
- To isolate a specific transport mode as the point of failure, you may also test the other transport modes to ensure that connectivity is correctly established and backup jobs work as intended via the other transport mode.
Additional Troubleshooting (vSphere 5.1 and below):
Backup via Standalone host – Configure backup job to backup via Standalone host rather than through vCenter; this will isolate vCenter as the point of failure. If backup via standalone host is successful, you can attempt restarting the vCenter as well as the management agents on the host(s) where the proxies/VM(s) reside.
Information: Hotadd will only work when the proxy is on the same host as the object being backed up
Additional Troubleshooting (vSphere 5.5):
When attempting to hotadd leveraging a standalone host configuration (that is managed by a vCenter object) with vSphere 5.5 you will receive VDDK Error 13, as well as the error listed below:
Error message: [00680 error 'transport'] Reconfigure attempt failed for VM "2" with Vmomi::MethodFault::Exception ("vim.fault.HostAccessRestrictedToManagementServer")\n
To resolve this particular issue, please leverage Network Mode or Direct SAN transport mode as this configuration is not supported due to limitations of VMware
Information: For more information regarding ‘HostAccessRestrictedToManagementServer’ please see below VMware documentation.