Storage requirements

You must understand the storage requirements for StorageGRID Webscale nodes, so you can provide the appropriate type and amount of storage for each host.

StorageGRID Webscale nodes require three logical categories of storage:

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 Webscale’s node migration capability, you must store both system metadata and object data on shared storage.

Performance requirements

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.

Number of hosts required

Each StorageGRID Webscale site requires a minimum of three Storage Nodes. As a best practice in a production deployment, you should run only one Storage Node on a physical or virtual host. This practice allows each Storage Node to be in its own isolated failure domain.

Other types of nodes, such as Admin Nodes or API Gateway Nodes, can be deployed on the same three hosts, or they can be deployed on their own dedicated hosts as required.

Number of storage volumes for each 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.

Note: These numbers are for each host, not for the entire grid.
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

Storage requirements for Storage Nodes

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

Minimum storage space for a host

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

Example: Calculating the storage requirements for a host

Suppose you plan to deploy three nodes on the same host: one Storage Node, one Admin Node, and one API Gateway Node. You should provide a minimum of nine storage volumes to the host. You will need a minimum of 300 GB of performance-tier storage for the node containers, 670 GB of performance-tier storage for system metadata and transaction logs, and 12 TB of capacity-tier storage for object data.
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

Storage requirements for Storage Nodes

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 Webscale 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.

Note: If you use only one storage volume for a Storage Node and you assign 3 TB or less to the volume, the Storage Node immediately enters the Storage Read-Only state on startup and stores object metadata only.
Note: If you assign less than 500 GB to volume 0 (non-production use only), 10% of the storage volume's capacity will be reserved for metadata.