I'm gettin interested in this...I really am...but I'm confused on some things, such as the "U"...1U, 2U, etc, what does it mean?

If I'm correct, you pay for the space that your server takes up, as well as the bandwidth.

With Co-location, from what I understand, you send them your components, and they hook it up to a backbone connection, is this correct? If so, I'm guessing they charge you by the amount of bandwidth, say something like (and this is only an example, I know it's no where near what it actually is) $20 per GB of bandwidth per month. But do you use the bandwidth then they charge you? Or do you pay for it up front, as with a normal host?

I've been looking at some different sites that offer co-location, and since I'm still new, I'd like some people to recommend some companies. I'm not sure who would be good, because I'm not all up on the terms and stuff for co-lo.

Thanks :)

Yes you pay by how much space your server takes up which is mesured in U's. A rack holds around 42Us.
Colo is when you send your machine to a provider and they give you a port on their switch/hub and charge you for bandwidth. Bandwidth pricing really varys between hosts. Some want customers so badly that they will give it to you at cost and others actually would like to stay in business more then a few months to a year. If you would like decent bandwidth non cogent crap it costs anywhere from $1.00-$3.00 per GB transfered. Some hosts only charge on outgoing some incomming and outgoing. You also pay up front for these services and there may be a setup fee with certian providers.

U is short for Units. Each unit is 1.7" high. If you're sending a minitower, it's usually 4U high and a shelf has to be mounted, because Unit servers have special rack mount hooks on each side.

As for bandwidth, you can expect to pay at least $1 per GB depending on quantity.

Originally posted by OneStop
U is short for Units. Each unit is 1.7" high. If you're sending a minitower, it's usually 4U high and a shelf has to be mounted, because Unit servers have special rack mount hooks on each side.

As for bandwidth, you can expect to pay at least $1 per GB depending on quantity.

Not to nitpick or split hairs, but for reference i think a U = 1.75"

Hope that helps.

The 1U, 2U server cases are quite a bit more expensive initially than a tower case to buy, Full ATX etc - But are cheaper in the long run as co-lo facilities charge you for the space - a tower is usually about 4U - Some co-lo's don't take towers at all.

If a company were to take a tower, as in an ATX tower, I'd be much more inclined due to the fact that I don't actually have a server that could be sent to a co-lo facility.

Thanks for the info thus far guys, a lot of my questions have been cleared up. :)

I was looking around at some co-lo sites, and I see that wholesalecolo.com allows you to have a mid-tower, and I'm sorry for asking this question, but what are the components needed for a server (in my case, a mid tower)?

Obviously you need a mobo and CPU,
hard drive,
RAM...

I wouldn't think you would need a video card...Correct me if I'm wrong...

Also, on wholesalecolo.com, I'm confused on something...

It says, "Bandwidth included in plan (All bandwidth list here is burstable to 100MBPS)" 1mpbs

OR

300GB


What is the difference?

Thanks guys! :)

Greetings:

In co-location you supply the equipment you want connected into their network. Typically the equipment is rack mountable.

Each rack unit is 1.75" high with the width and depth accomodating a standard rack.

In a co-location environment, you typically pay the provider for the space your equipment takes up, power for that equipment, and the bandwidth you use.

Typically bandwidth is sold by the speed per second such as 64 Kbps (approximately 20 GB per month) to 1 MBps and more.

Billing methods do vary, but be very careful of burstable bandwidth. Most providers use a 95% method which means they get rid of most (but not all peaks).

However, most overages are billed way about what you would have paid had you contracted for that amount to start.

Since it is your equipment, you are responsible for insuring your equipment.

Furthermore, most of the time you are responsible for repairing yur own equipment. If the co-location provider will repair your equipment for you (often for a fee), they often require you to keep spare parts at their location.

Co-location can be among the least to the most expensive depending on what you place, the data traffic you use, and your ability to manage your own hardware and equipment.

Thank you.

Sorry about all the questions, I just have so much jumping around in my head right now as I too will soon be getting into the co-location arena...

they often require you to keep spare parts at their location. Are you kiddin me? Even for fans, power supplies and memory sticks?

What is the standard for people who colocate? Do they go with local colocation facilities or do they ship their equipment off to another state / location for the co-location company to take care of hardware problems?

Since it is your equipment, you are responsible for insuring your equipment.Can you elaborate on what exactly this entails and the implications of not getting insurance? Does this mean if the colo facility burns down? If the colo actually drops the server? For loss of data on the hard drive?

And what about 1u versus 2u servers? I have heard that 2u servers are better for cooling, but it seems there are a lot more standard 1u servers around. Should cooling really be a concern? To the point where you might consider buying a 2u instead?

Also, since I'm fairly new at managing servers, should I look for a colo facility that specializes in the software I'm planning on running? Do most colocation facilities have the knowledge to work with both linux and windows, as well as IIS and Apache, SQL Server 2000 and MySQL? It seems to me that web hosting companies usually lean towards linux/apache/mysql, and some simply don't do windows stuff..?

