An autonomous mobility platform needs to migrate 40 TB of unstructured sensor logs from an on-premises storage system and a 500 GB relational database to Google Cloud within a 3-week planning window. The organization maintains an active 1 Gbps Dedicated Interconnect with 600 Mbps of consistent available bandwidth allocated for data migration. The operational requirement dictates that the relational database must remain fully operational for online transactions until a planned 2-hour final cutover window.
Which TWO architectural recommendations should be included in the cloud migration strategy to fulfill these business and technical requirements?
- Utilize Storage Transfer Service for agent-based transfers to move the 40 TB unstructured log dataset directly over the Dedicated Interconnect connection.Cevap
- Deploy Database Migration Service (DMS) to execute initial data loading and continuous Change Data Capture (CDC) replication for the relational database prior to final cutover.Cevap
- COrder a Google Cloud Transfer Appliance to perform an offline bulk migration of the 40 TB unstructured log files.
- DEstablish an IPsec High Availability (HA) VPN connection over the public internet specifically to isolate and transmit the database and file data transfers.
Cevap
The migration strategy should combine using Storage Transfer Service over the existing Dedicated Interconnect for the 40 TB log files and Database Migration Service with continuous replication for the relational database.
Combining Storage Transfer Service for unstructured logs over the Dedicated Interconnect and Database Migration Service with CDC for relational data satisfies both time constraints and low-downtime operational requirements. Online network migration of 40 TB completes well under a week over 600 Mbps available bandwidth, while continuous CDC replication ensures the database stays synchronized until the 2-hour cutover window.
Adım Adım Çözüm
Anahtar Kavram
Selecting online file transfer mechanisms versus offline appliances based on bandwidth calculations, alongside minimal-downtime database replication strategies.