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

by vdfs on 2/2/2017, 12:27 PM with 5 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

  • by lazyant on 2/2/2017, 4:43 PM

    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

  • by tronsymphony on 2/2/2017, 4:41 PM

    How to spell gitlab

  • by on 2/2/2017, 4:24 PM

    undefined

  • by itake on 2/2/2017, 3:47 PM

    what is gilab?