/
Network File System (NFS)

Network File System (NFS)



On This Page

Overview

The Network File System connector uses the NFS protocol to connect to your network file shares, allowing you to analyze, migrate, copy, and synchronize files. The connector is available in Microsoft Windows environments but not in Linux. However, it can access both Linux and Windows file shares.

The first step is to create the NFS connection by providing the information required for DryvIQ to connect to the file share. DryvIQ’s Network File System connector has specific permission-related requirements beyond the connector Identity. Additional configuration may be needed to allow DryvIQ to use the Network File System Connector. 

Account Requirements

  • When Network File System is the source platform, DryvIQ requires an account with read access to the content.

  • When Network File System is the destination platform, DryvIQ requires an account with full access to the content.

Prepare Source Environment  

  • Create a Windows domain user account that will be used for the migration and grant main admin privileges to that user on the file server.

  • Ensure the account used to create the NFS Connector has all necessary permissions. For proper job function, the account requires “Read,” “Write,” and “Update and Delete” privileges.

  • If using IP, ensure the IP is static and will not change.


Create an NFS Connection

  1. Select Connections > Add connection.

  2. Select Network File System as the platform on the Add connection modal.

  3. Enter the connection information. Reference the table below for details about each field.

  4. Test the connection to ensure DryvIQ can connect using the information entered.

  5. Select Done.

 

Field

Value

Description

Required

Field

Value

Description

Required

Display as

Any value

Enter the display name for the connection. If you need to create multiple connections, ensure the name readily identifies the connection. The name is displayed in the application, and you can use it to search for the connection and filter lists.

If you do not add a display name, the connection will automatically be assigned a default name. 

Optional

UNC Path

UNC Path/Domain Name

Enter the UNC path for the connector. The UNC path will be to a folder at least 1 level off the root of the server, for example: \\<server name>\<folder on server>

You can also use the server IP address (for example, \\<ipaddress>\<folder on server>).

You can locate the information using Windows>Control Panel>System and Security>System.

Required

User Name

Admin User Name

Enter the user name for the administrator account. The account must have the authority to access the content you will process.

When creating an NFS connection, DryvIQ can use a Domain Account (DOMAIN\USER) with the proper permissions to connect.

You should leave this field blank if you are using integrated authentication. If the User Name and Password fields are not filled in, DryvIQ will use the credentials for the account being used to run the DryvIQ Manager Windows Service Account to connect, which would also need permissions to connect to \\SERVER\SHARE. This account information was specified during installation.

*When creating an NFS connection with a UNC Path containing Unicode characters (for example, \\test\あああ), User Name and Password are REQUIRED.

Optional*

Password

Admin Password

Enter the password for the administrator account.

You should leave this field blank if you are using integrated authentication. If the User Name and Password fields are not filled in, DryvIQ will use the credentials for the account being used to run the DryvIQ Manager Windows Service Account to connect, which would also need permissions to connect to \\SERVER\SHARE. This account information was specified during installation.

*When creating an NFS connection with a UNC Path containing Unicode characters (for example, \\test\あああ), User Name and Password are REQUIRED

Optional*


Features and Limitations 

Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. Utilize the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.

  • The maximum length of any folder or file name is 32767

  • The maximum path length is 32767

  • No trailing spaces in folder names, file names, or file extensions

  • No trailing periods

  • DryvIQ will not filter any non-printable ASCII characters

  • Restricted characters in the file name: < > : " / \ | ? *

  • When creating a Connector, it must be one level down from the root. Example, C:/1st folder

 

Author Preservation (Windows Only)

Author Preservation for Network File System is supported when NFS is the source connection. It is not supported when NFS is the destination connection.

The NFS account owner can be identified in Properties>Security>Advanced>Advanced Security Settings.

Verify the Windows environment has Long Path support enabled. (Local Computer Policy>Computer Configuration>Administrative Templates>All Settings>Enable Win32 long paths). Refer to Microsoft's Maximum Path Length Limitation documentation for more information. 

.net core supports long paths, but functions that retrieve permissions for individual files still use old Win32 system calls. Long Path support with these functions is not enabled by default.
Without extended path support enabled, you will see the exception “invalid parameter: name” in the log file or the application user interface log tab when attempting to get permissions on files with long paths.

Failed User Mappings

The following message will be added to the Job log if DryvIQ fails to resolve a user in a Microsoft Windows environment: "Security Identifier could not be resolved: <windows exception>."

Last Accessed Date

DryvIQ processing affects the Last Accessed date for files, but DryvIQ restores the original Last Accessed date after reading the file to preserve this date. If the NFS account used to create the source connection has read-only permissions to the source files, DryvIQ cannot restore the Last Accessed date, so the date will be affected by DryvIQ processing.

Migrating to SharePoint Online

The file path length can be an issue when migrating from NFS to a Microsoft SharePoint Online (Microsoft Office 365 or Microsoft OneDrive for Business). Microsoft allows for 400 characters after the end of the base URL. If the file path in NFS exceeds this limit, DryvIQ can attempt to shorten the path by changing the file name to the first character and the extension. For example, here_is_a_long_file_name.txt would become h.txt. If the truncated file name is still not short enough, manual remediation for the identified content on NFS is needed. DryvIQ recommends having the end user reorganize the folder structure to get under the 400-character limit.

Permissions

When applying permissions to FS/NFS, DryvIQ sets read access permission to "Read and Execute" rather than just "Read."

“This Folder Only” Permissions

Network File System supports the ability to assign permissions only to a specific folder. DryvIQ does not support “This folder only” permissions when moving content from NFS to other destinations. DryvIQ will add permissions to the folder on the destination based on the platform rules.


NFS Connection Troubleshooting for Microsoft Windows

When DryvIQ runs on Microsoft Windows, some nuances can affect creating an NFS connection.

Multiple NFS Connections

You cannot create multiple connections that use the same UNC path and multiple users when DryvIQ runs on Windows. The connection creation will fail for the second user because the DryvIQ application uses an underlying Windows mechanism that requires unique names for each connection. If a connection to the same location but a different user is needed, a workaround is to use the domain name in the UNC path for one connection and the IP address in the UNC path for the second connection.

Failed Connection Tests after Correcting Username or Password

An underlying Microsoft Windows issue can cause problems when creating NFS connections. If you attempt to create a new NFS connection using an invalid username/password, the connection test will fail; this is expected behavior. Immediately entering the correct username/password may still result in a failed connection test even though it should pass. To prevent this issue, wait 15 seconds after entering the correct username/password before running the connection test. The extra time allows Windows to clear out the incorrect credentials and recognize the correct ones provided.


Create Connection | REST API

{    "name": "\\\\{{Your Machine Name}}\\{{Your NFS Directory or Folder}}",    "platform": {          "id": "nfs"    }, "auth": {      "unc": "\\\\{{Your Machine Name}}\\{{Your NFS Directory or Folder}}"       } }

 

 

Related content

DryvIQ Migrate Version: 5.9.5
Release Date: April 4, 2025