您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

Azure 存储冗余Azure Storage redundancy

Azure 存储始终会存储数据的多个副本,以防范各种计划内和计划外的事件,包括暂时性的硬件故障、网络中断或断电、大范围自然灾害等。Azure Storage always stores multiple copies of your data so that it is protected from planned and unplanned events, including transient hardware failures, network or power outages, and massive natural disasters. 冗余可确保即使在遇到故障时,存储帐户也能满足可用性和持续性目标。Redundancy ensures that your storage account meets its availability and durability targets even in the face of failures.

确定最适合你的方案的冗余选项时,请考虑降低成本和提高可用性之间的权衡。When deciding which redundancy option is best for your scenario, consider the tradeoffs between lower costs and higher availability. 可帮助你确定应选择哪种冗余选项的因素包括:The factors that help determine which redundancy option you should choose include:

  • 如何在主要区域中复制数据How your data is replicated in the primary region
  • 是否要将你的数据复制到地理上距主要区域较远的另一个区域,以防范区域性灾难Whether your data is replicated to a second region that is geographically distant to the primary region, to protect against regional disasters
  • 应用程序是否要求在主要区域出于任何原因而不可用时,能够对次要区域中复制的数据进行读取访问Whether your application requires read access to the replicated data in the secondary region if the primary region becomes unavailable for any reason

主要区域中的冗余Redundancy in the primary region

Azure 存储帐户中的数据在主要区域中始终复制三次。Data in an Azure Storage account is always replicated three times in the primary region. Azure 存储提供了两个有关如何在主要区域中复制数据的选项:Azure Storage offers two options for how your data is replicated in the primary region:

  • 本地冗余存储 (LRS) 在主要区域中的单个物理位置同步复制数据三次。Locally redundant storage (LRS) copies your data synchronously three times within a single physical location in the primary region. LRS 是成本最低的复制选项,但不建议对需要高可用性的应用程序使用此选项。LRS is the least expensive replication option, but is not recommended for applications requiring high availability.
  • 区域冗余存储 (ZRS) 跨主要区域中的三个 Azure 可用性区域同步复制数据。Zone-redundant storage (ZRS) copies your data synchronously across three Azure availability zones in the primary region. 对于需要高可用性的应用程序,Microsoft 建议在主要区域中使用 ZRS,并复制到次要区域。For applications requiring high availability, Microsoft recommends using ZRS in the primary region, and also replicating to a secondary region.

本地冗余存储Locally-redundant storage

本地冗余存储 (LRS) 在主要区域中的单个物理位置内复制数据三次。Locally redundant storage (LRS) replicates your data three times within a single physical location in the primary region. LRS 可在一年中提供至少 99.999999999%(11 个 9)的对象持久性。LRS provides at least 99.999999999% (11 nines) durability of objects over a given year.

与其他选项相比,LRS 是成本最低的冗余选项,但提供的持久性也最低。LRS is the lowest-cost redundancy option and offers the least durability compared to other options. LRS 可以保护数据,使其不受服务器机架和驱动器故障影响。LRS protects your data against server rack and drive failures. 但是,如果数据中心内发生火灾或洪水等灾难,使用 LRS 的存储帐户的所有副本可能会丢失或无法恢复。However, if a disaster such as fire or flooding occurs within the data center, all replicas of a storage account using LRS may be lost or unrecoverable. 若要缓解此风险,Microsoft 建议使用区域冗余存储 (ZRS)、异地冗余存储 (GRS) 或异地区域冗余存储 (GZRS)。To mitigate this risk, Microsoft recommends using zone-redundant storage (ZRS), geo-redundant storage (GRS), or geo-zone-redundant storage (GZRS).

会同步发生一个针对使用 LRS 的存储帐户的写入请求。A write request to a storage account that is using LRS happens synchronously. 只有将数据写入到所有三个副本后,写入操作才会成功返回。The write operation returns successfully only after the data is written to all three replicas.

