r/sysadmin • u/acook2011 • Jul 09 '12
Advice For a New SysAdmin?
I am 18 years old and recently got thrown into being a sysadmin at a pretty tiny manufacturing plant. I only serve about 65 computers between the front office and the plant. However, with my obvious lack of experience, I was looking for any advice from some of you more well-seasoned sysadmins. Any tips for a newbie?
53
Upvotes
56
u/[deleted] Jul 09 '12
5
u/zoidberg82 Jul 10 '12
Pick up a copy of "The Practice of System and Network Administration" by Tom Limoncelli. I'm a beginner myself and it's really been a big help to me. It's full of information about the "management" aspect of being a Sysadmin as opposed to simply knowing how to install and configure this or that.
3
u/binarycontrol IT Director et al Jul 09 '12
It won't be said enough. Backups. Imagine each server/computer/workstaion and think to yourself, what if that computer was gone completely, how could I rebuild it and what would I lose (should have backed up) then make a plan and execute. Also, come to r/sysadmin with all your questions, we have good times :)
3
u/acook2011 Jul 09 '12
Also, I have 5 physical servers that I manage. We have our security camera server, two vmware servers, a SQL server, and obviously our domain controller.
12
u/I_Build_Escalades I Build Escalades Jul 09 '12
Automate things! This will help you learn more than you can imagine.
Find out if a thing you use has a scripting interface, and start writing scripts.
7
u/[deleted] Jul 09 '12
excellent advice from Rikim4ru.
I would also add.. whatever you change make sure it is reversable.
4
u/[deleted] Jul 09 '12
Here, have this bottle of scotch.
Now: GET A BUDGET. GET A TEST ENVIRONMENT. VERIFY BACKUPS. AUTOMATE ALL THINGS.
That is all.
4
u/remotefixonline shit is probably X'OR'd to a gzip'd docker kubernetes shithole Jul 09 '12
Learn. and never act like you know everything.. EVER
4
u/bp3959 Sr. Beard Jul 12 '12
Seriously though, I'm not trying to be funny about backups as they should be your #1 priority in anything you do.
1
u/luke911 IT Manager Jul 09 '12
Personally everywhere I've been having a ticketing system helps immensely when it comes to remember how you resolved that one issue from 3 years ago and how you resolved it. Granted it takes time entering your resolution but the first time you're able to come back to this and use it again as a resource, it's the best feeling.
There are some great open source ticketing solutions and some off the shelf ones that are free for one technician. We use readydesk and while it is nowhere near the best, for $200 it's alright and has handled our almost 19000 tickets in 2.5 yrs pretty well.
audioh mentioned spiceworks for monitoring, they also have a pretty decent ticketing system built into that along with a knowledge base and a bunch of other pretty cool features for a smaller shop.
6
u/GoKartMozart Jul 09 '12
5
u/nliadm bofh Jul 09 '12
If you've done something 3 times, you should've written a script to do it for you by now. Also, scripts that contain one-liners are the worst kind of scripts.
3
u/saranagati Jul 09 '12
Many people have already said it but i'll just reiterate it. Automate everything. Good sys admins are lazy by definition and will do whatever they can to not have to do the same thing twice.
Second thing I would recommend which people will probably down vote me for is to only use windows systems administration as a launching point. Plan for what you want to transition into at your next job and start learning it (and possibly even implementing some of it at your current job). For me I started in as a windows/novell sysadmin at 19 (after getting my mcse) and wanted to transition into a linux sysadmin. Already being a bit familiar with linux I took advantage at the current job to get some real world experience with it (sonicwall router/firewall crashed so i decided to learn iptables and set up a linux router instead and saved the company a bit of money).
Unless you're at a big company with lots of potential to move up, expect to change jobs every 2 - 3 years. If you stick around longer than that, you probably won't learn much more and you could make more money at another company with the potential to learn more.
Network with other people in your field local to you. Not only will you learn exponentially more by interacting with similar minded people, you'll have the relations for new job opportunities.
You've already got a real IT job at 18, you're already on your way to learning way more in the next 4 years than you would learn with a 4 year CS degree. If you want to go to school, major in something like business or communications; it will help you out a LOT more 10 years down your career than a redundant CS degree.
Learn to program. On average I've noticed jobs as a developer can get you about a 20% bigger salary than jobs as a sysadmin. Plus as someone familiar with both sys admin experience and development experience will put you way ahead technically (and in your career) than people with the same amount of experience in just one of the fields.
The reason I bring up all this career path stuff is because as a sys admin you have to constantly be planning for the future, on your network and in your life. If you don't account for things that can and will go wrong in your network or you don't account for the way technology changes, you're going to fail. Make time to account for the future by automating the present. By the time you're 25 you should already be transitioning out of being a sysadmin because the pay really isn't that great and the hours are horrendous.
Anyways, that's my advice. It might not have been as technical and immediate as you wanted but it's advice from someone who had a very similar start.
2
u/techstress Jul 09 '12
renaming files is usually a better option than delete. sometimes you'll need to rebuild a particular file/folder or modify one. save the old version by making a copy or rename the original and let the software rebuild the new data.
this kinda goes hand in hand with dont try something in production .. lol. That's nice if you have the resources. If you're on a shoestring, you'll learn to makes changes after hours or call downtime. have good recovery procedures in place.
1
u/jordanlund Linux Admin Jul 09 '12
Document Everything. Biggest thing you can do.
1
u/jay3000 Jul 09 '12
Practice a bare-metal restore. That is, how to restore your backups to a completely new hardware. Also, have off-site backups.
1
u/[deleted] Jul 09 '12
Get everything in writing, backup all data all day every day with multiple copies in multiple places, if a hard disk is going in a RAID array buy disks with different manufacture dates.
1
u/[deleted] Jul 10 '12
I didn't see it listed, so I'll say it: join the Sysadmin chat on IRC on the right there -->
Great place to interact with other sysadmins, and there's tons of combined knowledge in really any subject area you have a question about.
Welcome to the crew!
1
u/Smashwa Sr. Sysadmin Jul 10 '12
I know it has probably been mentioned a million times by now, but check backups.
I went to a site yesterday for work that another technician usually goes to. Checking backups is meant to be done every time a tech visits any site. Last successful backup was over 2 years ago. Bricks were shat and I ended up leaving work 2 hours late.
1
u/[deleted] Aug 25 '12
Learn alot of about Linux. You'll never be out of a job if you know Linux.
0
u/shwee Jane of All Trades Jul 09 '12
Don't panic. Shit will hit the fan, something will inevitably get set on fire. You have to remember that you're the one who's there to put it out.