- Top Pick: WD My Book 8TB Desktop External Hard Drive
- Runner-up: WD Elements Desktop 14TB External Hard Drive
- Also consider: Samsung T7 Shield 4TB Portable SSD
A Linux gaming PC does not fail all at once; it fails in layers, and each layer fails differently. A bad graphics driver update can leave a machine booting to a black screen while the library sits untouched. A dying SSD takes everything in one afternoon. Saves scattered across Steam Cloud folders, Proton prefixes and launcher directories can survive both events and still be lost, because nobody mapped where they lived. A plan that treats the machine as one lump protects replaceable things well and irreplaceable things badly.
This guide is the strategy layer: how the three kinds of protection fit together, what to restore first, and the hardware that holds the copies. Other guides in this series go deep on the saves layer, on Btrfs snapshots, and on carrying a library across a distribution change; the job here is the plan that connects those pieces.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Back up a Linux gaming PC in three layers: frequent system snapshots for bad updates, a scheduled copy of the game library, and an often-synced archive of saves and launcher settings. Keep the backup target off the system drive, restore in the order system, library, saves, and test a restore before you need one.
Three layers, three different failures
Layer one: system snapshots
The system layer is your installation itself: the kernel, drivers, desktop and packages. Its characteristic failure is the broken update, and its cure is the snapshot. Tools such as Timeshift, or Snapper on a Btrfs root, record the state of the system files so a bad update can be rolled back in minutes. Snapshots are cheap because they store changes rather than whole files, so they can run daily. Their limit is clear: a snapshot on the system drive dies with that drive.
Layer two: the library copy
The library layer is the installed games, plus the launchers that manage them: Steam library folders, Heroic and Lutris libraries, and the configuration that remembers what is installed where. Games are re-downloadable, which tempts people to skip this layer. That holds for a small library on a fast connection; it collapses for a multi-terabyte library on a capped or slow one. A scheduled copy to an external drive or a NAS, using a file-level tool such as rsync, Restic or BorgBackup, turns days of downloads into an overnight local transfer. File-level copies also carry the launcher configuration, so the restored library is recognised as installed.
Layer three: saves and settings
The smallest layer is the one that cannot be rebuilt at any speed: save games, controller profiles, and per-game settings and tweaks. Saves on Linux live in more places than most players expect: native save folders in the home directory, Steam Cloud local caches, and inside Proton prefixes, where a Windows-style save path maps into the prefix tree. Because this layer is tiny, it can be copied often, even continuously, and it is the layer worth sending off the machine entirely, to a NAS or a cloud-synced folder. If only one layer survives a disaster, it should be this one.
What does not need backing up
Not everything earns space on the backup target. Shader caches are the biggest example: Steam downloads and compiles them per game and per driver, they grow to many gigabytes, and they are rebuilt automatically on a restored system; download and package caches are the same story. Proton prefixes sit in the middle: the bulk of a prefix is scaffolding Steam recreates on first launch, so copying whole prefixes wastes most of their size. The exception matters, though. Some games store saves inside the prefix, which is why the saves layer has an inventory step: find those saves, copy them specifically, and let the rest be disposable.
The restore order
When a system breaks, the restore order matters as much as the copies themselves. After a broken update, start with the snapshot: roll the system layer back, confirm the machine boots and the driver stack loads, and only then check the library.
After a dead drive, the order is system, library, saves. Restore the system layer onto the new drive first, launchers included. Bring the library copy back second, and let each launcher verify the restored folders. Restore saves and settings last. First launches on a fresh system often create default save slots, and restoring the real saves afterwards overwrites those placeholders instead of being overwritten by them. Pause cloud syncing until the restore finishes, then let it reconcile once, with the restored saves as the newest version.
A schedule that survives real life
Backup schedules fail socially first: a plan that needs a person to remember steps stops running by the second month. Build the schedule around automation. Snapshots should be automatic, on the tool’s own timer and before large updates. The library copy should run on a timer too, or be triggered by plugging in the external drive, so a big install gets copied within days. The saves layer is small enough to sync daily or continuously. Finally, rotate one copy offsite monthly, so theft, fire or a power event cannot take the PC and its backup together. A modest plan that runs beats an elaborate plan that needs you.
The test-restore habit
An untested backup is a hope, not a plan. Once a quarter, prove the layers still work. Boot a snapshot rollback and return. Mount the library backup and confirm a restored game folder verifies in its launcher. Open the saves archive and check its newest files are recent, which catches silently failing sync jobs. Run your backup tool’s integrity check, which reads the archive back and verifies it, on the same rhythm. Ten minutes of testing turns theory into something reliable.
How to choose backup hardware
Size the target against the data it must hold, not the drive you happen to own. The library copy dominates: the target needs room for the full library plus configuration, plus versioning headroom. Plan on a target roughly one and a half times the protected data. Large spinning disks are the budget tier for the library copy, where capacity matters and speed barely does. A portable SSD is the premium tier for the rotating offsite copy: it survives being carried and finishes transfers quickly. A NAS is the mid-range to premium tier for always-on automation, awake when timers fire, and with NAS-rated CMR drives in a mirrored pair it protects against its own disk failure too. Whichever tier you pick, keep one copy unplugged or offsite, since an always-mounted drive shares the system’s exposure.
Who should skip this
Skip the full strategy if one layer already carries everything. Players with a small, entirely Steam Cloud-backed library, a fast uncapped connection and a near-stock install can run snapshots alone and accept a re-download as their library plan. Players whose saves all live in one already-synced folder have layer three handled by accident. Handheld-only players face a different problem, centred on one device and its removable storage. Everyone else, especially anyone with a large library, local-only saves or a heavily tuned system, needs all three layers.
Five drives that fit the layers
WD My Book 8TB Desktop External Hard Drive
The classic library-copy target: a large desktop drive that sits next to the PC and takes the weekly scheduled copy. Eight terabytes covers a substantial Steam library plus configuration, with room for versions. It works as a standard USB drive under Linux; the vendor utilities target Windows and macOS.
- Capacity: 8TB
- Interface: USB 3.0
- Form factor: 3.5-inch desktop, mains powered
- Encryption: 256-bit AES hardware encryption with password protection
- Role in the strategy: attached library copy target
WD Elements Desktop 14TB External Hard Drive
The step up for very large libraries, or for one target holding the library copy and a full system image side by side. A plain drive with no management layer suits Linux use. It ships formatted for Windows, so reformatting to a Linux filesystem is the first step out of the box.
- Capacity: 14TB
- Interface: USB 3.0
- Form factor: 3.5-inch desktop, mains powered
- Filesystem as shipped: NTFS, reformat to ext4 or Btrfs for Linux use
- Role in the strategy: high-capacity archive target
Samsung T7 Shield 4TB Portable SSD
The rotating copy. Four terabytes of flash in a rugged, pocketable enclosure is the drive that leaves the house: quick, sealed against dust and water, and maker-rated for drops that would end a spinning disk. Use it for the monthly offsite rotation and for the saves layer, which it carries in seconds.
- Capacity: 4TB
- Interface: USB 3.2 Gen 2
- Maker-stated speed: up to 1,050 MB/s read
- Protection: IP65-rated sealing, drop resistance rated to 3 metres
- Role in the strategy: offsite and saves copy
WD Red Plus 8TB NAS Hard Drive (WD80EFPX)
The drive for the always-on target. Red Plus drives are built for NAS duty: CMR recording for predictable behaviour in mirrored arrays, a continuous-operation rating, and firmware tuned for multi-drive enclosures. A mirrored pair in a two-bay NAS gives the library and saves layers a home that is awake for every scheduled job.
- Capacity: 8TB
- Interface: SATA 6 Gb/s
- Recording: CMR, 5,640 RPM, 256MB cache
- Form factor: 3.5-inch internal
- Role in the strategy: NAS target drive
Seagate IronWolf 8TB NAS Hard Drive (ST8000VN004)
The alternative NAS spindle, spinning faster at 7,200 RPM with Seagate’s AgileArray firmware and rotational vibration sensors for multi-bay use. Pick one drive family per enclosure, mirror two of them, and let the NAS handle the schedule. Its health-management hooks report drive condition inside major NAS operating systems.
- Capacity: 8TB
- Interface: SATA 6 Gb/s
- Recording: CMR, 7,200 RPM, 256MB cache
- Form factor: 3.5-inch internal
- Role in the strategy: NAS mirror target
FAQ
Are system snapshots alone a complete backup?
No. Snapshots protect against bad updates, but they live on the system drive, so a drive failure takes them with the system. They are layer one of three; layers two and three need separate hardware.
Should the backup drive stay plugged in all the time?
A connected drive suits automated schedules, but it shares the machine’s exposure to power events and malicious encryption. The strategy answer is both: an attached or network target for frequent copies, and a disconnected or offsite copy on a slower rotation.
Do Proton prefixes need to be backed up whole?
Mostly no. The bulk of a prefix is regenerated by Steam on first launch. The exception is saves stored inside the prefix tree: inventory those, copy the save folders, and let the rest be disposable.
How large should the backup target be?
Large enough for everything it protects plus versioning headroom. The library copy dominates the maths: plan around your installed library’s size, with a target near one and a half times the protected data. A NAS mirror needs that figure per drive in the pair.
Final verdict
A Linux gaming PC backup strategy is three small plans wearing one coat. Snapshots make bad updates boring. A scheduled library copy turns a dead drive into an overnight transfer instead of a week of downloads. A synced saves archive protects the only data that cannot be re-downloaded. Restore in that order, test quarterly, and keep one copy somewhere else.










