Enable site-loss protection
If your StorageGRID deployment includes more than one site, you can use replication and erasure coding with appropriately configured storage pools to enable site-loss protection.
Replication and erasure coding require different storage pool configurations:
-
To use replication for site-loss protection, use the site-specific storage pools that are automatically created during StorageGRID installation. Then create ILM rules with placement instructions that specify multiple storage pools so that one copy of each object will be placed at each site.
-
To use erasure coding for site-loss protection, create storage pools that consist of multiple sites. Then create ILM rules that use one storage pool consisting of multiple sites and any available erasure-coding schema.
When configuring your StorageGRID deployment for site-loss protection, you must also take into account the effects of ingest options and consistency. |
Replication example
By default, one storage pool is created for each site during StorageGRID installation. Having storage pools that consist of only one site enables you to configure ILM rules that use replication for site-loss protection. In this example:
-
Storage pool 1 contains Site 1
-
Storage pool 2 contains Site 2
-
The ILM rule contains two placements:
-
Store objects by replicating 1 copy at Site 1
-
Store objects by replicating 1 copy at Site 2
-
ILM rule placements:
If one site is lost, copies of the objects are available at the other site.
Erasure coding example
Having storage pools that consist of more than one site per storage pool enables you to configure ILM rules that use erasure coding for site-loss protection. In this example:
-
Storage pool 1 contains Sites 1 through 3
-
The ILM rule contains one placement: Store objects by erasure coding using a 4+2 EC scheme at Storage pool 1, which contains three sites
ILM rule placements:
In this example:
-
The ILM rule uses a 4+2 erasure-coding scheme.
-
Each object is sliced into four equal data fragments, and two parity fragments are computed from the object data.
-
Each of the six fragments is stored on a different node across three data center sites to provide data protection for node failures or site loss.
Erasure coding is allowed in storage pools containing any number of sites except two sites. |
ILM rule using 4+2 erasure-coding scheme:
If one site is lost, data can still be recovered: