Ask Slashdot: Uses For a Small Office Server? 260
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?"
Don't Disrespect the Backups (Score:4, Informative)
Seriously, data backups are crucial in every enterprise, even small ones. That's a *great* use for your server. Are you checking on your process by restoring files once per month? Once per quarter? I joined a bioscience center that had faithfully been making backups for half a year before I joined but five months of the backups had no data. So do check, please.
I have more questions about your backup methods than I can easily list here. Still, there are other good uses for *every* server. They can all:
1) Provide DHCP addresses
2) Offer NTP to keep the clocks synchronized
3) Provide comprehensive system logging (for all systems of concern)
4) Store and/or offer common utilities like print services
Wrong way around (Score:5, Informative)
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.
Here's a suggestion (Score:1, Informative)
Stop! Stop right there!
RUN! RUN FOR YOUR LIFE!!!!
Re:Hire a professional... (Score:2, Informative)
Re:Hire a professional... (Score:2, Informative)
If you think macs are overpriced, you havent seen the price of that drobo boat anchor.
Re:It's Obvious (Score:5, Informative)
Hi. Welcome to I.T. A lot of us get started in the exact position where you are.
Top 3 things:
1. Make sure you have a handle on what needs to be backed up.
2. Make sure it's backed up.
3. Make sure you can restore at least one file.
Backups run daily or weekly based on your preference, but run through this entire list at least once a month. People create new shares and it gets missed from the rotation and then... kaboom.
In addition to the above..
Can you share your printer(s) through the server? Sharing a laser printer is almost always cheaper than having a bunch of inkjets on desks.
Can you setup some sort of offsite backup rotation? Is taking a tape home once a month an acceptable solution?
Does your company have a website and branded email? You could very inexpensively purchase a domain and setup a template based site for them. Email @yourco.com is more professional looking than an address @yahoo or @gmail.
Filemaker is an excellent database system. Do you have forms that drive your business? If so then consider if there are benefits to translating them into filemaker.
For all of the above, you are at a disadvantage that you don't have test systems. Making untested changes on a production box is scary. Always have a backup. Try to setup a "test" environment wherever possible. Most importantly, understand what you do before you do it.
Best of luck,
Ellie