Four rules of survival for qualified DBAs

1. Backup is more important than anything

We need to know that the system is always going to crash, there is no valid backup just waiting for the day to die! I often joke that the only thing that will wake the DBA in a dream is that there is no valid backup.

2. Think twice before you do it

Be aware of what you do at all times, or rather than do it! Sometimes a carriage return, a command can cause an unrecoverable disaster, so you must clearly confirm what you have done and protect the scene if necessary.

3.RM is dangerous.

To know that under Unix/linux, this operation means that you may lose something behind forever, so confirm your operation!!!

Too many people in the "RM-RF" on the grief, when writing this code, is a morning was awakened by a friend, he said Misoperation rm-rf deleted 200G database, and no backup.

What I can tell him at that time is only one sentence: Keep calm.

4. You make the rules.

A good specification is the basis for reducing failure. So, as a DBA, you need to develop specifications, standardize development, and even system personnel, so that you can even circumvent intentional or unintentional misuse. Reduce the risk of the database.

We know that on a well-managed database server, RM-RF may not even be allowed to use.

Perhaps we need to follow more, so I always stressed that the DBA must be rigorous focus, of course, I also very much like the other words: tough people, will be able to achieve everything.