Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Coming Soon!On This Page

Table of Contents
stylenone

Overview

The managed Network File System (NFS) connector allows you to analyze your on-premises network file shares. It uses SMBLibrary to make the connection (which performs faster than the native Samba). Because this connector is created with read-only access, the connection will be able to read content but cannot be used to take action against it. Therefore, the connector should not be used for Govern policies that require actions to be taken against content.

Tip

The managed Network File System (NFS) connector can be used on both Windows and Linus Network File Systems.

Tip

All current SMB2/SMB3 protocols are supported, including 2.0.2, 2.1.0, 3.0.0, 3.0.2, 3.1.0, 3.1.1.

Note

NFSv4, NFSv3, and NFSv2 protocols are not supported.

Warning

The following features are not supported:

  • Root level connections are not supported.

  • Integrated authentication is not supported.

SMB Azure File Share Protocol Settings

When using the SMB file system protocol in Azure Files, the default profile in Azure Files is Maximum compatibility. DryvIQ recommends leaving the default profile when using the DryvIQ managed NFS connector. The DryvIQ managed NFS connector does not support certain combinations of custom SMB protocol settings.

...

Creating a Connection

  1. Expand the Manage section in the left navigation menu.

  2. Click Connections.

  3. Click Add connection.

  4. Select Network File System (Managed) as the platform on the Add connection modal.

  5. Enter the connection information. All red fields are required for this connection.

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

  7. Click Done.

Add Connection Modal for NFS (Managed)

...

Field

Description

Required

Display as

Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays 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

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>. Root level connections are not supported.

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

Required

User Name

Enter the user name for the administrator account.

This needs to be an account with authority to access the content you will to process.

Required

Password

Enter the password for the administrator account.

Required