Disaster Recovery for a Computer network

Many people are looking to develop or create a disaster recovery plan for their business computer network. Fact is, this is actually a misnomer as there are never any static consequences in a disaster. Take a fire in the building. This could arguably be considered a disaster. Here's the problem. . .

Did the fire reach the data center? If NO then the problem is peripheral damage.

Did the fire burn up the connections of the data center to the outside world? If no, then the problem is much more localized.

What was actually impacted in the building from a network perspective? If not much than it's not as important as a fire in the data center room itself.

See a pattern? Disaster Recovery is NOT recovering from a given disaster but from a set of problems that were CAUSED by a disaster. It's much better to plan for water in the data center that how to recover than a fire or floodwater. Both can put an extreme amount of water in the data center but one has filthy water and the other may be limited. . . or the specialized equipment to extinguish the fire already did the job. So think problems or consequences and not simply a general disaster