Linux Backup: Build a Restore Plan Before You Need Recovery
A backup is only useful if it survives the failure you care about and you can restore it. Test a restore before you trust the process.
A Linux backup is a restore plan, not just a copy command
Decide what must survive, how quickly you need it back, and which failures the backup must survive. A second copy on the same physical disk does not protect against disk failure; a permanently attached drive may not protect against deletion, corruption or ransomware.
| Layer | What to consider | Restore test |
|---|---|---|
| Personal files | Home directories, project files, photos, documents | Restore selected files to a temporary folder. |
| System configuration | Documented files under /etc, service configs, keys/secrets with appropriate protection | Restore a copied config in a lab/VM or compare against a known-good copy. |
| Application data | Databases and apps may need consistent snapshots or app-aware dumps | Perform an application-level restore, not just a file copy. |
| Whole system | Disk images can shorten bare-metal recovery but are larger and less flexible | Boot recovery media and verify you can access the image. |
A conservative rsync example
For ordinary file trees, rsync can copy incrementally. Run a dry-run first, keep source and destination directions obvious, and do not add deletion flags until you intentionally want the destination to mirror deletions.
rsync -a --dry-run ~/Documents/ /media/backup/Documents/
rsync -a ~/Documents/ /media/backup/Documents/Keep at least one failure-independent copy
An external SSD can be useful for offline backup or migration staging, but the operational rule matters more than the model: disconnect or otherwise isolate a copy when it is not needed, and keep another copy in a different failure domain when the data justifies it.
Useful gear for this task
Official references
For current behavior and version-specific details, use the relevant upstream documentation alongside this guide.
Frequently asked questions
Is an external drive enough for a Linux backup?
An external drive can be one useful backup destination, but a complete plan also considers accidental deletion, theft, ransomware and device failure. Keep at least one copy independent of the primary system and test restores.
Is rsync --delete safe for backups?
Not as a default. --delete removes destination files that are absent from the source, which is useful for an intentional mirror but can also propagate accidental deletion into the backup.