Re: [NF] web server specs

Author: <kamcginnis@gmail.com>

Posted: 2012-07-24 at 12:39:37

If it is just a file server, I recommend webfaction (recommended to me by someone on this list). They recently offered

an upgrade to 100gb for the same low price.

Depending on how many people have to access it, you might check out a VPS. Some like infinitelyvirtual will 'rent'

terminal server licenses. It is reasonable for a small number of users, not sure if they have volume discounts. I like

this because if you run out of power, you can simply add memory or CPU cores and disk space. For us it was much less

expensive than continuing to maintain our own servers in house. Also, you access with RDP which means you can get full

speed performance with your old win2000 computers.

Outsourcing has set me free. I no longer have to worry about the servers going down when I am not there.

----- Original Message -----

From: "M Jarvis" <brewdaddy@gmail.com>

To: <profox@leafe.com>

Sent: Tuesday, July 24, 2012 9:48 AM

Subject: [NF] web server specs

My hardware skills and knowledge are woefully out of date... I've been

tasked with spec'ing out a new web server for our intranet. Our

current one is something like 12 years old, running out of space, and

frankly our big fear is that it will just up and die some day soon.

Mostly it just stores documents and runs some queries, does some light

web form work, nothing terribly demanding. What makes it so special is

that it is a mission critical machine (hospitals love their

documentation).

We have plans to virtualize servers down the road, but there is time

pressure to do something with this server right now.

It specs out as: Win2K, SP4, x86 AT box, 523K RAM, Seagate drive

partitioned as C: (4 gig - OS), D: (13 gig - data/other).

We have a media server available so the replacement won't have to do

much serving of streaming media or other heavy lifting.

I want to migrate the functionality to a CMS such as Drupal or

similar, so one of my concerns is to have enough horsepower to run the

CMS in addition to the documents etc that are on the machine. It would

be great to get a document management system in place as well but so

far that hasn't come up in this go-around.

What sort of size and capabilities should I be looking for? Bigger and

Faster sure, but what are folks putting into/on servers these days?

We're a windows shop (other than our phone system) so I'm stuck with

running that.

I'm hoping to gather some ideas then pass this off to our network guy

to do the actual pricing and ordering.

TIA,

--

Matt Jarvis

Eugene, Oregon USA

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/12aa01cd69c3$4c9f7430$7a00a8c0@w2k3s02

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.

©2012 <kamcginnis@gmail.com>