Aerospike asrestore record-count verification after namespace restore

The goal is to confirm that a namespace restored with asrestore contains the expected records without silently merging stale or missing data. Aerospike open-source tooling does not automatically compare backup contents against the restored cluster at the record level, and asrestore can write into a non-empty namespace without removing records created after the backup.

Because record-count parity alone may not prove logical equivalence, it is unclear whether comparing namespace counts through asinfo or asadm is sufficient, or whether application-level spot checks and checksums are required for each restored set. The answer may also depend on whether the deployment uses Community Edition or Enterprise Edition, since consistency guarantees differ between editions.

What validation approach provides adequate confidence after an asrestore operation? Is record-count comparison enough, or should teams perform primary-key spot checks against the source system? Are there edition-specific flags that affect post-restore verification?