On This Page

Network File System (NFS) Connector

The NFS connector in DryvIQ has specific permission-related requirements beyond that of the connector Identity. Additional configuration may be needed to allow DryvIQ to use of the NFS Connector. 

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 you plan to use to create the NFS Connector has all necessary permissions. For proper job function, the account requires Read, Write, Update and Delete privileges.

• If using IP, ensure that 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.

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

• Any non-printable ASCII characters will not be filtered by DryvIQ

• 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 only supported for Windows only.

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, however 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 long path support enabled, you will see the exception ‘invalid parameter: name’ in the log file or in the application user-interface log tab when attempting to get permissions on files with long paths.

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.

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 supports the ability to assign permissions only to a certain 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 is running on Microsoft Windows, there are some nuances that may affect creating an NFS connection.

Multiple NFS Connections

You cannot create multiple connections to the same location UNC path and multiple users when DryvIQ is running 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 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

There is an underlying Microsoft Windows issue that can cause issues when creating NFS connections. If an attempt is made to create a new NFS connection using an invalid username/password. The connection test will fail, which 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 about 15 seconds after entering the correct username/password before running the connection test. The extra time allows Windows time to clear out the incorrect credentials and recognize the correct ones that were 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}}"
      }
}