Anyone made the leap to using their "own" server?

How do you know when you're ready?

[benlieb]

The Situation: I am seriously tempted to quit "hosting" my sites altogether, and get my own server (machine) that I have unique access to and ownership of. There are data processing centers that agree to "house" your server and provide good connection and things of that nature.

The concern: I'm concerned that I don't have the skills or time to make this a wise move at present. I have been learning apache/sys admin/unix/lynux only for a little while now. I know eventually this will be the best move.

The question: The question I have is when do I know this is the best move? I subscribe to the look before I leap approach, let's avoid (please : ) ) the just "go for it and see" recommendations.

My request: Who could provide a "list" of skills that are essential to making a move to my "own" server successful?

Thanks.

[Mark_A]

I have not made that leap and have need to nor plans to but I would recommend you look at the economics primarily then as a secondary factor the extra services like backups and security you may have to lay on yourself but I think its primarily an economic decision.

Another aspect to the security issue is that you will then have all your eggs in one basket and this could be seen as a risk in any number of ways.

[SEOMike]

A list of skills... No I can't post that about Unix.

I can offer a word to the wise... Take your time. I thought I knew enough to launch my windows server but that proved incorrect shortly after a test launch (as described later). I had to learn fast and rely on a admin friend to help me troubleshoot the though issues.

If you just got started and think you know what you are doing... try setting up a server hooked up to your personal high speed connection and host your own personal site there for a while. Once you think you have all the bugs worked out, try hosting your main site there (access via IP only with a robots.txt to disallow all) and see if you can get everything to work. Once you can, THEN you are probably ready to put your real site on it and move it to a data center.

There's my 2¢.

[peterdaly]

If you are unsure of your own admin skills, have you considered leasing a "managed" dedicated server? I know of a least one major hosting provider that essentially does the basic admin for you.

In my experience, it is generally cheaper to lease a server at a large hosting provider unless you have very high end requirements.

Generally the monthly cost to colo your own machine will be close to, if not more than the cost to lease a "normal" machine at a hosting provider. That's even before you factor in the hastles that go along with owning your machine, getting it to and from the colo, initial purchase price etc.

I'm going to be in the market shortly for a new leased box, so if you work out the numbers differently for lease vs. own, I'd like to know.

[Webwork]

Win2K/IIS isn't that hard to admin and there's plenty of books to help you along the way. Just keep up with those patches - which you can automate.

The advantage of colo is you can build a killer box for a very reasonable price and then simply pay the hosting. When you go for a managed server you will notice the mark-up for all the needed extras for performance as you scale up its use come at a hefty monthly price increase. I hate the idea of paying extra monthly fees for added RAM, etc. I mean, when are you done paying for that extra GIG? When you've paid 3Xs what it would have cost to purchase outright?

Build a nice box that uses top of the line yet readily available components. If the box dies you will have to pay at the host's rate for service so determine what that is.

Oh, and yes, determine whether they are willing to repair a colo box.

My legal training didn't included server admin, but my ability to read and follow rules helped, as did my ability to perform research.