Ask HN: What did you learn from Gilab data loss? | Hacker News Reader

Ask HN: What did you learn from Gilab data loss?

6 pointsvdfs5 comments

> I don't get to work on databases this size and today has been an incredible lesson and a journey. I've been reading all the comments and blogs, watching the stream and Googling what I didn't know or understand.

I wonder what other HN readers have learned from the recent Gilab incident

View on HN

Not learned from this incident but in general:

  - you don't have a backup until you test restore  
  - use checklists and scripts  
  - use another person as soundboard, esp. to confirm destructive changes or "ad hoc" commands. Show intend. Acknowledge.   
  - every line entered in prod must have been tested in dev, with known result (ideally everythign in prod should be scripted)  
  - use cp or mv with date instead of rm (what changes are "irreversible")  
  - use different prompt/color background in prod terminals  
  - don't work tired

How to spell gitlab

Ftfy:

How to spell Gitlab

FTFY:

How to spell GitLab.

what is gilab?

Reply on news.ycombinator.com