Two different problems, sold as if they were one.
Backup answers a narrow question: can I get the data back? DR answers a much bigger one: can the business keep running?
You can have immaculate backups and still be down for a week. The data sits there, perfectly intact, while there is no failover target to bring it up on, no runbook for who does what, no tested process, and a restore of any real size measured in days rather than minutes.
Backup is a copy. DR is a capability. One is a file you retrieve. The other is people, process and infrastructure, rehearsed to bring a service back inside a window the business can actually survive.
The trap is treating them as one line on a quote, often bought together and assumed equivalent. It is one of the most common gaps I see in this market, and it stays invisible right up until the worst possible day.
If you test one thing this year, test a recovery, not a restore. That difference is the whole point.