Network File System (SMB)
On This Page
Overview
The Network File System (SMB) connector uses SMB protocol to connect to network file shares so you can analyze, migrate, copy, and synchronize files. The connector is available in Linux environments but not in Microsoft Windows. However, it can access both Linux and Windows file shares. There are some limitations regarding the SMB and NFS versions it supports, which are listed below.
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.
NFSv4, NFSv3, and NFSv2 protocols are not supported.
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 DryvIQ NFS (SMB) connector. The DryvIQ NFS (SMB) connector does not support some custom SMB protocol settings.
Creating a Connection
The first step is to create the connection by providing the connection information required for DryvIQ to connect to the file share.
Expand the Manage section in the left navigation menu.
Click Connections.
Click Add connection.
Select Network File System (SMB) as the platform on the Add connection modal. (The SMB connection only displays in the Connections list on Linux environments. It will not be available on machines running Microsoft Windows. However, it can access both Linux and Windows file shares.)
Enter the connection information. All red fields are required for this connection.
Test the connection to ensure DryvIQ can connect using the information entered.
Click Done.
Add Connection Modal for NFS (SMB)
Field | Description | Required |
|---|---|---|
Display as | Enter the display name for the connection. If you need to create multiple connections, ensure the name readily identifies each 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 | 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 administrator account's username. The account must have the authority to access the content you will process. | Required |
Password | Enter the password for the administrator account. | Required |
Preserve Last Access Time | This setting controls whether DryvIQ maintains the Last Access Time property on items during scans and transfers. It is enabled by default to help retain important file-access metadata. Disable this setting only if your environment restricts updating the Last Access Time property. This is most common when:
| Optional |
Use Kerberos Authentication | By default, the SMB connector uses NTLM authentication. Select No (or skip this field) if NTLM authentication is acceptable. Select Yes if you prefer to use Kerberos as the authentication method. | 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 migration job policies and behaviors. The information below is platform-specific. Use the Platform Comparison tool to see how your platforms may interact regarding features and limitations.
Supported Features | Unsupported Features | Other Features/Limitations |
|---|---|---|
Timestamp preservation | File size maximum: No maximum | |
Account map | Path length maximum: 32,767 | |
Group map | Restricted types: none | |
Permission preservation | Segment path length: No maximum | |
| ||
|
| |
|
|
Last Accessed Date
When NFS (SMB) is used as the destination platform for migrations, DryvIQ preserves the Last Accessed date for files.
During processing, DryvIQ must read the file, which temporarily updates the Last Accessed timestamp. DryvIQ restores the original Last Accessed date after the file is processed, so the timestamp remains unchanged. This behavior applies to both content scans and migrations.
If the NFS account used for the source connection has read-only permissions, DryvIQ cannot restore the original Last Accessed date. In this case, the Last Accessed timestamp will reflect the time the file was processed.
Owner Preservation
DryvIQ supports ownership preservation when NFS (SMB) is configured as the destination connector. When enabled in a transfer job, DryvIQ uses the source item’s CreatedBy value and applies it as the Owner on the destination SMB share.
Because NFS does not support directory-based user lookup, user identities may need to be explicitly mapped to ensure ownership is applied correctly. In scenarios where automatic resolution is not possible (for example, NFS-to-NFS transfers), a user mapping file is required. Usernames must be defined in the source_id and destination_id fields using <domain>\<user> format.
<domain>\<user>In the example mapping below, SOURCE-DOMAIN\source_user is mapped to DEST-DOMAIN\destination_user, allowing DryvIQ to correctly apply ownership on the destination NFS (SMB) share.
source_id,source_username,source_name,source_caption,destination_id,destination_username,destination_name,destination_caption
SOURCE-DOMAIN\source_user,,,,DEST-DOMAIN\destination_user,,,
Support applies when migrating to NFS (SMB). If NFS is used as the source, ownership preservation depends on the destination connector’s ability to resolve and apply permissions.
Permissions
Network File System supports assigning permissions to a specific folder (“This folder only”). 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.
Symbolic Link Limitation
The NFS SMB connector does not support following symbolic links. When the connector encounters a symbolic link, the item is skipped, and the following message will be logged: “The folder was skipped because it was a symbolic link.” Because symbolic links cannot be resolved through the SMB protocol, DryvIQ is unable to read or traverse the target location behind the link.
Unix Users and Groups
DryvIQ's SMB connector does not support viewing Unix users and groups.