6 Prevalent Themes in the Discussion
| Theme | Supporting Quote |
|---|---|
1️⃣ Backblaze silently excludes important folders (e.g., .git and cloud‑synced data). |
> “The fact that they’d exclude ‘.git’ and other things without being transparent about it is scandalous.” – benguild |
| 2️⃣ Lack of clear communication about backup‑policy changes erodes trust. | > “Complete lack of communication (outside of release notes, which nobody really reads) is incompetence and indeed worrying.” – patates |
| 3️⃣ Restores can silently fail, leaving users unaware that data is missing. | > “I tried restoring a file and it failed; the service offered only three months of credit.” – klausa |
| 4️⃣ Consumer‑grade GUI tools limit control; power users prefer deterministic backup software. | > “I use Restic, the cloud service doesn't know about what I send; it’s just encrypted blobs.” – palata |
| 5️⃣ “Unlimited” marketing hides real limits; the business model is inherently risky. | > “‘Unlimited’ marketing is a red flag; they use asterisks to hide limits.” – embedding‑shape |
| 6️⃣ Users are migrating to cheaper, self‑hosted alternatives (Hetzner, B2, rclone, Borg, etc.). | > “I run restic with rclone against Hetzner Storage Box; it’s cheap and works.” – mrighele |
These six threads capture the core concerns: exclusion policies, opaque communication, unreliable restores, tooling preferences, marketing vs. reality, and viable alternatives.