Latest
SMS Appointment RemindersDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksJoe Rockey: Ghostwriting His BookHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own FaultGrow a PairYou’re Broke Because You Want to BeIt’s Called Work for a Reason!No Time for TactShut Up, Stop Whining, and Get a LifeWilliam Bessette: AI Enablement and Child Welfare TechnologyFree Book Planning ToolsWhat’s New at The Writing King: Week of October 18, 2026Ghostwriting by the Numbers: Timelines, Word Counts and the First CallPromising Young Woman (2020) ReviewBillions for AI, Pennies for the Plumbing: AI Companies Should Pay to Keep PHP AlivePHP2Shell: AI Found a 22-Year-Old Crack Under Your Website in Two DaysPetrov Day: The Officer Who Didn’t Believe the ComputerKindle Unlimited Is Now Kindle+. AI Audiobooks Just Joined the BuffetMo Gawdat Says the AI Dystopia Starts in 2027. Read the List, Skip the DatesChina Is Using Bots to Fan the Data Center Backlash. The Backlash Is Still Real.The Society of Authors Signed an Ethical AI Charter, Then Ran From It in Eight DaysWhen to Quit Writing a Book: I’ve Abandoned Dozens, and I’d Do It AgainGetty Images Filed for Bankruptcy. Can You Prove You Licensed Your Book’s Images?Fluff Words: Cut Them From Your Prose, Keep Them in Your DialogueWhere Can Writers Learn Storytelling From Movies? Richard Lowe Publishes 1,226 Film and TV Reviews With Writing Craft NotesWhere Are the Independent Bookstores and Public Libraries Worth Visiting in Tampa Bay? Author Richard Lowe Profiles 44 of ThemWhat Should You Know Before Hiring a Ghostwriter? The Writing King Publishes 57 New Answers, Including What to Do When It Goes WrongWhere Can You Hear Founders and Executives Tell Their Own Stories? Richard Lowe’s Leaders and Their Stories Publishes Every Unscripted Interview With a Full TranscriptAuthor Richard Lowe Publishes Eight Volumes of Enemies of You, a Researched Series on the Forces Working Against Ordinary AmericansThe Jackal (1997) ReviewThe Day of the Jackal (2024) ReviewYour First Novel Is an Apprentice Piece: What Beta Readers and Editors Can’t FixWhen the Cloud Gets Bombed: What the AWS Data Center Strikes Teach About BackupsHuman-Written Book Labels Are Gatekeeping With a FeeThe Enshittification of Microsoft Office: Why I Switched to a Free CloneGlobal Encryption Day: The Padlock Every Writer Depends On
Disaster Recovery Resource Center

The Disaster Recovery Hub

I carried disaster recovery responsibility for twenty years, and the real disasters found me: lightning through the building, six safety nets failing in one morning, three days of downtime over a filename.

No pitch. No pressure.

TL;DR: I carried disaster recovery responsibility for twenty years, and this hub holds what the real disasters taught me. It’s for anyone who owns uptime or a recovery plan. The three chapters cover the day everything fails at once, what causes a major outage, and how to plan, test and run exercises, with an FAQ at the end.

This hub is laid out in chapters, from the day everything fails at once to what causes an outage and how to plan and test for it. If you’ve carried a company through a real disaster and want to write about it, see my ghostwriting services or start smaller with the Book Discovery Intensive.

The Disaster Recovery Hub’s three chapters
Chapter What it covers Example article
1. When everything fails at once Cascading failures, applications never designed to come back, a Friday night crash with nobody to call The Day Every Safety Net Failed
2. What causes a major outage Small untested things: a filename, a server under a desk, bombed cloud data centers Three Days Down Over a Filename
3. Planning, testing and exercises Twenty years of lessons, building a recovery site, website backups, hurricane backup plans Twenty Years of Disaster Recovery

1. When everything fails at once

↑ Back to chapters

2. What causes a major outage

↑ Back to chapters

3. Planning, testing and exercises

↑ Back to chapters

Thinking about a book of your own? Start with the Ghostwriting Hub. Related: Cybersecurity Hub, Digital Transformation Hub, Leadership Hub.

Frequently Asked Questions

What causes most major outages?
Small things nobody tested: a changed filename, a backup that stopped running months ago, a recovery path that only worked on paper. The lightning strike is rare. The quiet failure isn’t.
Is a tested recovery plan the same as a proven one?
No. A test proves the pieces work in a controlled window. You only know the plan works when you’ve failed over for real, and most companies never have.
How often should you test disaster recovery?
At least once a year end to end, plus smaller restore tests whenever systems change. A plan that’s never run is a hypothesis with a binder.
Who should own disaster recovery?
One named person with the authority to spend money and the responsibility when it fails. Shared ownership means nobody owns it.

What does owning disaster recovery mean to you?

The leaders who carried a company through real disasters hold judgment nobody can fake, and almost nobody writes it down. A book turns those scars into authority. Let’s talk about yours.

No pitch. No pressure.

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.