Home > Storage > PowerScale (Isilon) > Product Documentation > Cloud > Introduction to APEX File Storage for Azure > Supported cluster configurations
When setting up a new cluster, it is important to consider the type of storage configuration that is supported. Different configurations fulfill different requirements, depending on the intended use and the amount of data that needs to be stored. In general, a supported cluster configuration should be reliable, performant and offer enough storage capacity to meet your needs.
For a single cluster of APEX File Storage for Microsoft Azure, all nodes in the cluster must use the same configuration, including Azure VM size, Azure managed disk type, and Azure managed disk size.
Table 1 shows the supported configuration for a OneFS cluster in Azure.
Supported options | |
Cluster size | 4 to 18 nodes |
Azure VM size | All nodes in a cluster must use the same VM size. The supported VM sizes are:
|
Azure managed disk type | All nodes in a cluster muse use the same disk type. The supported disk types are:
Note: Premium SSDs are only supported with Ddsv5-series and Edsv5-series |
Azure managed disk size | All nodes in a cluster muse use the same disk size. The supported disk sizes are:
|
Disk count per node | All nodes in a cluster muse use the same disk count. The supported disk counts are:
|
Cluster raw capacity | Minimum: 10 TiB, maximum: 5760 TiB |
Cluster protection level | Default is +2n. Also supports +2d:1n with additional capacity restrictions. Refer to section OneFS protection level. |
Note: all criteria in this table must be met. Therefore, when using 16 TiB disk size, not all combinations of cluster size, disk count, and disk size are supported. For some combinations of cluster size, disk count, and disk size, the total cluster raw capacity may fall outside the maximum supported cluster raw capacity. For example, for an 18-nodes cluster, if each node contains 25 disks, and each disk size is P70 (16 TiB), the final total cluster raw capacity is 7200 TiB which exceeds the maximum supported raw capacity. Therefore, this combination is not supported.
See Appendix A: supported cluster configuration details for all supported combinations.