rm -rf on the wrong server: how GitLab lost its production database

DEV Community·1 points·axrisi·3 days ago·dev.to

rm -rf on the wrong host: in 2017 a GitLab engineer wiped the production PostgreSQL database, and none of the five backups worked. The full postmortem.

Read the full article at dev.to →

#gitlab #production #wrong #database #lost #server #wrong server #gitlab lost

Related stories

Show HN: Beyond "chat with your database" – agentic data explorationreportr.com
Hacker News · 1 points · about 11 hours ago
Show HN: I-server: Hide server using ICMP reflection/Destination Unreachablegithub.com
Hacker News · 4 points · 11 days ago
Show HN: Lathoa, a math app for kids where the AI is wrong on purposelathoa.ai
Hacker News · 28 points · about 12 hours ago
Don't test in production? Test in productionopensource.com
Lobsters · 6 points · over 7 years ago
I Ran My Career Like a Production System for 12 Weeks. The Dashboard Was Wrong Before I Was.dev.to
DEV Community · 16 points · 1 day ago
Linux Server Hardening Best Practices: Essential Steps to Secure Your Servermobilestuff2026.blogspot.com
Hacker News · 2 points · 3 days ago

Related topics

com39 leaked12 tool119 lost23 design138 production56 private45 free200 intended4 outage13