What is included

We work from the task: first we calculate the requirements, then select the hardware, not the other way round.

Discuss the scope

Configuration calculation

Processor, memory, disks and network sized for the specific load with headroom for growth.

Disk arrays

Choice of array level and drive type. For databases this is the decisive factor.

Storage systems

Separate storage arrays once volumes and availability requirements have outgrown local disks.

Fault tolerance

Duplicated power, disks and network paths, and a second node where required.

Supply and installation

Rack mounting, power and network connection, controller configuration.

Warranty

Service packages with an engineer on site and replacement within agreed timescales.

How the work runs

The timescale depends on availability: stock configurations take two weeks, built to order ones a month upwards.

01

Gathering requirements

Which systems will run, how many users, what volume of data and what growth.

02

Design

A configuration with a justification for every item and alternatives to fit the budget.

03

Supply

Order, delivery, acceptance, rack mounting.

04

Commissioning

Configuring the arrays, installing the hypervisor or the system, handover with documentation.

An array controller without cache protection is a hidden saving that costs you the database. When the power goes, unwritten data in the cache is lost and the database is left in an inconsistent state. A battery or capacitor module costs incomparably less than recovery.

Frequently asked questions

Your own is cheaper over four to five years and gives full control, but it needs a server room with cooling and uninterruptible power. Renting costs more in total but requires no capital outlay and scales within a day. For a small company without a server room, renting is usually the more sensible option.

The warranty is usually three years with the option to extend to five. In practice a server runs longer, but once vendor support ends you are left without spare parts and firmware updates, and that is a risk.

It is calculated from the cost of downtime. If an hour without the accounting system costs a noticeable sum, duplication pays for itself. If the company can survive a day on a backup, one server with a good warranty and configured backups is enough.

We will size a server for the task

Tell us what will run on it: 1C, virtualisation, files, databases. We will send a configuration with the reasoning behind it.