How to Set Up 3-2-1 Backups for Important Documents

The 3-2-1 backup rule is simple but effective: retain 3 total copies of your data, use 2 different storage media (for example, an internal drive plus an external SSD or optical disc), and keep 1 copy offsite (cloud or a physically separate location). The redundancy protects against hardware failure, accidental deletion, theft, and localized disasters.

Think in practical terms: if you have 100 GB of critical documents and photos, keep one working copy on your computer, one local copy on an external drive for fast restores, and one offsite for disaster recovery. That means budgeting roughly 200 to 300 GB of storage to allow for versions and growth over time; provision at least 1.5x the current dataset to accommodate versions and temporary snapshots.

Backups are only useful when you can restore them. Schedule automated checks and a manual restore test. A minimal schedule is daily incremental backups plus a weekly full backup, with a restore test at least every 90 days. Verification often takes 5 to 15 minutes for small data sets and up to an hour for larger collections; add that time to your maintenance calendar.

Choose the offsite option based on bandwidth and recovery needs: for a 150 GB household dataset, an online backup with weekly uploads is reasonable if you have at least 10 Mbps upload (expect ~32 hours to initially seed 150 GB at 10 Mbps). If that initial seed is impractical, ship an encrypted external drive to a trusted offsite location and then use incremental cloud sync for changes under 10 GB per week.

format_quote

“I recommend automated daily increments and a weekly full; it keeps recovery windows under 24 hours and retention simple to manage.”

—

Step 1: Inventory. List which files are ‘important’—for example, tax records, legal documents, contracts, and family photos. Count folders and estimate size using your OS tools (Windows: right-click folder > Properties; macOS: Get Info; Linux: du -sh /path). If the set is under 500 MB, full backups multiple times per day are feasible; for 100 GB to 1 TB, use incremental strategies to save space and bandwidth.

Step 2: Choose your three copies. Copy A: the working copy on your primary device. Copy B: a local external drive (USB 3.0 SSD or 2.5″ HDD). Choose a drive at least 1.5x the size of the data set (so a 150 GB drive for 100 GB data). Copy C: an offsite copy—either a cloud provider with end-to-end encryption or a physically separated external drive stored at another location. For physical rotation, have at least two offsite-capable drives so you can swap monthly.

Step 3: Select backup methods. For Windows, enable File History for incremental copies and create a scheduled weekly full image with task scheduler and a tool such as Macrium Reflect. For macOS, use Time Machine for hourly increments and a weekly clone with Carbon Copy Cloner. For Linux or power users, use rsync for local mirror copies and rclone to push encrypted archives to cloud storage. Example rsync command for a local incremental mirror: rsync -av –delete /home/user/Documents/ /mnt/backup/documents/.

Step 4: Set a schedule and automation. Configure automatic incremental backups every 24 hours and a full backup once per week; if files change frequently, set increments every 12 hours. Example cron line for nightly rsync at 2:00 a.m.: 0 2 * * * rsync -a –delete /home/user/Documents/ /mnt/backup/documents/. For cloud uploads with rclone, schedule a daily job at an off-peak hour and limit transfers to 3–4 simultaneous streams to avoid bandwidth saturation.

Step 5: Encrypt and verify. Encrypt offsite copies with 256-bit AES where available; with rclone use a client-side crypt remote. After each full backup, run a verification: compare checksums (sha256sum) of 10 representative files or run a quick file-level restore to a temporary folder to confirm readability. A checksum spot-check of 10 files should take under 10 minutes for small sets; make this a weekly task.

Step 6: Automate rotation for physical media. If you store an offsite external drive at a second location, rotate drives monthly: keep Drive X onsite and Drive Y offsite, swap once every 30 days. Label drives with the date format YYYY-MM (for example, 2026-09) and maintain a one-line log entry per swap: Date, Drive ID, Last backup size (GB), Verified? (Y/N). This log keeps accountability and shows last-known good backups.

Step 7: Test restores. Perform a full restore test quarterly. Pick a random folder of at least 1 GB and restore it to a clean machine or alternate disk, then open 5 to 10 files to confirm integrity. Document restore time (for example, 12 minutes to restore 5 GB from local SSD, 45–90 minutes from cloud depending on download speed) so you know realistic recovery windows.

Step 8: Monitor and maintain. Set alerts for failed backups and check logs weekly. Use SMART tools (smartctl -H /dev/sdb) to check drive health; if the SMART health check reports FAIL or reallocated sector counts exceed 10, retire the drive. Replace drives after 3 to 5 years or when SMART shows early warning signs.

Quick example plan for a household with 150 GB of important files: Primary device holds the working copy; a local external SSD (500 GB) stores daily incremental backups with weekly fulls; cloud storage holds a weekly encrypted archive pushed by rclone. Verify checksums weekly and run a restore test every 90 days; keep at least 30 daily increments and 12 weekly fulls as a minimum retention policy.

Further reading: What Size Fireproof Home Safe Do Your Documents Actually Need? · Why Are Mornings Chaotic? Taming Phone Notifications
Sources: This Old House