Plan multiple Accelerator instances.

Independent instances

Each instance keeps its own cache, sessions, CDC progress and in-memory queue. Use the same database endpoint and an external TCP load balancer to route application connections.

Copy configuration

Export settings, securely transfer the backup, and import it on the destination. Review listener ports, TLS and error-log paths, telemetry identity and engine-specific CDC identities before starting the new instance.

accel export /secure/backups/accelerator.sqlite3
accel --instance /srv/accelerator-b import /secure/backups/accelerator.sqlite3

CDC identities

Assign a distinct cdc_server_id to each MySQL or MariaDB instance. Configure the required replication or consumer resources for the other engines. Each instance consumes changes for its local cache.

Routing and recovery

Configure external health checks and application reconnection. A failed instance’s cache, queued writes and sessions do not move to another instance. Keep database availability and backup procedures in your deployment plan.