Skip to main content

Retention

You can inject the data retention policy through a strategy.

KeyParameterControl
Configuration.Node.Retention\[at <path>] after <value> (days | weeks) keep ((every <value> (hours|days|weeks))|none)

The possible values for these keys are:

  • \[at <path>]: optional parameter. If specified, indicates the path from which to apply retention. If not specified, retention is applied at the account root.
  • value: numeric value used to specify the start of the period (for the first value) and the retention frequency (for the second value).
  • time units:
    • hours: hours
    • days: days
    • weeks: weeks
    • none: no retention limit

Important Note​

Please refer to the Data Retention section for a detailed explanation of the data retention model.

Example​

You want to apply a linear retention of 60 days on your backup account and a progressive retention over 12 weeks on your D: drive according to the following model:

  • After 1 week, keep one version per week
  • After 4 weeks, keep one version every 4 weeks
  • After 12 weeks, keep no history

Resulting strategy:

    Configuration.Node.Retention : after 60 days keep none
    Configuration.Node.Retention : at D: after 1 week keep every 1 week
    Configuration.Node.Retention : at D: after 4 weeks keep every 4 weeks
    Configuration.Node.Retention : at D: after 12 weeks keep none