Which Verification Method Best Confirms Memcached Restore Integrity?

Goal

The goal is to confirm that data recovered into a fresh Memcached instance matches the original dataset after a backup and restore cycle.

Constraints

Because Memcached has no native persistence, the only available snapshot methods rely on external tools like memcached‑tool or mcp, which may miss items evicted under memory pressure.

Uncertainty

Additionally, there is no built‑in checksum or integrity check; verification currently depends on external scripts that compare key/value sets or replay traffic, raising uncertainty about completeness.

Questions

Which verification strategy—post‑restore key‑by‑key comparison, replaying a memtier‑benchmark log, or a custom checksum mechanism—provides the most reliable evidence of data integrity?
Does the snapshot process guarantee that all in‑memory items are captured before a restart, or must we implement additional safeguards?
Should Memcached eventually expose a dedicated persistence API to resolve these ambiguities?