How to Test Manually Mounting the Veeam vPower NFS Datastore

KB ID: 1284
Product: Veeam Backup & Replication | 9.5 | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13
Published: 2011-10-06
Last Modified: 2026-02-23
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.

Purpose

This article documents manually mounting the vPower NFS Datastore using the vSphere Web Client. 

The steps of this article are only intended as a troubleshooting step to help investigate and isolate an issue with vPower NFS-based restores failing.

Solution

Part 1: Information Collection

To add an NFS Datastore to an ESXi host, you will need to specify

  • Datastore name
  • Folder
  • Server
The vSphere datastore wizard page titled "Name and configuration" asks for NFS Share Details to create a new datastore. Fields for "Datastore name," "Folder," and "Server" are blank, with example paths provided below each field. An informational message recommends using the "Mount to additional hosts" action if configuring an existing datastore on new hosts.

Identify the Server Value

  1. Edit the repository where the backup files are stored.
  2. Switch to the Mount Server tab of the repository setting.
  3. Take note of which server is selected in the drop-down box under Mount server.
  4. Determine the Mount server's IP address and note it for later.
The "Edit Backup Repository" window is on the "Mount Server" step. The backup server is "VBR.domain.tld (Backup server)." The instant recovery write cache folder path is shown, and the option to enable vPower NFS service is available.
Identify the Folder Value
  1. Connect to the server that was identified as the Mount server in the last step.
  2. Open the Registry Editor (regedit)
  3. Open the Veeam NFS Shared Folders list:
    • Veeam Backup & Replication 12: HKLM\SOFTWARE\WOW6432Node\Veeam\Veeam NFS\Shared Folders\
    • Veeam Backup & Replication 13: HKLM\SOFTWARE\Veeam\Veeam NFS\Shared Folders
  4. Within one of the keys with a GUID value will be a string Value named nfsFolderName
  5. Take note of the nfsFolderName value's data for later.
The Registry Editor shows the "Shared Folders" key under Veeam NFS. The "nfsFolderName" REG_SZ value is set to "/VeeamBackup_VBR.LAB."
Identify the Datastore Name Value

Use the nfsFolderName value without the leading forward slash.

For example, if the nfsFolderName value is set to /VeeamBackup_VBR.LAB, then the Datastore name Veeam Backup & Replication would use will be VeeamBackup_VBR.LAB.

Part 2: Disable vPower NFS IP Authorization

Veeam Backup & Replication restricts access to the vPower NFS Share so that it is only accessible by the ESXi host during restore operations. When testing the manual mounting of the vPower NFS Datastore, the  IP Authorization system must be disabled to allow the inbound connection from the ESXi host to the Mount Server.

To disable the IP Authorization system, create the following registry value on the Mount Server associated with the repository where the backup files are stored.

Key Location: HKLM\SOFTWARE\WOW6432Node\Veeam\Veeam NFS\
Value Name: vPowerNFSDisableIPAuth
Value Type: DWORD (32-Bit) Value
Value Data: 1

After creating the above registry value, restart the Veeam vPower NFS Service.

This value disables built-in IP authentication for the vPower NFS Share and is only recommended for testing.
Remember to delete the value or set it to 0 after testing.

The Windows Registry Editor displays the Veeam NFS registry key. The "vPowerNFSDisableIPAuth" REG_DWORD entry is set to 0x00000001 (1).

Part 3: Manually add the VeeamBackup_ datastore

Note: The directions below document how to create an NFS datastore via the vSphere Client connected to a vCenter running vSphere 7.0. If the environment you are working with is running a previous version or does not have a vCenter, consult VMware documentation for creating an NFS datastore.

  1. Connect to the vCenter via the vSphere Client.
  2. In the Hosts & Clusters view (ctrl+alt+2), locate the host specified during the restore operation.
  3. Right-click on the host.
  4. In the context menu under Storage, select New Datastore.
The vSphere Client interface shows a context menu for the "O6.lab" node in the "Cloud" section. Under "Storage," the "New Datastore..." option is highlighted.
  1. Select NFS for the datastore type, and click Next.
The "New Datastore" wizard is on the "Type" step. The "NFS" option is selected, with alternatives for "VMFS" and "VVol." The "NEXT" button is highlighted.
  1. In the New Datastore wizard that opens, select NFS 3 and click Next.
The "New Datastore" wizard is on the "Select NFS version" step. The "NFS 3" option is selected, and "NFS 4.1" is also available. The "NEXT" button is highlighted.
  1. On the next page, enter the details you collect in Stage 1 of this article and Click Next.
    • For the Datastore name, enter the nfsFolderName value without the leading forward slash.
    • For the Folder, enter the value of nfsFolderName found in the registry on the Mount server.
    • For the Server, enter the Mount Server's IP address.
The "New Datastore" wizard is on the "Name and configuration" step. Datastore name is "VeeamBackup_VBR.LAB," Folder is "/VeeamBackup_VBR.LAB," and Server is "192.168.1.75." The "NEXT" button is highlighted.
Enter the information gathered in Stage 1 of this article.
  1. Review the summary information and click Finish to create the datastore.
The "New Datastore" wizard is on the "Ready to complete" step. The summary displays the Datastore name "VeeamBackup_VBR.LAB," type "NFS 3," server "192.168.1.75," folder "/VeeamBackup_VBR.LAB," and access mode "Read-write." The "FINISH" button is highlighted.
Observe whether the Create NAS Datstore task completes or fails.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

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

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.