Recover data from a verified independent copy ​

Coordinator DB does not provide a Keeper snapshot service or a Keeper recovery command. For a database that cannot be opened or read reliably, use a previously verified independent database copy or a logical export. Do not apply another product's snapshot repair instructions.

Preserve evidence first ​

Stop the process using the affected database before manipulating its files. Keep the damaged source intact for investigation. Do not overwrite the only available copy with a recovery attempt, and do not open one database file simultaneously from separate processes.

Validate an independent replacement ​

Place the selected known-good copy at a new path and start an independent instance with separate listener addresses. Confirm the expected tables, row counts and representative queries. Record the point represented by the copy so users understand which later writes may be absent.

If only logical exports are available, recreate explicit schemas and import them into a fresh database. Validate type conversions and the export's recorded source boundary before accepting application traffic.

The documented VACUUM INTO operation creates a copy from a readable supported source; it is not a repair command for arbitrary damaged bytes. Keep a regular, tested copy procedure outside the incident itself.

See database copy restrictions, local copy procedure and configuration paths.