Administrator Guide

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.
Example 3
NAS volumes can be created based on a feature (snapshots, replication, NDMP backup, and so on).
• Advantages – The NAS volumes are created to match the exact needs for each feature.
• Disadvantage – User mapping is required. A user needs to choose one security style (either NTFS or UNIX) and then, based on the
security style chosen, the correct mapping for other users is set.
FluidFS Administration
413