...
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 used to create the NFS Connector has all necessary permissions to edit, copy, delete, and create files and folders.
If using IP, ensure that the IP is static and will not change.
...
Create an NFS Connection
Select Connections > Add connection.
Select Network File Share as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Test the connection to ensure DryvIQ can connect using the information entered.
Select Done.
Field | Value | Description | Required |
|---|---|---|---|
Display as | Any value | 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 | UNC Path / Domain Name | 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> You can also use the server IP address, for example: \\<ipaddress>\<folder on server> You can locate the information by going to Windows>Control Panel>System and Security>System. | Required |
User Name | Admin User Name | Enter the user name for the administrator account. You should leave this field blank if you are using integrated authentication. This needs to be an account with authority to access the content you will to process. *When creating a NFS connection with a UNC Path containing unicode characters (i.e. \\test\あああ), User Name and Password are REQUIRED. | Optional* |
Password | Admin Password | Enter the password for the administrator account. You should leave this field blank if you are using integrated authentication. *When creating a NFS connection with a UNC Path containing unicode characters (i.e. \\test\あああ), User Name and Password are REQUIRED | Optional* |
...
Features and Limitations
...
.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."
...