How to Fix Veeam Instant Recovery Failed to Publish VM [Complete Guide]

How to fix the issue of failing to restore a virtual machine using Veeam Instant Recovery?

By @Crystal Last Updated November 20, 2024

Error: Veeam Instant Recovery Failed to Publish VM

When instant VM recovery fails in Veeam Backup and Replication, it shows some error messages like the following:

  • Publish the virtual machine fails
  • Unable to mount vPower NFS volume .
  • Error during host configuration: NFS error: Unable to mount file system: Unable to connect to NFS server

This problem occurs due to connectivity issues between the Instant Recovery server and the NFS datastore.

Fixed: Veeam Instant VM Recovery Fails [Troubleshooting Steps]

To resolve the failed to publish VM error, follow these steps.

πŸ’‘Note: Ensure that all ports required for the NFS datastore are open (especially port 111) and are not being used by any other application.

1. Connect to the Mount Server associated with the repository where the backup files are stored, and make sure the Veeam vPower NFS Service is 'Running'.

2. Open PowerShell prompt, and then run the following command

Get-Process -Id (Get-NetTCPConnection -LocalPort 111).OwningProcess

3. View the list of datastores listed in your vSphere environment and uninstall the datastores that begin with “VeeamBackup_” and are marked as (invalid) or (inaccessible).

4. Go to the vSphere Client and select the ESXi host specified during the recovery operation. Go to the Configuration tab. Click Networking > VMkernel adapters to write down a list of IPs for each VMkernel adapter. Ping the VMkernel IP on the same network segment as the Mount Server.

5. Use SSH to connect to the ESXi host and verify that the host can perform a vmkping operation on the mount server associated with the repository where the backup files are located.

6. Check the ESXi host and remove the old “VeeamBackup_” datastore.

7. Starting with Veeam Backup & Replication 9.5 U4, the vPower NFS service uses an IP Allow List to control access to its NFS share. Occasionally, the IP address of an ESXi host may not be added to this list automatically.

To check if this is the issue, you can temporarily disable the IP authorization control by creating a specific registry value on the installation server. However, this bypasses the built-in IP authentication of the vPower datastore and should only be used for testing purposes.

Powerful Alternative: Instant Recovery for VMs

AOMEI Cyber Backup is a robust backup and recovery tool that offers seamless protection and instant recovery for virtual machines, effectively addressing challenges of data loss.

Instant VM recovery can rapidly restore a virtual machine directly to its original or a new host with minimal downtime, ensuring business continuity.

πŸ“’Download and install AOMEI Cyber Backup from the button below:

Download FreewareVMware ESXi & Hyper-V
Secure Download

Simple Steps to Perform Instant Recovery

Step 1. Navigate to Task > Instant Recovery > + New Instant Recovery, and select Restore from task for an example.

Step 2. In the Source section, choose the virtual machine and backup version.

Step 3. In the Restore to section, choose the target device.

Step 4. Set the hardware settings for the new virtual machine, including CPU quantity, CPU Cores, and memory size.

Step 5. Click Start Restore to start the instant recovery.

Step 6. Click Start Migration to restore the virtual machine to the production environment after the production environment resumes normal.

Conclusion

The “Veeam Instant Recovery Failed to Publish Virtual Machine” error can be frustrating, but can usually be resolved with a systematic approach.

With the troubleshooting steps mentioned in this article, you can minimize downtime and ensure a smooth instant recovery operation.

For more robust backup and recovery solutions, tools such as AOMEI Cyber Backup can serve as a reliable alternative to virtual machine backup and instant recovery. Ensure your data security and business continuity.