#1 Global Leader in Data Resilience

Error "Unable to communicate with the remote host, since it is disconnected." with replication or restore

KB ID: 1880
Product: Veeam Backup & Replication | 7.0 | 8.0 | 9.0 | 9.5 | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1
Published: 2014-04-21
Last Modified: 2024-06-21
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Article Applicability
The error, "Unable to communicate with the remote host, since it is disconnected." may occur for many reasons, some more straightforward than others. This article is specifically related to a more obscure scenario where the destination ESXi host runs a vSphere version that does not support the replicated/restored VM's hardware version.

Challenge

A replication or VM restore operation in a vSphere environment where the destination ESXi host is running an older vSphere version than the VM's original host fails with the error:

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

Cause

This error occurs when the Replication or Restore destination ESXi host is not compatible with the VMs existing Hardware Version.

Restores

For restores, the error will be found in the VM.<VMName>.Restore.log file:

Error    Failed to restore vm. Name: [WMS Server]
Error    SetVmCustomConfigOption failed, vmRef ‘#’, name 'uuid.action', value 'keep' (System.Exception)
Error    Unable to communicate with the remote host, since it is disconnected. (System.IO.FileNotFoundException)

Replication

For replication, the error will be found in the Task.<vmname>.<morefid>.log file:

Error    SetVmCustomConfigOption failed, vmRef ‘#’, name 'uuid.action', value
Error    Unable to communicate with the remote host, since it is disconnected.

The error “Unable to communicate with the remote host, since it is disconnected” can be found within the vSphere client as well.

Solution

Ensure that the destination ESXi host for a replication or restore task is running a vSphere version that is compatible with the VM's original hardware version.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

Veeam Backup & Replication
Veeam Data Cloud for Microsoft 365
Veeam Data Cloud for Microsoft Entra ID
Veeam Data Cloud for Salesforce
Veeam Data Cloud for Microsoft Azure
Veeam Data Cloud Vault
Veeam Backup for Microsoft 365
Veeam Backup for Microsoft Entra ID
Veeam Backup for Salesforce
Veeam ONE
Veeam Service Provider Console
Veeam Agent for Microsoft Windows
Veeam Agent for Linux
Veeam Backup for Nutanix AHV
Veeam Backup for AWS
Veeam Backup for Microsoft Azure
Veeam Backup for Google Cloud
Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
Veeam Management Pack for Microsoft System Center
Veeam Recovery Orchestrator
Veeam Agent for Mac
Veeam Agent for IBM AIX
Veeam Agent for Oracle Solaris
Veeam Cloud Connect
Veeam Kasten for Kubernetes
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.