对于以下场景,LRS 是不错的选项:LRS is a good choice for the following scenarios:

  • 如果应用程序存储着在发生数据丢失时可轻松重构的数据,则可以选择 LRS。If your application stores data that can be easily reconstructed if data loss occurs, you may opt for LRS.
  • 如果由于数据治理需要,某些应用程序被限制为只能在一个国家/地区内复制数据,则可以选择 LRS。If your application is restricted to replicating data only within a country or region due to data governance requirements, you may opt for LRS. 在某些情况下,进行异地复制数据的配对区域可能在另一个国家/地区。In some cases, the paired regions across which the data is geo-replicated may be in another country or region. 有关配对区域的详细信息,请参阅 Azure 区域For more information on paired regions, see Azure regions.

区域冗余存储Zone-redundant storage

区域冗余存储 (ZRS) 在主区域中的三个 Azure 可用性区域同步复制 Azure 存储数据。Zone-redundant storage (ZRS) replicates your Azure Storage data synchronously across three Azure availability zones in the primary region. 每个可用性区域都是一个独立的物理位置,具有独立的电源、冷却系统和网络。Each availability zone is a separate physical location with independent power, cooling, and networking. ZRS 在一年中提供至少 99.9999999999%(12 个 9)的 Azure 存储数据对象持久性。ZRS offers durability for Azure Storage data objects of at least 99.9999999999% (12 9's) over a given year.

通过使用 ZRS,即使某个区域变得不可用,也仍可访问你的数据进行读写操作。With ZRS, your data is still accessible for both read and write operations even if a zone becomes unavailable. 如果某个区域变得不可用,则 Azure 会执行网络更新,例如 DNS 重新指向。If a zone becomes unavailable, Azure undertakes networking updates, such as DNS re-pointing. 如果完成更新之前访问数据,这些更新可能会影响应用程序。These updates may affect your application if you access data before the updates have completed. 在设计用于 ZRS 的应用程序时,遵循暂时性故障的处理做法,包括结合指数退让实施重试策略。When designing applications for ZRS, follow practices for transient fault handling, including implementing retry policies with exponential back-off.

会同步发生一个针对使用 ZRS 的存储帐户的写入请求。A write request to a storage account that is using ZRS happens synchronously. 写入操作仅在将数据写入三个可用性区域中的所有副本后才能成功返回。The write operation returns successfully only after the data is written to all replicas across the three availability zones.

对于需要一致性、耐用性和高可用性的方案,Microsoft 建议在主要区域中使用 ZRS。Microsoft recommends using ZRS in the primary region for scenarios that require consistency, durability, and high availability. 如果要将应用程序限制为仅在国家或地区内复制数据,则我们还建议使用 ZRS,因为数据治理要求。We also recommend using ZRS if you want to restrict an application to replicate data only within a country or region because of data governance requirements.

如果数据变为暂时不可用,ZRS 可提供出色的性能、低延迟和数据复原能力。ZRS provides excellent performance, low latency, and resiliency for your data if it becomes temporarily unavailable. 但是,如果多个区域永久受到影响,在发生区域性的灾难时,ZRS 本身可能无法保护数据。However, ZRS by itself may not protect your data against a regional disaster where multiple zones are permanently affected. 为了防御区域灾难,Microsoft 建议使用地理区域冗余存储 (GZRS),该存储在主要区域中使用 ZRS,并将数据异地复制到次要区域。For protection against regional disasters, Microsoft recommends using geo-zone-redundant storage (GZRS), which uses ZRS in the primary region and also geo-replicates your data to a secondary region.

下表显示了哪些类型的存储帐户支持哪些区域中的 ZRS:The following table shows which types of storage accounts support ZRS in which regions:

存储帐户类型Storage account type 支持的区域Supported regions 支持的服务Supported services
常规用途 v21General-purpose v21 亚洲东南部Asia Southeast
澳大利亚东部Australia East
北欧Europe North
西欧Europe West
法国中部France Central
日本东部Japan East
南非北部South Africa North
英国南部UK South
美国中部US Central
美国东部US East
美国东部 2US East 2
美国西部 2US West 2
块 BlobBlock blobs
页 Blob2Page blobs2
文件共享(共享)File shares (standard)
Tables
队列Queues
BlockBlobStorage1BlockBlobStorage1 亚洲东南部Asia Southeast
澳大利亚东部Australia East
北欧Europe North
西欧Europe West
日本东部Japan East
美国东部US East
美国东部 2US East 2
美国西部 2US West 2
仅限高级块 blobPremium block blobs only
FileStorageFileStorage 亚洲东南部Asia Southeast
澳大利亚东部Australia East
北欧Europe North
西欧Europe West
日本东部Japan East
美国东部US East
美国东部 2US East 2
美国西部 2US West 2
仅高级文件共享Premium files shares only

1 ZRS 帐户当前不支持存档层。1 The archive tier is not currently supported for ZRS accounts.
2 包含虚拟机的 Azure 托管磁盘的存储帐户始终使用 LRS。2 Storage accounts that contain Azure managed disks for virtual machines always use LRS. Azure 非托管磁盘还应使用 LRS。Azure unmanaged disks should also use LRS. 可以为使用 GRS 的 Azure 非托管磁盘创建存储帐户,但由于异步异地复制可能存在一致性问题,因此不建议这样做。It is possible to create a storage account for Azure unmanaged disks that uses GRS, but it is not recommended due to potential issues with consistency over asynchronous geo-replication. 托管磁盘和非托管磁盘都不支持 ZRS 或 GZRS。Neither managed nor unmanaged disks support ZRS or GZRS. 有关托管磁盘的详细信息,请参阅 Azure 托管磁盘定价For more information on managed disks, see Pricing for Azure managed disks.

若要详细了解哪些区域支持 ZRS,请参阅什么是 Azure 可用性区域?中的“服务支持(按区域)”。For information about which regions support ZRS, see Services support by region in What are Azure Availability Zones?.

次要区域中的冗余Redundancy in a secondary region

对于需要高可用性的应用程序,可以选择将存储帐户中的数据另外复制到距离主要区域数百英里以外的次要区域。For applications requiring high availability, you can choose to additionally copy the data in your storage account to a secondary region that is hundreds of miles away from the primary region. 如果存储帐户已复制到次要区域,则即使遇到区域性服务完全中断或导致主要区域不可恢复的灾难,数据也能持久保存。If your storage account is copied to a secondary region, then your data is durable even in the case of a complete regional outage or a disaster in which the primary region isn't recoverable.

创建存储帐户时,可以为帐户选择主要区域。When you create a storage account, you select the primary region for the account. 配对的次要区域是根据主要区域确定的且无法更改。The paired secondary region is determined based on the primary region, and can't be changed. 有关 Azure 支持的区域的详细信息,请参阅 Azure 区域For more information about regions supported by Azure, see Azure regions.

Azure 存储提供了两种将数据复制到次要区域的选项:Azure Storage offers two options for copying your data to a secondary region:

  • 异地冗余存储 (GRS) 使用 LRS 在主区域中的单个物理位置同步复制数据三次。Geo-redundant storage (GRS) copies your data synchronously three times within a single physical location in the primary region using LRS. 然后,它会将数据异步复制到次要区域中的单个物理位置。It then copies your data asynchronously to a single physical location in the secondary region.
  • 异地区域冗余存储 (GZRS) 使用 ZRS 在主区域中的三个 Azure 可用性区域同步复制数据。Geo-zone-redundant storage (GZRS) copies your data synchronously across three Azure availability zones in the primary region using ZRS. 然后,它会将数据异步复制到次要区域中的单个物理位置。It then copies your data asynchronously to a single physical location in the secondary region.

GRS 和 GZRS 之间的主要区别是在主要区域中复制数据的方式。The primary difference between GRS and GZRS is how data is replicated in the primary region. 在次要区域中,数据始终使用 LRS 同步复制三次。Within the secondary region, data is always replicated synchronously three times using LRS. 辅助区域中的 LRS 保护你的数据免受硬件故障的影响。LRS in the secondary region protects your data against hardware failures.

使用 GRS 或 GZRS 时,次要区域中的数据不可用于读取或写入访问,除非存在到次要区域的故障转移。With GRS or GZRS, the data in the secondary region isn't available for read or write access unless there is a failover to the secondary region. 若要对次要区域进行读取访问,请将存储帐户配置为使用读取访问异地冗余存储 (GRS) 或读取访问地域冗余存储 (GZRS) 。For read access to the secondary region, configure your storage account to use read-access geo-redundant storage (RA-GRS) or read-access geo-zone-redundant storage (RA-GZRS). 有关详细信息,请参阅对次要区域中数据的读取访问权限For more information, see Read access to data in the secondary region.

如果主要区域变得不可用,则可以选择故障转移到次要区域。If the primary region becomes unavailable, you can choose to fail over to the secondary region. 故障转移完成后,次要区域将成为主要区域,你便可以再次读取和写入数据。After the failover has completed, the secondary region becomes the primary region, and you can again read and write data. 有关灾难恢复以及如何故障转移到次要区域的详细信息,请参阅灾难恢复和存储帐户故障转移For more information on disaster recovery and to learn how to fail over to the secondary region, see Disaster recovery and storage account failover.

重要

由于数据以异步方式复制到次要区域,因此如果无法恢复主要区域,则影响主要区域的故障可能会导致数据丢失。Because data is replicated to the secondary region asynchronously, a failure that affects the primary region may result in data loss if the primary region cannot be recovered. 最近对主要区域的写入与最近对次要区域的写入之间的时间间隔称为恢复点目标 (RPO)。The interval between the most recent writes to the primary region and the last write to the secondary region is known as the recovery point objective (RPO). RPO 指示可以将数据恢复到的时间点。The RPO indicates the point in time to which data can be recovered. Azure 存储的 RPO 通常小于 15 分钟,但目前没有有关将数据复制到次要区域所用的时长的 SLA。Azure Storage typically has an RPO of less than 15 minutes, although there's currently no SLA on how long it takes to replicate data to the secondary region.

异地冗余存储Geo-redundant storage

异地冗余存储 (GRS) 使用 LRS 在主要区域中的单个物理位置内同步复制数据三次。Geo-redundant storage (GRS) copies your data synchronously three times within a single physical location in the primary region using LRS. 然后,它将数据异步复制到距离主要区域数百英里以外的次要区域中的单个物理位置。It then copies your data asynchronously to a single physical location in a secondary region that is hundreds of miles away from the primary region. GRS 在给定一年中提供至少 99.99999999999999%(16 个 9)的 Azure 存储数据对象持久性。GRS offers durability for Azure Storage data objects of at least 99.99999999999999% (16 9's) over a given year.

首先会将写入操作提交到主要位置,并使用 LRS 复制该操作。A write operation is first committed to the primary location and replicated using LRS. 然后会以异步方式将更新复制到次要区域。The update is then replicated asynchronously to the secondary region. 将数据写入次要位置后,还会使用 LRS 在该位置复制数据。When data is written to the secondary location, it's also replicated within that location using LRS.

下图显示了如何通过 GRS 或 GRS 复制数据:The following diagram shows how your data is replicated with GRS or RA-GRS:

显示如何将数据与 GRS 或 GRS 一起复制的关系图

异地区域冗余存储Geo-zone-redundant storage

地域区域冗余存储 (GZRS) 将冗余跨可用性区域提供的高可用性与异地复制提供的区域中断保护相结合。Geo-zone-redundant storage (GZRS) combines the high availability provided by redundancy across availability zones with protection from regional outages provided by geo-replication. 将跨主要区域中的三个 Azure 可用性区域复制 GZRS 存储帐户中的数据,并将其复制到次要地理区域,以防御区域灾难。Data in a GZRS storage account is copied across three Azure availability zones in the primary region and is also replicated to a secondary geographic region for protection from regional disasters. Microsoft 建议对需要最大程度的一致性、耐用性和可用性、卓越性能和灾难恢复复原能力的应用程序使用 GZRS。Microsoft recommends using GZRS for applications requiring maximum consistency, durability, and availability, excellent performance, and resilience for disaster recovery.

如果使用 GZRS 存储帐户,在可用性区域不可用或无法恢复的情况下,可以继续读取和写入数据。With a GZRS storage account, you can continue to read and write data if an availability zone becomes unavailable or is unrecoverable. 此外,即使在遇到区域完全停电或导致主要区域不可恢复的灾难,数据也能持久保存。Additionally, your data is also durable in the case of a complete regional outage or a disaster in which the primary region isn't recoverable. GZRS 可在一年中提供至少 99.99999999999999%(16 个 9)的对象持久性。GZRS is designed to provide at least 99.99999999999999% (16 9's) durability of objects over a given year.

下图显示了如何通过 GZRS 或 GZRS 复制数据:The following diagram shows how your data is replicated with GZRS or RA-GZRS:

显示如何将数据与 GZRS 或 GZRS 一起复制的关系图

仅常规用途 v2 存储帐户支持 GZRS 和 RA-GZRS。Only general-purpose v2 storage accounts support GZRS and RA-GZRS. 有关存储帐户类型的详细信息,请参阅 Azure 存储帐户概述For more information about storage account types, see Azure storage account overview. GZRS 和 RA-GZRS 支持块 Blob、页 Blob(但无法用于 VHD 磁盘)、文件、表和队列。GZRS and RA-GZRS support block blobs, page blobs (except for VHD disks), files, tables, and queues.

以下区域支持 GZRS 和 RA-GZRS:GZRS and RA-GZRS are supported in the following regions:

  • 亚洲东南部Asia Southeast
  • 北欧Europe North
  • 西欧Europe West
  • 日本东部Japan East
  • 英国南部UK South
  • 美国中部US Central
  • 美国东部US East
  • 美国东部 2US East 2
  • 美国西部 2US West 2

若要详细了解定价,请参阅 Blob文件列队的定价详细信息。For information on pricing, see pricing details for Blobs, Files, Queues, and Tables.

对次要区域中数据的读取访问权限Read access to data in the secondary region

异地冗余存储(使用 GRS 或 GZRS)将数据复制到次要区域中的另一个物理位置,以防止区域中断。Geo-redundant storage (with GRS or GZRS) replicates your data to another physical location in the secondary region to protect against regional outages. 但是,仅当客户或 Microsoft 启动了从主要区域到次要区域的故障转移时,才能读取该数据。However, that data is available to be read only if the customer or Microsoft initiates a failover from the primary to secondary region. 当你启用对辅助区域的读取访问权限时,你的数据将随时可供读取,其中包括在主要区域不可用的情况下。When you enable read access to the secondary region, your data is available to be read at all times, including in a situation where the primary region becomes unavailable. 若要对次要区域进行读取访问,可启用读取访问异地冗余存储 (RA-GRS) 或读取访问地理区域冗余存储 (RA-GZRS)。For read access to the secondary region, enable read-access geo-redundant storage (RA-GRS) or read-access geo-zone-redundant storage (RA-GZRS).

备注

Azure 文件不支持读取访问异地冗余存储 (GRS) 和读取访问地域冗余存储 (GZRS) 。Azure Files does not support read-access geo-redundant storage (RA-GRS) and read-access geo-zone-redundant storage (RA-GZRS).

设计应用程序以便能够对次要区域进行读取访问Design your applications for read access to the secondary

如果存储帐户已配置为对次要区域进行读取访问,则你可以设计自己的应用程序,以便在主要区域出于任何原因而不可用时,能够无缝转换为从次要区域读取数据。If your storage account is configured for read access to the secondary region, then you can design your applications to seamlessly shift to reading data from the secondary region if the primary region becomes unavailable for any reason.

启用 "GRS" 或 "GZRS" 后,辅助区域可用于读取访问权限,因此你可以提前测试应用程序,以确保在发生服务中断时,它将从辅助区域正确读取。The secondary region is available for read access after you enable RA-GRS or RA-GZRS, so that you can test your application in advance to make sure that it will properly read from the secondary in the event of an outage. 有关如何设计应用程序以实现高可用性的详细信息,请参阅使用异地冗余设计高度可用的应用程序For more information about how to design your applications for high availability, see Use geo-redundancy to design highly available applications.

启用对次要区域的读取访问后,应用程序可以从次要终结点以及主要终结点读取数据。When read access to the secondary is enabled, your application can be read from the secondary endpoint as well as from the primary endpoint. 辅助终结点将后缀“–secondary”追加到帐户名称。The secondary endpoint appends the suffix –secondary to the account name. 例如,如果 Blob 存储的主终结点是 myaccount.blob.core.windows.net,则辅助终结点是 myaccount-secondary.blob.core.windows.netFor example, if your primary endpoint for Blob storage is myaccount.blob.core.windows.net, then the secondary endpoint is myaccount-secondary.blob.core.windows.net. 存储帐户的帐户访问密钥对于主要终结点和次要终结点是相同的。The account access keys for your storage account are the same for both the primary and secondary endpoints.

检查“上次同步时间”属性Check the Last Sync Time property

由于数据以异步方式复制到次要区域,因此次要区域通常位于主要区域的后面。Because data is replicated to the secondary region asynchronously, the secondary region is often behind the primary region. 如果主要区域发生故障,对主要区域的所有写入有可能尚未复制到次要区域。If a failure happens in the primary region, it's likely that all writes to the primary will not yet have been replicated to the secondary.

若要确定哪些写入操作已复制到次要区域,应用程序可以检查存储帐户的“上次同步时间”属性。To determine which write operations have been replicated to the secondary region, your application can check the Last Sync Time property for your storage account. 在上次同步时间之前写入到主要区域的所有写入操作已成功复制到次要区域,这意味着,可以从次要区域读取这些操作。All write operations written to the primary region prior to the last sync time have been successfully replicated to the secondary region, meaning that they are available to be read from the secondary. 在上次同步时间之后写入到主要区域的任何写入操作不一定已复制到次要区域,这意味着,它们不一定可供读取操作使用。Any write operations written to the primary region after the last sync time may or may not have been replicated to the secondary region, meaning that they may not be available for read operations.

可以使用 Azure PowerShell、Azure CLI 或某个 Azure 存储客户端库查询“上次同步时间”属性的值。You can query the value of the Last Sync Time property using Azure PowerShell, Azure CLI, or one of the Azure Storage client libraries. “上次同步时间”属性是一个 GMT 日期/时间值。The Last Sync Time property is a GMT date/time value. 有关详细信息,请参阅检查存储帐户的“上次同步时间”属性For more information, see Check the Last Sync Time property for a storage account.

冗余选项摘要Summary of redundancy options

以下各部分中的表总结了可用于 Azure 存储的冗余选项The tables in the following sections summarize the redundancy options available for Azure Storage

持久性和可用性参数Durability and availability parameters

下表描述了每个冗余选项的关键参数:The following table describes key parameters for each redundancy option:

参数Parameter LRSLRS ZRSZRS GRS/RA-GRSGRS/RA-GRS GZRS/RA-GZRSGZRS/RA-GZRS
对象在给定年的持续性百分比Percent durability of objects over a given year 至少为 99.999999999% (11 9's)at least 99.999999999% (11 9's) 至少为 99.9999999999% (12 9's)at least 99.9999999999% (12 9's) 至少为 99.99999999999999% (16 9's)at least 99.99999999999999% (16 9's) 至少为 99.99999999999999% (16 9's)at least 99.99999999999999% (16 9's)
读取请求的可用性Availability for read requests 至少为 99.9%(冷访问层为 99%)At least 99.9% (99% for cool access tier) 至少为 99.9%(冷访问层为 99%)At least 99.9% (99% for cool access tier) GRS 至少为 99.9%(冷访问层为 99%)At least 99.9% (99% for cool access tier) for GRS

对于 RA-GRS,至少为 99.99%(冷访问层为 99.9%)At least 99.99% (99.9% for cool access tier) for RA-GRS
对于 GZRS,至少为 99.9%(冷访问层为 99%)At least 99.9% (99% for cool access tier) for GZRS

对于 RA-GZRS,至少为 99.99%(冷访问层为 99.9%)At least 99.99% (99.9% for cool access tier) for RA-GZRS
写入请求的可用性Availability for write requests 至少为 99.9%(冷访问层为 99%)At least 99.9% (99% for cool access tier) 至少为 99.9%(冷访问层为 99%)At least 99.9% (99% for cool access tier) 至少为 99.9%(冷访问层为 99%)At least 99.9% (99% for cool access tier) 至少为 99.9%(冷访问层为 99%)At least 99.9% (99% for cool access tier)
在单独的节点上维护的数据副本数Number of copies of data maintained on separate nodes 单个区域内的三个副本Three copies within a single region 在单个区域内跨不同的可用性区域的三个副本Three copies across separate availability zones within a single region 共六个副本,包括主要区域的三个副本和第三个副本Six copies total, including three in the primary region and three in the secondary region 六个副本总数,其中包括主要区域的三个不同的可用性区域和次要区域中的三个本地冗余副本Six copies total, including three across separate availability zones in the primary region and three locally redundant copies in the secondary region

持久性和可用性(按中断方案)Durability and availability by outage scenario

下表指示数据是否持久且在给定方案中可用,具体取决于对存储帐户启用的冗余类型:The following table indicates whether your data is durable and available in a given scenario, depending on which type of redundancy is in effect for your storage account:

中断方案Outage scenario LRSLRS ZRSZRS GRS/RA-GRSGRS/RA-GRS GZRS/RA-GZRSGZRS/RA-GZRS
数据中心内的节点变为不可用A node within a data center becomes unavailable Yes Yes Yes Yes
整个数据中心(区域性或非区域性)不可用An entire data center (zonal or non-zonal) becomes unavailable No Yes 1Yes1 Yes
主要区域发生区域范围的服务中断A region-wide outage occurs in the primary region No No 1Yes1 1Yes1
如果主区域变得不可用,可对次要区域进行读取访问Read access to the secondary region is available if the primary region becomes unavailable No No 是(通过 RA-GRS)Yes (with RA-GRS) 是(通过 RA-GZRS)Yes (with RA-GZRS)

1 如果主要区域变为不可用,则需要执行帐户故障转移来恢复写入可用性。1 Account failover is required to restore write availability if the primary region becomes unavailable. 有关详细信息,请参阅灾难恢复和存储帐户故障转移For more information, see Disaster recovery and storage account failover.

支持的存储帐户类型Supported storage account types

下表显示了每种存储帐户类型都支持哪些冗余选项。The following table shows which redundancy options are supported by each type of storage account. 有关存储帐户类型,请参阅存储帐户概述For information for storage account types, see Storage account overview.

LRSLRS ZRSZRS GRS/RA-GRSGRS/RA-GRS GZRS/RA-GZRSGZRS/RA-GZRS
常规用途 v2General-purpose v2
常规用途 v1General-purpose v1
块 Blob 存储Block blob storage
Blob 存储Blob storage
文件存储File storage
常规用途 v2General-purpose v2
块 Blob 存储Block blob storage
文件存储File storage
常规用途 v2General-purpose v2
常规用途 v1General-purpose v1
Blob 存储Blob storage
常规用途 v2General-purpose v2

所有存储帐户的所有数据的复制均基于存储帐户的冗余选项。All data for all storage accounts is copied according to the redundancy option for the storage account. 复制的对象包括块 Blob、追加 Blob、页 Blob、队列、表和文件。Objects including block blobs, append blobs, page blobs, queues, tables, and files are copied. 将复制所有层(包括存档层)中的数据。Data in all tiers, including the archive tier, is copied. 有关 blob 层的详细信息,请参阅 Azure Blob 存储:热、冷和存档访问层For more information about blob tiers, see Azure Blob storage: hot, cool, and archive access tiers.

有关每个冗余选项的定价信息,请参阅 Azure 存储定价For pricing information for each redundancy option, see Azure Storage pricing.

备注

Azure 高级磁盘存储目前仅支持本地冗余存储 (LRS)。Azure Premium Disk Storage currently supports only locally redundant storage (LRS). 块 Blob 存储帐户在本地支持特定区域中的本地冗余存储 (LRS) 和区域冗余存储 (ZRS)。Block blob storage accounts support locally redundant storage (LRS) and zone redundant storage (ZRS) in certain regions.

数据完整性Data integrity

Azure 存储使用循环冗余检查 (CRC) 定期验证存储的数据的完整性。Azure Storage regularly verifies the integrity of data stored using cyclic redundancy checks (CRCs). 如果检测到数据损坏,则使用冗余数据进行修复。If data corruption is detected, it is repaired using redundant data. Azure 存储还对所有网络流量计算校验和,以检测存储或检索数据时数据包损坏的情况。Azure Storage also calculates checksums on all network traffic to detect corruption of data packets when storing or retrieving data.

另请参阅See also