A healthcare organization is migrating its digital imaging archive and operational database from an on-premises data center to Google Cloud within a strict 14-day migration window. The data consists of of static DICOM medical imaging files and a transactional PostgreSQL database. The data center has a dedicated internet connection available for data transfer. The application requires that database downtime during the final cutover must not exceed 1 hour. Which migration strategy should you recommend?
- Order a Google Cloud Transfer Appliance to transfer the 180 TB imaging archive offline to Cloud Storage, and use Database Migration Service (DMS) with continuous replication for the PostgreSQL database.Cevap
- BUse Storage Transfer Service to stream both the 180 TB imaging archive and the PostgreSQL database backup directly over the 200 Mbps internet connection.
- CMigrate the PostgreSQL database by converting it to Cloud Spanner using Storage Transfer Service, while transferring the imaging archive over HA VPN tunnels.
- DProvision an HA VPN connection over the 200 Mbps link to compress and transfer both the imaging files and the PostgreSQL database before restoring them in Google Cloud.
Cevap
Order a Google Cloud Transfer Appliance for the 180 TB imaging archive and use Database Migration Service (DMS) with continuous replication for the PostgreSQL database.
The correct strategy combines offline physical transfer (Transfer Appliance) for large static archives with continuous online replication (Database Migration Service) for transactional databases. Transferring 180 TB over a 200 Mbps network line would take over 80 days, making offline appliance transport necessary to meet the 14-day window. Meanwhile, Database Migration Service continuously synchronizes PostgreSQL changes over the network, enabling a fast cutover that satisfies the sub-1-hour downtime requirement.
Adım Adım Çözüm
Anahtar Kavram
Selecting data transfer mechanisms based on bandwidth math and downtime constraints