Backups

Conceptual model for backups: scope by Service type, environments, and where task guides live.

Written By Zoro

Last updated 3 days ago

Backups in dFlow

Backups in dFlow are not a separate top-level object in the Application → Environment → Service model. Instead, backup behavior is scoped to the kind of thing you run, especially database Services and persistent volumes, plus platform-level expectations when you self-host the control plane.

What you are protecting

  • Database Services: Primary candidate for scheduled or on-demand backups and restore flows; credentials and connection details stay tied to the Service in its Environment.
  • App and Docker Services: Rely on Git, images, and configuration in dFlow for reproducibility; volumes hold data that may need explicit backup strategy if your app writes local state.
  • Self-hosted control plane: Your Organisation data, dashboard state, and configuration may require infrastructure backups separate from customer workloads; treat the install guide as source of truth.

Relationship to deployments

A deployment replaces runtime bits; it does not automatically replace database files or volume contents. Plan backups when losing the disk would hurt, not only when you redeploy.

See also