Backup / checksum copy (md5 file). If necessary?

Question

Backup

I am paranoid about data integrity and create md5 for almost every important file. When I copy through the total commander, I choose to copy with a checksum check. And when I make a backup of files, I always choose to check after creating a backup in one or another software. After that, I create md5 for this backup and also make a copy of the md5 file.
I do md5 so that if something gets corrupted in the backup, then you can understand it, and not think why errors occur ...
I make a copy of md5 in case the original md5 is damaged. After all, if the original md5 gets corrupted, then there will be an error when checking the backup, but in fact the backup can be intact, and for this I just make a copy of md5.
I also thought, just in case, I can make another copy of md5 and then there will be 3 pcs per file ... but it seems to me that this is already too much. You can also make a backup of a backup on one disk ... but it seems to me that this is already ridiculous.
Do you think it is necessary to bother so much with checksums and make backups of them?

Answer 1

Data integrity is checked not through md5, but through archive testing.
md5 allows you to quickly check that a file has not changed. At the same time, md5 does not guarantee that the file was not originally created broken.
It makes no sense. md5 can always be regenerated from a file. If something is wrong with md5, you should not look for another md5, but check the archive itself. Therefore, one md5 is enough.