0

My client asked me for a job description of a system administration because I might be assigned this position along with the other guy I'm working with. To be honest, I do not know much about a System Administrator's job but I'm willing to learn.

Questions:

  1. What are the security requirements of a server? *
  2. What are the key responsibilities in a system admin's job description?
  3. What are some of the day to day tasks of a system admin?
  4. What is the average monthly salary of a system admin?

Note: I will be working inside a Windows environment. But your replies do not necessarily need to be constricted to a Windows environment.

(*) Other software I know will be required are:

  • Windows Server 2008
  • IIS 7.0
  • MS SQL Server
  • .NET 4.0 Runtime

Let me know if there are other things I should be aware of as well. Thanks!

Kassem
  • 113
  • 3
  • This question is a bit confusing. What do you mean you might be assigned this position? Are you already working at the company? What is the geographic location (if you want salary info)? – SLY Mar 07 '11 at 22:21
  • @SLY: I am a freelance web developer. I am currently working on a client's project and we're considering a dedicated (or VPS) self-managed server as our hosting choice, but in this case she'll need a system admin and she is thinking of assigning this task to me and my partner. Accordingly, I'm doing some research on the subject. I live in Lebanon (Middle East). – Kassem Mar 07 '11 at 22:24
  • 3
    While the question itself is quite a good one in reality it needs far more discussion than is appropriate for a Q&A site such as this. Entire volumes have been written on each and every one of those points, plus the many others you haven't asked about but which you will need to understand. – John Gardeniers Mar 07 '11 at 22:41
  • http://www.sage.org/field/jobs-descriptions.html http://en.wikipedia.org/wiki/System_administrator – Zoredache Mar 07 '11 at 22:47
  • 2
    This is blatant self-promotion, but a nice visual guide to the complexities of this exact issue can be found here: http://sysadmin1138.net/mt/blog/2011/01/defining-system-administrator.shtml – sysadmin1138 Mar 07 '11 at 22:54
  • @John Gardeniers: I do understand that the job of a system admin is much more complex than being summarized by a few questions. I was just hoping to get some headlines in the answers on which I could concentrate my research. – Kassem Mar 07 '11 at 23:01
  • 1
    You could always look at this question: [What a beginner should know/learn for sysadmin job](http://serverfault.com/questions/9766/what-a-beginner-should-know-learn-for-sysadmin-job/9771#9771) – Zoredache Mar 07 '11 at 23:20

1 Answers1

3

Firstly

I hope you appreciate I'm writing this response not as a definitive answer but as an attempt to show you the actual size of the question you're asking. It's like you've asked for a glass of water but the only way to give you a useful reply is to dump the entire ocean on your head.

You wouldn't ask "What is a developer", hopefully, because you'd appreciate there's a big difference between developing a small web app (as important and valuable a skill as that is) and being the lead code architect for Windows or Linux or IBM DB2. So it is here.

On with the answers

1. What are the security requirements of a server?

To a certain degree this isn't a technical question because the answer is defined by the client/employer; both what they are and what they want and what they can afford (at the risk of stating the obvious a bank has different security requirements from a chain of restaurants). Whole books have been written about this first question alone, so there's a limit to what you can reasonably get out of a question here, perhaps.

Do they value security over getting stuff done in a hurry? Do they handle data or are they in a industry that places regulatory requirements on how they secure servers, services and data?

At a bare minimum, you'd probably want a baseline for how servers are configured, a framework for patching them and some kind of plan for both incident response and disaster recovery in the event an incident proves serious. And securing data, securing a server and securing services are different things that need to be considered both separately and together.

Just to be clear, a service might be something like your web site, or email. This can be provided by a number of servers, both in terms of distributing workload and providing redundancy.

2. What are the key responsibilities in a system admin's job description?

How long is a piece of string...

Typically a IT department is responsible for providing a bunch of services, and in a well organised department this is done using service level agreements; formal documents that describe what a service consists of, the expected availability and procedures and timings that come into play if the availability isn't there.

System Administrators work to ensure some (or all in smaller organisations) of the IT team's obligations for meeting that SLA are achieved. There may also be elements of R&D/planning, and so on added on but by and large that's what it boils down to.

Even in places without a formal SLA, there will be a bunch of services that is provided to the business by IT and its your job to keep them running. That's pretty much it.

3. What are some of the day to day tasks of a system admin?

In terms of day to day tasks... It's largely defined by the business again, there isn't a common professional definition of "system administrator". To a large degree we're the "almighty janitor" of the IT industry and that means we have to do stuff that others don't want to do and sweep up after others, so it really does depend on the job. I've seen system administrator jobs that include programming, jobs that include managing the phone system, jobs that include none of those but something else odd... it really does depend.

Monitor servers and services to ensure SLAs are being met, and take action to correct things if not. This may require working with a helpdesk team (and in smaller businesses will probably include being the helpdesk too).

There's a reactive element to this ("hey the CEO's email ain't working, find out why and fix it") and a proactive element ("hey the disk storage performance on the email server is appalling, better find out why and fix it before the CEO's email stops working").

Besides that, commonly scheduled maintenance tasks might include checking for physical problems with servers / server rooms, checking logs to ensure systems are performing well and appear secure, planning and carrying out planned changes. And mediocre stuff like making sure the backups went ok, tapes got changed in the backup system, etc.

4. What is the average monthly salary of a system admin? Note: I will be working inside a Windows environment. But your replies do not necessarily need to be constricted to a Windows environment.

That's very much a local market conditions question so no one here can answer it - a "worldwide" average is no help to you because it will include people in New York, Bangalore and London (as well as lots of other places) and those 3 cities alone have vastly different salary expectations. It varies based on location and industry, as well as obvious stuff like experience and qualifications, so even if you happened to live in the house across the street from mine my answer would still have to be "it depends".

Rob Moir
  • 31,884
  • 6
  • 58
  • 89
  • @Robert Moir: I wish I could vote you up on this one because that was some really good answer! BUT, I'm not really sure we're talking about the same thing? lol. My job will be restricted to taking care of a small server and keeping the website running, that's it. There aren't no server rooms or any "physical security" measures I should be taking because there machine will be at a web hosting company. Security is actually of high priority, so is data loss prevention. The website I'm working on is an online auction so you get the picture. Thanks again! :) – Kassem Mar 07 '11 at 22:58
  • @Kassem we are definitely talking about the same type of thing. My point is that "systems administration" is a deep ocean, and maybe you don't need to drink it all, but it will still be deeper and you'll find you need to drink more than you think. (& you may not need to physically check server rooms yourself but if you're selling a service to a customer then you're the one the customer holds responsible if your service goes down because the power in the datacentre hosting your server turns out to be rubbish, so actually you're more responsible for physical stuff than you probably think.) – Rob Moir Mar 07 '11 at 23:05
  • @Robert Moir: Hmmm... I see. I thought that was the responsibility of the web hosting company and not mine. Could you please elaborate on the software security aspect? What software would I need? Antivirus, Firewall, setting permissions...? And are there any specific software you would recommend for a Windows based environment? Again, I really appreciate your answers, definitely helpful! – Kassem Mar 07 '11 at 23:10
  • Kassem - the host is responsible to you. You are responsible to your customer. If the host drops the server on the floor and breaks it and its off for a day, your customer will scream at you. From their point of view the fact that its hosted is your problem. So you need to know enough about environmental factors to know if your proposed hosting service is a good one. – Rob Moir Mar 07 '11 at 23:13
  • As for AV, Firewall - you can use the built in Windows firewall, and see if the reseller includes further protection in the hosting package. AV - I'd suggest you need something, I use Kaspersky AV on my servers and I'm happy with it but that doesn't mean it would work for you. Permissions - application dependant, just make sure you document it and ideally use a checklist to make maintaining them simple. – Rob Moir Mar 07 '11 at 23:15
  • @Robert Moir: Alright, thanks a lot! I actually use Kaspersky on my personal computer and I'm really happy with it as well. I guess that's what I should be going for the server too. – Kassem Mar 07 '11 at 23:20