Table of Contents
See how long your backups are kept, and confirm which backup sets use which retention rule.
In Asigra DS-Client, how long your data stays in online storage is controlled by two settings that work together. To understand your true retention, it helps to check both.
Passive · Automatic Maximum Generations Set per backup set. Caps how many versions of each file are kept online; the oldest is overwritten. On by default. | Active · Enforced Retention Rules Named rules you assign to a set. Keep, delete, or archive generations by age — but only when enforced. |
Maximum Generations caps the number of versions kept and runs automatically during backup. Retention Rules are optional, more flexible policies you assign to a set — but they only take effect when enforced. A set may use one, the other, or both.
| Good to knowEvery step below is read-only. You can review all of this without changing any setting or deleting any data. |
1. See Which Retention Rule a Backup Set Uses
Start here to answer “which backups have which rule.” The retention rule assigned to a backup set — along with its Maximum Generations — lives in that set’s properties.
1 | Open the DS-User console and connect to your DS-Client. |
2 | In the Backup Sets list, select the backup set you want to check. |
3 | Open Backup Set Properties (double-click the set, or right-click it and choose Properties). You can also right-click a set to view or change its assigned rule directly. |
4 | Find the Retention Rule assigned to the set. If no rule is listed, that set’s online retention is governed only by Maximum Generations (see below). |
5 | While you’re here, note the Maximum Generations value for the set’s items — this caps how many versions are kept regardless of any rule. |
6 | Repeat for each backup set to see the full picture of which set uses which rule. |
| What it tells youThis is the authoritative, per-set view: exactly which rule (if any) is assigned, and how many versions Maximum Generations allows. Checking each set builds your full retention map. |
2. See What a Retention Rule Actually Keeps
Use this to read the rule itself. Once you know which rule a set uses, open that rule to see exactly how long data is kept and what happens when it ages out.
1 | Open the DS-User console and connect to your DS-Client. |
2 | Open the Retention Rules list (in DS-User, from the Setup menu — the exact label can vary slightly by version). This lists every rule defined on this DS-Client. |
3 | Select a rule and open it (in the Retention Rule Wizard) to read its settings without changing anything. |
4 | Check Keep most recent generations — the number of newest versions always kept, exempt from retention. |
5 | Review the time-based tiers — for example, keep one generation per week for a month, then one per month for a year. |
6 | Check the Delete Options (for files removed from the source) and whether obsolete data is deleted or moved to BLM Archiver (long-term archive). |
7 | Close the wizard when done — viewing a rule doesn’t change it. |
| ImportantAssigning a rule doesn’t delete anything on its own. A retention rule only acts when the Enforce Retention process runs — on its schedule, or when run on demand. |
3. Retention Rules vs. Maximum Generations
The two mechanisms answer different questions. Maximum Generations asks “how many versions?” Retention Rules ask “kept for how long, and then what?”
| Maximum Generations | Retention Rules | |
|---|---|---|
| Type | Passive — happens automatically | Active — must be assigned and enforced |
| Where it’s set | In each backup set’s properties (a number, 1–9999) | Created in the Retention Rules list, then assigned to a set |
| What it does | Caps how many versions are kept; the oldest is overwritten | Keeps, deletes, or archives generations by age and tier |
| When it acts | During each backup | When the Enforce Retention process runs (scheduled or on-demand) |
| By default | On for every backup set | Only applies if you create a rule and assign it |
4. Good to Know
No rule assigned? If a backup set has no retention rule, its online retention is governed solely by Maximum Generations — the oldest version is simply overwritten once the set reaches its version limit. That’s the default behavior, and it’s worth confirming it matches your expectations.
- Backup and retention are separate processes — Maximum Generations acts during backup, retention acts during enforcement.
- If two-factor authentication is enabled on your DS-Client, only authorized users can assign or change a retention rule.
- If a rule is set to move obsolete data to BLM Archiver, aged-out data is archived for long-term retention rather than deleted.
| Not sure your retention matches your requirements?Retention settings protect you against everything from accidental deletion to compliance audits, so it’s worth getting them right. If anything looks off — or you’re not sure a set is covered the way you need — reach out to the CyberFortress team and we’ll review it with you. We’re The Recovery People, and this is exactly what we’re here for. |