Long-term retention for Azure Database for MySQL - Flexible Server by using Azure Backup (preview)
Azure Backup and Azure Database Services together allow you to build an enterprise-class backup solution for Azure Database for MySQL - Flexible servers that retain backups for up to 10 years. If you have an Azure Database for MySQL - Flexible server, then you can extend the retention of backups beyond 35 days with built-in operational tier backup capability of MySQL - Flexible database.
This feature allows you to extend the current limitation of 35 days backup retention to 10 years, meeting your compliance and regulatory requirements.
Also, the backups are copied to an isolated storage environment outside of your tenant and subscription provide protection against ransomware attacks. In addition to long-term retention (LTR), this feature enhances the backup resiliency by protecting the source data from different levels of data loss, such as accidental deletions and ransomware protection. It's a zero-infrastructure solution with Azure Backup managing the backups with automated retention and backup scheduling. You can create a backup policy to define the backup schedule and retention. Based on the policy definition, Azure Backup transfers backups to the vault as blobs and manages their lifecycle. You can manage the backups centrally beside other protected workloads via the Azure Backup Center.
You can recover this backup in your specified storage containers, which can be used to rebuild the MySQL - Flexible server. You can also use native tools to restore this data as a new MySQL - Flexible server with database native tools.
Azure Database for MySQL - Flexible Server backup flow
To back up an Azure Database for MySQL - Flexible Server:
- Grant permissions to the Backup vault MSI on the target ARM resource (MySQL-Flexible server), establishing access and control.
- Configure backup policies, and specify the scheduling, retention, and other parameters.
Once the configuration is complete:
- Azure Backup invokes the backup based on the policy schedules on the ARM API of MySQL Flex server, writing data to a secure blob container with a SAS for enhanced security.
- Backup job runs independently, preventing disruptions during long-running tasks.
- The retention and recovery point lifecycles align with the backup policies for effective management.
- During the restore, Azure Backup invokes restore on the ARM API of the MySQL - Flexible Server using the Statistical Analysis System (SAS) for asynchronous, nondisruptive recovery.
Azure Backup authentication with MySQL - Flexible server
Azure Backup needs to connect to Azure MySQL - Flexible server while taking each backup.
Permissions for an Azure Database for MySQL - Flexible Server backup
The following table lists permissions that the vault MSI requires for successful backup operations:
| Operation | Permission |
|---|---|
| Backup | - MySQL Flexible Server Long-term Retention Backup Role - Reader Role on the server's resource group. |
| Restore | Storage Blob Data Contributor Role on the target storage account. |
Understand pricing
You incur charges for:
Protected instance fee: Azure Backup for MySQL - Flexible servers charges a protected instance fee as per the size of the database. When you configure backup for am Azure MySQL - Flexible server, a protected instance is created. Each instance is charged on the basis of its size (in GBs) on a per unit (250 GB) basis.
Backup Storage fee: Azure Backup for MySQL - Flexible servers store backups in Vault Tier. Restore points stored in the vault-standard tier are charged a separate fee called Backup Storage fee as per the total data stored (in GBs) and redundancy type enable on the Backup Vault.