Basic information
| Field | Details |
|---|---|
| English / full name | Snapshot vs Read Replica vs DMS vs S3 Import |
| Chinese | 数据库迁移方法对比 |
| Japanese | Database 移行方式の比較 |
| Review priority | 高频对比 |
| Often confused with | Point-in-time copy / Continuous replication / Table import |
In one sentence
Start with the source engine, target compatibility, and downtime window, then separate point-in-time migration, continuous synchronization, and table import.
Core summary
A snapshot is a point-in-time copy; an Aurora migration replica can follow changes; DMS can run full load plus CDC; S3 import depends on the backup format and target interface.
Study points
- For heterogeneous engines, convert schema and code before moving data with DMS.
- Before cutover, stop writes, catch up, verify data, and switch connections.
- Percona XtraBackup and mysqldump have different formats and restore paths.
- Replica lag of zero is an observation, not a complete safe-cutover protocol.
Common pitfalls
- Aurora PostgreSQL aws_s3 imports table data; it is not arbitrary full-database restore.
- Snapshot export to S3 is not a universal restore input.
Key memory
Snapshot for a point in time, replica or DMS for low-downtime sync, and inspect format and entry point for S3 files.