How to use Veeam vPower NFS server?

[spgsit5upport]

I would not mind using it to export my ISOs share, but can not find any logical explanation how to do it

The service runs, but showmount -e shows no exports on this server

Anybody can help?

http://www.veeam.com/kb_articles.html/KB1055

was of not much help

Seb

[Vitaliy S.]

Seb, please avoid posting log snippets as it is requested by our forum rules.

As to your initial question, then here you go more details on how to share your ISOs via vPower NFS datastore:
NFS client possible on VBR server?

Also if you want to add vPower NFS server to ESX(i) hosts manually, here is a step by step instruction:
add veeam NFS share to ESX for ISO repository

Hope this helps!

[spgsit5upport]

Sorry, but how is the first thread supposed to help me?

There is no explanation in it, HOW to configure vPower NFS server

As already stated:

The service runs, but showmount -e shows no exports on this server, hence it is not accessible/selectable from ESXi (or anything else for that matter)

I do NOT have export VeeamBackup_SERVERNAME

Seb

[spgsit5upport]

If I use haneWIN NFS Server for Windows, I have NO problem at all

Seb

[Vitaliy S.]

Sorry, but how is the first thread supposed to help me?

Maybe I misunderstood your question, but have you tried the solution below?

if you are looking to share some files (such as ISO images) on Veeam Backup server via NFS, then you can simply put the files into vPower NFS root folder (the one you specified during setup)

The service runs, but showmount -e shows no exports on this server, hence it is not accessible/selectable from ESXi (or anything else for that matter)
...
If I use haneWIN NFS Server for Windows, I have NO problem at all

I don't believe "Showmount -e" is supposed to show any exports from vPower NFS server, as this is intended to use with Windows NFS Server, not ours.

[spgsit5upport]

(the one you specified during setup) - no idea what I specified, I can change the registry entries & it seems to be OK

Code: Select all

[30.01.2012 14:43:27] < 4256> 
[30.01.2012 14:43:27] < 4256> =============================================================================
[30.01.2012 14:43:27] < 4256> {
[30.01.2012 14:43:27] < 4256>   Path to the executable module:C:\Program Files\Veeam\Backup and Replication\VeeamNFSSvc.exe
[30.01.2012 14:43:27] < 4256>   Agent version:5.0.2.230
[30.01.2012 14:43:27] < 4256>   OS version: 0.6.0.1
[30.01.2012 14:43:27] < 4256>   OS build: 7601
[30.01.2012 14:43:27] < 4256>   OS description: Service Pack 1
[30.01.2012 14:43:27] < 4256> }
[30.01.2012 14:43:27] < 3820> nfs| Initializing security constraints.
[30.01.2012 14:43:27] < 3820> nfs| Security constraints were initialized.
[30.01.2012 14:43:27] < 3820> nfs| Initializing virtual filesystem.
[30.01.2012 14:43:27] < 3820> nfs|   Registered shared folders:
[30.01.2012 14:43:27] < 3820> nfs|      NFS share [{c17aa9c3-56ac-41c7-a503-b8c8a003ac4b}]. NFS mount path: [\\Veeam\ISOs]. Local path: [\\Veeam\ISOs].
[30.01.2012 14:43:27] < 3820> nfs|   Enumerating NFS items mounted early.
[30.01.2012 14:43:27] < 3820> nfs|   Items were enumerated.
[30.01.2012 14:43:28] < 3820> nfs|     NewItem: [\\Veeam\ISOs]. FID: [41]. Parent: [0].
[30.01.2012 14:43:28] < 3820> nfs|   Resuming backup mounts.
[30.01.2012 14:43:28] < 3820> nfs|   Clearing NFS items registry cache.
[30.01.2012 14:43:28] < 3820> nfs| Virtual filesystem is initialized.
[30.01.2012 14:43:28] < 3820> nfs| 
[30.01.2012 14:43:28] < 3820> nfs| Starting server in asynchronous mode.
[30.01.2012 14:43:28] < 3288> nfs| Initializing TCP/UDP handlers.
[30.01.2012 14:43:28] < 3288> nfs|   Listening port "1058" (mount service).
[30.01.2012 14:43:28] < 3288> nfs|   Listening port "2049" (nfs).
[30.01.2012 14:43:28] < 3288> nfs|   Listening port "111" (portmapper).
[30.01.2012 14:43:28] < 3288> nfs| TCP/UDP handlers were initialized.
[30.01.2012 14:43:28] < 3288> nfs| IO dispatch loop is started.
[30.01.2012 14:43:28] < 3288> nfs|   Connection accepted from "127.0.0.1:49333". Target queue "portmapper".
[30.01.2012 14:43:28] < 3820> nfs| NFS server is ready to process incoming calls.
[30.01.2012 14:43:28] < 3820> nfs| 
[30.01.2012 14:43:28] < 4680> nfs| [EpMapper] Registering program: [100005]. Version: [3], Protocol: [6], Port: [1058]
[30.01.2012 14:43:28] < 4680> nfs| [EpMapper] Registering program: [100003]. Version: [3], Protocol: [6], Port: [2049]
[30.01.2012 14:43:28] < 3288> nfs|   Connection accepted from "10.0.6.1:63625". Target queue "portmapper".
[30.01.2012 14:43:29] < 4680> nfs| Return port number: [0].
[30.01.2012 14:43:29] < 4680> nfs| Return port number: [0].
[30.01.2012 14:43:31] < 3288> nfs|   Connection accepted from "10.0.0.53:806". Target queue "nfs".
[30.01.2012 14:43:31] < 3288> nfs|   Connection accepted from "10.0.0.58:963". Target queue "nfs".
[30.01.2012 14:43:31] < 3288> nfs|   Connection accepted from "10.0.0.57:600". Target queue "nfs".
[30.01.2012 14:43:31] < 3288> nfs|   Connection accepted from "10.0.6.1:63626". Target queue "portmapper".
[30.01.2012 14:43:31] < 4680> nfs| Return port number: [1058].
[30.01.2012 14:43:31] < 3288> nfs|   Connection accepted from "10.0.6.1:63627". Target queue "mount".
[30.01.2012 14:43:36] < 3848> nfs| ERR |Client 10.0.0.58:963: exception while handling request: The operation completed successfully
[30.01.2012 14:43:36] < 3848> nfs| >>  |Invalid size of the NFS handle (16).
[30.01.2012 14:43:36] < 3848> nfs| >>  |--tr:Failed to de-serialize GETATTR3args

