One isolated database restore checked for data and schema integrity

What was measured

One native Cloudflare D1 Time Travel restore on an isolated synthetic-only database, followed by row-level and schema-integrity checks. The database had no application binding.

Instrument: Native restore receipts and database row, schema, index and foreign-key queries

Recorded findings

1. One isolated synthetic database restore returned its saved baseline message and sent notification job; the restored job retained one recorded attempt and no error, all eleven outbox columns and the retry index were present, and the foreign-key check reported no errors.

   n=1; 2026-10-03 to 2026-10-03; method: Created an unbound database with the contact and outbox schema and synthetic baseline rows, retained a baseline restore bookmark, changed the fixture, performed the native restore, and compared restored rows, fields, index and foreign-key integrity with the baseline.; recorded value: 1 isolated synthetic database restore

Limits and privacy

• The rehearsal did not restore or copy production customer data.
• One isolated restore does not establish production recovery time, recovery point objectives, availability or behaviour at production data volumes.
• Restored database state does not prove that downstream messages can be replayed safely or that external side effects were reversed.
• Application reconnection, live traffic and mail-provider recovery were outside this observation.

Anonymisation: Database identifiers, restore bookmarks, message contents, addresses, account identifiers and private operating details are excluded.

This record is primary evidence from Hallermann Consulting. Its findings should not be extrapolated beyond the stated sample, period and method.