You must understand the storage requirements for StorageGRID nodes, so you can provide the appropriate type and amount of storage for each host.
You must use RAID-backed block devices for all storage categories. Non-redundant disks, SSDs, or JBODs are not supported. You can use shared or local RAID storage for any of the storage categories; however, if you want to use StorageGRID’s node migration capability, you must store both system metadata and object data on shared storage.
The performance of the volumes used for the container pool, system metadata, and object metadata significantly impacts the overall performance of the system. You should use performance-tier (10K SAS or SSD) storage for these volumes to ensure adequate disk performance in terms of latency, input/output operations per second (IOPS), and throughput. You can use capacity-tier (NL-SAS/SATA) storage for the persistent storage of object data.
The volumes used for the container pool, system metadata, and object data must have write-back caching enabled. The cache must be on a protected or persistent media.
Other types of nodes, such as Admin Nodes or Gateway Nodes, can be deployed on the same host, or they can be deployed on their own dedicated hosts as required. However, if you have multiple nodes of the same type (two Gateway Nodes, for example), do not install all instances on the same host.
The following table shows the number of storage volumes (LUNs) required for each host and the minimum size required for each LUN, based on which nodes will be deployed on that host.
The maximum tested LUN size is 39 TB.
| LUN purpose | Storage category | Number of LUNs | Minimum size/LUN |
|---|---|---|---|
| Docker storage pool | Container pool | 1 | Total number of nodes × 100 GB |
| /var/local volume | System metadata | 1 for each node on this host | 90 GB |
| Storage Node | Object data | 3 for each Storage Node on this host Note: A Storage Node can have 1 to 16 storage volumes; at least 3 storage volumes are recommended.
|
4,000 GB |
| Admin Node audit logs | System metadata | 1 for each Admin Node on this host | 200 GB |
| Admin Node tables | System metadata | 1 for each Admin Node on this host | 200 GB |
The following table shows the minimum storage space required for each type of node. You can use this table to determine the minimum amount of storage you must provide to the host in each storage category, based on which nodes will be deployed on that host.
| Type of node | Container pool | System metadata | Object data |
|---|---|---|---|
| Storage Node | 100 GB | 90 GB | 4,000 GB |
| Admin Node | 100 GB | 490 GB (3 LUNs) | not applicable |
| API Gateway Node | 100 GB | 90 GB | not applicable |
| Archive Node | 100 GB | 90 GB | not applicable |
| Type of node | LUN purpose | Number of LUNs | LUN size |
|---|---|---|---|
| Docker storage pool | 1 | 300 GB (100 GB/node) | |
| Storage Node | /var/local volume | 1 | 90 GB |
| Object data | 3 | 4,000 GB | |
| Admin Node | /var/local volume | 1 | 90 GB |
| Admin Node audit logs | 1 | 200 GB | |
| Admin Node tables | 1 | 200 GB | |
| API Gateway Node | /var/local volume | 1 | 90 GB |
| Total | 9 | Container pool: 300 GB System metadata: 670 GB Object data: 12,000 GB |
A Storage Node can have 1 to 16 storage volumes; however, 3 or more storage volumes are recommended. Each storage volume should be 4 TB or larger.
Note that you must assign at least 3 TB to volume 0. This requirement is because StorageGRID reserves 3 TB of space on first storage volume (volume 0) of each Storage Node. The Metadata Reserved Space (CAWM) is required for object metadata and for essential database operations, such as compaction and repair.
If you assign additional space to volume 0, that space will be used for object storage. Assigning 4 TB or more to volume 0 is recommended.