but it does NOTHING, definitely can NOT connect to it from ESXi

Mount should be shown, if it is not showing by design, then design is wrong

Also it relies on Windows SHARE to exist as UNC = \\Veeam\ISOs (really odd, as drive letter does not work)

Seb

[Vitaliy S.]

Can you mount it manually through this procedure?

1. vSphere Client, ESX, Add Storage, NFS.
2. Server: enter IP address or DNS name of Veeam Backup server. ESX has to have vmKernel on the corresponding interface.
3. Folder: enter /VeeamBackup_SERVERNAME (where SERVERNAME is NetBIOS name of Veeam Backup server).
4. Do NOT select Mount NFS read-only checkbox (leave this one unchecked). vPower engine will handle disk writes correctly by itself.
5. Datastore name: enter VeeamBackup_SERVERNAME (no forward slash here).

[spgsit5upport]

I DO know how to add NFS storager to ESXi (thank you very much)

But it does NOT work (shall I repeat it? - Does NOT work)

NFS mount 10.0.0.48:/VeeamBackup_VEEAM failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it.

Seb

[Vitaliy S.]

Sorry for that, looks like I misread your post, my bad. Anyway with all technical issues please contact our support team as it is advised when you click New Topic, as in most cases these kind of issues can easily be resolved via remote sessions or debug logs investigation.

[ThomasMc]

Think you should speak to support as I just ran through all my host and can do what Vitaliy posted on all of them, although I didn't have / in mines just;


Server: Veeam0x
Folder: VeeamBackup_Veeam0x
Name: Test_mount

[spgsit5upport]

Updating to v6 made it work

It seems that only RootFolder needs to be adjusted accordingly:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veeam\Veeam NFS]
"MountPort"=dword:00000423
"NfsPort"=dword:00000802
"RootFolder"="I:\\ISOs"
"AsyncTcp"=dword:00000000
"Port"=dword:00001811

Seb

[chimaera63]

@spgsit5support Thanks that did the trick. In my case the RootFolder key was pointing to a wrong location, after correcting this everything was working!

[spgsit5upport]

Nice think is, that with a little tweak, vPowerNFS can work standalone (no need for the rest of Veeam install) to make NFS Datastore accessible to ESXi (nice for ISO "sharing")

Seb

[spgsit5upport]

But just a little warning.

If root of NFS points to volume that is formatted with ReFS then vPower NFS:

- does work for ie ISO sharing
- does NOT work for any VM operation (ie Restore etc)

To have restore working I need to (each time) change the path to NTFS volume & restart vPower NFS service

Seb

[spgsit5upport]

Lost completely ability to use vPowerNFS for anything else. By design?

Used to use it to share iso folder via NFS to ESXi - like this - http://www.danilochiavari.com/2014/07/1 ... nfs-share/

but tried it recently & all I get is error:

Call "HostDatastoreSystem.CreateNasDatastore" for object "datastoreSystem-21440" on vCenter Server "VC5" failed.
NFS mount SR1-02:/VeeamBackup_SR1-02 failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it.
An unknown error has occurred.

while NFS Server 1.2.15 - haneWIN.net works OK.

The difference seems to be UDP ports:

NFS Server 1.2.15

zcm:~ # rpcinfo -p SR1-02
program vers proto port service
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 3 udp 1058 mountd
100005 2 udp 1058 mountd
100005 1 udp 1058 mountd
100005 3 tcp 1058 mountd
100005 2 tcp 1058 mountd
100005 1 tcp 1058 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs

vPowerNFS

zcm:~ # rpcinfo -p SR1-02
program vers proto port service
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 3 tcp 1063 mountd
100003 3 tcp 2049 nfs

