Backup software is good at telling you it worked. A green job means data was written somewhere. It does not mean the data is complete, that the copy is readable, or that anyone knows how long it would take to get your business running from it.
The three failures a green tick hides
The first is scope. The file server is backed up and the practice management database is not, because it was added after the job was configured and nobody revisited it. The second is readability: media degrades, agents silently stop, and a chain of incremental backups is only as good as its oldest link. The third is reach. If ransomware can encrypt the backup target from the same network, you do not have a backup, you have a second copy of the problem.
What a real test looks like
Pick a system that matters. Restore it somewhere isolated. Open the data and confirm it is what you expected. Write down how long the whole thing took, including the parts nobody counts: finding credentials, waiting on a download, working out which copy to use.
That number is your actual recovery time objective. It is usually longer than the one in the proposal, and knowing it is the entire point.
Then decide whether you can live with it
If the test says eleven hours and the business can tolerate two, that is a conversation about money and architecture, and it is a much better conversation to have on a Tuesday than during an incident. Most organisations have never run the test, so they are making the decision anyway, just without the number.