up vote 0 down vote favorite
share [g+] share [fb]

webdev here with my sysadmin hat on.

I am looking to colo some of my servers since I am located too far from the adsl exchange and can't afford a leased line.

I have the following servers:

  • 1 * SBS 2003 (soon to be replaced with SBS 2011) which also stores data used by the web server and runs services that access the DB.
  • 1 * Windows Web Server 2008
  • 1 * Windows 2008 Standard with SQL 2008 small business edition

So, here's my plan ( looking for comments ;) ):

  1. Retain new SBS server on premises
  2. Colocate web and DB.
  3. Either: 3a. Repurpose existing SBS as application server and colocate it, or 3b. Run applications on DB server - it can more than cope with this, and existing SBS server is getting old.

Also, how will the communication between the colo'd servers work now that they will no longer be part of the domain? I suppose it doesn't matter, I could just use the local admin account rather than the domain one, couldn't I?

link|improve this question
Questions that look like they're asking for a shopping list, like this one, are generally seen as inappropriate on StackExchange sites. Please check out the FAQ for more specifics on the types of questions we like to see. – Scott Pack Oct 8 '11 at 12:42
feedback

closed as not constructive by mailq, Richard, Ward, Iain♦, Scott Pack Oct 8 '11 at 12:39

This question is not a good fit to our Q&A format. We expect answers to generally involve facts, references, or specific expertise; this question will likely solicit opinion, debate, arguments, polling, or extended discussion. See the FAQ for guidance on how to improve it.

1 Answer

up vote 0 down vote

There is a lot of information you leave out that would be helpful in answering this question. Information like what does the application do, what uptime requirements you have and how fast the connection you have to your current premises would be helpful.

However, with the information you have provided, here are some things I hope will help. You can continue to run your existing domain if you deploy an VPN(Virtual Private Network) between your co-location provider and your premises. However, I recommend against exposing servers in your primary Windows Domain to the public internet (but it sounds like you've already done it).

I would seriously look into "cloud" providers rather co-locating your existing hardware. Amazon, Rackspace and many others offer windows servers at low monthly rates. Windows serves are more costly on these services than Linux or Open Solaris servers but still affordable. Moving your entire infrastructure into cloud based servers will likely be less costly than renting space for your existing servers. Also, the cost of upgrading to SBS 2011 goes away. :)

link|improve this answer
I think I've supplied enough information - it's a web site with a database. Pretty standard. Uptime should be 100% or as close as possible. My existing connection speed is clearly not enough, otherwise I wouldn't be considering colocating. Broadband has no SLA or fix time guarantee either. The cloud is one thing I have seriously considered, but my clients require that their data is under my control. I am not keen on having it sitting on some US data center being mined by the US govt. – Kryptonite Oct 7 '11 at 13:52
1  
@Kryptonite The 100% uptime is a funny thing: serverfault.com/questions/316637/100-uptime-for-web-application – mailq Oct 7 '11 at 14:11
@mailq Haha. Well, a man can dream. 99% then. Just another number. If we could get advanced warning of downtime that would be ideal. Anyway, the uptime is moot. ANY colo data centre would be better than my office ADSL, – Kryptonite Oct 7 '11 at 14:26
You think having your data in a DC outside the US makes it more secure? Interesting theory. You can get cloud hosting outside the US from non-US based companies I expect. Given your new requirements I would move it all to co-location. If a component is required for the application it should be on the most performant and reliable network available (within the co-location facility). – Jim Blizard Oct 7 '11 at 15:47
Any data which is housed, stored or processed by a company, which is a U.S. based company or is wholly owned by a U.S. parent company, is vulnerable to interception and inspection by U.S. authorities. See cio.co.uk/article/3257900/… I am in Europe btw. – Kryptonite Oct 10 '11 at 15:11
feedback

Not the answer you're looking for? Browse other questions tagged or ask your own question.