Quick Start
Simulate Time Series Scenarios
Standard Cluster Deployment
Data Modeling
Connecting to The database
Data Writing
Data Migration
Data Query
Scene Application Examples
Federal Query
Maintenance and Monitoring
Global Maintenance
Partition Maintenance
Backup and Restore
Cluster Expansion
Monitoring
Performance Tuning
Troubleshooting
Reference Guide
Tool Guide
Data Type
Storage Engine
Execution Engine
Configuration Parameters
SQL Reference
FAQ
YMatrix uses the mxshift tool to perform full-database data migration.
Currently, mxshift supports the following features:
WHERE clause.
If we compare the data migration process to water flowing through a pipe, and data transfer speed to the flow rate, then the overall rate is often limited by the narrowest part of the pipe—this creates a "bottleneck".
To address this, mxshift enables direct Segment-to-Segment data transfer, eliminating potential single-point bottlenecks common in traditional migration methods. When source and target clusters have different topologies (i.e., heterogeneous environments), mxshift automatically calculates the optimal mapping strategy based on factors such as the number of Segments in the source and target clusters, and whether Segments reside on the same physical host, enabling seamless automated migration.
mxshift runs using a configuration file. First, edit the configuration file config.toml.
Note!
For the complete configuration file, see mxshift.
$ vim config.toml
[database]
[database.source]
db-database= "testdb"
db-host="sdw3"
db-password="xxxx"
db-port=54322
db-user="mxadmin"
[database.target]
db-database="destdb"
db-host="172.16.100.32"
db-password="yyyy"
db-port=5432
db-user="mxadmin"
[scope]
install-dir="/usr/local/greenplum-db-6.7.1"
After preparing the TOML file, run the following command to start the migration with mxshift:
$ mxshift -c config_path.toml
Note!
For a complete list of mxshift parameters and usage, see mxshift.