A global media streaming platform is migrating its on-premises infrastructure to Google Cloud. The environment includes a 1.2 PB archive of video assets on network-attached storage (NAS) and a live 4 TB PostgreSQL database supporting user metadata. The business requires zero downtime for the database cutover and minimal disruption for video asset migration. Arrange the operational steps in the correct architectural sequence to execute this data transfer and migration strategy.
- 1Establish a Dedicated Interconnect connection and configure private routing between the on-premises environment and the Google Cloud VPC.
- 2Deploy Google Cloud Database Migration Service (DMS) to replicate the PostgreSQL schema and initiate continuous Change Data Capture (CDC).
- 3Perform initial bulk seeding of the 1.2 PB video archive into Cloud Storage using Google Cloud Transfer Appliance devices.
- 4Execute an incremental sync of newly created or modified media files using Storage Transfer Service over the Dedicated Interconnect.
- 5Validate database sync lag, promote the Cloud SQL replica to primary, and redirect application traffic to Google Cloud endpoints.
Answer
The correct sequence starts with establishing Dedicated Interconnect network connectivity, followed by configuring Database Migration Service (DMS) with continuous CDC for the relational database. Next, petabyte-scale offline data transfer is performed via Transfer Appliance, followed by an online delta sync using Storage Transfer Service. Finally, application traffic is cut over after verifying database replication synchronization.
The proper architectural sequence begins by provisioning dedicated hybrid networking to secure communications. Continuous database replication (CDC via DMS) is started next so that transactional changes stream continuously. Bulk offline storage transfer (Transfer Appliance) is executed for the 1.2 PB dataset to avoid network saturation, followed by an online delta catch-up sync (Storage Transfer Service) to synchronize changes generated during transit. Finally, database replication lag is verified and traffic cutover is completed.
Step-by-Step Solution
Key Concept
Staging Hybrid Cloud Migration and Data Transfer Strategies