What you are grateful for at three in the morning is the console.

The first is the same as with any large manufacturer and it is worth not taking it for granted: you order from a catalogue, a part number exists, there is a list of compatible parts and there is a support contract with a written term. A security installation lives ten years, and over ten years what matters is not how fast the machine ran on day one: it is that there is an identical power supply when one burns out.

The second is remote management, which in this house is one of the hallmarks. Independent electronics, with its own network address and its own password, that keeps responding with the server switched off. From there you power it up, watch it boot as if you were standing in front of it, read the fault log and change a setting that would otherwise mean a journey. Some functions come in the standard version and others are enabled with a licence, and that is asked about before buying, because the one you need in order to work remotely is usually the higher one.

As the rack recording and management server, and as the machine for the access control software or the database. And it fits very well where there are several sites and the same configuration has to be repeated at all of them: when the eight servers are identical, the update procedure is written once and the spare part fits any of them.

It also fits when the client already has this house in the data centre. The IT team already has the inventory, the fault alerts and the contract; coming in that way is cheaper to maintain than adding a new brand for the video alone. And it has an advantage you notice in the first meeting: the discussion stops being about ironmongery and becomes about what really has to be decided, which is how many days of recording and who watches.

The decoding peak, which is what really costs. Writing to a drive what comes in from the cameras does not exhaust a modern machine; what exhausts it is decompressing video in order to display it, and that happens when several people open large mosaics at the same time. You size for the bad moment, not for the average.

The bays, the drive controller and whether its write cache is protected. The memory slots left free. And the physical room for a graphics card, with enough power supply and air, even if none is going in today: reserving it costs little and not having it forces you to change the server the day somebody wants to analyse the video.

The one that gets forgotten here is the firmware. On a server of this class the recommendation is to apply firmware as a coherent set, not part by part, and that has to be planned: when the recorder is stopped, what version the video software supports and how you go back. A stable installation that breaks on a Monday has usually been updated on the Friday.

In small installations, no. Twelve cameras in one premises do not need a rack server with an annual contract: they need a self-contained recording unit, properly sized and with the right drives. The server would work, and the client would be paying for management capability nobody is going to use.

Nor where there is no decent cabinet or backup power for the whole chain. And we would not fit it if what you want is pure cheap capacity: filling a compute server with drives is the dearest way of buying terabytes.

And there is a case that is not technical: if the client has already standardised on another server brand and has a team that knows it inside out, bringing this one in just because it suits us is making their maintenance worse. The brand of the video server should be the one that team already knows how to run.

These servers are administered with the same tools an IT department uses for the rest: inventory, alerts, firmware and remote console. If there is already a house standard, the video server has to come inside it. A recorder only the installer understands is a blind spot, and it shows on the day the installer is not there.

There are two boundaries worth putting in writing. One, that the volume recorded onto is not shared with anything: the day another process fills it, the recording stops and it is almost never spotted in time. Two, that the video software governs the versions: the operating system and the firmware are updated when that software supports them, not when the calendar says so.

What we go on handling is what requires knowing the installation: redoing the sums when cameras are added, recovering the video configuration on a new machine and deciding what gets touched when a version has to go up. The network all of that travels over is another conversation, and we have that one too.