There are two critical questions you should ask yourself: 1) What if your server died; say the processor/memory/CPU failed - will the few-day-outage, while waiting for a spare part, be a problem for your customers? If so, you will want to consider a second hot-standby server.
2) What if the server HDD failed, and you had to replace and rebuild the OS - would this outage cause you or your customers a problem? If so, you will need RAID (and hot swappable RAID, if you can't tolerate an outage). As for specifications, this will entirely depend on the applications you are running, and the amount of clients you are expecting and there is no easy answer. Kris On Sat, May 23, 2009 at 10:33 PM, Chris Rowson <christopherrow...@gmail.com> wrote: > On Sat, May 23, 2009 at 5:03 PM, doug livesey <biot...@gmail.com> wrote: >> >> I appreciate the advice there, and that is definitely the route I take >> with external, client-facing websites (although I use Mampi -- just get a >> recommendation in there!). >> This, however, is for a suite of inter-operating internal apps, so the >> requirement is to have them hosted internally. >> Cheers, >> Doug. > > Hi Doug, > > It's hard to advise specific hardware without knowing the scale or mechanism > of the application you want to run on it. Additionally other hardware > options may also depend on any SLA you have with a customer you are > providing (i.e what level of uptime are they expecting etc). > > Personally if the most important factor is that the server is cheap, I'd go > with an entry level HP server with 3 years warranty as suggested in my > earlier post, although as I say, you 'get what you pay for' in terms of no > proper hardware RAID, non-swappable SATA drives, no redundant PSU etc. > > Chris > > > -- > ubuntu-uk@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk > https://wiki.ubuntu.com/UKTeam/ > > -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
