Cut over: migrate from Dragonfly to KiviDB

Cut over. Migrate to KiviDB: Move from Redis, Valkey, ElastiCache, Redis Cloud, Aiven, Aerospike, Hazelcast and more: getting the data out, loading it, cuttin

  1. Rehearse with a copy, and time it.

  2. Recreate search indexes on KiviDB (FT.CREATE) ahead of time if you use them; they index keys as they arrive.

  3. Stop writes to Dragonfly: stop the writers, or hold them at the server while reads continue:

    redis-cli -h dragonfly.internal CLIENT PAUSE 300000 WRITE   # up to 5 minutes

    Make the pause longer than the copy takes. CLIENT UNPAUSE ends it early, for a rollback.

  4. Take the copy: SAVE RDB and load it, or run RedisShake scan to the end.

  5. Verify (below).

  6. Point the clients at KiviDB and restart or reload them.

  7. Keep Dragonfly, without writes, until you are sure. Rolling back before clients have written to KiviDB is pointing them back.