No. Command generation is plain JavaScript in your browser. Hostnames, paths, usernames and passwords never leave your machine — important, because a backup configuration describes everything you own.
Free Server Tool — 100% In-Browser
Backup & Restore Script Builder
Generate exact, copy-paste backup commands for restic, BorgBackup, rsync snapshots and SFTP/SCP transfers — from a form, not from memory. Retention policy, encryption, cron wiring and the full restore runbook included. Built entirely in your browser.
Backups Fail for Boring, Preventable Reasons
Almost every backup disaster traces back to a config typo: a retention flag that deletes too much, a forgotten exclude that bloats the repo, a cron job that never ran because the password prompt blocked it — and above all, a restore command nobody remembers at 3 AM. This builder generates the exact commands from a short form: what to back up, where, how long to keep it, and exactly how to get it back.
Every command is produced by JavaScript in your browser. Paths, hostnames, ports and passwords you type are never sent to any server — which matters, because a backup config is a map of everything you own.
How It Works
1. Pick a Method
restic, Borg, rsync snapshots or SFTP/SCP — or compare all four with our guide table below.
2. Fill the Form
Sources, destination, retention (7 daily / 4 weekly / 12 monthly), excludes, schedule time.
3. Copy the Script
Install, init, backup, prune and check commands — plus a cron or systemd-timer entry for automation.
4. Save the Runbook
Every output includes a restore section: list snapshots, mount or extract, verify. Test it before you need it.
Backup & Restore Script Builder
What to back up
Destination & retention
Want backups without scripting?
restic, Borg and rsync give you full control — but if you'd rather have a managed, agent-based solution with bare-metal restore, versioning and ransomware protection, see Acronis Cloud Backup from Systron. The commands above remain useful even alongside it, as an independent second copy.
Everything above runs in JavaScript in your browser. Hosts, paths, usernames and passwords you enter are never uploaded — a backup configuration is a map of your infrastructure, and it stays on your machine.
Which Method Should You Use?
| Method | Best for | Encryption | Deduplication | Versioning | Restore style |
|---|---|---|---|---|---|
| restic | Modern default — servers, laptops, any destination | ✔ built-in (client-side) | ✔ excellent | ✔ snapshots + retention | Restore, mount (FUSE) or dump single files |
| Borg | Dedicated backup servers, large repos, archivists | ✔ built-in (repo-level) | ✔ excellent | ✔ archives + retention | Extract, mount (FUSE) or export tar |
| rsync + hard links | Plain VPS with only rsync/SSH available | ✖ (tunnels over SSH only) | ✔ hard-link snapshots | ✔ snapshot dirs | Copy files back — it is a plain directory |
| SFTP / SCP | One-off secure transfers, no repo needed | SSH transport | ✖ | ✖ (copy, not archive) | Copy back with the mirrored command |
| Acronis Cloud Backup | Zero scripting, bare-metal & ransomware protection | ✔ end-to-end | ✔ | ✔ managed | Full agent restore — see the service page |
Backup & Restore Builder — FAQ
Are my paths and passwords uploaded anywhere?
Why does the script dump the database first?
Copying database files while the engine is running produces a corrupt, unusable copy. The generated script runs mysqldump or pg_dumpall to a file first, and backs up that dump. Consistency is the difference between a backup and a wish.
How does the retention policy work?
The generated prune command keeps 7 daily, 4 weekly and 12 monthly snapshots by default (you can change each). Older snapshots are only deleted by the prune step — never by the backup step — so a fresh backup can never destroy history by itself.
Why is the restore section included?
Because a backup you cannot restore is not a backup. Every output block ends with the exact restore sequence: list snapshots, verify, extract or mount. Test it once on a scratch directory before disaster strikes — at 3 AM you will not remember the flags.
Do I still need Acronis if I run restic or Borg?
The 3-2-1 rule wants more than one method and more than one location. A scripted restic/Borg repo gives you control and low cost; Acronis Cloud Backup adds an independent, managed copy with bare-metal restore and ransomware protection. Many admins run both — they fail in different ways.
SFTP or SCP — which one?
Use SFTP for interactive sessions and resuming interrupted transfers; use SCP for quick, scripted one-shot copies. Both ride on SSH, so the same keys and port rules from our SSH tab apply. Neither is a versioned backup — pair them with restic or Borg for anything you care about.