Migrating to Exoscale Managed Valkey

WARNING
Due to the fact that migrations always involve interaction with third-party services running outside of Exoscale, only best-effort support is provided on all migrations.

Migrate your Redis® or Valkey server database to our Exoscale Managed Valkey service.

There are two methods:

• the replication method
• the scan method

The migration first attempts to use the replication method. If the replication method fails, it uses the scan method.

The replication method is preferred for production databases because it allows for the migration of data with minimal downtime. The scan method is slower and iterates over all keys, one database at a time.

Prerequisites

• A target Redis service - a new or an existing service.
• The hostname, port and password of the source Redis service.
• The source Redis service must be secured with SSL/TLS, which is the default for migration. Refer to Redis TLS support
• A publicly accessible source Redis service (you might need to set a bind parameter to a publicly reachable network interface in your Redis configuration file). Any firewalls need to be open on port TCP 6379 if using the default to allow traffic from the source to the target servers. Also pay attention to other protections that can restrict connections: SELinux should be disabled or set in permissive mode for the duration of the migration on the source server.
• The number of Redis databases from source to target needs to match. Use the command redis-cli config get databases. By default, Redis has 16 databases. If you are migrating more databases, adjust accordingly on the target with the command in the section below and create the target service first before migration.