Fork and restore from Managed ClickHouse® backups

Restore a Managed ClickHouse® service by forking it: the fork is a new service created from the backup of an existing service. The source service keeps running and is not modified.

List the available backups

Backups are part of the service description. List them with their names, dates and sizes:

exo dbaas show my-clickhouse -z ch-gva-2 --backups

Fork the service

Create a new service with --clickhouse-fork-from set to the name of the source service. Pick a plan with at least as many nodes as the source: startup-16 below matches a Startup source, a Business source needs a Business or Premium plan.

exo dbaas create clickhouse startup-16 my-clickhouse-fork -z ch-gva-2 \
  --clickhouse-fork-from my-clickhouse \
  --clickhouse-ip-filter <your-ip>/32

Watch the fork until the state is running, then connect to it and check your data:

exo dbaas show my-clickhouse-fork -z ch-gva-2 --output-template '{{ .State }}'

To fork from an older daily backup instead, add --clickhouse-recovery-backup-name with one of the backup names listed above:

exo dbaas create clickhouse startup-16 my-clickhouse-fork -z ch-gva-2 \
  --clickhouse-fork-from my-clickhouse \
  --clickhouse-recovery-backup-name 2026-08-04T11:34:26+00:00 \
  --clickhouse-ip-filter <your-ip>/32

The API validates the name and refuses the creation with Cannot find such backup to recover from. when it does not match an existing backup.

exo dbaas update my-clickhouse -z ch-gva-2 -f --plan startup-16

Once the new fork service is running, you can set up your application’s connection settings to point to this new fork service.

Related pages

• Disaster recovery in Managed ClickHouse®