Premium file share storage option in Azure Database for MySQL flexible server

Azure Database for MySQL flexible server offers Premium File Share storage, which supports everything from general-purpose applications to mission-critical, I/O-intensive workloads. This article describes the storage capabilities, including storage scaling, IOPS provisioning, autoscale IOPS, and pricing, so you can choose the right configuration for your workload.

Premium file share

Premium file share is the default storage option for Azure Database for MySQL flexible server. It delivers high-performance, low-latency storage for production workloads with input/output (IO)-intensive needs. The same storage technology is used across the Burstable, General Purpose, and Memory-Optimized service tiers, so you get a consistent storage experience regardless of the compute you choose. You can provision from 20 GiB up to 16 TiB of storage on the Burstable and General Purpose tiers, and up to 32 TiB on the Memory-Optimized tier, in 1-GiB increments. Storage scaling is an online operation and doesn't require a server restart. Premium file share supports both pre-provisioned IOPS and autoscale IOPS.

You can monitor your storage consumption in the Azure portal (with Azure Monitor) by using the storage limit, storage percentage, and storage used metrics. To learn about metrics, see the monitoring article.

Reach the storage limit

When storage consumption on the server is close to reaching the provisioned limit, the server goes into read-only mode to protect any lost writes on the server. Servers with less than or equal to 100 GiB provisioned storage are marked read-only if the free storage is less than 5% of the provisioned storage size. Servers with over 100 GiB provisioned storage are marked read-only when the free storage is less than 5 GiB.

For example, if you provision 110 GiB of storage, and the actual utilization exceeds 105 GiB, the server is marked read-only. Alternatively, if you provision 5 GiB of storage, the server is marked read-only when the free storage reaches less than 256 MB.

While the service attempts to make the server read-only, it blocks all new write transaction requests, and existing active transactions continue to execute. When the server is set to read-only, all subsequent write operations and transaction commits fail, but read queries continue to work uninterrupted.

To get the server out of read-only mode, increase the provisioned storage on the server. You can perform this action by using the Azure portal or Azure CLI. When increased, the server is ready to accept write transactions again.

Turn on storage auto-grow or set up an alert to notify you when your server storage is approaching the threshold so you can avoid getting into the read-only state. For more information, see the documentation on alert documentation how to set up an alert.

Storage autogrow

Storage autogrow prevents your server from running out of storage and becoming read-only. If storage autogrow is enabled, the storage automatically grows without affecting the workload. Storage autogrow is enabled by default for all new server creations. For servers with less than 100 GB provisioned storage, the provisioned storage size increases by 5 GB when the free storage is below 10% of the provisioned storage. For servers with more than 100 GB of provisioned storage, the provisioned storage size increases by 5% when the free storage space is below 10 GB of the provisioned storage size. The maximum storage limits specified earlier apply. Refresh the server instance to see the updated storage provisioned under Settings on the Compute + Storage page.

For example, if you provision 1,000 GB of storage, and the actual utilization exceeds 990 GB, the server storage size increases to 1,050 GB. Alternatively, if you provision 20 GB of storage, the storage size increases to 25 GB when less than 2 GB of storage is free.

Remember that storage, once autoscales up, can't be scaled down.

Note

Storage autogrow is enabled by default for a high-availability configured server and accelerated logs enabled servers and can't be disabled.

IOPS

Azure Database for MySQL Flexible Server supports pre-provisioned IOPS and autoscale IOPS. Storage IOPS in Azure Database for MySQL - Flexible Server The minimum IOPS is 360 across all compute sizes, and the maximum IOPS is determined by the selected compute size. To learn more about the maximum IOPS per compute size, see the documentation

Important

Minimum IOPS are 360 across all compute sizes.
Maximum IOPS are determined by the selected compute size.

You can monitor your I/O consumption in the Azure portal (with Azure Monitor) by using Monitor Azure Database for MySQL - Flexible Server metric. You need to scale your server's compute if you need more IOPS than the max IOPS based on compute.

Pre-provisioned IOPS

Azure Database for MySQL Flexible Server offers pre-provisioned IOPS, so you can allocate a specific number of IOPS to your Azure Database for MySQL Flexible Server instance. This setting ensures consistent and predictable performance for your workloads. By using pre-provisioned IOPS, you can define a specific IOPS limit for your storage volume, guaranteeing the ability to handle some requests per second. This capability results in a reliable and assured level of performance. Pre-provisioned IOPS enables you to provision additional IOPS above the IOPS limit. By using this feature, you can increase or decrease the number of IOPS provisioned based on your workload requirements at any time.

Autoscale IOPS

The cornerstone of Azure Database for MySQL Flexible Server is its ability to achieve the best performance for tier 1 workloads. This performance improves when you enable the server to automatically scale its database servers' performance (IO) seamlessly depending on the workload needs. This opt-in feature enables you to scale IOPS on demand without having to pre-provision a certain amount of IO per second. When you enable the Autoscale IOPS feature, you get worry-free IO management in Azure Database for MySQL Flexible Server because the server scales IOPs up or down automatically depending on workload needs. AutoScale IOPS automatically scales up to the Max Supported IOPS for each service tier and compute size. This scaling ensures optimal performance without the need for manual scaling efforts.

With Autoscale IOPS, you pay only for the IO the server uses and no longer need to provision and pay for resources you aren't fully using, saving time and money. In addition, mission-critical tier 1 applications can achieve consistent performance by making additional IO available to the workload anytime. Autoscale IOPS eliminates the administration required to provide the best performance at the least cost for Azure Database for MySQL Flexible Server customers.

Dynamic Scaling: Autoscale IOPS dynamically adjusts your database server's IOPS limit based on your workload's actual demand. This feature ensures optimal performance without manual intervention or configuration.

Handling Workload Spikes: Autoscale IOPS enables your database to seamlessly handle workload spikes or fluctuations without compromising the performance of your applications. This feature ensures consistent responsiveness even during peak usage periods.

Cost Savings: Unlike the pre-provisioned IOPS, which specifies a fixed IOPS limit and is paid for regardless of usage, Autoscale IOPS lets you pay only for the number of I/O operations that you consume.

Note

You can only increase the storage size. You can't go back to a smaller storage size after the increase.

Price

For the most up-to-date pricing information, see the service pricing page. To see the cost for the configuration you want, the Azure portal shows the monthly cost on the Compute + storage tab based on the options you select. If you don't have an Azure subscription, use the Azure pricing calculator to get an estimated price. On the Azure pricing calculator website, select Add items, expand the Databases category, choose Azure Database for MySQL, and Flexible Server as the deployment type to customize the options.