Examkin

Soru

Zorluk: OrtaDesigning Migration Plans and Data Transfer Strategies

A global retail enterprise is preparing to migrate its 12 TB12\text{ TB} on-premises transactional PostgreSQL database to Cloud SQL for PostgreSQL with minimal operational downtime. The architecture team has selected Database Migration Service (DMS) with continuous replication. Arrange the operational phases below into the correct chronological sequence required to complete the migration safely.

  1. 1Establish hybrid network connectivity via Cloud VPN or Interconnect and configure private connection profiles in Database Migration Service.
  2. 2Start the Database Migration Service job to perform the initial baseline database dump and restore into Cloud SQL.
  3. 3Enable continuous Change Data Capture (CDC) streaming to replicate ongoing write operations from on-premises to Cloud SQL.
  4. 4Set the on-premises application into read-only mode and wait for the Cloud SQL replication lag to reach zero.
  5. 5Promote the target Cloud SQL instance to a standalone database, update application connection strings, and resume production writes.

Cevap

The correct chronological sequence is: 1) Establish hybrid connectivity and connection profiles, 2) Start initial baseline dump and snapshot restore, 3) Enable continuous CDC streaming, 4) Set source application to read-only and allow replication lag to reach zero, 5) Promote target Cloud SQL instance and redirect application traffic.
Online database migrations require establishing infrastructure connectivity, loading a baseline data snapshot, maintaining real-time CDC synchronization, quiescing source writes to eliminate replication lag, and finally promoting the destination database for production cutover.

Adım Adım Çözüm

1
Configure network connectivity and DMS connection profiles.
Secure communication channel between source PostgreSQL and GCP target environment is verified.
Data transfer cannot start without established network routing and authentication credentials.
2
Execute the baseline data load.
Initial historical snapshot (12 TB12\text{ TB}) is transferred to Cloud SQL.
A baseline snapshot provides the starting state for continuous change data replication.
3
Activate continuous Change Data Capture (CDC).
Ongoing transaction log changes stream automatically to Cloud SQL.
CDC keeps the cloud database synchronized while the on-premises database remains active in production.
4
Quiesce on-premises writes and monitor replication lag.
Replication lag drops to zero seconds, confirming full parity.
Prevents data loss or data state mismatch during final cutover.
5
Perform cutover and promote Cloud SQL instance.
Cloud SQL becomes the active primary database and application endpoints are updated.
Completes the migration workflow and finalized switchover to Google Cloud.

Anahtar Kavram

Continuous Online Database Migration and Cutover Sequencing with DMS
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Designing Migration Plans and Data Transfer Strategies