Demo Mode: you're exploring a live BackupMGR panel with sample data. Everything is read-only. Get BackupMGR →
BackupMGR Demo

Demo Admin

demo@scriptgain.com

Admin
Settings Users & Admins Audit Log

Maintenance

Repository pruning and kopia maintenance windows.

Run Now

Apply retention and reclaim space on demand, without waiting for the next backup.

Repository Director Agent Actions
b2-offsite 3 jobs director-usw1 Agent 1.4.1
minio-euc1 3 jobs director-euc1 Agent 1.4.1
sftp-apse1 3 jobs director-apse1 Agent 1.4.1
wasabi-use1 3 jobs director-use1 Agent 1.4.1

Retention counts come from each job's retention policy. Pruning expires snapshots; the freed space is returned to the filesystem by maintenance, so Prune + Maintain is the pass that shrinks a repository on disk.

Prune This Repository?

Applies each job's retention policy to "b2-offsite" and deletes the snapshots that fall outside it. Deleted snapshots cannot be restored.

Run Repository Maintenance?

Runs kopia full maintenance on "b2-offsite": compaction and garbage collection, which reclaim the space already freed by expired snapshots. Nothing is deleted, but it can take a while on a large repository.

Prune And Maintain?

Applies retention to "b2-offsite", deletes the expired snapshots, then compacts and garbage-collects the repository. This is the pass that shrinks it on disk. Deleted snapshots cannot be restored.

Prune This Repository?

Applies each job's retention policy to "minio-euc1" and deletes the snapshots that fall outside it. Deleted snapshots cannot be restored.

Run Repository Maintenance?

Runs kopia full maintenance on "minio-euc1": compaction and garbage collection, which reclaim the space already freed by expired snapshots. Nothing is deleted, but it can take a while on a large repository.

Prune And Maintain?

Applies retention to "minio-euc1", deletes the expired snapshots, then compacts and garbage-collects the repository. This is the pass that shrinks it on disk. Deleted snapshots cannot be restored.

Prune This Repository?

Applies each job's retention policy to "sftp-apse1" and deletes the snapshots that fall outside it. Deleted snapshots cannot be restored.

Run Repository Maintenance?

Runs kopia full maintenance on "sftp-apse1": compaction and garbage collection, which reclaim the space already freed by expired snapshots. Nothing is deleted, but it can take a while on a large repository.

Prune And Maintain?

Applies retention to "sftp-apse1", deletes the expired snapshots, then compacts and garbage-collects the repository. This is the pass that shrinks it on disk. Deleted snapshots cannot be restored.

Prune This Repository?

Applies each job's retention policy to "wasabi-use1" and deletes the snapshots that fall outside it. Deleted snapshots cannot be restored.

Run Repository Maintenance?

Runs kopia full maintenance on "wasabi-use1": compaction and garbage collection, which reclaim the space already freed by expired snapshots. Nothing is deleted, but it can take a while on a large repository.

Prune And Maintain?

Applies retention to "wasabi-use1", deletes the expired snapshots, then compacts and garbage-collects the repository. This is the pass that shrinks it on disk. Deleted snapshots cannot be restored.

Automatic Maintenance

Compaction and garbage collection that reclaim space in kopia repositories.

Maintenance Window

Confine maintenance to off-peak hours so it never competes with production load.

Local time in UTC.

A window that ends before it starts wraps past midnight.

Days Maintenance May Run

Repository Pruning

Apply retention and expire old snapshots to keep repositories from growing without bound.

Retention counts (keep latest / daily / weekly / monthly) come from each job's retention policy. A post-backup prune only expires snapshots that share a kopia source, so it cannot retire ones recorded under a one-off source. Scheduled pruning below is the pass that can.

Scheduled Pruning

A prune pass on its own cron, independent of when backups run.

Cron expression in UTC. Maintenance is folded into the pass whenever the window above allows it.

Jobs With Their Own Prune Schedule

None. Give a job its own schedule on its Schedule tab to prune its repository more often than the fleet; a job schedule fires even when the toggle above is off.

Status

Right Now
Maintenance Allowed
Next Prune
Not Scheduled
Server Time
6:36 AM UTC
Repositories
4

Agents evaluate the window each time they check in; a backup that finishes outside the window skips maintenance until the next in-window run.