Does Relax-and-Recover on Rocky Linux verify restored data integrity, or is a separate checksum pass required?

When using Relax-and-Recover (rear) to restore a Rocky Linux system, administrators need to know whether the built-in recovery workflow validates the integrity of restored file contents or merely confirms that the disk layout and filesystem structures were recreated successfully. The default rear process focuses on structural restoration from rescue media, and its completion message does not necessarily indicate that every restored file matches the pre-backup state byte-for-byte.

This uncertainty is compounded by version-specific behavior, as rear configuration options and supported backup programs differ across Rocky Linux 8, 9, and 10, which can affect what verification steps are practical. Silent corruption from storage media or interrupted archive transfers may persist undetected unless a separate validation pass is explicitly performed, but it remains unclear whether rear exposes any native mechanism to detect such mismatches during recovery.

Does a successful rear recover command on Rocky Linux perform any built-in comparison of restored file contents against original checksums? If not, what is the recommended point in the workflow to inject an independent integrity check without disrupting the recovery process? Which rear configuration parameters, if any, control or influence data verification behavior during restoration?