Public Preview: Azure Files geo-redundancy for standard large file shares

We’re excited to announce Azure Files geo-redundancy for large file shares is now in public preview for standard SMB file shares.
Azure Files has supported large file shares for several years, which not only provides file share capacity up to 100TiB but improved IO operations per second (IOPS) and throughput as well. Large file shares are widely adopted by customers using locally redundant storage (LRS) and zone-redundant storage (ZRS) but has not been available for geo-redundant storage (GRS) and geo-zone redundant storage (GZRS) until now.
Geo-redundancy is critical for meeting various compliance and regulatory requirements. Geo-redundant storage asynchronously replicates to a secondary region and if the primary region becomes unavailable, you can initiate a failover to the secondary region.
Choosing between performance and scale or geo-redundancy is no longer necessary! You can now use geo-redundancy and enable large file shares on new and existing storage accounts to significantly increase your standard file share capacity and performance limits while benefiting from geo-redundancy:
Azure Files |
Previous limits |
Large file share limits |
Capacity per share |
5 TiB |
100 TiB (20x increase) |
Max IOPS per share |
1,000 IOPS |
20,000 IOPS (20x increase) |
Max throughput per share |
Up to 60 MiB/s |
Up to 300 MiB/s (5x increase) |
For more information on Azure storage redundancy and choosing what’s right for you, see Azure Storage redundancy.
Pricing and availability
Pricing is based on the standard file share tier and redundancy option configured for the storage account. To learn more, see Azure Files Pricing.
The public preview is currently available in 32 regions and we will be expanding to all regions. To view the latest information, see regional availability.
Getting started
Enabling geo-redundancy for new and existing standard large file shares is easy and can be accomplished in a few steps:
- Register for the preview using the portal or PowerShell.
- Enable geo-redundancy and large file shares for your standard SMB file shares.
More Information
To learn more, see the Azure Files geo-redundancy for large file shares preview documentation.
Feedback
If you have questions or feedback, please reach out to us at [email protected] or complete this feedback form.
Published on:
Learn moreRelated posts
Integrating Azure OpenAI models in your Projects: A Comprehensive Guide
In the previous blog, we have explored how to install and configure Azure OpenAI Service, now we will be unlocking its potential further by in...
Effortless Scaling: Autoscale goes GA on vCore-based Azure Cosmos DB for MongoDB
We’re thrilled to announce that Autoscale is now generally available (GA) for vCore-based Azure Cosmos DB for MongoDB! Say goodbye to manual s...
Making MongoDB workloads more affordable with M10/M20 tiers in vCore-based Azure Cosmos DB
vCore based Azure Cosmos DB for MongoDB is expanding its offerings with the new cost-effective M10 and M20 tiers for vCore-based deployments. ...
Replacing jackson-databind with azure-json and azure-xml
This blog post explains how azure-json and azure-xml replaced jackson-databind in the Azure SDK for Java. The post Replacing jackson-databind ...
March Patches for Azure DevOps Server
Today we are releasing patches that impact our self-hosted product, Azure DevOps Server. We strongly encourage and recommend that all customer...
Implementing Chat History for AI Applications Using Azure Cosmos DB Go SDK
This blog post covers how to build a chat history implementation using Azure Cosmos DB for NoSQL Go SDK and langchaingo. If you are new to the...