Skip to main content
Question

Problem with Nutanix worker after update to 13.1.1.18

  • September 18, 2026
  • 4 comments
  • 33 views

After updating VBR im having an issue with backups from Nutanix.
Jobs finish with errors:
9/18/2026 8:01:17 AM Failed : ... : No available worker was found


While testing worker getting following errors:

9/18/2026 4:00:11 AM Succeeded : Testing the worker WORKERNAME
9/18/2026 4:00:12 AM Succeeded : Finished searching for uploaded worker VM images
9/18/2026 4:00:49 AM Succeeded : The worker VM was deployed successfully (0:00:37)
9/18/2026 4:00:51 AM Succeeded : Configuration settings of the WORKERNAME were synchronized successfully (0:00:02)
9/18/2026 4:00:53 AM Succeeded : The worker VM was powered on successfully on the host HOSTNAME (0:00:02)
9/18/2026 4:01:16 AM Succeeded : The following IP address was successfully obtained: 10.XXX.XXX.XX (0:00:22)
9/18/2026 4:01:16 AM Succeeded : Successfully synchronized updater settings of the worker
9/18/2026 4:01:18 AM Succeeded : Local bundle available (0:00:01)

9/18/2026 4:06:28 AM Warning : Failed to install the local bundle: Cannot access a closed Stream. (0:05:10)
9/18/2026 4:07:43 AM Warning : Failed to download worker logs: No connection could be made because the target machine actively refused it. (0:01:15)
9/18/2026 4:07:45 AM Succeeded : The worker VM 694db5b2-59ee-401e-8afb-ec52c6ce07e7 was removed from the cluster successfully (0:00:02)
9/18/2026 4:12:26 AM Failed : Failed to connect to the worker service: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (0:04:41)
9/18/2026 4:12:26 AM Failed : Failed to retrieve the configuration of the worker VM: Error occurred while getting VM list: Request failed when executing remote operation vmGet: VM kNotFound: The VmGet request failed: NotFound: 10   :Unknown VMs: 694db5b2-59ee-401e-8afb-ec52c6ce07e7 not found
9/18/2026 4:12:28 AM Failed : Worker WORKERNAME test failed: Failed to connect to the worker service: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
 

Any idea please?
 

    4 comments

    Chris.Childerhose
    Forum|alt.badge.img+23
    • Chris.Childerhose
    • Veeam Legend, Veeam Vanguard
    • September 18, 2026

    Did you check the system requirements for Nutanix versions - https://helpcenter.veeam.com/docs/vbr/userguide/ahv_system_requirements.html?ver=13

    Don't use Nutanix so only thing I can think of other than opening a support ticket as well.  Best of luck 

    Chris Childerhose (Enterprise Architect) - VMCE+ | VMCA | VMCE | VMCE-SP | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 7* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV/VCP-VVF | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    coolsport00
    Forum|alt.badge.img+23
    • coolsport00
    • Veeam Legend
    • September 18, 2026

    ​@mawo - Veeam creates Worker VMs. This is the same technology Veeam uses for other newly added hypervisors. It’s a small Linux Proxy appliance used for hotadd backup functionality. From your log there it appears...somehow….maybe the Transport/Data Mover service may not be installed or running maybe? 

    Since the Worker is an automated process done within VBR, I recommend getting ahold of Support as Chris suggested.

    Keep us posted what they say if you can.

    Best.

    Shane Williford - Veeam VMCA/VMCE+ | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
    • mawo
    • Author
    • New Here
    • September 18, 2026

    forgot to add, Nutanix version pc.7.5.1.4

      eblack
      Forum|alt.badge.img+4
      • eblack
      • Influencer
      • September 21, 2026

      I would check connectivity from the VBR server to the worker IP while the worker is up. TCP 443 is used by the Platform Service to communicate with the Veeam Updater service on the worker, and TCP 19000 is used for communication with the worker itself.

      If those are open and the plug-in is at 13.10.0.605, I would probably open a Veeam support case. 

        Terms & ConditionsAccessibility statement