awit Flashcards
are usually charged with
installing, supporting, and maintaining servers
or other computer systems, and planning for
and responding to service outages and other
problems.
System Administrator?
it means that the smallest solution that solves entire problem is the best solution.
Simplicity
it keeps the system easy to understand and reduces complex component interactions that can cause debugging nightmares
Simplicity
it means that the solution is straightforward. it can be easily explained to someone on the project or even outside the project
Clarity
Many problems are user driven, and different users have different levels of
competency and understanding of technology. Users are often frustrated over
the problem, and sometimes need to vent.
Resolving Problems and Troubleshooting
makes it easier to change the system, as well as to maintain & debug it. In the system administration world, it’s better to write five lines of understandable code than one line that’s incomprehensible to anyone else.
Clarity
It means that the solutions aren’t inherently limited to a particular case. Solutions can be reused.
generality
Using vendor-independent open standard protocols makes systems more flexible and makes it easier to link software packages together for better services.
generality
It means using software to replace human effort.
automation
It improves repeatability and scalability, w/c is key to easing the system administration burden, and eliminates tedious repetitive tasks, giving SAs more time to improve services.
automation
It ensures that everyone is working toward the same goals. Lack of communication leaves people concerned and annoyed. Communication also includes documentation.
communication
Documentation makes systems easier to support, maintain, and upgrade. Good communication & proper documentation also make it easier to hand off projects and maintenance when you leave or take on a new role.
communication
makes adding advanced features considerably easier and makes services more robust.
basic first
It means that you build the site on strong foundations by identifying and solving the basic problems before trying to attack more advanced ones.
basic first
Establish a routine and try to stick to it. If you schedule deliveries of
new computer equipment only on Tuesday, then you don’t have to
worry about matching equipment to orders while trying to get the
mail server that failed over the weekend back up.
Planning and Routines
Estimate how long tasks will take and measure how long they actually do. (Document them both in terms of “hours of actual work” and “clock time”. It might take only 20 minutes to get a new machine set
up in terms of “actual work”, but it may take the better part of a day
for all of the hardware and software to get installed.)
Planning and Routines
People want to know when they are going to see results, so try and think in terms of what your clients are seeing. If the server will arrive in 5 days, but it will take 2 days of setup and 2 days of testing, that is approx. 2 weeks of work, if all goes according to schedule.
Manage and Fulfill Expectations
Many companies have support hotlines and e-mail areas where users can get support for
their questions. Often, however, sys admins complain that users ask those questions in
person or call them directly to get around these processes. If you have a formal system,
first make sure it’s integrated.
Create a process and stick to it
