Backup automation

Automated backups with a visible control loop.

Rested automates encrypted backups for Linux servers. Configure schedules, run backups on demand, spot failures, and keep history close to the servers you protect.

Automate backups View server backup

Scheduled backups for Linux servers.

Manual runs when you need them.

Status, logs, and history in one place.

Automation example

Example of how scheduled and manual backups can look after setup.

Example only

Next run

02:00 UTC

example schedule window

Manual run

Queued

example on-demand backup

Server

Checking in

example server connection

Last result

Succeeded

example backup result

Scheduling without losing operational context

Automation is not just a timer. You need to know what ran, what failed, and what can be restored.

Set schedule policy

Choose how often each server should be backed up.

Let backups run automatically

Rested keeps the schedule visible so you can see what should run next.

Run a backup now

Start an on-demand backup when you are about to deploy, migrate, or make a risky change.

Record run results

Keep status, timing, logs, and recovery points connected to the backup history.

Automation that still keeps recovery understandable

Rested helps run the backup schedule without hiding storage, keys, or restore responsibilities.

No cron archaeology

Schedules and backup history live in the app instead of being scattered across shell history and cron files.

Backups run on the server

The machine with the data runs the backup, keeping file access local.

Encrypted backups

Automation should not make recovery less secure or harder to understand.

Visible failures

Failed backups should be easy to spot, investigate, and rerun.

Good to know

Good backup automation is honest about offline servers, failed storage access, and overlapping work.

Guardrail

Avoid duplicate work

Backup automation should avoid overlapping runs for the same server.

Reality

Offline servers cannot back up

A server needs to be online for scheduled backups to complete.

Security

Storage access should stay narrow

Automated backups should only have the storage access they need.

Example

Example status

The status card is illustrative; the app shows real backup results after setup.

Make backup schedules visible before they become incidents.

Connect a server, set a schedule, and let backup history show what actually happened.

Create account View server backup