Overview
The managed Network File System (NFS) connector enables 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 connection can be used for content scans where DryvIQ only needs to read content or as a source connection for migrations. The connector should not be used as the destination connection for migrations or in content scans requiring actions against content.
The managed Network File System (NFS) connector can be used on Windows and Linux Network File Systems. However, there are some limitations regarding the SMB and NFS versions it supports, which are listed below.
Supported Protocols
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.
Unsupported Protocols
NFSv4, NFSv3, and NFSv2 protocols are not supported.
Unsupported Features
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 is Maximum compatibility. DryvIQ recommends leaving the default profile when using the managed NFS connector. DryvIQ’s managed NFS connector does not support some custom SMB protocol settings.
Creating a Connection
- Expand the Manage section in the left navigation menu.
- Click Connections.
- Click Add connection.
- Select Network File System (Managed) as the platform on the Add connection modal.
- Enter the connection information. Red fields are required.
- Test the connection to ensure DryvIQ can connect using the information entered.
- Click Done.
| 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 server's root, 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. The account must have the authority to access the content you will process. | Required |
| Password | Enter the password for the administrator account. | Required |
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms, allowing you to configure actions based on Job Policies and Behaviors. The information below is platform-specific. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.
| Supported Features | Unsupported Features | Other Features/Limitations |
|---|---|---|
|
Timestamp Preservation (When used as the source connection) |
Author/Owner Preservation | File Size Maximum: No maximum |
|
Account Map (When used as the source connection) |
File Lock Propagation | Path Length Maximum: 32,767 |
|
Group Map (When used as the source connection) |
Mirror Lock Ownership | Restricted Types: None |
|
Permission Preservation (When used as the source connection) |
User Impersonation | Segment Path Length: No maximum |
| Tags Map | Invalid Characters: / | |
| Version Preservation | ||
| Metadata Map |