[smarechal]

Hello,

On my new veeam backup server, i had Windows NFS Server installed to publish my ISOS on ESXi.
After veeam installation, it dosen't work anymore, maybe ports conflicts?
I tried to mount vPowerNFS share like this : http://www.danilochiavari.com/2014/07/1 ... nfs-share/
It doens't work.
Is it supported in V8?

Thanks a lot.

[foggy]

Should work, please review this thread for some hints and contact technical support for further assistance. Thanks.

[smarechal]

Hello Foggy,

I've reviewed all this post, but it doesn't work.

Here is the log on the veeam backup server:

Code: Select all

[06.01.2016 11:52:27] < 12520> nfs| Client [10.1.10.141] connected.
[06.01.2016 11:52:27] < 12520> nfs| Return port number: [1058].
[06.01.2016 11:52:27] < 12520> nfs| ERR |Client thread error.
[06.01.2016 11:52:27] < 12520> nfs| >>  |Une connexion existante a dre fermpar lӨdistant. Error code: 10054
[06.01.2016 11:52:27] < 12520> nfs| >>  |recv error.
[06.01.2016 11:52:27] < 12520> nfs| >>  |An exception was thrown from thread [12520].
[06.01.2016 11:52:27] < 14044> nfs| Client [10.1.10.141] connected.
[06.01.2016 11:52:27] < 14044> nfs| ERR |Client thread error.
[06.01.2016 11:52:27] < 14044> nfs| >>  |Une connexion existante a dre fermpar lӨdistant. Error code: 10054
[06.01.2016 11:52:27] < 14044> nfs| >>  |recv error.
[06.01.2016 11:52:27] < 14044> nfs| >>  |An exception was thrown from thread [14044].

[Vitaliy S.]

You don't need to install Windows NFS server at the backup server (there will indeed be port conflicts). Why not to use Veeam NFS server to share the ISOs?

if you are looking to share some files (such as ISO images) on Veeam Backup server via NFS, then you can simply put the files into vPower NFS root folder (the one you specified during setup)

[smarechal]

You don't need to install Windows NFS server at the backup server (there will indeed be port conflicts). Why not to use Veeam NFS server to share the ISOs?

Windows NFS Server is not installed. (It was, but i uninstalled it before installing VBR).
This logs are veeam's.

[Vitaliy S.]

Ok! In this case let our support team take a look at your setup.

[masonit]

Hi

I have a odd problem mounting nfs storage from any esxi host that has never mounted NFS to the VBR server before. Because of our network design we have to manually mount the nfs storage. (I have tried solving this in 01289565 without any luck)
But when I try to manually mount the NFS I always get an error:

NFS mount xxx.xx.xxx.xx:/VeeamBackup_xxxx failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it.
An unknown error has occurred.

The workaround for this is to let VBR try to mount the NFS storage. This will fail because of our network design. But after it has failed I am able to manually mount the NFS storage. It seems like when VBR server tries to mount. Somewhere VBR gives the esxi host permission to mount the NFS. Where is this done?

\Masonit

[Vitaliy S.]

Hi Magnus,

The only requirement I'm aware of is that ESXi must have a vmKernel on a network Veeam Backup server is using, but I can double check with the devs.

BTW, what did our technical engineer suggested to check? I see that your ticket is going to be auto-closed soon due to no response from your side.

Thanks!

[masonit]

Target ip of the Veeam NFS server is on the same subnet as ESXi vmkernel.

Veeam support wanted me to trick the vbr server by editing the hosts file. But this is not something I want to do.

Also our way of mounting NFS worked fine in VBR 7. But does not work anymore in VBR 8. I asked Veeam suppport:

"Are you able to find if the logic has changed? As I said before our approach worked in vbr 7.."

Veeam support:
Frankly speaking - no, as I'm not QA or developer engineer, but I believe if you add those details to hosts file and to DC, it should work as expected.
By the way, today VeeamBR v9 is officially being released, so I think it is a good point to consider to upgrade in the nearest future.

Yes the ticket is going to be auto-closed soon due to no response from your side. But I can't say I got the answer I need.

\Masonit

[Vitaliy S.]

Magnus, I have informed our support manager about your case. Also we have just reproduced your situation with our dev and QA teams.

The problem has nothing to do with the permissions. When you initiate a mount of the NFS datastore from the backup console, NFS server creates an export list. If you don't do this, this list is empty and ESXi host fails with the error message above when trying to mount our NFS datastore.

In order to resolve this, you should create this reg key on the backup server:

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veeam\Veeam NFS\Shared Folders\{488f4631-1c52-4066-80be-1632b77d4afb} (This UID key can be random)

"nfsFolderName"="/VeeamBackup_FQDN OF YOUR BACKUP SERVER" (STRING TYPE)

This will export all required data for ESXi host to mount your NFS datastore.

P.S. finally, we will investigate why this change was made in the later version of Veeam B&R and based on the results either include this key be default or not.

Hope this helps!

[masonit]

It sure helps. Thank you for great support!

\Masonit