AOMEI Cyber Backup
Troubleshooting: Veeam Instant Recovery Failed to Mount NFS Volume
How to fix the Veeam instant recovery failed to mount NFS volume issue? When this issue ouccurs, you need to solve this immediately, otherwise, it may influence the operation of instant recovery.
By Amelia / Updated on November 22, 2024
Instant recovery an NFS volume
I’m trying to test an instant recovery but all it doesn’t start because can’t find volume. For this reason I’ve checked on my VMware ESXi host if it have any NFS Volume but I can find only the datastore on which are stored all VMs and none vPower NFS Datastore. The question is: Why I can’t find mounted NSF folder and vPower NFS Datastore on my ESXi host? In this vPowerNFS Datastore automatically created during the Veeam inistial setup or, rather, must I manually mount on ESXi host afterwards?
- Question from Veeam R&D Forums
Veeam Instant Recovery allows users to quickly boot a virtual machine (VM) from a backup file by mounting the backup file directly into the hypervisor using the Network File System (NFS) protocol. However, when the failed to mount NFS volume issue occurs, it may not be possible to open the VM for recovery. This article will provide you with the reasons for this situation and how to resolve it.
Common Causes of NFS Mount Failures
Some reasons may cause failure to mount NFS volume, the following are some common causes.
1. Firewall or Port Blockage
NFS communication between the Veeam server and the hypervisor requires specific ports to be open. If the firewall blocks these ports, the mounting process will fail.
2. Incorrect Host Configuration
The ESXi host may be incorrectly configured to access the NFS datastore. It may not have permission to access the Veeam server or recognize the NFS share.
3. NFS Service Not Running
During Instant Recovery, Veeam acts as the NFS server, but if the NFS service on the Veeam server is not running or is misconfigured, it will cause a failure to mount NFS volume.
Steps for Veeam Instant Recovery Failed to mount NFS Volume
Since failing to mount NFS volume is capable of causing instant recovery failure, you need to resolve this issue instantly and the following provides you with steps to resolve failed to mount NFS volume.
1. Check Network Connectivity
Use ping and traceroute to test connectivity between both systems and confirm proper DNS resolution for hostnames if they are being used to ensure the Veeam server and the ESXi host can communicate.
2. Verify Firewall Rules
Ensure that the following ports are open between the Veeam server and the ESXi host:
TCP/UDP 111: NFS port mapper.
TCP/UDP 2049: NFS service.
3. Restart the Veeam NFS Service
Open the Windows Services management console(services.msc).
Locate Veeam NFS Service, restart it, and ensure it is running.
4. Confirm ESXi Host NFS Configuration
On the ESXi host, ensure it allows the Veeam server’s IP to connect to the NFS datastore.
Navigate to ESXi Host > Configuration > Storage > Add Datastore > NFS. Add the Veeam server IP if it’s missing.
5. Test Manual Mounting
Try mounting the NFS datastore manually on the ESXi host to check for errors:
▶SSH into the ESXi host.
▶Run the command:
Efficient Instant Recovery Tool for VMware ESXi
An effective instant recovery tool is essential for maintaining business continuity and minimizing downtime. AOMEI Cyber Backup offers a robust solution designed not only to keep your data secure but also to facilitate the seamless and rapid recovery of your virtual machines in the event of a disaster. With this tool in place, you can ensure that your operations run smoothly and that your critical information is protected against potential disruptions.
You can also enjoy the following features while using AOMEI Cyber Backup:
🎯Centralized Management: It allows users to oversee and coordinate their virtual environment without being constrained by specific hardware configurations, such as sockets and hosts.
🔰Instant VM Recovery: You can quickly restore virtual machines to a runnable state, reducing downtime and avoiding losses without the lengthy process of creating new ones from scratch.
😊Easy-to-use Interface: The intuitive web console simplifies backing up and restoring virtual machines, enabling backup administrators to manage data protection efficiently.
✨Agentless Backup for VMs: It can create full, standalone image-level virtual machine backups of VMware ESXi virtual machines.
Step 1. Navigate to Task > Instant Recovery > + New Instant Recovery, you can choose to Restore from task or Restore from local path. The following steps we choose Restore from task as 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 resumes normal.
Conclusion
Failed to mount NFS volume in Veeam Instant Recovery may cause errors in Instant Recovery, but these issues can be resolved. The steps provided in this article can quickly bring the issue back to normal, ensuring that Instant Recovery is working properly and minimizing downtime, also AOMEI Cyber Backup can offer you instant recovery and backup solutions for VMware.
