An enterprise is planning a near-zero downtime database migration from an on-premises PostgreSQL database to Google Cloud SQL for PostgreSQL using Database Migration Service (DMS). Place the following migration steps in the correct chronological execution order from initial preparation to final cutover.
- 1Configure source database write-ahead logging (WAL) replication settings and establish secure private network connectivity to Google Cloud.
- 2Provision the target Cloud SQL for PostgreSQL instance and apply the schema DDL scripts matching the source environment.
- 3Start the Database Migration Service job to perform the initial full historical data snapshot transfer.
- 4Monitor real-time Change Data Capture (CDC) replication streams until replication latency drops near zero.
- 5Stop application writing traffic to the source database, verify zero remaining replication lag, promote Cloud SQL to primary, and update application endpoint connection strings.
Cevap
The correct sequential order for a Database Migration Service baseline and CDC workflow is: first configure source WAL and private network access, then provision Cloud SQL and establish schema structures, launch the initial full data snapshot transfer, monitor CDC replication latency until synced, and finally halt source writes, promote Cloud SQL, and update application connection endpoints.
A structured online migration requires enabling WAL logging and network connectivity first, provisioning the destination schema, running the full baseline dump via DMS, monitoring CDC until lag reaches near zero, and performing final application cutover.
Adım Adım Çözüm
Anahtar Kavram
Homogeneous database migration sequencing using Google Cloud Database Migration Service (DMS) with continuous CDC.
Tahmini Süre:2m 0s