Storage pool functions

When a cluster is installed, and whenever nodes are added to the cluster, OneFS automatically groups nodes into node pools. Autoprovisioning of nodes into node pools enables OneFS to optimize performance, reliability, and data protection on the cluster.

Without an active SmartPools license, OneFS applies a default file pool policy to organize all data into a single file pool. With this policy, OneFS distributes data across the entire cluster so that data is protected and readily accessible. When you activate a SmartPools license, additional functions become available.

OneFS provides the following functions, with or without an active SmartPools license:

Autoprovisioning of node pools
Automatically groups equivalence-class nodes into node pools for optimal storage efficiency and protection. At least three nodes of an equivalence class are required for autoprovisioning to work.
Node class compatibilities (node equivalency)
Enables certain nodes that are not equivalence-class to join existing node pools. OneFS supports node class compatibilities between Isilon S200 and S210 nodes, X200 and X210 nodes, X400 and X410 nodes, and NL400 and NL410 nodes. L3 cache must be enabled on the node pools for node class compatibilities to work.
SSD capacity compatibilities
Enables nodes with different SSD capacities to be provisioned to an existing compatible node pool. Otherwise, compatible nodes that have different SSD capacities cannot join the same node pool. If you have fewer than three nodes with differences in SSD capacity, these nodes remain unprovisioned, and, therefore, not functional. L3 cache must be enabled on node pools for SSD capacity compatibilities to work.
SSD count compatibilities
Enables nodes with different numbers of SSDs to be provisioned to the same node pool. Otherwise, compatible nodes that have different SSD counts cannot join the same node pool. If you have fewer than three nodes with a particular SSD count, these nodes remain unprovisioned, and, therefore, not functional until you create an SSD count compatibility. L3 cache must be enabled on node pools for SSD count compatibilities to work.
Tiers
Groups node pools into logical tiers of storage. If you activate a SmartPools license for this feature, you can create custom file pool policies and direct different file pools to appropriate storage tiers.
Default file pool policy
Governs all file types and can store files anywhere on the cluster. Custom file pool policies, which require a SmartPools license, take precedence over the default file pool policy.
Requested protection
Specifies a requested protection setting for the default file pool, per node pool, or even on individual files. You can leave the default setting in place, or choose the suggested protection calculated by OneFS for optimal data protection.
Virtual hot spare
Reserves a portion of available storage space for data repair in the event of a disk failure.
SSD strategies
Defines the type of data that is stored on SSDs in the cluster. For example, storing metadata for read/write acceleration.
L3 cache
Specifies that SSDs in nodes are used to increase cache memory and speed up file system performance across larger working file sets.
Global namespace acceleration
Activates global namespace acceleration (GNA), which enables data stored on node pools without SSDs to access SSDs elsewhere in the cluster to store extra metadata mirrors. Extra metadata mirrors accelerate metadata read operations.

When you activate a SmartPools license, OneFS provides the following additional functions:

Custom file pool policies
Creates custom file pool policies to identify different classes of files, and stores these file pools in logical storage tiers. For example, you can define a high-performance tier of Isilon S-series node pools and an archival tier of high-capacity Isilon NL400 and HD400 node pools. Then, with custom file pool policies, you can identify file pools based on matching criteria, and you can define actions to perform on these pools. For example, one file pool policy can identify all JPEG files older than a year and store them in an archival tier. Another policy can move all files that were created or modified within the last three months to a performance tier.
Storage pool spillover
Enables automated capacity overflow management for storage pools. Spillover defines how to handle write operations when a storage pool is not writable. If spillover is enabled, data is redirected to a specified storage pool. If spillover is disabled, new data writes fail and an error message is sent to the client that is attempting the write operation.