System Administrator:
An Overview
Michael Tsai 2017/03/06
“ ”
! Account provisioning
! Adding and removing hardware
! Performing backups
! Installing and upgrading software
! Monitoring the system
! Troubleshooting
! Maintaining local documentation
! Vigilantly monitoring security
1.1
Service Level Agreement
! SA is a service
! People and computers are the recipient of the service
! Service Level Agreement (SLA) sets appropriate expectations (we don’t have an official one here)
! Users are happy when:
! Computers are up and running
! Printers and file servers are available
! Data files stay as they left them
! Application software installed and works as it’s supposed to
! Friendly, knowledgable help is available when needed
Service Level Agreement
! When are users miserable?
! Downtime, scheduled (better) or unscheduled (worst)
! Upgrades introduce sudden, incompatible changes
! They receive incomprehensible messages from the system or system administrators
! They receive long explanations of why things aren’t working
! “No news is good news” ( )
Prioritize the queue
! Many people cannot work
! One person cannot work
! Requests for improvements
! Which one is more severe?
! FIFO
!
( + )
!
3:00-4:00
!
:
!
5:00-6:00
! ?
:
! 1:
!
! 2:
!
! 3:
( T_T)
: switch
!
switch
: switch
! : !
! :
! ( )
! ( )
! ( )
! ( )
! /
(
!)
! :
!
! :
!
7 “rules” for Sys Admins
• Please spend a few minutes to read: https://goo.gl/HkpI56 1. Knowledge-centric approach
(as opposed to person-centric approach) 2. Paranoia
3. Testing (make sure everything works)
4. Documentation (to prevent person-centric)