Sizing Guidelines for HyperScale X

HyperScale X sizing can be simplified using the following steps:

Estimate the backend capacity required at each location
Decide on a deployment model - Appliance or Reference Architecture
Decide the node type (N4, N12 or N24)
Determine the number of nodes required based on capacity

All nodes come fully-populated with disks (HDD’s) and have appropriate compute resources to meet or exceed resilience and performance needs. The modular nature of the architecture allows for easy scaling of capacity with performance, as the data needs grow.

Initial storage pool creation requires a minimum of 3 similarly configured HyperScale X nodes. (This is also referred to as a block.) Subsequent expansion of a pool can take place by adding any number of nodes. Appliances are sold based on backend usable capacity.

The following capacity points are available for HyperScale X Appliances and/or supported for HyperScale X Reference Architecture:

Appliance or Node Type	Drive Size	Drives per Node	Initial Block Capacity (TiB)*	Individual Node Capacity (TiB)**
N4	4	4	25	8
N4	8	4	50	17
N4	12	4	74	25
N4	14	4	88	29
N4	20	4	124	41
N12	8	12	151	50
N12	10	12	189	63
N12	12	12	226	75
N12	14	12	264	88
N12	16	12	300	100
N12	18	12	339	113
N12	20	12	372	124
N24	8	24	302	101
N24	10	24	377	126
N24	12	24	453	151
N24	14	24	528	176
N24	16	24	604	201
N24	18	24	678	226
N24	20	24	745	248

* Initial storage pool creation requires a minimum of 3 similarly configured HyperScale X nodes. ** Expand Storage Pool by adding one or more nodes

Note

All HyperScale X nodes are to be fully populated with drives (HDD's). Servers with less than a full compliment of disks (HDD's) are not supported.
For example, an N4 type server needs to have 4x LFF HDD's, N12 type server needs to have 12x LFF HDD's and N24 type server needs to have 24x LFF HDD's.