Is not obvious? Disaster Recovery. lol
I think RHD's point is that it
isn't obvious.
What it means to you may not be what it means to me. If I run Mon - Fri 9-5 with a 4-hour RPO and 24-hour RTO, whereas you run 24/7/365 with a 2-min RPO and 1-hour RTO, we have different needs and we should have different configurations and different DR plans.
There are other factors that matter too, like network topology, third-party integration, etc. Which parts of the production environment can you live without temporarily in a disaster? Which ones are essential? How will your clients connect to the DR DB(s)? Is the code and configuration replicated along with the data? Will authentication services still be available? There are dozens more questions you could ask that would determine the contents of a DR plan. For some organizations these questions don't apply or are overkill. For others, they matter.
Maybe the fact that the acronym "DR" stands for "Disaster Recovery" is obvious. But IMHO, what DR is
isn't obvious.