Or, are there third parties that can do performance tweaking for you from a remote location if things go awfully wrong? Thus, eliminating the need for your colocation facility to be able to work with all the software you want to use.

And remote reboots.. I would think you could log in, power down, and then wait a minute a log back in again. So why all the fuss about remote reboot power strips and remote hands? Or is for the times when your server is on its deathbed? From my experiences, servers - if managed correctly - should not need to be rebooted more then once in a blue moon.

Thanks for any help. I've been holding back on asking all of these questions, but this seems to be the appropriate thread.

Andrew

Greetings Andrew:

RE: Spare parts

"Are you kiddin me? Even for fans, power supplies and memory sticks?"

No, I'm not kidding you. The true definition of co-location is that you provide your equipment that they hook into their network.

You are 100% responsible for your equipment. It is your equipment, not their equipment.

Some companies will provide a service for a fee where they will make repairs to your equipment; and, if you don't provide spare parts for your equpment, they will purchase those spare parts on your behalf (sometimes they will mark up the costs which is their right; after all it is your equipment not their equipment).

RE: insuring your equipment

"Can you elaborate on what exactly this entails and the implications of not getting insurance? Does this mean if the colo facility burns down? If the colo actually drops the server? For loss of data on the hard drive?"

Many companies will have you sign a disclamer taking responsibility for any damages to your equipment away from them.

It is your equipment, therefore, you are responsible for your equipment. Keep repeating the word "the equipment belongs to me therefore the responsibility is mine." <smile>

"And what about 1u versus 2u servers? I have heard that 2u servers are better for cooling, but it seems there are a lot more standard 1u servers around. Should cooling really be a concern? To the point where you might consider buying a 2u instead?"

If your purchase quality equipment (Compaq, Dell), then unless you are jamping them in the rack with no air flow between the units or the rack does not have the proper air flow and cooling, then you buy the rack unit size that makes sense for your hardware configuration needs.

For instance, most quality vendors cannot create a RAID-5 configuration in a 1 rack unit box; the smallest quality box they can create is 2 rack units.

"Also, since I'm fairly new at managing servers, should I look for a colo facility that specializes in the software I'm planning on running?"

Co-location is where you supply your equipment and put it into their location / network.

I keep repeating the "your equipment" statement because it is crucial to understand. They don't have to manage it, they just have to know how to plug it in, assign IP addresses, and provide the services for which you are contracting.

Now, there are going to be co-location providers that can provide managed services. More often than not they will be hardware or appliance based managed services such as load balancing, network / tape backup, and the like. However, there are those that can provide server / database management and administration.

Most companies that do pure co-location may not have any or limited expertise in an operating system, server software, etc. After all the service they are selling is to allow you to put your equipment into their network.

The co-location companies that also provide web hosting often have expertise in the areas they concentrate in which can vary.

"Or, are there third parties that can do performance tweaking for you from a remote location if things go awfully wrong?"

Yes, there are such companies.

"And remote reboots.. I would think you could log in, power down, and then wait a minute a log back in again. So why all the fuss about remote reboot power strips and remote hands? Or is for the times when your server is on its deathbed? "

From our experience of providing remote management, there are extremely few times in the course of years where the server is so dead that a technician has to do a hard reboot (physical power down and power up).

However, those occasions do occur.

Please note that when done properly co-location can be among the most economical methods of hosting equipment.

However, it is a road that is often traveled because it looks economical without looking to see what are all of the costs for a given situation.

Then in the worse case situations, co-location can be the most expensive route to take.

Andrew, you are doing your homework which is a fantastic start.

And the questions you ask here should be asked to co-location providers you may be checking out. There is no such thing as a dumb question.

Thank you.

dynamicnet:

Thanks for the great reply with tons of information.

Please note that when done properly co-location can be among the most economical methods of hosting equipment. Exactly why it looks so good to us. When leasing the equipment we can get two dual 2 Ghz Machines with 1 Gig of ram each, and colocation for around $300 a month. That is compared to one dedicated server that is a single CPU 1.4 Ghz machine with 256 Megs of ram that costs slightly less then the co-location option (since I'm looking at Windows servers)

And yes, software costs do add up in the beginning! (Dang me for not going Linux / PHP / MySQL) :mad:

Jake, John, Laura, Peter, & Ryan
We Manage ServersHey, I might get to know you guys quite well in the future ;)

Andrew

"And what about 1u versus 2u servers? I have heard that 2u servers are better for cooling, but it seems there are a lot more standard 1u servers around. Should cooling really be a concern? To the point where you might consider buying a 2u instead?"

If you went AMD on the processor you'd be better off with at least a 2U.. allowing more fans and space for cooling. Intels are fine in a 1U.