Neo4j Admin Upgrade: Recovering from an In‑Place Upgrade Failure

Goal

The objective is to restore a Neo4j instance to a consistent state after an in‑place neo4j-admin upgrade that did not complete successfully.

Constraints & Uncertainty

Neo4j’s neo4j-admin backup does not capture the transaction log, so changes committed after the backup but before the upgrade can be lost. A failed in‑place upgrade may leave the store in an inconsistent format that cannot be automatically reverted. Administrators must decide whether to rely solely on a pre‑upgrade backup, attempt manual cleanup, or apply another recovery strategy.

Unresolved Questions

1. Is there a documented method to revert an in‑place upgrade without restoring from a full backup?
2. What verification steps can confirm the integrity of the data directory after a partial upgrade?
3. Can the transaction log be recovered post‑failure to mitigate data loss, and if so, how?