Haseeb ArshadHaseeb Arshad
← All projects
Data resilienceProduction

Replicated Storage, Backup, and Disaster Recovery

A tiered data design that separates replicated application state, bulk storage, encrypted backups, and rebuildable caches.

LonghornCloudNativePGSMBResticsystemdS.M.A.R.T.

3x

critical volume replicas

4

recovery layers

0

secrets committed

The challenge

What the system needed to solve

Protect mutable data without pretending that replication is a backup or filling Git with databases, secrets, and media.

The build

Engineering decisions

01

Classified data by recovery need: Git-rebuildable configuration, replicated cluster state, bulk NAS data, encrypted backup sets, and disposable caches.

02

Used Longhorn for replicated application volumes and CloudNativePG for database high availability.

03

Built capacity, inode, mount-state, backup-age, and time-to-full monitoring with alerts before failures become emergencies.

04

Documented bare-metal rebuilds, cluster recovery order, application restore checks, and evidence required before retiring old copies.

Architecture

How the pieces connect

  1. 1Application state
  2. 2Replicated Longhorn or PostgreSQL
  3. 3Encrypted backup jobs
  4. 4Separate bulk target
  5. 5Restore verification

Results

What changed

  • Recovery procedures identify what can be rebuilt, what must be restored, and what must never enter source control.
  • Storage growth and backup freshness are visible before capacity or retention becomes critical.
  • The original host and cold artifacts remain available until replacement paths pass real restore checks.