ClickHouse 22.x → 25.x · self-hosted & ClickHouse Cloud
Back up ClickHouse databases on a schedule through the HTTP interface — no backup disk to configure on the server, no extra binaries, and it works the same for self-hosted servers and ClickHouse Cloud.
Tables are exported in ClickHouse’s own Native format so every type round-trips exactly, then compressed and encrypted with AES-256 before being stored on your PC, NAS, cloud bucket or SFTP server.
ClickHouse holds the analytics your product decisions run on — events, metrics, logs, billing aggregates — often billions of rows that took months to collect. BACKUP TABLE … TO Disk() needs a backup disk configured by an admin and leaves the file on the server; replication is not a backup. A scheduled, off-server copy in a format ClickHouse itself understands is.
A DROP on the wrong database, an ALTER TABLE … DELETE with the wrong condition or a botched TTL change removes months of events in seconds. A backup from last night puts the table back, schema and all.
Many ClickHouse deployments run on a single node with local NVMe. When the disk or the host dies, the only copy dies with it unless a backup was streamed to a NAS or a cloud bucket.
A ClickHouse HTTP port reachable from the internet with a weak default password is found by scanners quickly. Encrypted backups kept off the server are the clean copy you restore from.
Moving from self-hosted to ClickHouse Cloud, between clouds or between versions? Back up, point the restore at the new server, and tables are recreated with the same DDL and data.
Major version upgrades occasionally change behaviour or reject old settings. A backup taken just before the upgrade is the rollback plan for every table.
Financial and usage reports have to be reproducible later. Retention tiers keep daily, weekly, monthly and yearly copies automatically, so the data behind last quarter’s numbers is a restore away.
Everything you need to back up ClickHouse databases automatically and restore them anywhere.
The backup runs entirely over ClickHouse’s HTTP interface (port 8123, or 8443 for HTTPS). No clickhouse-backup binary, no backup disk to configure, no shell access to the host — if you can query the server, you can back it up.
Rows are exported with SELECT … FORMAT Native, ClickHouse’s own compact binary encoding. Decimal, LowCardinality, Nullable, Array, Map, DateTime64 and enums come back exactly as they were — where CSV or JSON would quietly flatten them.
Each table’s CREATE statement is captured with SHOW CREATE TABLE and stored beside its data, so a restore recreates engines, ORDER BY keys, partitions, codecs and TTLs before loading rows.
Set HTTPS to yes, use port 8443 and the default user’s password from the console, and ClickHouse Cloud backs up exactly like a self-hosted server.
system, information_schema and other internal databases are left out automatically — backing them up is meaningless and restoring them would be harmful.
Set a run time and switch on the daily, weekly, monthly or yearly tiers you want. Each tier is also its retention: keep the last 7 daily, 4 weekly and 3 monthly copies and older ones are pruned for you.
Store ClickHouse backups on your PC, a NAS share, OneDrive, Amazon S3, Wasabi, Backblaze B2, Cloudflare R2, MinIO, SFTP or FTP — and add a secondary destination so every run is copied to two places.
Files are gzipped as they stream, then encrypted with AES-256-GCM using a key derived from your password. Analytics data in a shared bucket is unreadable to anyone without it.
Try every feature of the ClickHouse backup software free for 15 days — no credit card, no hidden charges. If it fits, continue for just $9 per month, billed annually, with a 14-day money-back guarantee.
The ClickHouse Backup Tool turns a server-side backup command into a four-step wizard: connect over HTTP, choose where the backup goes, set the plan, and the software handles every run from then on.
The software exports every table of each selected database, compresses and encrypts the file, and stores it at the chosen location on every scheduled run.
Connect the tool to ClickHouse wherever it is hosted — your own server, a container, a Kubernetes cluster or ClickHouse Cloud. Only the HTTP endpoint and a login are needed:
ClickHouse installed on your own server or VPS. Connect to the HTTP interface on port 8123 with the default user (or a dedicated read-only backup user) and back up any database.
Use the HTTP port 8123, not the native port 9000 — the one mistake everyone makes.
ClickHouse Cloud services expose an HTTPS endpoint on port 8443. Paste the host from the console, use the default user’s password and switch HTTPS on.
No backup disk, no S3 credentials on the server side — the export streams to your PC.
The clickhouse/clickhouse-server image is backed up over the network — use the compose service name or the port you mapped to the host. Nothing needs to be mounted into the container.
A ClickHouse installation managed by the Altinity operator or a Helm chart is reachable through its service name inside the cluster, or through an ingress or port-forward from your PC.
ClickHouse on a Linux virtual machine — VMware, Hyper-V, Proxmox or a cloud VM — is reachable by its IP address and backed up like any other server.
A colocated or partner-hosted server is backed up over the internet from your PC. Put the HTTP interface behind TLS (port 8443) and use a read-only user for the backup job.
Recovering a ClickHouse database takes four steps in the app: choose the job, choose the point in time, choose what to do with it, review. The tool downloads the file, decrypts it, decompresses it, recreates each table from its stored DDL and streams the rows back with INSERT … FORMAT Native — into the original database or a new one, on any ClickHouse server you can reach over HTTP. Press play to watch every step.
Restoring into a fresh database is the safest rehearsal: create events_test, restore into it and query it side by side with production before you touch anything live.
The ClickHouse backup tool is a desktop application, not a hosted service — it runs on your machine and writes each backup straight to the storage you picked. Nobody charges you per gigabyte, and no copy of your ClickHouse data ever sits on somebody else’s server.
| Capability | Prapl SQL Backup Tool | Other Tools |
|---|---|---|
| Backup Automation | Automatically Scheduled | Require manual setup |
| Deployment Support | Self-hosted, Docker, Kubernetes, VMs & ClickHouse Cloud — HTTP only | Limited |
| Storage Destination | Local/NAS, OneDrive, S3, Wasabi, Backblaze, R2, MinIO, SFTP & FTP | Limited storage options |
| Data security | AES-256 before the file leaves your PC | Good |
| Backup Compression | Yes | Supported but limited |
| Backup Monitoring | Dashboard, email & cloud alerts | No |
| Setup Process | Simple wizard, four steps | Complex |
| You hold the keys | Always | No |
| Storage cost | Your own storage · no per-GB fee | Often rented per GB |
| Price | start from $9/month | start from $39/month |
ClickHouse sits under applications where downtime and data loss have real consequences. This backup tool exists to make regular backups effortless, remove the manual steps people forget, and make sure a restorable copy of your data is always within reach when something goes wrong.
01. ExperienceYou should always know how your backups are made and protected. The ClickHouse backup workflow is simple, documented on this page step by step, and built on ClickHouse’s own, publicly documented interfaces rather than on anything proprietary or hidden.
02. AuthoritativenessEvery backup is made with interfaces ClickHouse documents and supports: the HTTP interface for transport, SHOW CREATE TABLE for schema, and the Native format for rows in both directions. On top of that the tool adds streaming compression and AES-256-GCM encryption before the file reaches its destination.
03. ExpertiseYour ClickHouse backup belongs to you, not to the software. Files are encrypted before they are stored and only your key can unlock them. The tool keeps no password and no hidden access to your backups — they remain under your control, wherever you decide to keep them.
04. TrustworthinessSQLBackup builds directly on ClickHouse’s own, documented interfaces. Verify our approach against the official docs:
Native) — the binary format that round-trips every column type exactly.BACKUP command, and why an off-server copy is still needed..chdump) holding each table’s SHOW CREATE TABLE DDL followed by its rows in Native formatAES-256-GCM, key via scrypt, per-file salt, per-chunk nonce · secrets in the Windows Credential ManagerOne flat price covers every engine on the machine. Explore the others:
Create a backup of your ClickHouse data and save it to local or cloud storage. Download the ClickHouse Backup Tool and use every feature free for 15 days — no credit card required. If it fits, subscribe for just $9/month with a 14-day money-back guarantee.