Article

The single point of failure on your team isn't a server

· Adrian Sullivan

You have spent years building resilience into your systems. Redundant power. Clustered servers. Failover for the things that matter. And the whole estate still rests on one person who, if they were hit by a bus, would take half of what you know about your databases with them.

That person might be you.

Nobody likes naming this, because it sounds like admitting a weakness, and because the person in question is usually capable, loyal, and quietly holding things together. That is exactly why it is dangerous. Competence hides the risk. The more capable your one database person is, the less anyone else needs to understand, and the deeper the hole when they go.

You do not fix this by hiring a second expensive specialist. You fix it by making the knowledge leave the person’s head and live somewhere the team can reach it. What runs where. What has to be patched in what order. How the failover actually works, tested, not assumed. Where the backups go and whether they have ever been restored. In writing. Reviewed. Owned by more than one human.

Here is a quiet test. Pick your most important database. Could a competent person who is not your specialist bring it back from a total loss, using only what is written down, inside the time you have promised? If the answer depends on one phone call, you have found your single point of failure, and it is not a server.

This is most of what an outside assessment is actually for. We run a free, read-only check and hand you, in plain English, what your databases need and how to recover them. The point is not to replace your person. It is to make sure the business does not stand or fall on whether they answer the phone.

Free health check

Want to know if this is sitting in your estate? We run a read-only check and hand you a graded report in plain English.

Get your free health check

← All posts