Cloud SQL for MySQL: Improved Percona XtraBackup migration, larger system tablespace
Cloud SQL for MySQL now supports specifying multiple data files for Percona XtraBackup physical file migrations, removing the default naming requirement. This change also enables larger system tablespace files, exceeding 16TB. These enhancements benefit engineers migrating large MySQL instances to Cloud SQL.
Enhancements (2) ›
- Cloud SQL for MySQL
When you migrate from Percona XtraBackup physical file to Cloud SQL for MySQL , you can now specify multiple data files in the innodb_data_file_path parameter of your external server configuration. Also, you are no longer required to use the default name for your data files.
- Cloud SQL for MySQL
Cloud SQL for MySQL now supports multiple system tablespace files, allowing system tablespace size to grow larger than 16TB.
https://docs.cloud.google.com/release-notes#June_19_2026
Related releases
- Config Connector 1.154.1 Adds New Alpha Resources and Field Support Google Cloud release notes ·
- Cloud SQL for PostgreSQL: Private Service Connect changes August 2026 Google Cloud release notes ·
- Cloud SQL for SQL Server: Private Service Connect connection behavior changes Google Cloud release notes ·
- Cloud SQL for MySQL: Private Service Connect and QueryData Updates Google Cloud release notes ·
- Cloud SQL for PostgreSQL: Faster CMEK Re-encryption Google Cloud release notes ·
- Cloud SQL for SQL Server: Faster CMEK re-encryption with zero downtime Google Cloud release notes ·