Backups

A backup in strackt is a point-in-time snapshot of an environment that you can restore onto any compatible server in your team. You choose where the snapshots go and how often they're taken; strackt handles taking them and putting them back.

Where your backups go

There are two destinations, and you can use either:

• A backup destination on a server you own. You set up a receiver on one of your own servers, and strackt replicates snapshots to it. Everything stays on infrastructure you control.
• Your own object storage. Point strackt at an S3-compatible bucket — Hetzner Object Storage, AWS S3, Backblaze B2, or anything that speaks the same protocol — using your own credentials. Snapshots are encrypted before they leave your server.

You hold the key

When you back up to your own object storage, strackt generates one encryption key for your team and shows it to you once to save. From then on, every backup is encrypted with it. strackt stores the key only in its secret vault and never writes it into a backup — which means the backups are yours in the strongest sense: with your key and your storage credentials, you can restore your own data using standard open-source tooling, even if strackt itself were unavailable. The point of customer-owned encryption is that strackt doesn't have to be in the loop for you to get your data back.

Scheduling

Each backup runs on a schedule you pick — anything from every fifteen minutes up to weekly, or a custom schedule if you need something specific — in the timezone you choose. When you set it up, strackt shows you the next several times it will run, so you can confirm the timing before saving.

Restoring

To restore, open an environment's backups, pick a snapshot, and choose the server to restore it onto. strackt stops the running services on the target, puts the snapshot's data back in place, and redeploys the environment so it comes back up on the restored data. A restore is a tracked operation you can watch, the same as a deploy.

Restores can land on a different server than the one the backup came from, as long as it's a connected server in the same team — useful when you're recovering onto fresh hardware.