← All Tags

#data-redundancy

8 episodes

#3033: 3,000 Episodes, 3 Copies: Is This Backup Setup Enough?

Three copies, two clouds, one NAS. But is this setup truly protecting 3,000 podcast episodes?

backup-strategiesdata-redundancydata-integrity

#3024: How to Incrementally Back Up Google Photos to Your NAS

Build a quarterly backup pipeline for Google Photos using the Library API, hash deduplication, and your NAS.

backup-strategiesdata-redundancydata-integrity

#2694: When AI Agents Write Your Backup Scripts

Borg, Restic, and Kopia compared for whole-server incremental backups on Ubuntu Docker hosts.

backup-strategiesdata-redundancydata-integrity

#1931: Where Your AI Pipeline Actually Dies

Why do AI pipelines crash? It’s not the models—it’s the plumbing. We break down how to manage data between stages.

distributed-systemsdata-redundancyhigh-availability

#1925: The Plumbing That Keeps Science From Collapsing

Half of all links in academic papers are dead. Here’s the plumbing that keeps knowledge from vanishing.

digital-forensicsdata-redundancyknowledge-management

#636: The Hidden Costs of Ultimate Redundancy

Can a decentralized network replace Amazon and Google? Herman and Corn dive into IPFS, content-addressing, and the risks of "forever" data.

decentralized-storagedata-redundancybackup-strategiescloud-computingipfs

#410: Redundancy Is Not a Backup

When a 7-year-old server dies, the recovery is a wake-up call. Discover why RAID isn't a backup and how to build a resilient "Server V2."

home-server-backupdata-redundancyhardware-failure-recovery

#205: The Rebuild Nightmare: Why 30TB Drives Break RAID

Herman and Corn dive into the history and math of RAID, exploring why 30TB drives make classic setups like RAID 5 more dangerous than ever.

raid-levelsdata-redundancyhamr-drives