Skip to content

Commit 51a39f2

Browse files
committed
OR preview
1 parent f7acc0b commit 51a39f2

File tree

2 files changed

+21
-10
lines changed

2 files changed

+21
-10
lines changed

articles/storage/blobs/object-replication-configure.md

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -100,9 +100,11 @@ Connect-AzAccount
100100
# Set resource group and account variables.
101101
$rgName = "<resource-group>"
102102
$srcAccountName = "<source-storage-account>"
103-
$srcContainerName = "<source-container>"
104103
$destAccountName = "<destination-storage-account>"
105-
$destContainerName = "<destination-container>"
104+
$srcContainerName1 = "source-container1"
105+
$destContainerName1 = "dest-container1"
106+
$srcContainerName2 = "source-container2"
107+
$destContainerName2 = "dest-container2"
106108
107109
# Enable change feed on the source account.
108110
Update-AzStorageBlobServiceProperty -ResourceGroupName $rgName `
@@ -112,6 +114,13 @@ Update-AzStorageBlobServiceProperty -ResourceGroupName $rgName `
112114
# View the service settings.
113115
Get-AzStorageBlobServiceProperty -ResourceGroupName $rgName `
114116
-StorageAccountName $accountName
117+
118+
# Create new containers in the source and destination accounts.
119+
$srcAccount | New-AzStorageContainer $srcContainerName1
120+
$destAccount | New-AzStorageContainer $destContainerName1
121+
$srcAccount | New-AzStorageContainer $srcContainerName2
122+
$destAccount | New-AzStorageContainer $destContainerName2
123+
115124
```
116125

117126

@@ -275,4 +284,4 @@ az storage account ors-policy remove \\
275284

276285
## Next steps
277286

278-
- [Object replication (preview)](object-replication-overview.md)
287+
- [Object replication overview (preview)](object-replication-overview.md)

articles/storage/blobs/object-replication-overview.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -25,15 +25,18 @@ To learn how to configure object replication, see [Configure object replication
2525

2626
## How object replication works
2727

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.
2932
3033
### Configure a replication policy
3134

3235
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.
3336

3437
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.
3538

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.
3740

3841
### Create rules on the replication policy
3942

@@ -47,9 +50,9 @@ You can also specify one or more filters as part of a replication rule to filter
4750

4851
Object replication is supported for general-purpose v2 storage accounts only. Object replication is available in the following regions in preview:
4952

50-
- US East 2
51-
- US Central
52-
- Europe West
53+
- France Central
54+
- Canada East
55+
- Canada Central
5356

5457
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.
5558

@@ -87,8 +90,7 @@ Register-AzProviderFeature -FeatureName AllowObjectReplication -ProviderNamespac
8790
Register-AzProviderFeature -FeatureName Changefeed -ProviderNamespace Microsoft.Storage
8891
8992
# Register for blob versioning (preview)
90-
Register-AzProviderFeature -ProviderNamespace Microsoft.Storage `
91-
-FeatureName Versioning
93+
Register-AzProviderFeature -FeatureName Versioning -ProviderNamespace Microsoft.Storage
9294
9395
# Refresh the Azure Storage provider namespace
9496
Register-AzResourceProvider -ProviderNamespace Microsoft.Storage

0 commit comments

Comments
 (0)