The NFS SMB connector was completed as part of MVP1, but not all functionality has been completed. MVP1 includes the foundational work for this connector. The connector will allow the application to connect to NFS while running on Linux machines and is being implemented as part of the platform's long-term technology goals. Because it is still a work in progress, it will not be announced in the release notes. Instead, it will be announced when all functionality and features have been completed and tested. No customers are waiting for this connector, and we do not expect any customers to use this connection any time in the near future.
More details about this connector will be made available both in sprint demos as additional work is completed and in the documentation as it becomes available. The behavior is still being tested for migration so any differences between the NFS connector and NFS SMB connector behavior can be documented.
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.
Creating a Connection
Expand the Manage section in the left navigation menu.
Click Connections.
Click Add connection.
Select Network File Share (SMB) as the platform on the Add connection modal. (Note that the SMB connection will only display in the Connections list on Linux environments. It will not be available on machines running Microsoft Windows.)
Enter the connection information. All three fields are required for this connection.
Test the connection to ensure SkySync 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 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 |
Features and Limitations
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. This applies to migrations, policy scans, and discover scans.
Permissions
Network File Share supports the ability to assign permissions only to a certain 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.