Rested
Backup restore workflow

Restore backups from the same place you watch them fail.

Rested keeps encrypted backup recovery close to backup history. Browse recovery points, choose where files should come back, start restores, and keep recovery logs visible.

Plan restore workflowView automation

Recovery points close to backup history.

Restores with explicit targets.

Recovery key stays outside the web app.

Restore example
Example of recovery status after backups have run.
Example only

Snapshots

28 listed

example recovery points

Selected restore

latest

example snapshot selection

Target path

/tmp/recovery

example restore destination

Recovery key

Kept by you

example encrypted backup key

Recovery is part of the backup promise

Rested treats restore work as a first-class workflow instead of an afterthought buried in old notes.

List snapshots
Load the recovery points available for a protected server.
Choose recovery target
Pick the snapshot and restore destination deliberately, especially when recovering onto a live server.
Run the restore
Restore files back to the selected destination when you are ready.
Review logs and outcome
Keep restore status and logs visible after recovery work completes.

Restore visibility without hiding key ownership

Rested can make restore work visible without taking ownership of the key that unlocks your backups.

Restore without web-app decryption
Rested can help start recovery without becoming the place that stores your decryption key.
Snapshot context
Restores start from known recovery points instead of old notes or guesswork.
Safer target paths
Restores can target an explicit recovery directory instead of overwriting live data by default.
Operational history
Recovery attempts belong beside backup runs and failures so the whole loop stays visible.

Restore realities

Good recovery UX says the uncomfortable parts out loud: keys, target paths, and test restores matter.

Important
Recovery key is critical
If the recovery key is lost, Rested cannot unlock encrypted backups for you.
Target
Restore on the right host
Restore where the backup storage and chosen target path are available.
Practice
Test restores matter
A backup strategy is incomplete until restore paths have been practiced and documented.
Example
Example status
The status card is illustrative; real restore options come from your backup history.

Make restores boring before the emergency.

Connect a server, run backups, load recovery points, and know where restore work lives.

Create accountView automation