• Configure shares

    PDF

    Configure shares

    Share local paths and export paths

    The following table describes the path settings for shares:

    Setting
    Description
    Local path
    The path to the file system storage resource on the storage system. This path specifies the unique location of the share on the storage system.

    SMB shares

    • An SMB file system allows you to create multiple shares with the same local path. In these cases, you can specify different host-side access controls for different users, but the shares within the file system will all access common content.
    • A directory must exist before you can create shares on it. Therefore, if you want the SMB shares within the same file system to access different content, you must first create a directory on the Windows host that is mapped to the file system. Then, you can create corresponding shares using Unisphere. You can also create and manage SMB shares from the Microsoft Management Console.

    NFS shares

    • Each NFS share must have a unique local path. Unisphere automatically assigns this path to the initial share created within a new file system. The local path name is based on the file system name.
    • Before you can create additional shares within an NFS file system, you must create a directory to share from a Linux/UNIX host that is connected to the file system. Then, you can create a share from Unisphere and set access permissions accordingly.
    Export path
    The path used by the host to connect to the share. Unisphere creates the share export path based on the name of the share and the name of the file system where it resides. Hosts use either the file name or the export path to mount or map to the share from a network host.

    This behavior is enabled by using NFS aliases for shares.

    Create an SMB share

    Before you begin

    The file system or snapshot you choose as the share's source must be associated with a NAS server that supports the SMB protocol.

    Procedure
    1. Under Storage, select File > File Systems.
    2. Select the relevant file system, and then select More Actions > Create an SMB share (CIFS).
    3. On the File System page, specify whether the share is for the selected file system or for a snapshot of the selected file system.
    4. On the General page, enter the relevant information, noting the following:
      • The value specified in the Share Name field, along with the NAS server name, constitutes the name by which hosts access the share.
      • Share names must be unique at the NAS server level per protocol.
      • Local Path must correspond to an existing folder name within the file system that was created from the host-side.
    5. On the Advanced page, optionally configure advanced settings for the share.
    After you finish

    Once you create a share, you can modify it using the Microsoft Management Console. For information, see Configuring Hosts to Access SMB File Systems, which is available on the support website.

    Advanced SMB share properties

    You can configure the following advanced SMB share properties when you create an SMB share or change its properties:

    Option
    Description
    Continuous Availability
    Gives host applications transparent, continuous access to a share following a failover of the NAS server on the system (with the NAS server internal state saved or restored during the failover process).
    Enable continuous availability for a share only when you want to use Microsoft Server Message Block (SMB) 3.0 protocol clients with the specific share.
    Protocol Encryption
    Enables SMB encryption of the network traffic through the share. SMB encryption is supported by SMB 3.0 clients and above. By default, access is denied if an SMB 2 client attempts to access a share with protocol encryption enabled.

    You can control this by configuring the RejectUnencryptedAccess registry key on the NAS Server. 1 (default) rejects non-encrypted access and 0 allows clients that do not support encryption to access the file system without encryption.

    Access-Based Enumeration
    Filters the list of available files and directories on the share to include only those to which the requesting user has read access.
    Administrators can always list all files.
    Branch Cache Enabled
    Copies content from the share and caches it at branch offices. This allows client computers at branch offices to access the content locally rather than over the WAN.

    BranchCache is managed from Microsoft hosts.

    Distributed File System (DFS)
    (Read only) Lets you group files located on different shares by transparently connecting them to one or more DFS namespaces. This simplifies the process of moving data from one share to another. This option is read only in Unisphere because you manage DFS from Microsoft hosts. For information, see the MIcrosoft Distributed File System documentation.
    Offline Availability
    Configures the client-side caching of offline files:
    • Manual: Files are cached and available offline only when caching is explicitly requested.
    • Programs and files opened by users: All files that clients open from the share are automatically cached and available offline. Clients open these files from the share when they are connected to it. This option is recommended for files with shared work.
    • Programs and files opened by users, optimize for performance: All files that clients open from the share are automatically cached and available offline. Clients open these files from the share's local cache, if possible, even when they are connected to the network. This option is recommended for executable programs.
    • None: Client-side caching of offline files is not configured.
    UMASK
    (Applies to SMB shares of a file system that supports multiprotocol access with a Unix access policy or a Native access policy.) A Bitmask that shows which Unix permissions are excluded for files created on the share. The default permissions are:
    • 666 for files, which allows read and write permissions for all.
    • 777 for directories, which allows read, write, and execute permissions for all.

    If UMASK is set to 022, following permissions are granted:

    • 644 for files, which allows read and write permissions for the file owner, and read permission for everyone else.
    • 755 for directories, which allows read, write and execute permissions for directory owners, and read and execute permissions for everyone else.
    If NFSv4 ACL inheritance is present, it takes precedence over the UMASK setting,
    • To change the excluded permissions, click Modify, and then select or clear permissions.
    • To set the bitmask to the default value (022), click Set default. A value of 022 allows only you to write data, but lets anyone read data. For more information, see the Unix documentation.

    Create an NFS share

    Before you begin

    The file system or snapshot you choose as the share's source must be associated with a NAS server that supports the NFS protocol.

    Procedure
    1. Under Storage, select File > File Systems.
    2. Select the file system for which you want to add a share, and then select More Actions > Create an NFS share (NFS export).
    3. On the File System page, specify whether the share is for the selected file system or for a snapshot of the selected file system.
    4. On the Name & Path page, enter the relevant information, noting the following:
      • The value specified in the Share Name field, along with the NAS server name, constitutes the alias by which hosts can access the share.
      • Share names must be unique at the NAS server level per protocol. However, you can specify the same name for an SMB and NFS share.
      • Local Path must correspond to an existing folder name within the file system that was created from the host-side.
        A given file system path can only be shared once using the NFS protocol.
      • By default, users can set bit s in the execute portion of the owner or group permissions of a file. Users can then set the setuid and setgid Unix permission bits. This allows users to run the executable with the privileges of the file's owner (such as root). De-select Allow SUID if you do not want users to have this ability.
      • Optionally change the default anonymous UID and GID for the share. If the permission of a host is read-only or read-write (without allowing root access), and the UID of the client is 0 (which is typically the UID of the root account), then the UID is mapped to the anonymous UID on the NAS server. By default, the values of the anonymous UID and anonymous GID are 4294967294, which is typically associated with the nobody user.
    5. On the Access page, optionally specify the name of the hosts that can access the share, along with their access privileges. In the Default Access field, select the access setting you want all hosts to have for the share. In the Customize access for the following hosts section do either of the following:
      • Change the access privileges for existing hosts.
      • Add new hosts and specify individual access privileges for those hosts.