You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ZRS currently supports standard general-purpose v2 account types. For more information on storage account types, see [Azure storage account overview](storage-account-overview.md).
17
+
ZRS currently supports standard general-purpose v2 account types. For more information about storage account types, see [Azure storage account overview](storage-account-overview.md).
18
18
19
19
ZRS is available for block blobs, non-disk page blobs, files, tables, and queues.
20
20
@@ -32,60 +32,70 @@ ZRS is generally available in the following regions:
32
32
Microsoft continues to enable ZRS in additional Azure regions. Check the [Azure Service Updates](https://azure.microsoft.com/updates/) page regularly for information about new regions.
33
33
34
34
## What happens when a zone becomes unavailable?
35
-
Your data remains resilient if a zone becomes unavailable. Microsoft recommends that you continue to follow practices for transient fault handling, such as implementing retry policies with exponential back-off. When a zone is unavailable, Azure undertakes networking updates, such as DNS repointing. These updates may affect your application if you are accessing your data before they have completed.
35
+
Your data is still accessible even if a zone becomes unavailable. Microsoft recommends that you continue to follow practices for transient fault handling. These practices include implementing retry policies with exponential back-off.
36
+
37
+
When a zone is unavailable, Azure undertakes networking updates, such as DNS repointing. These updates may affect your application if you are accessing your data before the updates have completed.
36
38
37
39
ZRS may not protect your data against a regional disaster where multiple zones are permanently affected. Instead, ZRS offers resiliency for your data if it becomes temporarily unavailable. For protection against regional disasters, Microsoft recommends using geo-redundant storage (GRS). For more information about GRS, see [Geo-redundant storage (GRS): Cross-regional replication for Azure Storage](storage-redundancy-grs.md).
38
40
39
41
## Converting to ZRS replication
40
-
Today, you can use either the Azure portal or the Storage Resource Provider API to change your account's redundancy type, as long as you are migrating to or from to LRS, GRS, and RA-GRS. With ZRS, however, migration is not as straightforward because it involves the physical data movement from a single storage stamp to multiple stamps within a region.
42
+
Migrating to or from LRS, GRS, and RA-GRS is straightforward. Use the Azure portal or the Storage Resource Provider API to change your account's redundancy type. Azure will then replicate your data accordingly.
43
+
44
+
Migrating data to or from ZRS requires a different strategy. ZRS migration involves the physical movement of data from a single storage stamp to multiple stamps within a region.
45
+
46
+
There are two primary options for migration to or from ZRS:
41
47
42
-
You have two primary options for migration to or from ZRS. You can manually copy or move data to a new ZRS account from your existing account. You can also request a live migration. Microsoft strongly recommends that you perform a manual migration because there is no guarantee as to when a live migration will complete. A manual migration route provides more flexibility than a live migration does, and you are in control of the timing of the migration.
48
+
- Manually copy or move data to a new ZRS account from an existing account.
49
+
- Request a live migration.
43
50
44
-
To perform a manual migration, you have a variety options:
45
-
- Use existing tooling like AzCopy, the storage SDK, reliable third-party tools, etc.
46
-
- If you are familiar with Hadoop or HDInsight, you can attach both source and destination (ZRS) account to your cluster and use something like DistCp to massively parallelize the data copy process
47
-
- Build your own tooling leveraging one flavor of the storage SDK
51
+
Microsoft strongly recommends that you perform a manual migration. A manual migration provides more flexibility than a live migration. With a manual migration, you're in control of the timing.
48
52
49
-
If, however, a manual migration will result in some application downtime and you are unable to absorb that on your end, then Microsoft provides a live migration option. A live migration is an in-place migration that allows you to continue using your existing storage account while your data is migrated between source and destination storage stamps. During migration, you will still have the same level of durability and availability SLA as you do normally.
53
+
To perform a manual migration, you have options:
54
+
- Use existing tooling like AzCopy, one of the Azure Storage client libraries, or reliable third-party tools.
55
+
- If you're familiar with Hadoop or HDInsight, attach both source and destination (ZRS) account to your cluster. Then, parallelize the data copy process with a tool like DistCp.
56
+
- Build your own tooling using one of the Azure Storage client libraries.
50
57
51
-
Live migration does come with certain restrictions, however. They are listed below.
58
+
A manual migration can result in application downtime. If your application requires high availability, Microsoft also provides a live migration option. A live migration is an in-place migration.
52
59
53
-
- While Microsoft will address your live migration request promptly, there is no guarantee as to when the migration will complete. If you need your data to be in ZRS by a certain time, then you should do a manual migration. Generally, the more data you have in your account, the longer it will take to migrate that data.
54
-
- You may only perform a live migration from an account using LRS or GRS replication. If your account uses RA-GRS, then you will need to first migrate to one of these replication types before proceeding. This intermediary step ensures that the secondary read-only endpoint which RA-GRS provides is removed prior to migration.
60
+
During a live migration, you can use your storage account while your data is migrated between source and destination storage stamps. During the migration process, you have the same level of durability and availability SLA as you do normally.
61
+
62
+
Keep in mind the following restrictions on live migration:
63
+
64
+
- While Microsoft handles your request for live migration promptly, there's no guarantee as to when a live migration will complete. If you need your data migrated to ZRS by a certain date, then Microsoft recommends that you perform a manual migration instead. Generally, the more data you have in your account, the longer it takes to migrate that data.
65
+
- Live migration is supported only for storage accounts that use LRS or GRS replication. If your account uses RA-GRS, then you need to first change your account's replication type to either LRS or GRS before proceeding. This intermediary step removes the secondary read-only endpoint provided by RA-GRS before migration.
55
66
- Your account must contain data.
56
-
- Only intra-region migrations are supported. If you want to migrate your data into a ZRS account located in a region different than the source account, then you must perform a manual migration.
57
-
- Only standard storage account types are supported. You cannot migrate from a premium storage account.
58
-
59
-
Live migration requests go through Azure Support portal. From the portal, you select the storage account you want to convert to ZRS.
60
-
1. Click **New Support Request**
61
-
2. Verify the Basics. Click **Next**.
62
-
3. On the **Problem** section,
63
-
- Leave Severity as-is.
64
-
- Problem Type = **Data Migration**
65
-
- Category = **Migrate to ZRS within a region**
66
-
- Title = **ZRS account migration** (or something descriptive)
67
-
- Details = I would like to migrate to ZRS from [LRS, GRS] in the ______ region.
68
-
4. Click **Next**.
69
-
5. Verify that the Contact Info is correct on the Contact Info blade.
70
-
6. Click **Submit**.
71
-
72
-
A support person will then be in contact with you. That person will be available to provide any assistance you may require.
67
+
- You can only migrate data within the same region. If you want to migrate your data into a ZRS account located in a region different than the source account, then you must perform a manual migration.
68
+
- Only standard storage account types support live migration. Premium storage accounts must be migrated manually.
69
+
70
+
You can request live migration through the [Azure Support portal](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview). From the portal, select the storage account you want to convert to ZRS.
71
+
1. Select **New Support Request**
72
+
2. Complete the **Basics** based on your account information. In the **Service** section, select **Storage Account Management** and the resource you want to convert to ZRS.
73
+
3. Select **Next**.
74
+
4. Specify the following values the **Problem** section:
75
+
-**Severity**: Leave the default value as-is.
76
+
-**Problem Type**: Select **Data Migration**.
77
+
-**Category**: Select **Migrate to ZRS within a region**.
78
+
-**Title**: Type a descriptive title, for example, **ZRS account migration**.
79
+
-**Details**: Type additional details in the **Details** box, for example, I would like to migrate to ZRS from [LRS, GRS] in the ______ region.
80
+
5. Select **Next**.
81
+
6. Verify that the contact information is correct on the **Contact information** blade.
82
+
7. Select **Create**.
83
+
84
+
A support person will contact you and provide any assistance you need.
73
85
74
86
## ZRS Classic: A legacy option for block blobs redundancy
75
87
> [!NOTE]
76
-
> Microsoft will deprecate and migrate ZRS Classic accounts on March 31, 2021. More details will be provided to ZRS Classic customers prior to deprecation.
88
+
> Microsoft will deprecate and migrate ZRS Classic accounts on March 31, 2021. More details will be provided to ZRS Classic customers before deprecation.
77
89
>
78
-
> When ZRS becomes [generally available](#support-coverage-and-regional-availability) in a region, customers will no longer be able to create ZRS Classic accounts from the portal in that region. Using Microsoft PowerShell and Azure CLI to create ZRS Classic accounts is supported until ZRS Classic is deprecated.
90
+
> Once ZRS becomes [generally available](#support-coverage-and-regional-availability) in a region, customers won't be able to create ZRS Classic accounts from the portal in that region. Using Microsoft PowerShell and Azure CLI to create ZRS Classic accounts is an option until ZRS Classic is deprecated.
79
91
80
-
ZRS Classic asynchronously replicates data across data centers within one to two regions. A replica may not be available unless Microsoft initiates failover to the secondary. A ZRS Classic account cannot be converted to or from LRSor GRS, and does not have metrics or logging capability.
92
+
ZRS Classic asynchronously replicates data across data centers within one to two regions. Replicated data may not be available unless Microsoft initiates failover to the secondary. A ZRS Classic account can't be converted to or from LRS, GRS, or RA-GRS. ZRS Classic accounts also don't support metrics or logging.
81
93
82
94
ZRS Classic is available only for **block blobs** in general-purpose V1 (GPv1) storage accounts. For more information about storage accounts, see [Azure storage account overview](storage-account-overview.md).
83
95
84
-
ZRS Classic accounts cannot be converted to or from LRS, GRS, or RA-GRS. ZRS Classic accounts also do not support metrics or logging.
85
-
86
-
To manually migrate ZRS account data to or from an LRS, ZRS Classic, GRS, or RA-GRS account, use AzCopy, Azure Storage Explorer, Azure PowerShell, or Azure CLI. You can also build your own migration solution with one of the Azure Storage client libraries.
96
+
To manually migrate ZRS account data to or from an LRS, ZRS Classic, GRS, or RA-GRS account, use one of the following tools: AzCopy, Azure Storage Explorer, Azure PowerShell, or Azure CLI. You can also build your own migration solution with one of the Azure Storage client libraries.
Copy file name to clipboardExpand all lines: includes/storage-common-redundancy-zrs.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,15 @@
5
5
author: tamram
6
6
ms.service: storage
7
7
ms.topic: include
8
-
ms.date: 07/11/2018
8
+
ms.date: 11/04/2018
9
9
ms.author: tamram
10
10
ms.custom: include file
11
11
---
12
12
13
-
Zone-redundant storage (ZRS) replicates your data synchronously across three storage clusters in a single region. Each storage cluster is physically separated from the others and resides in its own availability zone (AZ). Each availability zone, and the ZRS cluster within it, is autonomous, with separate utilities and networking capabilities.
13
+
Zone-redundant storage (ZRS) replicates your data synchronously across three storage clusters in a single region. Each storage cluster is physically separated from the others and is located in its own availability zone (AZ). Each availability zone—and the ZRS cluster within it—is autonomous and includes separate utilities and networking features.
14
14
15
-
Storing your data in a ZRS account ensures that you will be able access and manage your data in the event that a zone becomes unavailable. ZRS provides excellent performance and low latency. ZRS offers the same [scalability targets](../articles/storage/common/storage-scalability-targets.md) as [locally-redundant storage (LRS)](../articles/storage/common/storage-redundancy-lrs.md).
15
+
When you store your data in a storage account using ZRS replication, you can continue to access and manage your data if an availability zone becomes unavailable. ZRS provides excellent performance and low latency. ZRS offers the same [scalability targets](../articles/storage/common/storage-scalability-targets.md) as [locallyredundant storage (LRS)](../articles/storage/common/storage-redundancy-lrs.md).
16
16
17
-
Consider ZRS for scenarios that require strong consistency, strong durability, and high availability even if an outage or natural disaster renders a zonal data center unavailable. ZRS offers durability for storage objects of at least 99.9999999999% (12 9's) over a given year.
17
+
Consider ZRS for scenarios that require consistency, durability, and high availability. Even if an outage or natural disaster renders an availability zone unavailable, ZRS offers durability for storage objects of at least 99.9999999999% (12 9's) over a given year.
18
18
19
19
For more information about availability zones, see [Availability Zones overview](https://docs.microsoft.com/azure/availability-zones/az-overview).
0 commit comments