NFS with Windows Server

[PHILIP_SONNTAG]

Hey guys,

we want to connect a WindowsServer 2019 with a nfs-share. We can see the nfs-share within the WindowsServer. But we have no write-access to it. We are not sure wich parameter we should set, to get write access. 

Also tried to create a volume with security-Style ntfs instead of unix wasn't helpful. Seems that a minimal configuration error is stopping us. Is someone able to help? Want to store backupdata for Commvault (mediaagent) there, which cannot be backuped by IntelliSnap. 

Marcel & Philip

[parisi]

Why can't you use SMB for this?

If you require Windows NFS, you'd need to enable the export policy rule to allow writes.

I cover Windows NFS here in TR-4067:

https://www.netapp.com/us/media/tr-4067.pdf

[PHILIP_SONNTAG]

Hey parisi

Thanks. The TR doesnt face configuration of netapp Volumes. Should I use ntfs security style? Should ist use usermapping?

We Export 0.0.0.0/0 and check all.

Philip


Philip Sonntag | ACP IT Solutions AG | philip.sonntag@acp.de

[parisi]

Security style just covers how you want to handle permissions.

If you want UNIX perms, use UNIX security style. NFS users will use a UID/GID to gain access based on how you set the volume permissions.

If you want Windows perms, use NTFS. Then the user will need to map to a valid Windows user.

This blog also covers it.

https://whyistheinternetbroken.wordpress.com/2019/02/05/windows-nfs-who-does-that/

[liu]

The security style is Unix and still some parameters need to be changed.  

Enable access for Windows NFS clients

[Kamran_Alam]

I understand that CIFS for Windows will work more efficient here as the ONTAP 9 and above will allow to create CIFS server in ONTAP without joining the CIFS server to a domain.