diff --git a/guides/backup-restore-clickhouse.md b/guides/backup-restore-clickhouse.md
index 8f17fa3..9922faf 100644
--- a/guides/backup-restore-clickhouse.md
+++ b/guides/backup-restore-clickhouse.md
@@ -6,14 +6,15 @@ Guide to backing up and restoring `plausible_events_db`. Based on ["Backup and R
 
 ### Plan
 
-1. dump contents of the Plausible tables (events, sessions, imported\_\*) to files in a mounted volume
-1. load dumps from the mounted volume into `plausible_events_db`
+1. dump contents of the Plausible tables to a file
+1. optionally copy that file to a new host
+1. restore the tables from that file into `plausible_events_db`
 
 ---
 
 ### Backup
 
-1. Add backup config to allow reading backup files in the ClickHouse container
+1. Add backup config to allow reading and writing backup files in the ClickHouse container
 
 ```console
 $ touch clickhouse/backups.xml
@@ -21,115 +22,59 @@ $ touch clickhouse/backups.xml
 
 ```xml
 <clickhouse>
-    <storage_configuration>
-        <disks>
-            <backups>
-                <type>local</type>
-                <path>/backups/</path>
-            </backups>
-        </disks>
-    </storage_configuration>
-    <backups>
-        <allowed_disk>backups</allowed_disk>
-        <allowed_path>/backups/</allowed_path>
-    </backups>
+  <backups>
+    <allowed_path>/backups/</allowed_path>
+  </backups>
 </clickhouse>
 ```
 
-2. Add backups volume to `plausible_events_db` in your `docker-compose.yml`
+2. Mount new configuration to volume to `plausible_events_db` in your `docker-compose.yml`
 
 ```diff
   plausible_events_db:
-    image: clickhouse/clickhouse-server:22.6
+    image: clickhouse/clickhouse-server:23-alpine
     volumes:
       - event-data:/var/lib/clickhouse
       - ./clickhouse/:/etc/clickhouse-server/config.d/
-+     - ./clickhouse-backups:/backups
 ```
 
-3. Stop relevant containers to avoid writing to old `plausible_events_db`
+3. Dump old `plausible_events_db` contents to a backup file
 
 ```console
-> docker compose stop plausible plausible_events_db
-[+] Running 2/2
- ⠿ Container hosting-plausible-1            Stopped           6.5s
- ⠿ Container hosting-plausible_events_db-1  Stopped           0.2s
+> docker compose exec plausible_events_db sh -c "clickhouse-client -q 'BACKUP DATABASE plausible_events_db TO File(\'/backups/plausible_events_db.zip\')'"
 ```
 
-4. Restart `plausible_events_db` container to attach volume
+4. Copy the dump to the host
 
 ```console
-> docker compose up plausible_events_db -d
-[+] Running 1/1
- ⠿ Container hosting-plausible_events_db-1  Started           0.3s
+> docker compose cp plausible_events_db:/backups/plausible_events_db.zip plausible_events_db.zip
 ```
 
-5. Dump old `plausible_events_db` contents to backup files
+5. (Optional) verify backup went OK
 
 ```console
-> docker compose exec plausible_events_db sh -c "clickhouse-client --query 'BACKUP TABLE plausible_events_db.events TO Disk('backups', 'events.zip')'"
-> docker compose exec plausible_events_db sh -c "clickhouse-client --query 'BACKUP TABLE plausible_events_db.sessions TO Disk('backups', 'sessions.zip')'"
-> docker compose exec plausible_events_db sh -c "clickhouse-client --query 'BACKUP TABLE plausible_events_db.imported_visitors TO Disk('backups', 'imported_visitors.zip')'"
-
-# etc.
+> unzip -l plausible_events_db.zip
 ```
 
-**TODO:** script
-
-6. (Optional) verify backup went OK
-
-```console
-> ls backups
-events.zip  sessions.zip  imported_visitors.zip ...
-```
-
-7. Move the backups somewhere, like a different host
+6. Move the dump somewhere, like a different host
 
 ### Restore
 
-1. Ensure relevant containers are stopped
+1. Copy the dump into the container
 
 ```console
-> docker compose stop plausible plausible_events_db
-[+] Running 2/2
- ⠿ Container hosting-plausible-1            Stopped           0.0s
- ⠿ Container hosting-plausible_events_db-1  Stopped           0.2s
+> docker compose cp plausible_events_db.zip plausible_events_dh:/backups/plausible_events_db.zip
 ```
 
-3. Ensure backup config from step 1 and backups mount from step 2 are still present.
-
-4. Load data into from backups. **TODO:** User + permissions
+2. Restore
 
 ```console
-> docker compose exec plausible_events_db sh -c "clickhouse-client --query 'RESTORE TABLE plausible_events_db.events FROM Disk('backups', 'events.zip')'"
-> docker compose exec plausible_events_db sh -c "clickhouse-client --query 'RESTORE TABLE plausible_events_db.sessions FROM Disk('backups', 'sessions.zip')'"
-> docker compose exec plausible_events_db sh -c "clickhouse-client --query 'RESTORE TABLE plausible_events_db.imported_visitors FROM Disk('backups', 'imported_visitors.zip')'"
-
-# etc.
+> docker compose exec plausible_events_db sh -c "clickhouse-client -q 'RESTORE DATABSE plausible_events_db FROM File(\'/backups/plausible_events_db.zip\')'"
 ```
 
-6. Start all other containers
+3. (Optional) Remove backups from the container and the host
 
 ```console
-> docker compose up -d
-[+] Running 4/4
- ⠿ Container hosting-plausible_events_db-1  Running           0.0s
- ⠿ Container hosting-mail-1                 Running           0.0s
- ⠿ Container hosting-plausible_db-1         Started           0.5s
- ⠿ Container hosting-plausible-1            Started           0.5s
-```
-
-7. (Optional) Remove backups from `docker-compose.yml` and your filesystem
-
-```diff
-  plausible_events_db:
-    image: clickhouse/clickhouse-server:22.6
-    volumes:
-      - event-data:/var/lib/clickhouse
-      - ./clickhouse/:/etc/clickhouse-server/config.d/
--     - ./clickhouse-backups:/backups
-```
-
-```
-> rm -rf ./clickhouse-backups
+> docker compose exec plausible_events_db rm -rf /backups/plausible_events_db.zip
+> rm plausible_events_db.zip
 ```