Administrator Guide

3. In the Summary tab navigation pane, select Edit NAS Pool Settings.
4. The Set NAS Pool Space Settings dialog box appears.
5. Enable or disable the NAS pool unused space alert.
• To enable the NAS pool used space alert, select the Unused Space Alert check box.
• To disable the NAS pool used space alert, clear the Unused Space Alert check box.
6. If the Unused Space Alert check box is enabled, in the Unused Space Threshold eld, type a number (from 0 to 100) to
specify the percentage of unused NAS pool space that triggers an alert.
7. Click OK.
Managing NAS Volumes
A NAS volume is a subset of the NAS pool in which you create SMB shares and/or NFS exports to make storage space available to
clients. NAS volumes have specic management policies controlling their space allocation, data protection, security style, and so on.
You can either create one large NAS volume consuming the entire NAS pool or divide the NAS pool into multiple NAS volumes. In
either case you can create, resize, or delete these NAS volumes.
NAS volume availability depends on the availability of the Storage Centers. If a Storage Center is oine, storage center LUNs will not
be available for the FluidFS cluster, and access to the shares and/or exports will be lost. Correct the Storage Center problem to
resume service.
The following NAS features can be congured on each NAS volume:
• File security styles
• Quota rules
• Data reduction
• Snapshots
• NDMP backup
• Replication
File Security Styles
The Windows and UNIX/Linux operating systems use dierent mechanisms for resource access control. Therefore, you assign each
NAS volume a le security style (NTFS, UNIX, or Mixed) that controls the type of access controls (permission and ownership) for
the les and directories that clients create in the NAS volume.
A NAS volume supports the following security styles:
• UNIX: Controls le access using UNIX permissions. A client can change permissions only by using the chmod and chown
commands on the NFS mount point.
• NTFS: Controls le access by Windows permissions. A client can change the permission and ownership using Windows (File
Properties → Security tab).
• Mixed: Supports both NTFS and UNIX security styles. If you choose this option, the default security of a le or directory is the
last one set. Permissions and access rights from one method to another are automatically translated. (For example, if a Windows
administrator sets up le access permissions on a le through an SMB share, a Linux user can access the le system through
NFS and change all the le permissions.) Therefore, this option is not recommended in production environments, except where
you are not concerned about le access security and just need some NAS volume space to store les temporarily.
Both NTFS and UNIX security styles allow multi-protocol le access. The security style only determines the method of storing and
managing the le access permissions information within the NAS volume.
If you need to access the same set of les from both Windows and UNIX or Linux, the best way to implement multi-protocol access
is by setting up individual user mapping rules or by enabling automatic user mapping. Ownership and access permissions are
automatically translated based on user mapping settings and le access credentials.
Modifying the le security style of a NAS volume aects only those les and directories created after the modication.
FluidFS NAS Volumes, Shares, and Exports
557