Storage and performance requirements

You must ensure that each Storage Node hosted by a virtual machine has enough space to support the initial configuration and future storage expansion.

Note: You cannot change the size of the storage volumes used by StorageGRID Webscale appliances.

When assigning space to virtual machine Storage Nodes, keep in mind that StorageGRID Webscale reserves 2 TB of space on each Storage Node for the Cassandra database. This database stores all object metadata as well as certain configuration data. Cassandra data is stored on the first storage volume (also known as RangeDB 0 or object store 0) of each Storage Node. Any additional capacity in this volume is used for object storage.

If you are using only one storage volume for each Storage Node, you must assign it at least 4 TB of space.
Note: If you are using only one storage volume on the Storage Node and you assign 2 TB or less to that volume, the Storage Node immediately enters the Storage Read-Only state on startup and stores object metadata only.
If you are using more than one storage volume for each Storage Node, you must assign at least 2 TB to object store 0; however, 4 TB is recommended. Using 4 TB ensures that the Storage Node has adequate capacity for object metadata and that object store 0 can also be used for object data.

The performance of the OS volume and of the first storage volume significantly impacts the overall performance of the system. Ensure that these provide adequate disk performance in terms of latency, input/output operations per second (IOPS), and throughput. Refer to documentation related to performance sizing.

All StorageGRID Webscale nodes require that the OS drive and all storage volumes have write-back caching enabled. The cache must be on a protected or persistent media.