Quick onboard
Deployment
Data Modeling
Connecting
Migration
Query
Operations and Maintenance
Common Maintenance
Partition
Backup and Restore
Expansion
Mirroring
Resource Management
Security
Monitoring
Performance Tuning
Troubleshooting
Reference Guide
Tool guide
Data type
Storage Engine
Executor
Stream
DR (Disaster Recovery)
Configuration
Index
Extension
SQL Reference
Data migration in YMatrix consists of three main phases:
Phase 1: Environment Preparation;
Phase 2: Migration Execution;
Phase 3: Post-Migration Tasks.
For a full-database migration, thorough preparation is required. This typically includes, but is not limited to, the following steps (adjust as needed based on your specific scenario):
Before stopping services: Back up the source data, prepare the software environment of the target cluster, stop all DDL operations from client applications, back up the DDL statements required for migration, and refine and optimize these DDLs (we recommend excluding index creation statements from the source schema to improve migration efficiency) to align with the target database.
After stopping services: Collect hardware and software configuration details of the target cluster. Compare and analyze architectural differences between the source and target clusters to determine the most suitable migration strategy.
These steps are essential. You must ensure the safety of existing data and identify the optimal migration method to minimize downtime cost and risk.
For single-table migration, use mxgate to export the table data into a file for backup.
Once preparations are complete, proceed to the migration execution phase.
For full-database migration, we recommend not migrating Mirror segments. Instead, perform the migration using the Full Database Migration Tool - mxshift, then add Mirrors afterward. This approach significantly improves migration efficiency. The mxshift tool automatically prints progress upon completion of each table migration and performs real-time validation to ensure data correctness.
For single-table migration, use the Single Table Migration Tool - mxgate.
After migration completes:
If you performed a full-database migration, we recommend recreating indexes and running the analyzedb command across the entire database to update statistics. Then restore service access, monitor application behavior, and continuously observe system performance for a period appropriate to your workload pattern before considering the migration complete.
Examples of full-database migration:
Migration from Greenplum 6 to YMatrix 5
Migration from YMatrix 4 to YMatrix 5
Example of single-table migration:
Single Table Migration
