To embbed (a)scan for fs errors (b)fs errors fixing into backup process

Hi,
I think scanning the hdd/ssd on regular basis is as critical as backing them up is.
So, optimally the scanning disks for errors in file system, failures on hardware
(bad sectors, similar) and fixing them should be an integrated part of backup process.

Furthermore, best backup concept will not help if the generated images/backup files
go to/are stored on dirty storage device - drawn by errors in file system, or failure
in hardware.
One has to to ensure the first volume the produced image is sent to is fine.
One has also to ensure the recovery of system used for storing image/backup files
is possible as soon as it gets corrupted.
The job becomes more difficult if backup is a chain: full+several differentials, or full+several incrementals.

The Windows on-board tool for scanning disk for fs errors, bad sectors, others does
not make this job easier. It can't provide reliable results if not run in dedicated/stand-alone mode.
It can't provide reliable scan results without fixing the errors.
Fixing errors is destructive.
Therefore the generic recommendation: Always before fixing disk errors do the backup of it!
It is not my recommendation, just seen several times.

What are the best practices to meet all these requirements?
Best practices providing the best chance for success?

Aspects like test recovery at regular basis and other not mentioned here at all!