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
Copy file name to clipboardExpand all lines: articles/storage/blobs/object-replication-overview.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,15 +25,18 @@ To learn how to configure object replication, see [Configure object replication
25
25
26
26
## How object replication works
27
27
28
-
Object replication asynchronously copies a specified set of block blobs from a container in one storage account to a container in another account. Object replication happens asynchronously and is [eventually consistent](https://en.wikipedia.org/wiki/Eventual_consistency). After you configure object replication on the source account, Azure Storage checks the change feed every minute(???) and replicates any write or delete operations to the destination account. Replication latency depends on the size of the block blob being replicated.
28
+
Object replication asynchronously copies all or a specified set of block blobs from a container in one storage account to a container in another account. After you configure object replication on the source account, Azure Storage checks the change feed regularly and replicates any write or delete operations to the destination account. Replication latency depends on the size of the block blob being replicated.
29
+
30
+
> [!IMPORTANT]
31
+
> Because block blob data is replicated asynchronously, the source account and destination account are not immediately in sync. There's currently no SLA on how long it takes to replicate data to the destination account.
29
32
30
33
### Configure a replication policy
31
34
32
35
To use object replication, create a replication policy on the source account that specifies the destination account. Then add one or more replication rules to the policy. Replication rules specify the source and destination containers and determine which block blobs in those containers will be copied.
33
36
34
37
A storage account can serve as the source account for up to two destination accounts. Each destination account may be in a different region. You can configure two separate replication policies to replicate data to each of the destination accounts.
35
38
36
-
The source and destination containers must both exist before you can create the replication policy. After you create the policy, the destination container is read-only. Any attempts to write to the destination container fail with error code 409 (Conflict).
39
+
The source and destination containers must both exist before you can create the replication policy. After you create the policy, the destination container is read-only. Any attempts to write to the destination container fail with error code 409 (Conflict). However, you can call the [Set Blob Tier](/rest/api/storageservices/set-blob-tier.md) operation on a blob in the destination container to move it to a different access tier. For example, you can move blobs in the destination container to the archive tier to save costs.
37
40
38
41
### Create rules on the replication policy
39
42
@@ -47,9 +50,9 @@ You can also specify one or more filters as part of a replication rule to filter
47
50
48
51
Object replication is supported for general-purpose v2 storage accounts only. Object replication is available in the following regions in preview:
49
52
50
-
-US East 2
51
-
-US Central
52
-
-Europe West
53
+
-France Central
54
+
-Canada East
55
+
-Canada Central
53
56
54
57
Both the source and destination accounts must reside in one of these regions in order to use object replication. The accounts can be in two different regions.
0 commit comments