Example 1: ILM rules and policy for object storage
You can use the following example rules and policy as a starting point when defining an ILM policy to meet your object protection and retention requirements.
The following ILM rules and policy are only examples. There are many ways to configure ILM rules. Before activating a new policy, simulate it to confirm it will work as intended to protect content from loss. |
ILM rule 1 for example 1: Copy object data to two sites
This example ILM rule copies object data to storage pools in two sites.
Rule definition | Example value |
---|---|
One-site storage pools |
Two storage pools, each containing different sites, named Site 1 and Site 2. |
Rule name |
Two Copies Two Sites |
Reference time |
Ingest time |
Placements |
On Day 0 to forever, keep one replicated copy at Site 1 and one replicated copy at Site 2. |
The Rule analysis section of the Retention diagram states:
-
StorageGRID site-loss protection will apply for the duration of this rule.
-
Objects processed by this rule will not be deleted by ILM.
ILM rule 2 for example 1: Erasure-coding profile with bucket matching
This example ILM rule uses an erasure-coding profile and an S3 bucket to determine where and how long the object is stored.
Rule definition | Example value |
---|---|
Storage pool with multiple sites |
|
Rule name |
S3 Bucket finance-records |
Reference time |
Ingest time |
Placements |
For objects in the S3 bucket named finance-records, create one erasure-coded copy in the pool specified by the erasure-coding profile. Keep this copy forever. |
ILM policy for example 1
In practice, most ILM policies are simple, even though the StorageGRID system allows you to design sophisticated and complex ILM policies.
A typical ILM policy for a multi-site grid might include ILM rules such as the following:
-
At ingest, store all objects belonging to the S3 bucket named
finance-records
in a storage pool that contains three sites. Use 6+3 erasure coding. -
If an object does not match the first ILM rule, use the policy's default ILM rule, Two Copies Two Data Centers, to store one copy of that object in Site 1, and one copy in Site 2.