Colocation or rented dedicated server: how do they differ?

VPS 4 min read

If a website or application needs its own physical server, there are two ways: you place your own machine in a data centre (colocation), or you rent a server whose hardware the provider supplies and maintains (dedicated server). In both cases a whole machine is yours; the difference is who owns the hardware and who takes on which part of running it.

aWh does not offer colocation: with us you can rent a dedicated server, a KVM VPS or a dedicated cPanel server. This article helps you decide which option suits you, and what to watch out for if you move from your own server to a rented one.

What is colocation?

With colocation (also called server housing), the server is your property: you buy it, you bring it to the data centre, and it gets a place in a rack cabinet there. The data centre provides the infrastructure:

  • space in a rack (measured in rack units, “U”), or a whole cabinet;
  • uninterruptible, generator-backed power;
  • cooling, fire protection and physical security with access control;
  • network connectivity, IP addresses and bandwidth.

The fee is typically based on the space used, the power drawn and the network connection. Installing, maintaining and repairing the machine is your job: either you go to the data centre in person, or, for an extra fee, you ask the on-site technicians to carry out simple tasks (this is called a remote hands service).

What is a rented dedicated server?

With a rented dedicated server, the hardware belongs to the provider and you pay a monthly fee to use it. You get full administrator access to the machine and choose the operating system and software yourself, but hardware faults are fixed by the provider: if a disk, power supply or memory module fails, the provider replaces it.

So that the machine can be managed even when the operating system does not boot, our dedicated servers come with IPMI access: remote management built into the motherboard, through which you reach the server’s console and can restart or reinstall the machine. With colocation, the same requires that the motherboard of your own machine supports this and that the data centre also connects the remote management port.

Comparison

  Colocation Rented dedicated server
Who owns the hardware? yours the provider’s
Costs one-off purchase, then space, power and network fees monthly fee (with us, plus a one-off setup fee)
Hardware fault, part replacement you handle it (warranty, parts, site visit or remote hands) the provider replaces it
Operating system, software your job your job
Console if the system does not boot if your machine and the network support it IPMI
Upgrade, bigger machine buying new parts or a new machine switching to a bigger configuration
Obsolescence your risk; needs replacing every few years the provider renews its hardware

When does colocation pay off?

  • You already have your own server and want to keep using it for years.
  • You need special hardware (for example a custom expansion card) that you cannot get with a rented machine.
  • A regulation or internal policy requires the hardware to be owned by the company.
  • You have many machines, and in the long run buying works out cheaper than renting, because you have your own staff to maintain the hardware.

When is renting better?

  • You don’t want to spend a large sum on hardware at once, and you plan with a predictable monthly fee.
  • You have no staff of your own to deal with a hardware fault.
  • You want to get started quickly and switch to a bigger machine later.
  • You don’t actually need a whole physical machine: for most websites and applications a KVM VPS is enough, which costs less and can be upgraded to a bigger plan with a short restart. We wrote about the differences between shared hosting, a VPS and a dedicated server in a separate article.

Moving from your own server to a rented machine

If you are moving from your own server, colocated or in your office, to a dedicated server or a VPS:

  1. Assess how much CPU, memory and storage you actually need: going by the usage of the old machine, a smaller rented machine is often enough.
  2. Install the same operating system and software on the new machine, then copy the data over, for example with rsync (see: copying files between servers).
  3. Test the new machine before switching your domain over, for example with its address set in the hosts file.
  4. Lower the TTL of the DNS records in advance, then, after the final data sync, point the records to the new IP address.
  5. Only switch off the old machine once every service (web, email, scheduled tasks) is running on the new one.

If you can’t decide which machine suits the task, or you need a custom configuration, contact us and we will send you a quote.

Back: VPS articles (15)