Slashdot Mirror
Ask Slashdot: Uses For a Small Office Server?
ragnvaldr writes "I'm the 'IT guy' for an office of about a dozen people. And when I say IT guy, I mean I'm the only one here who can use google well enough to figure out how to make things work. We have a 500GB Mac server with a Drobo with 6TB of storage attached. So far all this server does is back up data, and I want to make it a little more useful. We also have a Filemaker server on it, which I have yet to learn how to use at all, let alone efficiently. Any suggestions to make this machine a little more useful?"
Porn server, of course!
Great minds think alike; fools seldom differ.
...you let a perceived need dictate a use, not the other way around.
Ah yes, the good old "if you don't know, don't even bother asking just fuck off"! Thank god not ALL slashdotters are as worthless as you are, but that argument comes up waaay too often.
It's generally better to start a project from "I want to accomplish [x], so what do I need?" rather than "I have [x], so what can I accomplish with it?" The first approach will be much more focused and more likely to succeed.
Second thing to keep in mind: you don't want to experiment on a production server. I don't care if the "production server" is only a backup server-- if you don't want to endanger your backups, then it's still a production server. This means you shouldn't do anything with this server until you've planned what you want to install on it, and you've already set up a test implementation and you know what you're doing.
Third thing to keep in mind: in current IT practices, it's often not worth it for a small company to do things for themselves unless they need to. You probably need a local file server and therefore also a backup scheme. Aside from that, things like web hosting, email, and chat are usually better handled by a big company that can afford a datacenter. If you do try to do email internally, make sure you back it up and have a plan for outages and disaster recovery.
All that aside, you could start with basic services: directory services, file sharing, email, etc. Filemaker has its uses, but let the use determine the tool. Don't go around pounding on everything just because you've found yourself a hammer. Define the job, and then pick the best tool for the job.
It isn't that at all. I've worked in the field and taken plenty of calls from guys like this. Guys who thought, yeah, I know just enough to be dangerous, let's see what I can do. Then he's sitting there, no backups, no duplication of media, nothing to keep his ass out of the frying pan, and then he's on the phone to me because he's got some hot project that he needs the system for and it suddenly becomes my priority to unfuck the mess he's in.
Either way, he should call the pro. It's cheaper if he calls before he fucks everything up beyond belief.
You non-science, non-engineering types, especially in IT, love to exaggerate and use pontificating language. You clearly don't mean "fucks everything up beyond belief" because it's a meaningless phrase that you picked up from your stupid colleagues in IT. "nothing to keep his ass out of the frying pan" -- is that really necessary? Get to the point and move on.
How hard are backups? rsync, RAID, different storage media, onsite and offsite backups, and cost / benefit analysis to defend the choices. Some of it will be subjective (the "benefit" of something is obviously difficult to gauge and liable to debate). You could suggest some points of reference. That's what every good scientist and every good engineer I've met does -- because they know their worth is not limited to learning some quirks about programs. They design and build stuff. They often debug it. The bad ones constantly overstate their worth and present themselves with a really irritating know-it-all attitude. The bad ones think that by communicating their ideas and helping others out, they are risking job security. The good ones help others learn how to learn. The good ones demonstrate that they know their stuff and understand their worth is not rooted just in knowledge or wisdom, but also in interpersonal skills, often overlooked or downplayed in STEM fields.
I used to be like you in high school. I had worked at a few Fortune 100 companies as a coder / sysadmin type and I didn't realize my douchiness until I left the field in college for computer science, electrical engineering, physics, and chemistry. I know my comments sound a bit harsh, but maybe my tone may make you reevaluate how you behave.