testWhileIdle
diff --git a/docs/dcs/umn/dcs-faq-221222.html b/docs/dcs/umn/dcs-faq-221222.html
index a1e87574d..086556022 100644
--- a/docs/dcs/umn/dcs-faq-221222.html
+++ b/docs/dcs/umn/dcs-faq-221222.html
@@ -1,8 +1,8 @@
Is the Read-only Address of a Master/Standby Instance Connected to the Master or Standby Node?
-A master/standby DCS Redis 4.0/5.0/6.0 instance has a Connection Address and a Read-only Address. The connection address is used to connect to the master node of the instance, and the read-only address is used to connect to the standby node of the instance.
- For details, see Architecture of Master/Standby DCS Redis 4.0/5.0/6.0 Instances.
+ A master/standby DCS Redis 4.0 or later instance has a Connection Address and a Read-only Address. The connection address is used to connect to the master node of the instance, and the read-only address is used to connect to the standby node of the instance.
+ For details, see Architecture of Master/Standby DCS Redis Instances.
Figure 1 Instance addresses
By default, the client reads and writes data on the master node. Data is synchronized to the standby node. To implement read/write splitting, ensure that your client can distinguish between read and write requests. The client directs write requests to the read/write domain name and read requests to the read-only domain name.
diff --git a/docs/dcs/umn/dcs-migrate-0220411.html b/docs/dcs/umn/dcs-migrate-0220411.html
index f8f359a33..aab6f68d4 100644
--- a/docs/dcs/umn/dcs-migrate-0220411.html
+++ b/docs/dcs/umn/dcs-migrate-0220411.html
@@ -1,10 +1,13 @@
- Online Full Migration of Redis from Another Cloud with redis-shake
- redis-shake is an open-source Redis migration tool. Its rump mode allows you to obtain the full data of a source Redis using the SCAN command and write the data to a target Redis. This migration solution does not involve the SYNC or PSYNC command and can be widely used for migration between self-built Redis and cloud Redis.
- This section describes how to use the rump mode of redis-shake to migrate the full Redis data of another cloud service vendor at a time online to DCS.
+ Migrating from Another Cloud Online Using redis-shake
+ redis-shake is an open-source Redis migration tool. Its rump mode allows you to obtain the full data of a source Redis using the SCAN command and write the data to a target Redis. This migration solution does not involve the SYNC or PSYNC command and can be widely used for migration between self-built Redis and cloud Redis.
+ This section describes how to use the rump mode of redis-shake to migrate the full Redis data of another cloud service vendor at a time online to DCS.
Figure 1 Data flow in this solution
- Prerequisites- A DCS Redis instance has been created on the target cloud.
- An ECS has been created on the target cloud for running redis-shake.
- The ECS is in the same VPC as the DCS Redis instance and bound with an EIP.
- The rump mode does not support incremental data migration. To keep data consistency, stop writing data to the source Redis before migration.
- This solution applies only to same-database mapping and does not apply to inter-database mapping.
- If the source Redis has multiple databases (there are databases other than DB0), and your DCS instance is a cluster, this solution cannot be used. (Cluster DCS instances support only DB0.)
+
+ Notes and Constraints- The rump mode does not support incremental data migration. To keep data consistency, stop writing data to the source Redis before migration.
- This solution applies only to same-database mapping and does not apply to inter-database mapping.
- If the source Redis has multiple databases (there are databases other than DB0), and your DCS instance is a cluster, this solution cannot be used. (Cluster DCS instances support only DB0.)
- To migrate to an instance with SSL enabled, disable the SSL setting first. For details, see Transmitting DCS Redis Data with Encryption Using SSL.
+
+ Prerequisites- A DCS Redis instance has been created.
- An ECS has been created for running redis-shake. The ECS must use the same VPC as the Redis instance, and be bound to EIPs.
Procedure- Install Nginx on the ECS and the source forwarding server. The following describes how to install Nginx on an ECS running CentOS 7.x. The commands vary depending on the OS.
- Add Nginx to the Yum repository.
sudo rpm -Uvh http://nginx.org/packages/centos/7/noarch/RPMS/nginx-release-centos-7-0.el7.ngx.noarch.rpm
- Check whether Nginx has been added successfully.
yum search nginx
@@ -33,8 +36,8 @@ vi nginx.conf
If the port is being listened, Nginx has been started successfully.
Figure 3 Verification result
- - Configure Nginx forwarding for the ECS.
- Log in to the Linux ECS and run the following commands to open and modify the configuration file:
cd /etc/nginx
-vi nginx.conf
+ - Configure Nginx forwarding for the ECS.
- Log in to the Linux ECS and run the following commands to open and modify the configuration file:
cd /etc/nginx
+vi nginx.conf
- Configuration example:
stream {
server {
listen 6666;
@@ -53,7 +56,7 @@ vi nginx.conf
- Run the following command on the ECS to test the network connection of port 6666:
redis-cli -h {target_ecs_address} -p 6666 -a {password}
{target_ecs_address} is the EIP of the ECS, 6666 is the listening port of the ECS, and {password} is the source Redis password. If there is no password, leave it blank.
Figure 6 Connection example
- - Prepare the migration tool redis-shake.
- Log in to the ECS.
- Download redis-shake. Version 2.0.3 is used as an example. You can use other redis-shake versions as required.
wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.0.3-20200724/redis-shake-v2.0.3.tar.gz
+ - Prepare the migration tool redis-shake.
- Log in to the ECS.
- Download redis-shake on the ECS. Version 2.0.3 is used as an example. You can use other redis-shake versions as required.
wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.0.3-20200724/redis-shake-v2.0.3.tar.gz
- Decompress the redis-shake file.
tar -xvf redis-shake-v2.0.3.tar.gz
- Configure the redis-shake configuration file.
- Go to the directory generated after the decompression.
cd redis-shake-v2.0.3
@@ -79,7 +82,7 @@ vi nginx.conf
diff --git a/docs/dcs/umn/dcs-migrate-1117003.html b/docs/dcs/umn/dcs-migrate-1117003.html
index 419f872de..c20ec51c0 100644
--- a/docs/dcs/umn/dcs-migrate-1117003.html
+++ b/docs/dcs/umn/dcs-migrate-1117003.html
@@ -1,53 +1,44 @@
- Offline Migration of Redis Cluster from Another Cloud with redis-shake
+ Backup Import from Another Cloud Using redis-shake
redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. If the source Redis Cluster is deployed in another cloud, and online migration is not supported, you can migrate data by importing backup files.
+ If the source Redis and the target Redis cannot be connected, or the source Redis is deployed on other clouds, you can migrate data by importing backup files.
The following describes how to use redis-shake for backup migration to a DCS Redis Cluster instance.
- Importing Backup FilesIf the source Redis and the destitution Redis cannot be connected, or the source Redis is deployed on other clouds, you can migrate data by importing backup files.
- - Create a Redis Cluster instance on the DCS console.
The memory of this instance cannot be smaller than that of the source Redis.
- - Run the following command to obtain the IP addresses and port numbers of all masters of the source Redis and target Redis:
redis-cli -h {redis_address} -p {redis_port} -a {redis_password} cluster nodes
+
+Prerequisites- A DCS Redis instance has been created. Note that the memory of the DCS Redis Cluster instance cannot be smaller than that of the source cluster.
- An ECS has been created for running redis-shake. The ECS must use the same VPC, subnet, and security group as the Redis instance.
+ Procedure- Access the target Redis instance using redis-cli. Obtain the IP address and port of the master node of the target instance.
redis-cli -h {target_redis_address} -p {target_redis_port} -a {target_redis_password} cluster nodes
+- {target_redis_address}: connection address of the target DCS Redis instance.
- {target_redis_port}: port of the target DCS Redis instance.
- {target_redis_password}: password for connecting to the target DCS Redis instance.
In the command output similar to the following, obtain the IP addresses and ports of all masters.
- After Redis is installed, it runs with redis-cli. To install Redis on CentOS, run the yum install redis command.
+ - Install redis-shake on the prepared ECS.
- Log in to the ECS.
- Download redis-shake on the ECS. Version 2.0.3 is used as an example. You can use other redis-shake versions as required.
wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.0.3-20200724/redis-shake-v2.0.3.tar.gz
+ - Decompress the redis-shake file.
tar -xvf redis-shake-v2.0.3.tar.gz
+
+ If the source Redis is deployed in the data center intranet, install redis-shake on the intranet server. Export data and then upload the data to the cloud server as instructed by the following steps.
- - Prepare a cloud server and install redis-shake.
redis-shake must be able to access the target Redis and bound to an EIP.
-You can use ECS and configure the same VPC, subnet, and security group for the ECS and the DCS instance.
-Download and decompress the release version of redis-shake. (The following uses v2.1.2 as an example. You can also use other redis-shake versions.)
-
- If the source Redis is deployed in the data center intranet, install redis-shake on the intranet server. Export data and then upload the data to the cloud server as instructed by the following steps
-
- - Export the RDB file.
- Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target:
source.type = cluster
-# If there is no password, skip the following parameter.
-source.password_raw = {source_redis_password}
-# IP addresses and port numbers of all masters of the source Redis Cluster, which are separated by semicolons (;).
-source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
- - Run the following command to export the RDB file:
./redis-shake -type dump -conf redis-shake.conf
-If the following information is displayed in the execution log, the backup file is exported successfully:
-execute runner[*run.CmdDump] finished!
- If you cannot export the source Redis backup files using this method due to cloud vendors' restrictions on the SYNC and PSYNC commands, export the files on the source console or contact the source technical support.
-
-
- - Import the RDB file.
- Import the RDB file (or files) to the cloud server. The cloud server must be connected to the target DCS instance.
- Edit the redis-shake configuration file.
Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target: target.type = cluster
+ - Export the RDB file from the source Redis console. If the RDB file cannot be exported, contact customer service of the source.
- Import the RDB file.
- Import the RDB file (or files) to the cloud server. The cloud server must be connected to the target DCS instance.
- Edit the redis-shake configuration file redis-shake.conf.
vim redis-shake.conf
+Add the following information about all the masters of the target: target.type = cluster
# If there is no password, skip the following parameter.
target.password_raw = {target_redis_password}
# IP addresses and port numbers of all masters of the target instance, which are separated by semicolons (;).
-target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
+target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
# List the RDB files to be imported, separated by semicolons (;).
rdb.input = {local_dump.0};{local_dump.1};{local_dump.2};{local_dump.3}
Save and exit.
- - Run the following command to import the RDB file to the target instance:
./redis-shake -type restore -conf redis-shake.conf
+Press Esc to exit the editing mode and enter :wq!. Press Enter to save the configuration and exit the editing interface.
+ - Run the following command to import the RDB file to the target instance:
./redis-shake -type restore -conf redis-shake.conf
If the following information is displayed in the execution log, the backup file is imported successfully:
Enabled http stats, set status (incr), and wait forever.
- - Verify the migration.
After data synchronization, access the DCS Redis Cluster instance using redis-cli. Run the info command to query the number of keys in the Keyspace section to confirm that data has been fully imported.
+ - Verify the migration.
After data synchronization, access the target Redis Cluster DCS instance using redis-cli. Run the info command to query the number of keys in the Keyspace section to confirm that data has been fully imported.
If the data has not been fully imported, run the flushall or flushdb command to clear the cached data in the instance, and synchronize data again.
diff --git a/docs/dcs/umn/dcs-migrate-demo02.html b/docs/dcs/umn/dcs-migrate-demo02.html
index f7a16e9f4..a443c154e 100644
--- a/docs/dcs/umn/dcs-migrate-demo02.html
+++ b/docs/dcs/umn/dcs-migrate-demo02.html
@@ -1,83 +1,49 @@
- Self-Hosted Redis Cluster Migration with redis-shake
- redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. Data can be migrated to DCS Redis Cluster instances seamlessly because DCS Redis Cluster inherits the native Redis Cluster design.
- The following describes how to use redis-shake to migrate data to a DCS Redis Cluster instance.
- Migrating Data OnlineYou can migrate data online from a self-hosted Redis Cluster to a DCS Redis Cluster instance as long as the two clusters are directly connected or connected through a transit server.
- Data in Redis Clusters of another cloud cannot be migrated online because the SYNC and PSYNC commands are disabled by some vendors.
- - Create a Redis Cluster instance on the DCS console.
The memory of this instance cannot be smaller than that of the source Redis.
- - Prepare a cloud server and install redis-shake.
redis-shake must be able to access both the source and target Redis. Bound an EIP to the cloud server.
-You can use ECS and configure the same VPC, subnet, and security group for the ECS and the DCS instance. If the source Redis is deployed on cloud servers of another cloud, allow public access to the servers.
-Download and decompress the release version of redis-shake. (The following uses v2.1.2 as an example. You can also use other redis-shake versions.)
-
- - Locate the masters of the source and target Redis Clusters and obtain the IP addresses of the masters.
Online data migration must be performed node by node. Run the following command to query the IP addresses and port numbers of all nodes in both the source and target Redis Clusters.
-redis-cli -h {redis_address} -p {redis_port} -a {redis_password} cluster nodes
-In the command output similar to the following, obtain the IP addresses and ports of all masters.
-
- After Redis is installed, it runs with redis-cli. To install Redis on CentOS, run the yum install redis command.
-
- - Edit the redis-shake configuration file.
Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target:
-source.type = cluster
+Self-Hosted Redis Cluster Migration with redis-shake (Online)
+redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. Data can be migrated to DCS Redis Cluster instances seamlessly because DCS Redis Cluster inherits the native Redis Cluster design.
+ The following describes how to use Linux redis-shake to migrate self-hosted Redis Cluster to a DCS Redis Cluster instance online.
+ Notes and Constraints- To migrate data from a self-hosted Redis Cluster instance to a DCS Redis Cluster instance online, ensure that the source Redis is connected to the target Redis, or use a transit cloud server to connect the source and target cluster instances.
- To migrate to an instance with SSL enabled, disable the SSL setting first. For details, see Transmitting DCS Redis Data with Encryption Using SSL.
+
+ Prerequisites- If a target DCS Redis instance is not available, create one first. For details, see Creating a DCS Redis Instance.
- If you already have a DCS Redis instance, you do not need to create one again. For comparing migration data and reserving sufficient memory, you are advised to clear the instance data before the migration. For details, see Clearing DCS Instance Data. If any data exists on the target instance, duplicate data between the source and target is overwritten. If the data exists only on the target instance, the data will be retained.
+ - An Elastic Cloud Server (ECS) has been created. For details about how to create an ECS, see Elastic Cloud Server User Guide.
Select the same VPC, subnet, and security group as the DCS Redis Cluster instance, and bind EIPs to the ECS.
+ - If the source self-hosted Redis Cluster is deployed on cloud servers of another cloud, allow public access to the servers.
+
+ Obtaining Information of the Source and Target Redis Nodes- Connect to the source and target Redis instances, respectively. Connect to Redis by referring to Accessing a DCS Redis Instance Through redis-cli.
- In online migration of Redis Clusters, the migration must be performed node by node. Run the following command to query the IP addresses and ports of all nodes in both the source and target Redis Clusters.
redis-cli -h {redis_address} -p {redis_port} -a {redis_password} cluster nodes
+{redis_address} indicates the Redis connection address, {redis_port} indicates the Redis port, and {redis_password} indicates the Redis connection password.
+In the command output similar to the following, obtain the IP addresses and ports of all masters.
+
+
+
+ Configuring the redis-shake Tool- Log in to the ECS.
- Run the following command on the ECS to download the redis-shake: This section uses v2.1.2 as an example. You can also download other redis-shake versions as required.
wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.1.2-20220329/release-v2.1.2-20220329.tar.gz
+ - Decompress the redis-shake file.
tar -xvf redis-shake-v2.1.2.tar.gz
+
+ - Go to the redis-shake directory.
cd redis-shake-v2.0.3
+ - Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target:
vim redis-shake.conf
+The modification is as follows: source.type = cluster
# If there is no password, skip the following parameter.
source.password_raw = {source_redis_password}
# IP addresses and port numbers of all masters of the source Redis Cluster, which are separated by semicolons (;).
-source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
+source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
target.type = cluster
# If there is no password, skip the following parameter.
target.password_raw = {target_redis_password}
# IP addresses and port numbers of all masters of the target instance, which are separated by semicolons (;).
-target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
- Save and exit.
- - Migrate data online.
Run the following command to synchronize data between the source and the target Redis:
-./redis-shake -type sync -conf redis-shake.conf
-If the following information is displayed, the full synchronization has been completed and incremental synchronization begins.
-sync rdb done.
-If the following information is displayed, no new data is incremented. You can stop the incremental synchronization by pressing Ctrl+C.
-sync: +forwardCommands=0 +filterCommands=0 +writeBytes=0
-Figure 1 Online migration using redis-shake
- - Verify the migration.
After data synchronization, access the DCS Redis Cluster instance using redis-cli. Run the info command to query the number of keys in the Keyspace section to confirm that data has been fully imported.
-If the data has not been fully imported, run the flushall or flushdb command to clear the cached data in the instance, and synchronize data again.
- - Clear the redis-shake configuration file.
+target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
Importing Backup FilesIf the source Redis and the destitution Redis cannot be connected, or the source Redis is deployed on other clouds, you can migrate data by importing backup files.
-
- - Create a Redis Cluster instance on the DCS console.
The memory of this instance cannot be smaller than that of the source Redis.
- - Run the following command to obtain the IP addresses and port numbers of all masters of the source Redis and target Redis:
redis-cli -h {redis_address} -p {redis_port} -a {redis_password} cluster nodes
-In the command output similar to the following, obtain the IP addresses and ports of all masters.
-
- After Redis is installed, it runs with redis-cli. To install Redis on CentOS, run the yum install redis command.
-
- - Prepare a cloud server and install redis-shake.
redis-shake must be able to access the target Redis and bound to an EIP.
-You can use ECS and configure the same VPC, subnet, and security group for the ECS and the DCS instance.
-Download and decompress the release version of redis-shake. (The following uses v2.1.2 as an example.)
-
- If the source Redis is deployed in the data center intranet, install redis-shake on the intranet server. Export data and then upload the data to the cloud server as instructed by the following steps
-
- - Export the RDB file.
- Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target:
source.type = cluster
-# If there is no password, skip the following parameter.
-source.password_raw = {source_redis_password}
-# IP addresses and port numbers of all masters of the source Redis Cluster, which are separated by semicolons (;).
-source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
- - Run the following command to export the RDB file:
./redis-shake -type dump -conf redis-shake.conf
-If the following information is displayed in the execution log, the backup file is exported successfully:
-execute runner[*run.CmdDump] finished!
-
- - Import the RDB file.
- Import the RDB file (or files) to the cloud server. The cloud server must be connected to the target DCS instance.
- Edit the redis-shake configuration file.
Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target: target.type = cluster
-# If there is no password, skip the following parameter.
-target.password_raw = {target_redis_password}
-# IP addresses and port numbers of all masters of the target instance, which are separated by semicolons (;).
-target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
-# List the RDB files to be imported, separated by semicolons (;).
-rdb.input = {local_dump.0};{local_dump.1};{local_dump.2};{local_dump.3}
+ Press Esc to exit the editing mode and enter :wq!. Press Enter to save the configuration and exit the editing interface.
+
Save and exit.
- - Run the following command to import the RDB file to the target instance:
./redis-shake -type restore -conf redis-shake.conf
-If the following information is displayed in the execution log, the backup file is imported successfully:
-Enabled http stats, set status (incr), and wait forever.
-
- - Verify the migration.
After data synchronization, access the DCS Redis Cluster instance using redis-cli. Run the info command to query the number of keys in the Keyspace section to confirm that data has been fully imported.
-If the data has not been fully imported, run the flushall or flushdb command to clear the cached data in the instance, and synchronize data again.
-
+ Migrating Data OnlineRun the following command to synchronize data between the source and the target Redis: ./redis-shake -type sync -conf redis-shake.conf
+
+ If the following information is displayed, the full synchronization has been completed and incremental synchronization begins.
+ sync rdb done.
+ If the following information is displayed, no new data is incremented. You can stop the incremental synchronization by pressing Ctrl+C.
+ sync: +forwardCommands=0 +filterCommands=0 +writeBytes=0
+ Figure 1 Online migration using redis-shake
+
+ Verifying the Migration- After the data synchronization, connect to the Redis Cluster DCS instance by referring to Accessing a DCS Redis Instance Through redis-cli.
- Run the info command to check whether the data has been successfully imported as required.
If the data has not been fully imported, run the flushall or flushdb command to clear the cached data in the target instance, and migrate data again.
+ - After the verification is complete, delete the redis shake configuration file.
diff --git a/docs/dcs/umn/dcs-migrate-demo03.html b/docs/dcs/umn/dcs-migrate-demo03.html
new file mode 100644
index 000000000..c85fc0c18
--- /dev/null
+++ b/docs/dcs/umn/dcs-migrate-demo03.html
@@ -0,0 +1,64 @@
+
+
+ Self-Hosted Redis Cluster Migration with redis-shake (RDB)
+ redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. Data can be migrated to DCS Redis Cluster instances seamlessly because DCS Redis Cluster inherits the native Redis Cluster design.
+ The following describes how to use Linux redis-shake to migrate self-hosted Redis Cluster to a DCS Redis Cluster instance offline.
+ If the source Redis and the target Redis cannot be connected, or the source Redis is deployed on other clouds, you can migrate data by importing backup files.
+
+
+
+ Obtaining Information of the Source and Target Redis Nodes- Connect to the source and target Redis instances, respectively. Connect to Redis by referring to Accessing a DCS Redis Instance Through redis-cli.
- In online migration of Redis Clusters, the migration must be performed node by node. Run the following command to query the IP addresses and ports of all nodes in both the source and target Redis Clusters.
redis-cli -h {redis_address} -p {redis_port} -a {redis_password} cluster nodes
+{redis_address} indicates the Redis connection address, {redis_port} indicates the Redis port, and {redis_password} indicates the Redis connection password.
+In the command output similar to the following, obtain the IP addresses and ports of all masters.
+
+
+
+ Installing RedisShake- Log in to the ECS.
- Run the following command on the ECS to download the redis-shake: This section uses v2.1.2 as an example. You can also download other redis-shake versions as required.
wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.1.2-20220329/release-v2.1.2-20220329.tar.gz
+ - Decompress the redis-shake file.
tar -xvf redis-shake-v2.1.2.tar.gz
+
+
+ If the source cluster is deployed in the data center intranet, install redis-shake on the intranet server. Export the source cluster backup file by referring to Exporting the Backup File. Upload the backup to the cloud server as instructed by the following steps
+
+
+ Exporting the Backup File- Go to the redis-shake directory.
cd redis-shake-v2.0.3
+ - Edit the redis-shake.conf file by providing the following information about all the masters of the source:
vim redis-shake.conf
+The modification is as follows: source.type = cluster
+# If there is no password, skip the following parameter.
+source.password_raw = {source_redis_password}
+# IP addresses and port numbers of all masters of the source Redis Cluster, which are separated by semicolons (;).
+source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
+ Press Esc to exit the editing mode and enter :wq!. Press Enter to save the configuration and exit the editing interface.
+ - Run the following command to export the RDB file:
./redis-shake -type dump -conf redis-shake.conf
+If the following information is displayed in the execution log, the backup file is exported successfully:
+execute runner[*run.CmdDump] finished!
+
+
+ Importing the Backup File- Import the RDB file (or files) to the cloud server. The cloud server must be connected to the target DCS instance.
- Edit the redis-shake.conf file by providing the following information about all the masters of the target:
vim redis-shake.conf
+The modification is as follows: target.type = cluster
+# If there is no password, skip the following parameter.
+target.password_raw = {target_redis_password}
+# IP addresses and port numbers of all masters of the target instance, which are separated by semicolons (;).
+target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
+# List the RDB files to be imported, separated by semicolons (;).
+rdb.input = {local_dump.0};{local_dump.1};{local_dump.2};{local_dump.3}
+ Press Esc to exit the editing mode and enter :wq!. Press Enter to save the configuration and exit the editing interface.
+ - Run the following command to import the RDB file to the target instance:
./redis-shake -type restore -conf redis-shake.conf
+If the following information is displayed in the execution log, the backup file is imported successfully:
+Enabled http stats, set status (incr), and wait forever.
+
+
+ Verifying the Migration- After the data synchronization, connect to the Redis Cluster DCS instance by referring to Accessing a DCS Redis Instance Through redis-cli.
- Run the info command to check whether the data has been successfully imported as required.
If the data has not been fully imported, run the flushall or flushdb command to clear the cached data in the target instance, and migrate data again.
+ - After the verification is complete, delete the redis shake configuration file.
+
+
+
+
diff --git a/docs/dcs/umn/dcs-migration-0312001.html b/docs/dcs/umn/dcs-migration-0312001.html
index e7adb5eb5..70115e654 100644
--- a/docs/dcs/umn/dcs-migration-0312001.html
+++ b/docs/dcs/umn/dcs-migration-0312001.html
@@ -6,7 +6,7 @@
- Number of instances
- Number of databases (DBs) configured for each instance
- Number of keys in each DB
- DBs used for your services
- Space occupied by each instance
- Redis version
- Redis instance configurations (single-node, master/standby, or cluster)
- Mapping relationships between your services and instances
Plan the following information about DCS instances based on the collected information: - Number of instances to be applied for
- Specifications and type (single-node, master/standby, or cluster) of each instance
- Virtual Private Clouds (VPCs), security groups, and subnets, and security groups, to which the instances and services belong
- redis-cli -h ${redis_address} -p ${port}
+ redis-cli -h ${redis_address} -p ${port}
@@ -20,7 +20,7 @@
- Network resources
Create VPCs and subnets based on service planning.
- Server resources
Apply for ECSs to bear Redis clients. The ECSs are used to export or import cached data.
Recommended ECS specifications are 8 vCPUs | 16 GB or higher.
- - DCS instances
Create DCS instances based on the migration planning. If the number of instances exceeds the default quota, submit a service ticket or contact technical support.
+ - DCS instances
Create DCS instances based on the migration planning. If the number of instances exceeds the default quota, submit a service ticket or contact customer service.
- Related tools
Install the FTP tool and Redis migration tools.
- Information to be collected
Collect the contact information of people involved in the migration, server addresses, login credentials, cache instance information, and DB information.
- Overall migration plan
Formulate the overall migration plan, including the personnel arrangement, rehearsal, migration, verification, service switchover, and rollback solutions.
diff --git a/docs/dcs/umn/dcs-migration-0312002.html b/docs/dcs/umn/dcs-migration-0312002.html
index 55ea2b652..0a31aff31 100644
--- a/docs/dcs/umn/dcs-migration-0312002.html
+++ b/docs/dcs/umn/dcs-migration-0312002.html
@@ -4,15 +4,17 @@
diff --git a/docs/dcs/umn/dcs-migration-0312003.html b/docs/dcs/umn/dcs-migration-0312003.html
index 12d1acd6f..488e7cd93 100644
--- a/docs/dcs/umn/dcs-migration-0312003.html
+++ b/docs/dcs/umn/dcs-migration-0312003.html
@@ -1,69 +1,79 @@
-
- Online Migration Between DCS Redis Instances
-
- Application ScenariosIf the source and target instances are interconnected and the SYNC and PSYNC commands are supported by the source instance, data can be migrated online in full or incrementally from the source to the target.
-  - If the SYNC and PSYNC commands are disabled on the source Redis instance, enable them before performing online migration. Otherwise, the migration fails. If you use a DCS Redis instance for online migration, the SYNC command is automatically enabled.
- You cannot use public networks for online migration.
- During online migration, you are advised to set repl-timeout on the source instance to 300s and client-output-buffer-limit to 20% of the maximum memory of the instance.
- The source must be Redis 3.0 or later.
+ Online Migration Between Instances
+ If the source and target instances are interconnected and the SYNC and PSYNC commands are supported by the source instance, data can be migrated online in full or incrementally from the source to the target.
+ During online migration, data is essentially synchronized in full to a new replica. Therefore, perform online migration during low-demand hours. Otherwise, source instance CPU usage may surge and latency may increase.
+ Notes and Constraints- You cannot use public networks for online migration.
- Before migrating data, read through Migration Solution Notes to learn about the DCS data migration function and select an appropriate target instance.
- Migrating a later Redis instance to an earlier one may fail.
- For earlier instances whose passwords contain single quotation marks ('), modify the password for online migration or try other methods.
- By default, a cluster instance has only one DB (DB0). Before you migrate data from a multi-DB single-node or master/standby instance to a Redis Cluster instance, check whether any data exists on databases other than DB0. To ensure that the migration succeeds, move all data to DB0 by referring to Online Migration with Rump.
- During online migration, you are advised to set repl-timeout on the source instance to 300s and client-output-buffer-slave-hard-limit and client-output-buffer-slave-soft-limit to 20% of the maximum memory of the instance.
- To migrate to an instance with SSL enabled, disable the SSL setting first. For details, see Transmitting DCS Redis Data with Encryption Using SSL.
- Impacts on ServicesDuring online migration, data is essentially synchronized in full to a new replica. Therefore, perform online migration during low-demand hours.
-
- Prerequisites- Before migrating data, read through Migration Tools and Schemes to learn about the DCS data migration function and select an appropriate target instance.
- By default, a cluster instance has only one DB (DB0). Before you migrate data from a multi-DB single-node or master/standby instance to a Redis Cluster instance, check whether any data exists on databases other than DB0. To ensure that the migration succeeds, move all data to DB0 by referring to Online Migration with Rump.
-
- Step 1: Obtain the Source Redis AddressObtain the IP address/domain name and port number of the source Redis instance.
-
- Step 2: Prepare the Target DCS Redis Instance
|
