You can add an SMB (CIFS) share in the NAS Manager.
-
Click
add to display the
Add Share page.
The following table describes the fields on this page:
Field/Item Description EVS/File System Currently selected file system to which the CIFS share will link. Cluster Namespace Currently selected cluster namespace to which the CIFS share will link. change / browse (depending on Web browser) Enables the user to select a different file system or (on a cluster) a different cluster namespace. Share Name Name of the CIFS share. Comment Additional information associated with the CIFS share. This information is often displayed to clients along with the share name. Path or CNS Path The directory to which the CIFS share points. Users accessing the share are able to access this directory, and any directories under it in the directory tree. To find a directory, click change / browse. On a file system only, select the Create path if it does not exist option to create the path if it does not already exist. If the file system is mounted read-only, for example it is an object replication target, it is not possible to create a new directory. Select a path to an existing directory.
Max Users The maximum number of users who can be associated with the CIFS share. The default is unlimited. Show Snapshots - Show and Allow Access: Displays and allows access to snapshots.
- Hide and Allow Access: Hides snapshots, but still allows access to the hidden snapshots.
- Hide and Disable Access: Hides and disallows access to snapshots.
Changes to this setting become effective when a CIFS client refreshes its folder view.
Cache Options - Manual Local Caching for Documents. The Manual mode permits the user to specify individual files required for offline access. This operation guarantees a user can obtain access to the specified files whether online or offline.
- Automatic Local Caching for Documents. The Automatic mode is applied for all non-executable files on the entire share. When a user accesses any non-executable file in this share, it is made available to the user for offline access. This operation does not guarantee that a user can access all the non-executable files, because only those files that have been used at least once are cached. Automatic can also be defined for programs.
- Automatic Local Caching for Programs. The Automatic mode is applied for all executable files on the entire share. When a user accesses any executable file in this share, it is made available to the user for offline access. This operation does not guarantee that a user can access all the executable files, because only those executable files that have been used at least once are cached. Automatic can also be defined for documents.
- Local Caching Disabled. No caching of files or folders occurs.
Note: The server supports Offline Files Access. This allows Windows 2000 and later clients to cache files that are commonly used from a network/file share. To use Offline Files, the client computer must be running Windows 2000 or later.Transfer to Object Replication Target When a file system is recovered from a snapshot, one of the final steps is to import the CIFS shares found in the snapshot representing the selected version of the file system. Only those CIFS shares marked as transferable will be imported. Use the list to specify one of the following:- Enable: CIFS shares will be transferred to recovered file systems.
- Disable: CIFS shares will not be transferred to recovered file systems.
- Use FS default (the default): When the target file system is brought online, CIFS shares will be transferred if Transfer Access Points During Object Replication is enabled for the file system.
Access Configuration IP addresses of the clients who can access the share (up to 5,957 characters allowed in this field). Refer to IP Address Configuration** at the end of this table. Follow Symbolic Links Enables the following of symlinks for this share. Note: As of release 12.2 of the NAS Platform, clients using SMB2 or later are able to follow relative symlinks to files on storage without the use of global symlinks, if smb2-client-side-symlink-handling is enabled.Follow Global Symbolic Links Enables CIFS clients to follow global (absolute) symlinks via the Microsoft DFS mechanism for this share. Force Filename to be Lowercase Forces all filenames generated on this share to be lowercase. This is useful for interoperability of UNIX applications. Enable ABE By default, ABE is enabled for shares and on the server/cluster as a whole.
When enabled, ABE filters the contents of a CIFS share so that only the files and directories to which a user has read access rights are visible to the user.
Note: Enabling ABE can impact CIFS performance. To disable, use the CLI command fsm set disable-ABE-support true.Enable Virus Scanning If virus scanning is enabled and configured for the global context or for the EVS hosting the file system pointed to by the share then, when the share is created, virus scanning is enabled by default. If virus scanning is not enabled for the global context or for the EVS hosting the file system pointed to by the share then, when the share is created, virus scanning is not enabled by default, but you can enable it a per-EVS basis.
Note: Virus scanning is set up on a per-EVS basis, or for all EVSs using the global configuration context, but cannot be set up on a per-server or per-cluster basis.Ensure Share Continuously Available Enables persistent file handles and transparent failover on the CIFS share. When enabled, Windows-based clients can continuously access the CIFS share if a network failure or a cluster node failure occurs. For example, if one cluster node fails, the client transparently migrates to another cluster node without any interruption to the client applications.
This SMB3 option is available only in a clustered environment of more than one cluster node, and is disabled by default.
Note: Continuous Availability can impact CIFS performance and should only be enabled where it is required, such as with Microsoft Hyper-V or Microsoft SQL Server. When this feature is in use, it is also recommended that the Administrator disables DDNS on the server. If the file system is an object replication target, continuous availability is not effective until the file system is promoted.Share Permissions Share Permissions List By default, when a CIFS share is created, the group Everyone is added to the share permissions list. User Home Directory Mapping Mode Used to specify how per-user home directories are created. The following options are available:- Off. Disable the home directory feature for this share. Do not automatically create home directories on this share for users. This is the default.
- ADS. Create the user home directories based on the home directory information supplied by the Active Directory server for each user. If you select ADS, do not specify a Path.
- User. Create the user's home directory by converting the user's Windows user name to lower case. (The user's Window's domain name, if any, is ignored.) For example, a user DOMAIN\John Smith would result in a home directory of john_smith.
- DomainAndUser. Create the user's home directory by creating a directory named for the user's Windows domain name, then converting the user's Windows user name to lower case and creating a sub-directory by that name. For example, a user DOMAIN\John Smith would result in a home directory of domain\john_smith.
- Unix. Create the user's home directory by converting the user's UNIX user name to lower case.
Path Per-user home directories will be created in the specified Path, relative to the share root, which is specified without a leading \. If this field is left blank, user home directories will be created directly in the share root.
By default, only one share per file system can be configured with home directories. The cifs-home-directory command can be used to relax this restriction, in which case great care must be taken not to configure conflicting home directories.
For example, a share with a path of \home1 and a share with a path of \home2 would not cause a conflict, whatever home directory paths were configured. However, a share with a path of \ and a default home directory path would conflict with a share with a path of \dir and a default home directory path.