redis-cli --rdb, and import an RDB file with RedisShake, which replays its keys into the running database. Both work over the database’s external connection. Redis can’t load an RDB file sent over the network on its own, which is why the import needs RedisShake; Sevalla uses it for its own Redis restores too.
Before you begin
- Create the database on Sevalla first, on the same Redis version as the source or a newer one. See Create a database.
- Enable the external connection. If IP restrictions are on, allow your IP address.
- To export, install
redis-cliat the database’s major version or newer: on macOSbrew install redis, on Debian or Ubuntu theredis-toolspackage from packages.redis.io, on Windows inside WSL. - To import, download RedisShake 4.6 or later for your system from its releases and unpack it.
- Copy the Host, Port and Password from the database’s Overview tab, under Connection > External. See Find the connection details.
- With TLS on, the external connection accepts only TLS: on the Networking tab, click Download CA certificate and save the file next to where you run the commands.
orders-db-k3j4h.ext.sevalla.app, port 20145 and CA certificate orders-db-k3j4h-ca.crt; replace them, and <password>, with yours. For a database without TLS, leave out --tls and --cacert.
Export a database
redis-cli asks the server for a point-in-time snapshot over the replication protocol and writes it to orders-cache.rdb. The file holds every logical database (db0, db1 and so on). While the snapshot is taken, the server forks as it does for a background save, so its memory use rises briefly. To export from another Redis server, run the same command with its host, port and password.
Import a database
1
Write the configuration
Save this as RedisShake encrypts the connection with
shake.toml next to the redis-shake binary, with the path to your RDB file and the Sevalla database’s external host, port and password:shake.toml
tls = true but doesn’t verify the server’s certificate. For a database without TLS, set tls = false.2
Run RedisShake
3
Check the keys
Open the database’s Redis studio tab and look through the Keys page, or count the keys:
rdb_restore_command_behavior = "rewrite" under an [advanced] section of shake.toml; to keep them, use "skip".