pitr

Author: tamram

articles/storage/blobs/point-in-time-restore-manage.md

@@ -60,34 +60,35 @@ Before you enable and configure point-in-time restore, enable its prerequisites:
 - [Enable and disable the change feed](storage-blob-change-feed.md#enable-and-disable-the-change-feed)
 - [Enable and manage blob versioning](versioning-enable.md)
 
-To configure Azure point-in-time restore with PowerShell, call the Enable-AzStorageBlobRestorePolicy command. The following example enables soft delete and sets the soft-delete retention period, enables change feed, and then enables point-in-time restore. Note that the retention period for point-in-time restore must be less than that set for soft delete.
+To configure Azure point-in-time restore with PowerShell, call the Enable-AzStorageBlobRestorePolicy command. The following example enables soft delete and sets the soft-delete retention period, enables change feed, and then enables point-in-time restore. Before running the example, use the Azure portal or an Azure Resource Manager template to also enable blob versioning.
 
 When running the example, remember to replace the values in angle brackets with your own values:
 
 ```powershell
-# Sign in to your Azure account
+# Sign in to your Azure account.
 Connect-AzAccount
 
-# Set resource group and account variables
+# Set resource group and account variables.
 $rgName = "<resource-group>"
 $accountName = "<storage-account>"
 
-# Enable soft delete with a retention of 6 days
+# Enable soft delete with a retention of 6 days.
 Enable-AzStorageBlobDeleteRetentionPolicy -ResourceGroupName $rgName `
     -StorageAccountName $accountName `
     -RetentionDays 6
 
-# Enable change feed
+# Enable change feed.
 Update-AzStorageBlobServiceProperty -ResourceGroupName $rgName `
     -StorageAccountName $accountName `
     -EnableChangeFeed $true
 
-# Enable point-in-time restore with a retention period of 5 days
+# Enable point-in-time restore with a retention period of 5 days.
+# The retention period for point-in-time restore must be at least one day less than that set for soft delete.
 Enable-AzStorageBlobRestorePolicy -ResourceGroupName $rgName `
     -StorageAccountName $accountName `
     -RestoreDays 5
 
-# View the service settings
+# View the service settings.
 Get-AzStorageBlobServiceProperty -ResourceGroupName $rgName `
     -StorageAccountName $accountName
 ```

articles/storage/blobs/point-in-time-restore-overview.md

@@ -96,6 +96,10 @@ Register-AzProviderFeature -FeatureName RestoreBlobRanges -ProviderNamespace Mic
 # Register for change feed (preview)
 Register-AzProviderFeature -FeatureName Changefeed -ProviderNamespace Microsoft.Storage
 
+# Register for blob versioning (preview)
+Register-AzProviderFeature -ProviderNamespace Microsoft.Storage `
+    -FeatureName Versioning
+
 # Refresh the Azure Storage provider namespace
 Register-AzResourceProvider -ProviderNamespace Microsoft.Storage
 ```
@@ -114,9 +118,9 @@ Get-AzProviderFeature -ProviderNamespace Microsoft.Storage `
 
 ## Pricing and billing
 
-Billing for point-in-time restore depends on the quantity of data processed to perform the restore operation. The quantity of data processed is a function of the number of objects in the storage account and the number of changes that occurred between the restore point and the present moment. For example, assuming a relatively constant rate of change to block blob data in a storage account, a restore operation that goes back in time 1 day would cost 1/10th of a restore that goes back in time 10 days.
+Billing for point-in-time restore depends on the amount of data processed to perform the restore operation. The amount of data processed is based on the number of changes that occurred between the restore point and the present moment. For example, assuming a relatively constant rate of change to block blob data in a storage account, a restore operation that goes back in time 1 day would cost 1/10th of a restore that goes back in time 10 days.
 
-To estimate the cost of a restore operation, review the change feed log to estimate the quantity of data modified during the restore period. For example, if the retention period for change feed is 30 days, and the size of the change feed is 10 MB, then restoring to a point 10 days earlier for a locally redundant (LRS) storage account would cost approximately one-third of the price listed for an LRS account in that region. Restoring to a point that is 27 days earlier would cost approximately nine-tenths of the price listed.
+To estimate the cost of a restore operation, review the change feed log to estimate the amount of data that was modified during the restore period. For example, if the retention period for change feed is 30 days, and the size of the change feed is 10 MB, then restoring to a point 10 days earlier would cost approximately one-third of the price listed for an LRS account in that region. Restoring to a point that is 27 days earlier would cost approximately nine-tenths of the price listed.
 
 For more information about pricing for point-in-time restore, see [Block blob pricing](https://azure.microsoft.com/pricing/details/storage/blobs/).
 

articles/storage/blobs/versioning-overview.md

@@ -221,9 +221,10 @@ To enroll in the blob versioning preview, use PowerShell or Azure CLI to submit
 To register with PowerShell, call the [Get-AzProviderFeature](/powershell/module/az.resources/get-azproviderfeature) command.
 
 ```powershell
+# Register for blob versioning (preview)
 Register-AzProviderFeature -ProviderNamespace Microsoft.Storage `
     -FeatureName Versioning
-    
+
 # Refresh the Azure Storage provider namespace
 Register-AzResourceProvider -ProviderNamespace Microsoft.Storage
 ```