Skip to main content

VMware backup fails with error: VMWARE VMOMI65535-Unable to communicate with the remote host

Problem description

Virtual machine snapshot creation fails with the following error:

VMWARE_VMOMI65535-Unable to communicate with the remote host.

Traceback

C:\programdata\Phoenix\Vmware\backup\<Backupset>\<job_id>

[2020-03-10 22:35:56,424] [INFO] Taking Snapshot...

[2020-03-10 22:35:56,433] [INFO] Waiting for tasks to complete

[2020-03-10 22:35:56,454] [ERROR] SyncError: Unable to communicate with the remote host, since it is disconnected.

msg = 'Unable to communicate with the remote host, since it is disconnected.',

[2020-03-10 22:35:56,454] [INFO] Exception occurred while snapshot:

[2020-03-10 22:35:56,454] [ERROR] Error <class 'inSyncLib.inSyncError.SyncError'>:Unable to communicate with the remote host, since it is disconnected. (#10006ffff : vmodl.fault.HostNotConnected) (Error Code : VMWARE_VMOMI65535). Traceback -Traceback (most recent call last):

File "agents/vmware/vSphereAdapter.py", line 972, in create_snapshot

File "agents/vmware/vSphereAdapter.py", line 945, in _create_snapshot

File "inSyncLib/inSyncError.py", line 30, in raise_error

SyncError: Unable to communicate with the remote host, since it is disconnected. (#10006ffff : vmodl.fault.HostNotConnected) (Error Code : VMWARE_VMOMI65535)

Resolution

  1. Ensure that the backup proxy is in a connected state.

  2. Ensure that the virtual machine does not show VM_name(disconnected) state under vCenter.

  3. Check the connection to ESXi port 902 from backup proxy. Run the following command:
    #telnet <Esxi_IP / Esxi_Name> 902

  4. If the ESXi/vSphere host should be licensed for vStorage APIs, verify if the VMware license is installed.
    For example, for vSphere 6.0:

    1. In the vSphere Web Client, select Administration, and under Licensing, select Licenses.

    2. Select the Licenses tab.

    3. In the table, select a license.

    4. Click View License Key.

  5. Update vCenter Credentials

    Verify whether the vCenter credentials have been changed in the VMware environment. If the credentials were updated, ensure that the same credentials are also updated in the Druva console.

    Refer to the following article for instructions on updating vCenter credentials in Druva.How to update vCenter credentials over a vCenter backup proxy from Phoenix Management Console | Druva | Documentation

See also

Did this answer your question?