Step 2 of 3: Define placements

Step 2 of the Create ILM Rule wizard allows you to define the placement instructions that determine how long objects are stored, the type of copies (replicated or erasure coded), the storage location, and the number of copies.

About this task

An ILM rule can include one or more placement instructions. Each placement instruction applies to a single period of time. When you use more than one instruction, the time periods must be contiguous, and at least one instruction must start on day 0. The instructions can continue either forever, or until you no longer require any object copies.

Each placement instruction can have multiple lines if you want to create different types of copies or use different locations during that time period.


Create ILM Rule Wizard Page 2

Steps

  1. For Reference Time, select the type of time to use when calculating the start time for a placement instruction.
    Option Description
    Ingest Time The time when the object was ingested.
    Last Access Time The time when the object was last retrieved (read or viewed).
    Note: To use this option, updates to Last Access Time must be enabled for the S3 bucket or Swift container.
    Noncurrent Time The time an object version became noncurrent because a new version was ingested and replaced it as the current version.
    Note: Noncurrent Time applies only to S3 objects in versioning-enabled buckets.

    You can use this option to reduce the storage impact of versioned objects by filtering for noncurrent object versions. See "Example 4: ILM rules and policy for S3 versioned objects."

    User Defined Creation Time A time specified in user-defined metadata.
    Note: If you want to create a compliant rule, you must select Ingest Time.
  2. In the Placements section, select a starting time and a duration for the first time period.
    For example, you might want to specify where to store objects for the first year ("day 0 for 365 days"). At least one instruction must start at day 0.
  3. If you want to create replicated copies on one or more storage pools:
    1. From the Type drop-down list, select replicated.
    2. In the Location field, optionally click Add Pool. Then, select one or more storage pools.
      If you are specifying more than one storage pool, keep these rules in mind:
      • If you are specifying more than one storage pool and creating n copies, you must add n or more pools. For example, if you plan to specify three copies, you must specify three or more storage pools.
      • If the number of copies equals the number of storage pools, one copy of the object is stored in each storage pool.
      • If the number of copies is less than the number of storage pools, the system distributes the copies to keep disk usage among the pools balanced, while ensuring that one copy goes only to one site.
      • If the storage pools overlap (contain the same Storage Nodes), all copies of the object might be saved at only one site. For this reason, do not specify the default storage pool (All Storage Nodes) and another storage pool.

      Placement instructions for multiple storage pools
    3. Select the number of copies you want to make.
      Attention: A warning appears if you change the number of copies to 1. An ILM rule that creates only one replicated copy for any time period puts data at risk of permanent loss. If only one replicated copy of an object exists during a time period, that object is lost if a Storage Node fails or has a significant error. You also temporarily lose access to the object during maintenance procedures such as upgrades.
      Create ILM Rule Page 2 Warning for 1 Copy
      To avoid these risks, do one or more of the following:
      • Increase the number of copies for the time period.
      • Click the plus sign icon plus sign black on white or Add to create additional copies during the time period. Then, select a different storage pool or a Cloud Storage Pool.
      • Select erasure coded for Type, instead of replicated.
      You can safely ignore this warning if this rule already creates multiple copies for all time periods.
      Note: StorageGRID can store only one replicated copy of an object on any given Storage Node. If your grid includes three Storage Nodes and you select 4 as the number of copies, be aware that only three copies will be made—one copy for each Storage Node.
    4. If you are using a single storage pool, do not specify a temporary location.
      Note: Temporary locations are deprecated and will be removed in an upcoming release.
      • Existing rules that use a temporary location will continue to work as before.
      • If you select the Strict ingest behavior (on the next page of the wizard), the temporary location is not used.
  4. If you want to store objects in a Cloud Storage Pool:
    1. From the Type drop-down list, select replicated.
    2. In the Location field, remove All Storage Nodes, and click Add Pool. Then, select a Cloud Storage Pool.

      Adding a Cloud Storage Pool to a placement instruction
      When using Cloud Storage Pools, keep these rules in mind:
      • You cannot store an object in more than one Cloud Storage Pool at one time. An error message appears if you select more than one Cloud Storage Pool for any given time period.
        ILM rule > Cloud Storage Pool error
      • You can store only one copy of an object in any given Cloud Storage Pool. An error message appears if you set Copies to 2 or more.
        ILM rule: Cloud Storage Pool error if more than one copy
      • You can store an object in a Cloud Storage Pool at the same time that object is being stored as replicated or erasure coded copies in StorageGRID; however, as shown in this example, you must add a line to the instruction for each location, so you can specify the number and types of copies you want.
        ILM rule > Cloud Storage Pool and other location
  5. If you want to create an erasure-coded copy:
    1. From the Type drop-down list, select erasure coded.
      The number of copies changes to 1.
    2. Select the storage location.
      The storage locations for an erasure-coded copy include the name of the storage pool, followed by the name of the Erasure Coding profile.


      Storage pool and EC profile name

      Attention: When adding a rule that makes an erasure-coded copy to the ILM policy, you must ensure that the policy has at least one rule that filters by Object Size. Due to the overhead of managing the number of fragments associated with an erasure-coded copy, do not erasure code objects smaller than 200 KB.
  6. Optionally, add different time periods or create additional copies at different locations:
    • Click the plus icon to create additional copies at a different location during the same time period.
    • Click Add to add a different time period to the placement instructions.
      Note: Objects are automatically deleted at the end of the final time period unless the final time period ends with forever.
  7. Click Refresh to update the Retention Diagram and to confirm your placement instructions.
    Each line in the diagram shows where and when object copies will be placed. The type of copy is represented by one of the following icons:
    • Icon for replicated copiesReplicated copy
    • Icon for erasure coded copyErasure-coded copy
    • Cloud Storage Pool icon Cloud Storage Pool copy
    In this example, three replicated copies will be saved to three storage pools (DC1, DC2, and DC3) for one year. Then, an erasure-coded copy will be saved for an additional 10 years, using a 6+3 erasure-coding scheme. After 11 years, the objects will be deleted from StorageGRID.


    Retention diagram

  8. Click Next.
    Step 3 of the Create ILM Rule wizard appears. You use the Define ingest behavior page to choose how objects are protected as they are ingested.