A regional healthcare provider needs to migrate its core application workload to Google Cloud within a strict 3-week cutover window. The existing environment consists of a 650 TB static medical imaging archive and an active 400 GB MySQL operational database. The facility has a dedicated network connection with 100 Mbps of available uplink bandwidth, and the database requires minimal downtime during final cutover. Which migration strategy should a Cloud Architect recommend?
- Order a Google Cloud Transfer Appliance to transfer the 650 TB medical imaging archive offline, and use Database Migration Service (DMS) with continuous replication for the 400 GB MySQL database cutover.Cevap
- BUse Storage Transfer Service to stream both the 650 TB medical imaging archive and the operational database snapshot concurrently over the 100 Mbps network connection.
- CMigrate the 400 GB operational database into Cloud Spanner, and stream the 650 TB imaging archive directly into Cloud Spanner tables using batch upload scripts.
- DConfigure an HA VPN connection to a transit VPC, and rely on transitive routing over VPC Network Peering to stream all imaging files and database data to destination buckets in a peered workload VPC.
Cevap
Order a Google Cloud Transfer Appliance to transfer the 650 TB medical imaging archive offline, and use Database Migration Service (DMS) with continuous replication for the 400 GB MySQL database cutover.
The solution correctly identifies that moving 650 TB over a 100 Mbps internet connection takes over 600 days, making online transfer impossible within a 3-week timeframe. Transfer Appliance provides an offline physical shipping device capable of ingesting petabyte-scale data into Cloud Storage. Meanwhile, the 400 GB operational MySQL database can easily be seeded online and kept in continuous synchronization using Database Migration Service (DMS) with Change Data Capture (CDC) until final cutover.
Adım Adım Çözüm
Anahtar Kavram
Selecting data transfer mechanisms based on data volume, bandwidth constraints, and downtime requirements