Limits of Consul Snapshot: Agent‑Level Data Exclusion and Restoration Options

Goal

Ensure that a Consul cluster can be fully recovered, including both server‑side state and agent‑specific data such as local service definitions and intentions, after a disaster.

Constraints / Uncertainty

The built‑in consul snapshot command captures a consistent copy of the server raft state but deliberately omits agent‑level data. Administrators must decide whether to supplement snapshots with a separate backup mechanism for agent data, and how to verify that the supplemental data is correctly restored.

Questions remain about the supported way to back up agent data, the impact of version differences on that data, and the verification steps needed after a combined restore.

• What is the recommended method to back up and restore agent‑specific data (local service definitions, intentions) alongside Consul snapshots?
• Are there any version compatibility considerations when restoring agent data across Consul minor releases?
• How should administrators verify that agent data has been correctly reinstated after a snapshot restore?