What skills should a system administrator have?

Question

linux

The other day I came across a vacancy for a system administrator and became very interested in this area, such as "Knowledge of Windows Server 2008 R2, network protocols, AD" were noted as important qualities, where you can get acquainted with these natural phenomena in more detail and quickly and get to work as efficiently as possible ? I would also be very grateful for help in finding literature in the field of Linux and working with it.

Answer 1

To work as a good system administrator, you need:
zero level - strong nerves and endurance - often tantrums usually call, for whom "ah, nothing works, you are all goats." Well, or really, something big and thick fell and does not work, you are engaged in restoration.
The first level - technical user support - show how to run a working software, like Word and Excel, how to format a document in them or make a formula, set up a mail client.
The first, advanced one, is to be able to diagnose software and hardware problems - a component has died, such as a network card or video card.
Next - optimization and accounting of their work and problems, writing documentation for frequently arising questions, such as how to change the password yourself when the time comes to change it, like "half an hour - replacing the motherboard to Pupkin, half an hour explaining to Tarasova what a powerpoint is."
Accounting and inventory of user hardware, installed software and which computers are registered with whom, together with accounting.
Further - optimization of the reinstallation of workstations - a service like WDS - do not manually download Windows, office and other internal software every time (two hours per machine, yeah
) stuck. what are vlans and subnets, masks - this is well described in the Cisco ICND and older CCNA courses - routing and TCP / IP stack
Well, then - already any server staff - server hardware, remote control technologies for the servers themselves (ssh / rdp) and their hardware - ipkvm, ipmi, iLO, monitoring, diagnostics.
It's the same with storage systems - disk shelves, tape backup tape drives, and tape libraries.
The software part of servers - Active Directory and Windows Server roles, what they are, why they are needed and how they are configured, how data is backed up and restored, how to store backups correctly and where to store them, how the axis is installed - linux, windows, how it is correctly configured for specific tasks - mail, dns, dhcp, firewall / firewall, etc., how it is released to the Internet, what is a demilitarized network segment.
How to correctly install more complex services - SQL, mail, web, installation wizard - 10 minutes Next, Next, and competent deployment - and configuration - is quite normal from a few days.
Virtualization - what is, what the hell is needed.
Diagnostics, monitoring, server hardware, disaster risk planning and IT infrastructure recovery - from the failure of a specific service (the mail daemon fell) to everything, arrived - "there is no more office building."
Side - small scripting - powershell, bash or large-scale programming - C #, python, perl, in some places web like html / css.
Looks like I didn't forget anything.

Answer 2

do not forget an important attribute

Answer 3

Think carefully before deciding on this path :)
It is very thorny.
Firstly, you need psychological preparation, which can be obtained by working for a year in technical support. Learn to communicate with users calmly, ignoring any tantrums, methodically diagnosing the problem. Very useful for life.
Secondly, you will regularly have to work after hours, since it is not always possible to carry out routine maintenance when users are present and it is not always possible to automate everything in this process. From time to time, fak-ups or other emergencies also get here, which can guarantee an overnight stay at the office until morning.
Thirdly, you must have in your blood the desire to ensure reliability and safety. It goes a little against the desire to experiment with something new.
Fourth, each system administrator seeks to reduce his workload through automation and competent design. As the ultimate dream - to get a system that will work without your participation 24/7. Question: what to do in the remaining free time? What to do if the management realizes that you have a lot of free time? Will it be able to understand then that you are a cool system administrator, and not a bum?
In general, I once worked in technical support and aspired to become a system administrator. And when I became one, I realized that it was not mine.

Answer 4

Sysdamina has three main weapons: experience, manual, google.
The most commonly used for me is Google, since the field of activity is very wide.