Linux Server / Filesystems, LVM & Recovery
Use a checksum manifest as one part of backup validation
A copied archive can be unreadable or different from the intended source. A trusted manifest helps detect changed content but is not a recovery test.
Environment and inputs: Linux server baseline · Ubuntu 24.04 LTS / RHEL 9-style systems. Use the specified distribution, init system and installed tool; service names, privileges and supported options can differ.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
sha256sum --check SHA256SUMSRead the result
In the approved backup directory, this reads the named manifest and verifies referenced files. It can cause substantial I/O and trusts the manifest's filenames and origin.
Resolve and verify
Confirm the manifest came from the intended source and backup generation. Investigate mismatches and add a separate isolated application restore test.
Before changing production
Do not use a manifest from an untrusted channel or conclude that matching hashes prove database consistency and key availability.