3tears-backup
Encrypted, grandfather-father-son (GFS) rotated database backups to any
ObjectStore, with restore verification — built on 3tears primitives so it
drops into any 3tears app.
- Storage-agnostic. The engine takes an injected
ObjectStore(3tears-object-store— S3 is the first driver, filesystem the second) and streams the dump throughEncryptedObjectStore, so a multi-GB dump is client-side AES-256-GCM encrypted and never sits whole in memory. - Postgres and Yugabyte. A pluggable
DbDumpDriverwraps the right dump tool; the engine autodetects the target fromversion(). - GFS retention. Keep N daily / weekly / monthly backups; prune the rest.
- Restore-verified. Backups are proven by restoring into a throwaway temporary database, with an optional hook to spin a stack against it.
Configuration is an injected, frozen BackupConfig — construct it however you
like (a from_env factory reads THREETEARS_BACKUP_* with defaults; most apps
will build it from control-plane settings instead).
1 maintainer
Metadata
1 maintainer
Release files for 3tears-backup 0.71.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| 3tears_backup-0.71.0.tar.gz | 79.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| 3tears_backup-0.71.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 130.8 kB
Release files / 3tears_backup-0.71.0.tar.gz
| Download URL | 3tears_backup-0.71.0.tar.gz |
|---|---|
| Size | 79.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6c85d4e1197270e0f703e09b65cb700bebb80604d51d935fff581ea5d2fa4ba4
|
|
BLAKE2b-256 checksum How to use checksums |
d6d8ba56503b5a335ef2948e987cc6ff3ff2ff83c5f3029c3c7998b6a9795aa7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logRelease files / 3tears_backup-0.71.0-py3-none-any.whl
| Download URL | 3tears_backup-0.71.0-py3-none-any.whl |
|---|---|
| Size | 51.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f39c2c8a36466b0c45439b5571fcbd45a5eaf41b1531956677a0ea11462adb0
|
|
BLAKE2b-256 checksum How to use checksums |
0e0cb55a561d45ac5c2076514bab96f5137bb55a7c203557fd7d6477895b231c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logSecurity for 3tears-backup 0.71.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for 3tears_backup-0.71.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logA 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.
