Replicating a production MySQL database from an on‑prem datacenter to GCP over Cloud VPN suffers latency and packet loss disrupting replication. What should you do?

Provisioning a Google Cloud Dedicated Interconnect establishes a direct, private connection between your on-premises data center and Google Cloud, bypassing the public internet. This significantly reduces latency and packet loss compared to Cloud VPN, which uses encrypted tunnels over the public internet. Dedicated Interconnect provides higher bandwidth and more reliable connectivity, making it ideal for critical, high-throughput workloads like database replication. Configuring replication to use UDP is not a solution for network latency and packet loss; UDP is a connectionless protocol that doesn't guarantee delivery, which is unsuitable for database replication. Restoring the database daily into Cloud SQL is a backup and recovery strategy, not a real-time replication solution, and would still require a reliable network for the initial transfer. Adding additional VPN tunnels and load balancing them might offer some redundancy but wouldn't fundamentally solve the underlying latency and packet loss issues inherent with VPN over the public internet. Sending replicated transactions to Cloud Pub/Sub is an architectural change for event-driven processing, not a direct solution for improving network performance for existing database replication.