Error Message

V-79-57344-38381

0xe00095ed - Backup Exec cannot create the NFS datastore.  Ensure that the ESXi host can communicate with the Backup Exec server and that you have not exceeded the maximum number of NFS mounts on the ESXi host.
Final error category: Resource Errors.

1. Maximum number of NFS mounts was reached on an ESXi host.
2. ESXi is unable to access the NFS Share created by Backup Exec.  
3.  ESXi cannot resolve the name of Backup Exec server.

1.  For this issue please refer the related article to increase number of NFS mounts on ESXi.

2.  While performing IR, Backup Exec grants NFS Share access to the ESXi host selected in the job.  Permission is granted to host name, and IP address (As per DNS name resolution). If ESXi server tries to connect to NFS share on Backup Exec server using a different IP address, than the one which was granted access then the job will fail with the above error. 
From the Backup Exec server, go to Operational events from the Windows Event Viewer -> Application and Services Logs -> Microsoft Windows -> ServicesforNFS-Server and look for Event ID 2 with the “Mount Operation failed” as below:

Log Name:      Microsoft-Windows-ServicesForNFS-Server/Operational
Source:        Microsoft-Windows-ServicesForNFS-Server
Date:          01/01/2017 12:30 PM
Event ID:      2
Task Category: None
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      BACKUP EXEC SERVERNAME

Description:
Mount operation failed. 

Address:IP Address of ESX
Share: NFS Share name created inside Backup Exec server

Event detail will show the address using which ESXi tried to access the NFS share. If the IP given in the event is not the IP of the ESXi host resolved by DNS (which got the access rights on NFS share), IR job fails.

3.  To resolve this issue make sure that ESXi server uses same IP which is resolved by DNS while connecting back to Backup Exec server.

Backup Exec Instant Recovery (IR) job for VMware virtual machine fails with error 0xe00095ed

ETrack: 3906663