Get advice
Article

When the database dies at 3am, who actually gets called?

· Adrian Sullivan

Picture the worst night. Your most important database is down at 3am. Walk it through, honestly, step by step. Who notices first, and how? Who do they call? Does that person answer? Do they know what to do, or do they know who knows? How long is each link in that chain, at 3am, on a weekend, when one key person is on holiday?

Most organisations have never actually walked this through, and the walk-through is free. You do not need a single tool to do it. You need an hour and a willingness to find the gaps before the gaps find you.

The gaps are almost always the same. The alert goes to an inbox nobody watches overnight. The one person who understands the system is a single point of failure with a phone that might be on silent. The recovery steps live in that person’s head, not in a document. The escalation path is keep ringing people until someone picks up. Each of these is fixable, cheaply, in calm daylight. None of them is fixable at 3am.

If you are the person who will be asked, the morning after, why it took so long, this is worth your hour. Write down the chain. Find the weak link. Fix it before you need it.

For the database half of that picture, a free, read-only check tells you what is monitored, what is recoverable, and how, in writing. The other half, the human chain, you can map this afternoon. Both halves are cheaper today than at 3am.

Not sure who you need?

Tell us what is going on. A senior DBA reads every message and points you at the right next step, even when that is not us. A free read-only check will tell you whether this one is sitting in your estate.

Get pointed in the right direction

← All posts