Advantages, disadvantages, and limitations of the data-protection options

Each of the three options for protecting data at ingest (Balanced, Strict, or Dual commit) is suitable in some circumstances. Understanding the advantages and disadvantages of each method can help you decide which one to select for an ILM rule.

Summary of advantages, disadvantages, and limitations of all options

The table gives a quick summary of the advantages, disadvantages, and limitations of the different options for protecting object data at ingest. The following sections provide more information about each item.
Option Advantages Disadvantages Limitations

Balanced

(default)
  • Recommended for single site grids due to performance improvements
  • Better data security
  • More efficient grid operation
  • Slower ingest in multi-site grids
Cannot be used for these object placements:
  • Cloud Storage Pool at day 0
  • Archive Node at day 0
  • Placement in a Cloud Storage Pool or Archive Node when the rule uses a User Defined Creation Time as a Reference Time
Strict
  • Certainty of object locations
  • Better data security
  • More efficient grid operation
  • More ingest failures
  • Slower ingest
  • For S3 multipart uploads, placements might not be as expected in some circumstances
  • Ingest does not fail if object tags or user metadata are updated and newly-required placements cannot be made
  • For erasure-coded objects, Strict should only be used in specified configurations
Cannot be used for these object placements:
  • Cloud Storage Pool at day 0
  • Archive Node at day 0
  • Placement in a Cloud Storage Pool or Archive Node when the rule uses a User Defined Creation Time as a Reference Time
Dual commit
  • Faster ingest
  • High rate of ingest success
  • Can be used with all types of ILM placements
  • Data protection is limited to protection against the loss of a single local copy
  • Less efficient grid operation
  • Less certainty as to object locations
None

Advantages of the Balanced and Strict options

When compared to Dual commit, which creates interim copies during ingest, these options can provide the following advantages:

Disadvantages of the Balanced and Strict options

When compared to Dual commit, the Balanced and Strict options offer some disadvantages:

Limitations on object placements with the Balanced or Strict options

Limitations and recommendations for using the Strict or Balanced options with erasure-coded objects

Advantages of using Dual commit

When compared to the Balanced or Strict options, Dual commit offers the following advantages: