A global retail firm is migrating its legacy inventory management system to Google Cloud. The environment consists of a archive of unstructured product catalog images and a operational PostgreSQL database. The on-premises facility has a shared internet uplink that must remain available for active business operations. The migration must complete within a target window of 14 days with minimal database downtime during cutover. Which migration strategy should the Cloud Architect recommend?
- Order a Google Cloud Transfer Appliance to perform an offline data transfer for the image archive to Cloud Storage, and use Database Migration Service (DMS) with continuous Change Data Capture (CDC) over a secure VPN for the PostgreSQL database.Answer
- BConfigure Storage Transfer Service to stream the image archive directly over the existing internet link, and use Database Migration Service (DMS) for the PostgreSQL database.
- COrder a Google Cloud Transfer Appliance for the image archive, and migrate the operational PostgreSQL database to a Cloud Spanner instance using automated schema conversion and continuous replication.
- DProvision a 10 Gbps Dedicated Interconnect connection to stream the image archive via Storage Transfer Service, and perform a one-time database backup and restore using pg_dump during cutover.
Answer
Order a Google Cloud Transfer Appliance for the image archive, and use Database Migration Service (DMS) with continuous Change Data Capture (CDC) over a VPN for the PostgreSQL database.
The solution combining a Google Cloud Transfer Appliance with Database Migration Service (DMS) via CDC addresses both data scale and network limitations. Moving of data over a shared pipe takes several months online; Transfer Appliance circumvents this by physically shipping the data to GCP within days. Meanwhile, DMS continuously replicates the PostgreSQL database using CDC, enabling a low-downtime cutover without requiring lengthy circuit provisioning.
Step-by-Step Solution
Key Concept
Designing hybrid data transfer strategies based on bandwidth constraints, dataset size, downtime tolerance, and lead-time requirements.