Data loss in Influxdb3 database, but files still available

InfluxDB 3
1

InfluxDB 3 Enterprise 3.12.2 (Home license), single node, PachaTree: lost V2 checkpoints, need to rebuild compactor lineage

A crash-consistent Proxmox VM backup (no guest agent, so no fs-freeze) left 0-byte files from the moment of the snapshot: all three cluster0/cv2/checkpoints/*.ptv2chk.lz4, several pt_snapshots/*.ptsnap, gen0/*.pt, pt_wal/*.pt and a few cv2/windows/.../run_sets/*.idx / files/*.pt. The same pattern exists in every nightly backup.

Startup failed with Failed to decompress V2 checkpoint: expected another byte, found none. After moving all 0-byte files aside:

  • --mode=all starts with “no checkpoint found, starting empty” and queries return num_rows=0. The orphan sweep (mode=armed) then ran with checkpoint_sequence=0, reachable_files=0, live_run_sets=0 and listed almost all cv2/windows files (data back to Feb 2026) as candidates. Nothing has been deleted; I stopped the server and moved that sweep_audit pass aside.
  • --mode=ingest,query,process runs and new writes are queryable, but all historical data is invisible.

All ~4,400 compacted files (PACH magic, ~26 GB) are still on disk.

  1. How can I rebuild the V2 checkpoint/lineage from the existing cv2/windows files?
  2. How can I safely disable the orphan sweep until then?
  3. Is INFLUXDB3_UPGRADE_PACHA_TREE=true still needed after migration?
1 Like