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:

exo x get-dbaas-service-clickhouse my-clickhouse -z ch-gva-2 -q 'backups'

Fork the service

Create a new service with fork-from-service 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.

echo '{"plan":"startup-16","ip-filter":["<your-ip>/32"],"fork-from-service":"my-clickhouse"}' | \
  exo x create-dbaas-service-clickhouse my-clickhouse-fork -z ch-gva-2

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

exo x get-dbaas-service-clickhouse my-clickhouse-fork -z ch-gva-2

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

echo '{"plan":"startup-16","ip-filter":["<your-ip>/32"],"fork-from-service":"my-clickhouse","recovery-backup-name":"2026-08-04T11:34:26+00:00"}' | \
  exo x create-dbaas-service-clickhouse my-clickhouse-fork -z ch-gva-2

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.

echo '{"plan":"startup-16"}' | \
  exo x update-dbaas-service-clickhouse my-clickhouse -z ch-gva-2

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®