The roll of the System Administrator on a linux or unix like system involves a number of varied and complicated tasks. A defined and well thought out approach to these tasks is the key to running efficient and reliable systems. The following is a small list of some of the important duties of the System Administrator.
Filesystem Integrity and Free Space: A breakdown in filesystem integrity means the potential loss of critical data. As such, the System Administrator must check filesystem integrity on a regular basis and repair any inconsistencies as soon as they are found. The availability of free space is also the concern of the System Administrator. Periodic checking, daily, hourly, or as required is essential in preventing a file system from filling completely and causing downtime.
Configuration Files: Many configuration files will require modification over the lifetime of an installed system. The System Administrator must document all changes and maintain backup copies of previous revisions.
Software Installs: The System Administrator is responsible for proper installation and operation of all system software. Additionally, the removal of software is also the responsibility of the System Administrator.
User Accounts: The days when anyone with a little experience could be trusted with administrator level access are long gone. User accounts must be carefully managed and restricted to the minimum amount of access needed to fulfill job requirements.
Security: It is incumbent upon the System Administrator to perform all tasks in the most secure manner possible. This means evaluating every action taken as to its possible impact on system security. Adherence to well thought out and documented procedures will go a long way in maintaining system security.
System Monitoring: In the simplest terms the System Administrator is responsible for “knowing what is going on.” In practical terms this means keeping track of the state of each and every installed machine on an ongoing basis. Items to track include, but are not limited to: cpu load, memory usage, and reboots.
Deployment of New Systems: The more hands on “expert” level work that is required to deploy a new system, the more chances there are for something to go wrong. The process of taking a system from bare-metal to ready to use should be as automated as possible to remove the possibility of human error, not to mention a lot of repetitive work!
there Lots of Remain's Duties. these Find Out According My Experience
V.S Chauhan
Filesystem Integrity and Free Space: A breakdown in filesystem integrity means the potential loss of critical data. As such, the System Administrator must check filesystem integrity on a regular basis and repair any inconsistencies as soon as they are found. The availability of free space is also the concern of the System Administrator. Periodic checking, daily, hourly, or as required is essential in preventing a file system from filling completely and causing downtime.
Configuration Files: Many configuration files will require modification over the lifetime of an installed system. The System Administrator must document all changes and maintain backup copies of previous revisions.
Software Installs: The System Administrator is responsible for proper installation and operation of all system software. Additionally, the removal of software is also the responsibility of the System Administrator.
User Accounts: The days when anyone with a little experience could be trusted with administrator level access are long gone. User accounts must be carefully managed and restricted to the minimum amount of access needed to fulfill job requirements.
Security: It is incumbent upon the System Administrator to perform all tasks in the most secure manner possible. This means evaluating every action taken as to its possible impact on system security. Adherence to well thought out and documented procedures will go a long way in maintaining system security.
System Monitoring: In the simplest terms the System Administrator is responsible for “knowing what is going on.” In practical terms this means keeping track of the state of each and every installed machine on an ongoing basis. Items to track include, but are not limited to: cpu load, memory usage, and reboots.
Deployment of New Systems: The more hands on “expert” level work that is required to deploy a new system, the more chances there are for something to go wrong. The process of taking a system from bare-metal to ready to use should be as automated as possible to remove the possibility of human error, not to mention a lot of repetitive work!
there Lots of Remain's Duties. these Find Out According My Experience
V.S Chauhan
Comments
Post a Comment