A backup is only useful if you can restore it
A short restore drill for a small Linux server.
Pick one directory you would miss tomorrow. A small application configuration or a photo album is a good first drill. Write down where it normally lives, who owns the files, and what must work when it comes back. Treat that list as your acceptance criteria.
Restore beside the live copy
Create a temporary directory on a separate disk or machine with enough free space. Use your
backup tool's restore command and point it explicitly at that directory. Leave the live path
alone. Start with a single recent file and compare sha256sum output with the original
if it has not changed since the backup. Then restore the whole directory.
Check behavior
Look for hidden files, permissions, ownership and symlinks. For a database, restore using its documented backup method and run a read-only query against the test instance. A raw copy of a running database can miss changes that still reside in its write-ahead log.
Record the snapshot date, elapsed restore time and any credential or network access the drill needed. Repeat from a backup older than your last configuration change. With those two timings, you can give someone a realistic estimate of how long recovery would take.
Did this work on your setup, or did you spot a mistake? Send the editor a private note or leave a public note for the next reader.