A protection domain (PD) is a group of nodes or storage data servers that provide data isolation, security, and performance benefits. A node participates in only one protection domain at a time. Only nodes in the same protection domain can affect each other, nodes outside the protection domain are isolated. Secure multi-tenancy can be created with protection domains since data does not mingle across protection domains. You can create different protection domains for different node types with unequal performance profiles. All the hosts in the domain must have the same type and configuration. A PowerFlex hyperconverged node should not be in the same protection domain as a PowerFlex storage-only node. The node configuration must match, which includes the drives, CPU, and memory. Any difference in the node configuration leads to an unknown performance impact.
Storage pools are a subset of physical storage devices in a protection domain. Each storage device belongs to one (and only one) storage pool. The best practice is to have the same type of storage devices (HDD versus SSD or SSD versus NVMe) within a storage pool to ensure that the volumes are distributed over the same type of storage within the protection domain.
PowerFlex supports two types of storage pools. You can choose between both layouts. A system can support both fine granularity (FG) and medium granularity (MG) pools on the same storage data server nodes. Volumes can be non-disruptively migrated between the two layouts. Within an fine granularity pool, you can enable or disable compression on a per-volume basis:
A fault set is a logical entity that contains a group of storage data servers within a protection domain that have a higher chance of going down together; for example, if they are all powered in the same rack. By grouping them into a fault set, PowerFlex mirrors data for a fault set on storage data servers that are outside the fault set. Thus, availability is assured even if all the servers within one fault set fail simultaneously.