Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Product Version: 9.1 
Last Modified: 27 September 2019


VM processing fails. The following error message appears:

An error has occurred while backing up/replicating/recovering one or more disks of the VM.

Possible Causes

DNS Issues

  • There might be a problem with resolving a host DNS name on the Transporter machine.
  • Host might have multiple IPs, while some of them are not reachable by the Transporter.

Make sure that:

  • Source and target hosts can be pinged from the appropriate Transporter (using both DNS name and IP).
  • If ping fails, edit the HOSTS file on the Transporter machine and specify the proper DNS resolution rules.

Closed Ports

NAKIVO Backup & Replication requires certain TCP ports to be open for successful VM processing. Refer to the Deployment Requirements article for details. 

Make sure that: 

  • Required ports are not used by other applications.
  • Required ports are not blocked.
  • The ports are accessible from the appropriate endpoints.

Server Outage

  • Source or target host might be disconnected or powered off.
  • Source or target Transporter might be disconnected or powered off.

Make sure that all hosts and Transporters are available.

VMware specific issues

Outdated Free VMware ESXi host

  • Free VMware ESXi host certificate might be outdated

Make sure that the certificate is up-to-date. To generate the latest certificate for Free ESXi, read the corresponding section of the VMware Security guide.

VPXA service issue

  • VPXA service on the target ESXi host could be stuck or work incorrectly.

Try to restart the service. Refer to the VMware Knowledge Base article for details.

VM disk issues

  • The target VM disk might not exist
  • The target VM could not be changed
  • Host might have failed to write some data blocks to the target VM.

Perform the following actions:

  •  If possible, use a different datastore for recovery
  • Check host events/logs of the storage device to see if there is any indication of problems.
  • No labels