Ensuring No Data Loss During Zero‑Downtime InfluxDB 2.x Migration

Zero‑Downtime Migration Using InfluxDB 2.x Backup

We want to move a small application’s data from one InfluxDB 2.x instance to another without interrupting its write traffic. The plan is to run influx backup --incremental while writes continue, then restore the snapshot to a fresh node and switch writes over. The key uncertainty is whether the incremental backup captures points that are being written during the backup window, and how to guarantee that the final set of writes is not lost.

Specifically, we need to know:

• Does an influx backup --incremental include all writes that occur during its execution, or are those in‑flight writes excluded?
• What mechanisms (if any) does InfluxDB provide to replay or recover the tail of writes that happen after the last incremental backup but before the cutover?
• Is there an official recommendation for the timing of the final full backup relative to the cutover to ensure a consistent, point‑in‑time state?