Three golden rules that the system administrator cannot know

BKJIA: When I draft this article, I proposed seven system administrators, but in those seven habits, only three of them stood out. Although the habit is good, sometimes the rule is better, especially when the system administrator processes the production environment.

BKJIA is recommended for editing: SA, xianshen and installation male: What is O & M work like?

Rule 1: Back up everything and regularly verify the backup)

Experienced System Administrators know that no matter how forward we are, the production system will crash one day. The best way to prepare for this situation is to make a valid backup.

BKJIA recommended topics: Linux system backup-operation practices and tools

If you haven't backed up your critical system, you should plan immediately. When planning backup, you should always consider the following issues:

If you have not backed up your critical system, do not read this article. Go back to work and plan your backup immediately.

Some time ago, in a group of studies, I remember that they mentioned that only 70% of productive applications were backed up. The remaining 30% of backups are invalid or damaged.

Assume that Sam regularly backs up critical applications, but does not verify their backup. Jack did not back up any of his key applications. It sounds like the Sam that has been backed up is much better than Jack who has not backed up. In my opinion, both Sam and Jack are in the same situation, because Sam has never verified his backup to ensure that it can be used for recovery when a disaster occurs.

If you are a system administrator and do not want to follow this golden rule 1 or want to break this rule), you should seriously consider giving up the work of the system administrator, the good news for developers is that, according to BKJIA's previous reports, the boundaries between system administrators and developers have become increasingly vague ).

Rule 2: Be proficient in command line. If possible, avoid using the UI)

On Unix/Linux servers, any task can be executed through the command line. Although some UIS can easily complete some administrator tasks, you really don't need them, and you should always use the command line.

BKJIA recommended reading: Several Linux commands that must be memorized by the system administrator

Therefore, if you are a Linux system administrator, you should be proficient in command line.

In any system, if you want to become "fluent)" and "productive high-yielding)", you should be proficient in command line. The main difference between Windows System Administrators and Linux system administrators is GUI Vs command line. The Windows System Administrator does not like command lines very much, while the Linux System Administrator does.

Even if you have a UI that can complete a task, you should give priority to the command line, because if you use the command line, you can understand how a specific service works. In many production server environments, system administrators usually Uninstall all GUI services and tools.

If you are a Unix/Linux system administrator and do not want to follow this rule, you may want to become a Windows system administrator in your heart.

Rule 3: automate and become lazy)

The lazy System Administrator is the best system administrator.

BKJIA recommended reading: how to be a good and lazy System Administrator

As far as I know, no system administrator prefers to break this rule. To become lazy, there may be something to do.

Take a few minutes to think about and list all the routine tasks you may do every day, every week, or every month. Once you have such a schedule, think about how you can automate it. The best system administrators usually do not like to be busy. He prefers to make the system work for him and make himself easy.

Original article: http://www.thegeekstuff.com/2010/07/three-sysadmin-rules/