Question

Difficulty: MediumDesigning Migration Plans and Data Transfer Strategies

A multinational e-commerce company plans to migrate its legacy product management system to Google Cloud. The environment includes an active 2 TB MySQL database requiring continuous replication with near-zero downtime cutover, along with 80 TB80\text{ TB} of static product image assets stored on an on-premises NAS network. The company already maintains an active 10 Gbps Dedicated Interconnect with Google Cloud with ample unutilized bandwidth. Which migration strategy should the Cloud Architect recommend to minimize cutover downtime and operational overhead?

  1. Use Storage Transfer Service with on-premises agents to stream static media assets over the Dedicated Interconnect into Cloud Storage, and deploy Database Migration Service (DMS) with continuous Change Data Capture (CDC) to replicate the MySQL database to Cloud SQL.Answer
  2. B
    Order a Google Cloud Transfer Appliance to physically ingest and ship the 80 TB80\text{ TB} static image repository to Google Cloud, and use Database Migration Service (DMS) with continuous replication for the MySQL database.
  3. C
    Use Storage Transfer Service for static image files, but migrate the MySQL database to Cloud Spanner using custom export/import scripts during the cutover window to achieve higher scale.
  4. D
    Establish multiple high-availability Cloud VPN tunnels to isolate static file migration traffic from the primary network, and perform a dump and restore of the MySQL database using mysqldump during cutover.

Answer

Use Storage Transfer Service with on-premises agents over Dedicated Interconnect for static media files, combined with Database Migration Service using continuous CDC for the MySQL database migration to Cloud SQL.
The combination of Storage Transfer Service for file ingestion and Database Migration Service (DMS) with continuous CDC for relational database replication provides an automated, managed migration path. Because an active 10 Gbps Dedicated Interconnect with spare capacity exists, online transfer of 80 TB80\text{ TB} is optimal and avoids the delay of physical appliance shipping, while DMS ensures near-zero database downtime during cutover.

Step-by-Step Solution

1
Analyze data volume and network throughput capacity
An 80 TB80\text{ TB} dataset over a 10 Gbps Dedicated Interconnect can easily be transferred online via network streaming within a few days, eliminating the need for offline physical appliance shipping.
Calculating network transfer capacity ensures online tools like Storage Transfer Service are prioritized when high-speed dedicated connectivity is active.
2
Evaluate database continuous replication requirements
Database Migration Service (DMS) supports native MySQL binlog-based Change Data Capture (CDC) to keep target Cloud SQL instances synchronized until final cutover.
Continuous CDC minimizes cutover downtime to just the time needed to switch application connection endpoints.
3
Select optimal managed GCP services
Combining Storage Transfer Service for unstructured files and Database Migration Service for transactional databases provides a fully managed, low-overhead migration architecture.
Using native GCP managed migration services minimizes operational overhead and custom script maintenance.

Key Concept

Combining Storage Transfer Service for online file transfer over Interconnect with Database Migration Service for low-downtime database cutover.
Rate this question