Administrator Guide

– A single NAS volume can contain NFS exports, SMB shares, or a combination of NFS exports and SMB shares.
– The minimum size of a NAS volume is 20 MB. (If the volume has already been used, the minimum size should be more than
the used space or reserved space, whichever is highest.)
• Business requirements – A company or application requirement for separation or for using a single NAS volume must be
considered. NAS volumes can be used to allocate storage for departments on demand, using the threshold mechanism to notify
administrators when they approach the end of their allocated free space.
• Data reduction – Each NAS volume can have a dedicated data reduction policy to best suit the type of data it stores.
• Snapshots – Each NAS volume can have a dedicated snapshot scheduling policy to best protect the type of data it stores.
• Security style – In multiple-protocol environments, it might be benecial to separate the data and dene NAS volumes with
UNIX security style for UNIX/Linux-based clients and NTFS security style for Windows-based clients. This separation enables
the administrator to match the security style with business requirements and various data access patterns. The security style can
also be set to Mixed, which supports both POSIX security and Windows ACLs on the same NAS volume. When a NAS volume is
created, the default le permissions is set to Windows. The settings should be edited immediately after the NAS volume has been
created.
• Quotas – Dierent quota policies can be applied to dierent NAS volumes, allowing the administrator to focus on managing
quotas when it is appropriate.
• Replication schedules – Dierent volumes can have dierent replication schedules and policies.
• Auditing SACL SMB Access – Dierent volumes can have dierent policies for handling the auditing of SACL SMB accesses.
Examples of NAS Volume Creation
This section includes examples that show how NAS volumes can be created to meet the needs of an organization with the
departments and NAS volume requirements described in the following table.
Department Security
Style
Snapshots Replication NDMP
Backup
Number of
SMB/NFS
Clients
Read/Write
Mix
Hourly
Change % of
Existing Data
Post
Production
UNIX Hourly No Weekly 20 20/80 1%
Administration
and Finance
NTFS No No Weekly 10 50/50 None
Broadcast Mixed No No Weekly 10 90/10 None
Press NTFS Daily No No 5 10/90 5%
Marketing NTFS Daily Yes No 5 50/50 None
An average read/write mix is 20/80. An average hourly change rate for existing data is less than 1 percent.
Example 1
Create NAS volumes based on departments. The administrator breaks up storage and management into functional groups. In this
example, the departmental requirements are dierent and support the design to create NAS volumes along department lines.
• Advantages
– The NAS volumes are easier to manage because they are set up logically.
– The NAS volumes are created to match the exact needs of the department.
• Disadvantage – The NAS volumes become harder to manage if the number of departments in the organization increases.
Example 2
Group departments that have similar security requirements into NAS volumes. The administrator creates three NAS volumes: one for
UNIX, one for NTFS, and one for mixed.
• Advantages – The NAS volumes work separately between Windows and Linux.
• Disadvantage – Unwanted services could be provided to certain departments. For example, when the SMB volume is backed up
weekly for the administration and nance departments, the press and marketing departments also get backups even though
they do not require them.
FluidFS NAS Volumes, Shares, and Exports
401