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
- Cloud SDK 580.0.0 Updates Include Deprecation, New Features, and GA Promotions Google Cloud release notes ·
- Gemini AI-Assisted Code Conversion Now Available in Google Cloud's DMS Google Cloud Blog ·
- Cloud SQL for SQL Server HA instances integrate with Knowledge Catalog by default Google Cloud release notes ·
- Cloud SQL for PostgreSQL: Knowledge Catalog Enabled by Default for New HA Instances Google Cloud release notes ·
- Google Cloud adds direct management for Database Migration Service jobs in Cloud SQL/AlloyDB Google Cloud release notes ·
- Cloud SQL for PostgreSQL: Remote MCP Server Enhancements Google Cloud release notes ·