English
  • Data Archive 6.4.3
  • All Products

Table of Contents

Search

  1. Version 6.4.3
  2. Version 6.4 HotFix 2
  3. Version 6.4 HotFix 1
  4. Version 6.4
  5. Version 6.3
  6. Version 6.2 Hot Fix 2
  7. Version 6.2 Hot Fix 1
  8. Version 6.2
  9. Version 6.1.1
  10. Version 6.1

Release Guide

Release Guide

Back Next

Retention Policies

Retention Policies

Effective in version 6.1, the performance and scalability of applying retention policies have been improved in the following ways:
  • You can resume the application of a retention policy from the point of failure.
    Previously, when you resumed the application of a retention policy, the job restarted.
  • The query construction for a retention policy is optimized. Child tables have a metadata column, either a tag or legal-hold column, that gets populated with the attribute applied to the parent. This allows the query to construct a join of just the child and immediate parent.
    Previously, the query constructed a join that included the child, immediate parent, grandparent, and beyond. This strategy did not successfully scale to more than seven to eight levels.
Applying a retention policy at the application level and unrelated-entity level does not depend on the relationship between tables. Because of this, any relation-based search or navigation on unrelated entities is not supported.