Gitlab deleted production database

Gitlab deleted production database

New thing I learned today: Gitlab developer deleted production database. According to video I watched with my mentor(shout out to Gaurav Sharma for being awesome and patient mentor), the developer first deleted their backup of production database and then deleted the production database. Another thing to note was there was not proper documentation or backups.

Gitlab was backup in operation within 18 hours of the production database deletion. This was done through snapshot captured on staging. But any new data created between the database deletion time and last snapshot of staging (total 6 hours of data) was permanently lost.

Lessons Learned wih Yogisha's opinions:

• First and foremost, document properly. But I am still unsure on how and what to document. How do I know which things are important to document and which things are minors?

• Secondly, make backups.

• The gitlab employee made a mistake of running rm -rf command on the wrong terminal. This is a very silly mistake. I also make silly and common mistake attributing to my lack of proper observation. So, another thing would be to make sure I am observant of my surroundings and works.

• Have a recovery plan. I never do have recovery plan. Whatever I code is stored in github and that's it. My mentor would probably say github wouldn't ever do that mistake as gitlab did. But even in life there is no recovery plan. So, goal would be to be prepared for the worst case scenario.

More than learning, today's blog is just Yogisha's opinions on her own ways of thinking and learning.