Managed MySQL Backups
Each Managed Database plan includes automated backups and continuous recording of binary logs. The backup retention period depends on the backup tier, independently of the cluster node count: Mini (3 days) with Developer compute plans, and Regular (15 days) or Extended (31 days) with Standard and High Memory compute plans. Legacy plans retain backups for 2, 8, or 15 days, depending on the plan. This allows users to restore to any given point in time (PITR) within the selected retention window.
The backup time configuration can be adjusted in the service settings, which will shift the backup schedule accordingly. If a recent backup was taken, it might require an additional backup cycle before the new schedule takes effect.
For safe backups, MySQL INSTANT ALTER TABLE operations use either the INPLACE or COPY algorithm instead of INSTANT. Although specifying ALGORITHM=INSTANT won't cause a failure, it automatically defaults to INPLACE or COPY.
Backups and Encryption:
For encryption during backups, myhoard open-source software is used, which internally employs Percona XtraBackup for full or incremental snapshots of MySQL®.
Starting with Percona XtraBackup 8.0.23, the --lock-ddl option is enabled by default. This prevents DDL changes during a backup, ensuring the backup service's consistency and reliability for restoration. If you attempt to execute commands like CREATE, ALTER, DROP, TRUNCATE, or similar during a backup, you may encounter a "Waiting for backup lock" message. In such cases, wait for the backup to complete before proceeding with these operations.
All backups are encrypted and stored separately from the database, so they don't use the cluster's storage capacity.
Where backups are stored
By design, backups are kept off-site, in another location in the same region as the database. This keeps them available even in the unlikely event that the database's whole location goes down. Databases in Singapore and Chicago are the exception: their backups are stored in the same location as the database.
| Database location | Backups stored in |
|---|---|
| Amsterdam (NL-AMS1) London (UK-LON1) Madrid (ES-MAD1) Warsaw (PL-WAW1) | Frankfurt (DE-FRA1) |
| Frankfurt (DE-FRA1) Helsinki (FI-HEL1) Stockholm (SE-STO1) | Helsinki (FI-HEL2) |
| Copenhagen (DK-CPH1) Helsinki (FI-HEL2) Stavanger (NO-SVG1) | Stockholm (SE-STO1) |
| Chicago (US-CHI1) New York (US-NYC1) San Jose (US-SJO1) | Chicago (US-CHI1) |
| Singapore (SG-SIN1) Sydney (AU-SYD1) | Singapore (SG-SIN1) |
Restore to a point in time
You can restore a database as it was at any point in its backup retention period. The restore creates a new service and leaves the original as it is. The new service has its own hostname, and it keeps the original's users and passwords, its configuration properties and its termination protection setting.
In the Control Panel, the new service is created in the original's location, with the original's plan and networks. Through the API, you can choose another location and plan.
To restore a database, see How to restore a Managed Database to a point in time.
MySQL is a registered trademark of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.