This guide explains how to set up a separate Redis server on a Google Cloud Platform (GCP) Linux VM and connect CloudM Migrate to it. A separate Redis server is not required for every migration, but it is recommended for large migrations (25,000+ users or 10 million+ objects). It takes the migration cache off the primary server, which improves performance and stability.
1. Prerequisites and VM setup
This guide assumes you are familiar with GCP and can create a virtual machine.
- Platform: Google Cloud Platform (GCP)
- Operating system: Ubuntu 24.04 LTS (not a Pro version)
- Disk type: Standard or Balanced
- VM specification: size the CPUs, memory and disk to the scale of your migration
To create the VM:
- Sign in to the Google Cloud Console.
- Create a VM instance running Ubuntu 24.04 LTS in the same subnet as your CloudM Migrate servers. The servers must be able to reach each other directly.
- Choose a machine type and disk size that can handle the expected load.
- Connect to the VM over SSH, from a terminal or the GCP console.
2. Install and configure Redis
Install Redis
Run the following commands on the VM:
sudo apt-get update
sudo apt-get install redis-server
sudo systemctl enable redis-server.service
Check that Redis is running. A successful response is PONG.
redis-cli ping
Allow connections and set a password
By default, Redis only accepts connections from the machine it runs on. To let your CloudM Migrate servers connect, you need to change the bind address and set a password.
- Open the Redis configuration file:
sudo nano /etc/redis/redis.conf - Find the
bindline and change it frombind 127.0.0.1tobind 0.0.0.0so Redis accepts connections from other machines. - Find the
requirepassline, uncomment it and set a strong password:requirepass your_strong_password - Save and close the file (Ctrl+X, then Y, then Enter).
- Restart Redis to apply the changes:
sudo systemctl restart redis-server
Always set a password. Do not disable protected mode instead, as that leaves Redis open to anyone who can reach the server. Make sure your GCP firewall rules only allow your CloudM Migrate servers to reach the Redis port (6379).
If Redis does not start, check the log:
sudo tail -f /var/log/redis/redis-server.log
3. Configure CloudM Migrate
Point your CloudM Migrate installation at the new Redis server.
- On your primary migration server, disable the local Redis service to prevent conflicts.
- Open the CloudM Migrate Service Manager.
- In the Redis Server Location field, enter the internal IP address or hostname of the Redis server.
- Enter the password you set in the Redis Password field.
- Click Update Configuration.
- Restart the CloudM Migrate service to apply the new configuration.