Servers

Backups

A backup server keeps a copy of your servers' data. If disks fail beyond what RAID survives, customers keep their data instead of leaving.

RAID protects against one dead disk. A backup protects against the rest: a second failure, a fire, a flood or a burglar taking the disks. Without one, a lost array means customers lose their data, many of them leave, and your reputation drops.

The quick way: a rack NAS

The Vendor shop sells a rack NAS: a closed 1U box with 500 GB of backup space on four drives in RAID 5. There is nothing to fit and no operating system to install. Mount it in a cabinet, cable it to a switch and it is ready: point your servers at it like at a storage server. When 500 GB is not enough, build a backup server.

Building a backup server

  1. Buy a storage chassis (lots of 3.5" bays) and fill it with large disks.
  2. Fit a processor, memory and a power supply as for any server.
  3. Install the Storage Server OS. The machine becomes a backup target; it cannot be sold to customers.
  4. Rack it, cable it and keep it online.

Its page shows Data stored, the servers that back up to it and how much space is free.

Protecting a server

On the Nodes list, click Set backup server on a server and pick a storage server or a NAS: Back up here. The Nodes list then shows Backed up for that server, or No backup, and shows for each storage server how much of its space is in use, such as 15 GB / 1 TB. A storage chassis without an operating system shows N/A: it is waiting to become a backup server, so it does not need one itself.

The storage server must hold the data in use on each server it protects: the operating system, customers' virtual machines, hosting accounts and part of a dedicated tenant's disk. Servers are covered in the order you attached them until the space runs out; the panel tells you when there is no room.

When disks fail

If a protected server loses its array, customers keep their data. Reinstall the operating system (for VPS, a hypervisor) and the virtual machines come back. An unprotected server is simply wiped.

Moving customers off a server

A backup also makes moving virtual machines safe. Move all virtual machines on a server's page moves every VM to another running hypervisor in the same datacenter. With a working backup nothing is lost; without one there is a 60% chance that one or a few customers (up to a third) lose their files on the way and leave. See Nodes.

Keep it safe

A backup server in the same cabinet shares that cabinet's fate. If you can, put it in another cabinet or building, and keep it online: an offline backup server protects nothing.

Storage servers and NAS boxes hold backups, not customers, so their downtime does not count towards your uptime. The uptime panel marks them Not counted.

The Maintenance tab gets a red dot when a server with customers has no working backup (see Overview).

Common mistakes

  • A backup server too small for everything attached to it.
  • Backing up only the first server and adding more later without checking space.
  • Treating RAID as a backup.

Want the numbers? The full rules: Building servers

Start a hosting company with $50,000

Free to play in your browser. One shared world, running in real time.