No engines found for work (Generally occurs after an environmental change, or UVB deployment).
Nov. 3, 2016, 5:20 p.m. Error 192.168.5.141 No engines found for work (SERVER-RP)
Nov. 3, 2016, 5:20 p.m. Error 192.168.5.141 No engines found for work (SERVER-QA)
Nov. 3, 2016, 5:20 p.m. Error 192.168.5.141 No engines found for work (DEV-SVR)
Delete the current Jobs, and create new ones. Use the PROTECT section, click and check the VM listed, then click on Settings then Edit. Click on the BDS checkbox, and see what engines are listed. If you do not see one, then you need to add a VBA and give it the Engine designation so that you can protect those VMs. The Engine designation occurs when you assign storage to a VBA.
The messages are related to the Engine it expects. When you made the change, the Unique Identifier changed in value. Thus, the jobs you have scheduled, can not find the Engine. The other possible reason it can not find the Engine is that there is no Engine on the Host or Storage where the VMs reside.
Another item to consider is if we can access the storage. Shared storage pools need a UVB VBA Engine on the ESXi hosts. However, a Local Storage will also need to have a UVB VBA Engine on it to allow restores to be sent to that storage.