Work often need to migrate redis; Ali cloud has a redis tools, support for Redis data is parsed (decode), recovery (restore), backup (dump), synchronization (sync / rump).
Original blog: https://help.aliyun.com/document_detail/117311.html?spm=a2c4g.11186623.2.16.13835957dhO7NV#concept-226440
GitHub Address:
The following record some of the work common operations: restore, and real-time synchronization of data
Restore operation
1, to complete the backup of data is downloaded to the same directory redis-shake, FIG. 
2, modified redis-shake.conf configurations, modify these items:
(specific reference: https://help.aliyun.com/document_detail/ 116378.html? SPM = 5176.11065259.1996646101.searchclickresult.74f05fe2CkrEwz )
rdb.input, Target.Address, target.password_raw, rewrite, Parallel 
3, execute command.
./redis-shake.linux64 -type = restore -conf = redis- shake.conf
Remarks: None. The import process cpu pressure on redis purpose will be relatively large, should pay attention to the next
Synchronous operation
1, redis-shake.conf modified configuration, modify these items:
Reference 1 links: https://help.aliyun.com/document_detail/97027.html?spm=a2c4g.11174283.6.683.6169dce0vFE7rY
Reference links 2: HTTPS: / /help.aliyun.com/document_detail/117311.html?spm=a2c4g.11186623.2.16.13835957U62eVS#concept-226440
2, execute command.
./redis-shake.linux64 -type = sync -conf = redis- shake.conf
Note: synchronization process, not redis pressure source, a relatively great pressure on the object redis