4 ms·
>Worst of all, our database is not backed up, so we lost our data backed up, but the backups don't work, so we lost our data sharded, so we lost our data twi
by gozur88 9y ago
>Worst of all, our database is not backed up, so we lost our data backed up, but the backups don't work, so we lost our data sharded, so we lost our data twice NoSQL, so we're webscale, and we've been losing data for years
Heh. What I keep running into at various companies: "Backed up, but for some reason the restore is going to take three days (if it works), and it will be faster to tap original sources.
Why are we doing backups, then? Company policy.
- itsjustjoe 9y agoBecause backing up stuff is super easy, but no one actually tests restoring data until they need to do it live.
- apple4ever 9y agoWe'll do it live! We'll write it and we'll do it live!
- gozur88 9y agoIt adds to the excitement.
- Sgoettschkes 9y agoNo one ever got fired for doing backups. It's "industry standard" so if you don't do it, you'll be out of your job faster than the server which went down. Backups being actually restorable in a reasonable amount of time isn't "industry standard", so nobody cares.