permalink | sidebar | keywords | summary |
---|---|---|---|
ilm/example-3-ilm-rules-and-policy-for-better-protection-for-image-files.html |
sidebar |
example ILM rule, information lifecycle rule examples |
You can use the following example rules and policy to ensure that images greater than 1 MB are erasure-coded and that two copies are made of smaller images. |
You can use the following example rules and policy to ensure that images greater than 1 MB are erasure-coded and that two copies are made of smaller images.
Caution
|
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. |
This example ILM rule uses advanced filtering to erasure code all image files greater than 1 MB.
Note
|
Erasure coding is best suited for objects greater than 1 MB. Don’t use erasure coding for objects smaller than 200 KB to avoid the overhead of managing very small erasure-coded fragments. |
Rule definition | Example value |
---|---|
Rule name |
EC Image Files > 1 MB |
Reference time |
Ingest time |
Advanced filter for Object size |
Object size greater than 1 MB |
Advanced filters for Key |
|
Placements |
Create a 2+1 erasure-coded copy using three sites |
Because this rule is configured as the first rule in the policy, the erasure-coding placement instruction only applies to .jpg and .png files that are greater than 1 MB.
This example ILM rule uses advanced filtering to specify that smaller image files be replicated. Because the first rule in the policy has already matched image files greater than 1 MB, this rule applies to image files that are 1 MB or smaller.
Rule definition | Example value |
---|---|
Rule name |
2 Copies for Image Files |
Reference time |
Ingest time |
Advanced filters for Key |
|
Placements |
Create 2 replicated copies in two storage pools |