Migrate from a Redis to Valkey cluster

If you previously used Redis, you can migrate from this database to Valkey in one of the following ways:

• Smooth migration — without shutting down the BRIX application.
• Migration with downtime — requiring the BRIX application to be stopped.

Smooth migration from the Redis cluster to the Valkey cluster

For smooth migration:

1. Use additional node. On this node, install Valkey as specified from the first to the fourth steps in the Valkey cluster article.
2. Change the BRIX parameters by specifying the connection string to Valkey:

• Connection string for Valkey:

redis://:SecretPassword@valkey-server1.your_domain:26379,valkey-server2.your_domain:26379,valkey-server3.your_domain:26379/0?masterName=mymaster

• Connection string for Valkey in case of access by password only:

redis://:SecretPassword@valkey-server1.your_domain:26379,valkey-server2.your_domain:26379,valkey-server3.your_domain:26379/0?masterName=mymaster&sentinelUsername=default&sentinelPassword=SecretPassword

• Connection string for Valkey with TLS/SSL:

rediss://:SecretPassword@valkey-server1.your_domain:26379,valkey-server2.your_domain:26379,valkey-server3.your_domain:26379/0?&masterName=mymaster

• Connection string for Valkey with TLS/SSL in case of access by password only:

rediss://:SecretPassword@valkey-server1.your_domain:26379,valkey-server2.your_domain:26379,valkey-server3.your_domain:26379/0?masterName=mymaster&sentinelUsername=default&sentinelPassword=SecretPassword

3. After successfully connecting to Valkey, disable the Redis server to free up system resources. It is no longer in use.

Migration from Redis to Valkey with BRIX application downtime

To migrate from Redis to Valkey using the current Redis server:

1. Stop all BRIX services and wait for them to complete. To do this, use the command:

kubectl scale deploy --replicas=0 --all [-n <elma365-namespace>]

2. Stop all Redis and Sentinel services:

sudo systemctl disable --now redis-server
sudo systemctl disable --now redis-sentinel

3. Install Valkey as specified from the first to the fourth steps in the Valkey cluster article.

4. Start all BRIX application services with the command:

kubectl scale deploy --replicas=1 --all [-n <elma365-namespace>]

Was this helpful?

Thanks for your feedback!

Please specify why:

Recommendations did not help meArticle is hard to understandDidn`t answer my questionContent does not match the topicOther

How we can improve it?

YesNo

Please specify whyRecommendations did not help meArticle is hard to understandDidn`t answer my questionContent does not match the topicOther

Found a typo? Select it and press Ctrl+Enter to send us feedback