Skip to main content

warrantor-backup

File-level backup and disaster-recovery coordinator for AumOS. Coordinates backups of AumOS state: signed evidence stores (E1), attestation ledgers, AAE policy snapshots, RBAC role bindings, SLA target configs.

Each BackupTarget names:

  • name — human-readable identifier.
  • path — absolute source path (file or directory) to back up.
  • backup_path — directory where timestamped backup copies land.
  • retention_days — backups older than this are pruned.
  • frequency_hours — advisory cadence for external schedulers.

Properties

  • Content-addressed: each backup's filename embeds the first 8 hex chars of the SHA-256 of the backup content. run_backup is idempotent — the same source at the same timestamp produces the same backup path.
  • Verified restores: by default, restore recomputes the SHA-256 of the backup and matches it against the digest encoded in the filename, failing fast on tampering.
  • Atomic-ish writes: a copy lands in a .partial directory first and is renamed into place only after the digest is computed, so partial copies are never exposed under their final name.
  • Pluggable retention: prune_expired deletes backups older than each target's retention_days.

Usage

from warrantor_backup import BackupManager, BackupTarget

mgr = BackupManager()
mgr.add_target(
    BackupTarget(
        name="evidence",
        path="/var/aumos/evidence",
        backup_path="/backups/evidence",
        retention_days=30,
        frequency_hours=6,
    )
)
result = mgr.run_backup("evidence")
assert result.success

# Later, restore a specific backup:
mgr.restore("evidence", result.backup_path)

# Discover and prune:
mgr.list_backups("evidence")
mgr.prune_expired()

Development

pip install -e ".[dev]"
pytest
ruff check .

Metadata

Release files for warrantor-backup 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for warrantor-backup 1.0.0
File Interpreter ABI Platform
warrantor_backup-1.0.0-py3-none-any.whl Python 3 none any Details

Release files / warrantor_backup-1.0.0-py3-none-any.whl

Download URL warrantor_backup-1.0.0-py3-none-any.whl
Size 6.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f4690b4a55eb0c60d2b5a2f3830c0bf8cd785950310dda2b8a4e4ed9da6db52e
BLAKE2b-256 checksum
How to use checksums
ae20469189c180b51c1fde90651f4f7f0a3547bb76b2ea41f23234d05c3d9390
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.9

Security for warrantor-backup 1.0.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.0.0 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page