Manage recovery point retention

Product Zbix CRM · Version 1.2.0 · Source reviewed · Reviewed 28 October 2026
Audience Administrators and implementation teams · Deployment Release specific self hosted

Overview

Retention uses the daily, weekly and monthly counts attached to a backup schedule. After successful integrity verification, the worker evaluates usable artifacts by day, week and month and records keep/delete decisions. Retention is not a substitute for off-host custody or restore testing.

Purpose

Control local storage growth while preserving usable recovery history and respecting immutable destinations.

Prerequisites

• An approved business retention policy and a storage owner.

• A schedule with reviewed daily/weekly/monthly retention counts.

• At least one independently verified and restore-tested recovery point.

Procedure

1. Determine how far back the business needs to recover and how many daily, weekly and monthly points it can store. Keep statutory or contractual retention requirements separate from unsupported compliance claims.

2. Enter the approved counts in Schedules and save the configuration. Review capacity before enabling a new cadence or increasing retention.

3. After a scheduled point is created and independently verified, review the resulting history and storage use. Retention operates on usable catalogued artifacts, not on arbitrary files in a directory.

4. Confirm that the newest usable point and artifacts involved in active verification or restore work remain protected.

5. Coordinate remote-object lifecycle and immutability with the storage provider. Do not assume the application will delete remote artifacts according to the same local policy.

6. Investigate cleanup failures before storage fills. Preserve the decision history and resolve the underlying permission or storage problem rather than deleting files outside the managed process.

Expected result

Storage growth follows the approved policy while protected usable points and active recovery work are retained.

Important notes

• The retention grouping uses UTC day, ISO week and month buckets, even when the schedule is expressed in a local timezone.

• The newest usable recovery point, active verification/restore jobs and immutable destinations are protected.

• Application deletion is limited to catalogued local objects under the managed destination. Remote deletion remains provider controlled.

• A backup retained for a long period still depends on recoverable keys and a compatible tested recovery process.

Troubleshooting

• If disk use does not fall after a retention change, check immutability, active jobs, artifact usability and cleanup-failed status.

• If no recent verified point exists, restore the backup/verification process before reducing retention.

• Escalate storage pressure with current capacity, policy and failed operation details. Do not remove the newest usable point as an emergency shortcut.

Related articles

• Schedule recurring recovery points

• Configure and validate backup storage

• Verify a recovery point independently

• Plan capacity for CRM workloads