Restore Workflows, Validation, Point-in-Time/Transaction-Log Reasoning, and Isolated Recovery Testing

Learning outcomes

Reproducible AtlasMart setup

The drill adds one tiny course-owned marker so recovery correctness has a deterministic invariant even if your earlier AtlasMart graph has grown. The marker is not a substitute for business reconciliation; it is a canary.

CYPHER 25
CREATE CONSTRAINT recovery_marker_id IF NOT EXISTS
FOR (m:RecoveryMarker) REQUIRE m.markerId IS UNIQUE;
MERGE (c:Customer {customerId:'C-1001'})
ON CREATE SET c.name = 'Mina Rahimi'
MERGE (m:RecoveryMarker {markerId:'DR-CH16-001'})
SET m.createdAt = datetime('2026-09-09T17:00:00Z'),
    m.expectedState = 'before-dump',
    m.exercise = 'chapter-16'
MERGE (c)-[:HAS_RECOVERY_MARKER]->(m);
MATCH (m:RecoveryMarker {markerId:'DR-CH16-001'})
RETURN m.markerId, m.expectedState;

1. Restore is the test that turns a file into evidence

AtlasMart’s backup is not “verified” until operators can build a usable database from it without relying on the original store. The safest drill creates a new Docker volume and new ports so no command can silently overwrite atlasmart-neo4j-data.

2. Inspect the archive before load

neo4j-admin database load --info reads archive information without loading it. Keep the previously recorded hash beside this metadata.

docker run --rm \
  -v "$PWD/neo4j-dr/backups:/backups" \
  neo4j/neo4j-admin:2026.07.1 \
  neo4j-admin database load --info --from-path=/backups neo4j
sha256sum ./neo4j-dr/backups/neo4j.dump

3. Load into a new volume

Use a separate restore volume. The admin image writes the recovered store there; afterward a separate Neo4j container exposes it on alternate loopback ports. The local credential is freshly supplied for the disposable restored DBMS; do not assume a database dump is a complete identity/secrets backup.

docker rm -f atlasmart-neo4j-restore 2>/dev/null || true
docker volume rm atlasmart-neo4j-restore-data 2>/dev/null || true
docker volume create atlasmart-neo4j-restore-data

docker run --rm \
  -v atlasmart-neo4j-restore-data:/data \
  -v "$PWD/neo4j-dr/backups:/backups" \
  neo4j/neo4j-admin:2026.07.1 \
  neo4j-admin database load neo4j --from-path=/backups --overwrite-destination=true

docker run -d --name atlasmart-neo4j-restore \
  -p 127.0.0.1:7475:7474 -p 127.0.0.1:7688:7687 \
  -v atlasmart-neo4j-restore-data:/data \
  -e NEO4J_AUTH=neo4j/atlasmart-course-2026 \
  neo4j:2026.07.1

4. Reconcile state, not just process health

Wait until Bolt is ready, then query the deterministic recovery canary and capture broad counts. In a real system, compare the restored graph to independently recorded source totals/orders/payments and external-system checkpoints.

docker exec atlasmart-neo4j-restore cypher-shell \
  -a bolt://127.0.0.1:7687 -u neo4j -p atlasmart-course-2026 \
  "CYPHER 25 MATCH (m:RecoveryMarker {markerId:'DR-CH16-001'}) RETURN m.expectedState;"

CYPHER 25
MATCH (n) RETURN count(n) AS nodes;
MATCH ()-[r]->() RETURN count(r) AS relationships;
MATCH (c:Customer {customerId:'C-1001'})-[:HAS_RECOVERY_MARKER]->(m:RecoveryMarker {markerId:'DR-CH16-001'})
RETURN c.customerId, m.expectedState;
SHOW CONSTRAINTS;

5. Consistency check and application smoke test are different layers

Stop the restore container before checking its store directly. A clean store check does not validate API permissions, driver routing, Cypher compatibility or business behavior.

docker stop atlasmart-neo4j-restore
docker run --rm \
  -v atlasmart-neo4j-restore-data:/data \
  neo4j/neo4j-admin:2026.07.1 \
  neo4j-admin database check neo4j

6. Point-in-time reasoning belongs to the Enterprise backup chain

A differential backup artifact contains transaction logs that can be replayed onto the full store during restore. Current Enterprise restore accepts --restore-until by transaction ID or UTC timestamp. The boundary is precise: transaction-ID recovery stops before the specified transaction.

# Licensed/self-managed Enterprise example only:
neo4j-admin database restore \
  --from-path=/srv/neo4j-backups \
  --restore-until="2026-09-09 16:45:00" \
  atlasmart

7. Measure RPO and RTO from evidence

8. Cleanup/reset

docker rm -f atlasmart-neo4j-restore 2>/dev/null || true
docker volume rm atlasmart-neo4j-restore-data
# Keep the source volume and backup artifact for the next lessons.
docker start atlasmart-neo4j

Production judgment

Summary and next step

A restore drill proves much more than archive creation. Lesson 3 treats the artifact itself as high-value sensitive data and builds off-host, retention, immutability and chain-of-custody evidence around it.

Authoritative references

• Current Neo4j versions — Current server and 5.26 LTS release snapshot.
• Backup and restore — Edition-aware entry point for dump/load, online backup, restore and planning.
• Backup and restore planning — RPO/RTO, backup mode, storage location, cadence and retention planning.
• Back up an offline database — neo4j-admin database dump semantics and Community offline boundary.
• Restore a database dump — neo4j-admin database load semantics, overwrite rules and edition differences.
• Back up an online database — Enterprise full/differential backup artifacts and chain semantics.
• Restore a database backup — Enterprise recovery of backup chains and restore-until predicates.
• Check database consistency — neo4j-admin database check for stores, dumps and recovered full backups.
• Transaction logging — Transaction-log retention, checkpointing and pruning behavior.
• Store formats — Current aligned/block formats, limits and legacy-format deprecation.
• Migrate a database — neo4j-admin database migrate and store-format migration boundaries.
• System requirements — Supported Java/runtime and platform requirements for current Neo4j.
• APOC installation — APOC/server release compatibility and restart/deployment coupling.
• GDS compatibility — Graph Data Science and Neo4j version compatibility matrix.
• Python driver installation — Current 6.x driver/server compatibility baseline.