Changes for GA

Author: David Curwin

articles/backup/azure-file-share-backup-overview.md

@@ -12,6 +12,7 @@ Azure file share backup is a native, cloud based backup solution that protects y
 ## Key benefits of Azure file share backup
 
 * Zero infrastructure: No deployment is needed to configure protection for your file shares.
+* Customized Retention: You can configure backups with daily/weekly/monthly/yearly retention according to your requirements.
 * Built in management capabilities: You can schedule backups and specify the desired retention period without the additional overhead of data pruning.
 * Instant restore: Azure file share backup uses file share snapshots, so you can select just the files you want to restore instantly.
 * Alerting and reporting: You can configure alerts for backup and restore failures and use the reporting solution provided by Azure Backup to get insights on backups across your files shares.
@@ -46,7 +47,7 @@ Azure File share backup is a snapshot-based solution and storage charges incurre
 However, the protected instance fee for leveraging the backup solution is according to the pricing model described under the [Backup For Azure Files](https://azure.microsoft.com/pricing/details/backup/) section. Currently, the actual price has been updated only for West Central US. For other regions, exact prices will be updated soon with some regional variations, but using the same pricing model.
 
 >[!NOTE]
->During preview, there is no "Protected Instance fee" and you will be charged only for snapshots according to the pricing mentioned [here](https://azure.microsoft.com/pricing/details/storage/files/).
+>There is now no "Protected Instance fee" and you will be charged only for snapshots according to the pricing mentioned [here](https://azure.microsoft.com/pricing/details/storage/files/).
 
 ## Next steps
 

articles/backup/backup-afs.md

@@ -18,19 +18,7 @@ In this article, you'll learn how to:
 ## Prerequisites
 
 * Identify or create a [Recovery Services vault](#create-a-recovery-services-vault) in the same region as the storage account that hosts the file share.
-* Ensure that the file share is present in one of the [supported storage account types](#limitations-for-azure-file-share-backup-during-preview).
-
-## Limitations for Azure file share backup during preview
-
-Backup for Azure file shares is in preview. Azure file shares in both general-purpose v1 and general-purpose v2 storage accounts are supported. Here are the limitations for backing up Azure file shares:
-
-* Support for backup of Azure file shares in storage accounts with [zone-redundant storage](https://docs.microsoft.com/azure/storage/common/storage-redundancy-zrs) (ZRS) replication is currently limited to [these regions](https://docs.microsoft.com/azure/backup/backup-azure-files-faq#in-which-geos-can-i-back-up-azure-file-shares).
-* Azure Backup currently supports configuring scheduled once-daily backups of Azure file shares.
-* The maximum number of scheduled backups per day is one.
-* The maximum number of on-demand backups per day is four.
-* Use [resource locks](https://docs.microsoft.com/cli/azure/resource/lock?view=azure-cli-latest) on the storage account to prevent accidental deletion of backups in your Recovery Services vault.
-* Don't delete snapshots created by Azure Backup. Deleting snapshots can result in loss of recovery points or restore failures.
-* Don't delete file shares that are protected by Azure Backup. The current solution deletes all snapshots taken by Azure Backup after the file share is deleted, so all restore points will be lost.
+* Ensure that the file share is present in one of the [supported storage account types](afs-support-matrix.md).
 
 [!INCLUDE [How to create a Recovery Services vault](../../includes/backup-create-rs-vault.md)]
 
@@ -75,20 +63,23 @@ To modify the storage replication type:
 
 1. After you select **Backup**, the **Backup** pane opens and prompts you to select a storage account from a list of discovered supported storage accounts. They're either associated with this vault or present in the same region as the vault, but not yet associated to any Recovery Services vault.
 
-   ![Select storage account](./media/backup-afs/select-storage-account.png)
-
 1. From the list of discovered storage accounts, select an account, and select **OK**. Azure searches the storage account for file shares that can be backed up. If you recently added your file shares and don't see them in the list, allow some time for the file shares to appear.
 
     ![Discovering file shares](./media/backup-afs/discovering-file-shares.png)
 
 1. From the **File Shares** list, select one or more of the file shares you want to back up. Select **OK**.
 
+   ![Select the file shares](./media/backup-afs/select-file-shares.png)
+
 1. After you choose your file shares, the **Backup** menu switches to **Backup policy**. From this menu, either select an existing backup policy or create a new one. Then select **Enable Backup**.
 
     ![Select Backup policy](./media/backup-afs/select-backup-policy.png)
 
 After you set a backup policy, a snapshot of the file shares is taken at the scheduled time. The recovery point is also retained for the chosen period.
 
+>[!NOTE]
+>Azure Backup now supports policies with daily/weekly/monthly/yearly retention for Azure file share backup.
+
 ## Create an on-demand backup
 
 Occasionally, you might want to generate a backup snapshot, or recovery point, outside of the times scheduled in the backup policy. A common reason to generate an on-demand backup is right after you've configured the backup policy. Based on the schedule in the backup policy, it might be hours or days until a snapshot is taken. To protect your data until the backup policy engages, initiate an on-demand backup. Creating an on-demand backup is often required before you make planned changes to your file shares.
@@ -119,8 +110,15 @@ Occasionally, you might want to generate a backup snapshot, or recovery point, o
 
 1. Monitor the portal notifications to keep a track of backup job run completion. You can monitor the job progress in the vault dashboard. Select **Backup Jobs** > **In progress**.
 
+## Best practices
+
+* Don't delete snapshots created by Azure Backup. Deleting snapshots can result in loss of recovery points and/or restore failures.
+
+* Use [resource locks](https://docs.microsoft.com/cli/azure/resource/lock?view=azure-cli-latest) on the storage account to prevent accidental deletion of backups in your Recovery services vault.
+
 ## Next steps
 
 Learn how to:
+
 * [Restore Azure file shares](restore-afs.md)
 * [Manage Azure file share backups](manage-afs-backup.md)

articles/backup/backup-azure-afs-automation.md

@@ -21,7 +21,6 @@ This article explains how to:
 ## Before you start
 
 * [Learn more](backup-azure-recovery-services-vault-overview.md) about Recovery Services vaults.
-* Read about the preview capabilities for [backing up Azure file shares](backup-afs.md).
 * Review the PowerShell object hierarchy for Recovery Services.
 
 ## Recovery Services object hierarchy
@@ -40,12 +39,12 @@ Set up PowerShell as follows:
 
 1. [Download the latest version of Az PowerShell](/powershell/azure/install-az-ps). The minimum version required is 1.0.0.
 
-> [!WARNING]
-> The minimum version of PS required for preview was 'Az 1.0.0'. Due to upcoming changes for GA, the minimum PS version required will be 'Az.RecoveryServices 2.6.0'. It is very important to upgrade all existing PS versions to this version. Otherwise, the existing scripts will break after GA. Install the minimum version with the following PS commands
+    > [!WARNING]
+    > The minimum PS version required for Azure file share backup is **Az.RecoveryServices 2.6.0**. Please upgrade your version to avoid any issues with the existing scripts. Install the minimum version with the following PS command:
 
-```powershell
-Install-module -Name Az.RecoveryServices -RequiredVersion 2.6.0
-```
+    ```powershell
+    Install-module -Name Az.RecoveryServices -RequiredVersion 2.6.0
+    ```
 
 2. Find the Azure Backup PowerShell cmdlets with this command:
 
@@ -282,14 +281,12 @@ testAzureFS       Backup               Completed            11/12/2018 2:42:07 P
 
 Azure file share snapshots are used while the backups are taken, so usually the job completes by the time the command returns this output.
 
-### Using on-demand backups to extend retention
+### Using a runbook to schedule backups
 
-On-demand backups can be used to retain your snapshots for 10 years. Schedulers can be used to run on-demand PowerShell scripts with chosen retention and thus take snapshots at regular intervals every week, month, or year. While taking regular snapshots, refer to the [limitations of on-demand backups](https://docs.microsoft.com/azure/backup/backup-azure-files-faq#how-many-on-demand-backups-can-i-take-per-file-share) using Azure backup.
+If you are looking for sample scripts, you can refer to the [sample script on GitHub](https://github.com/Azure-Samples/Use-PowerShell-for-long-term-retention-of-Azure-Files-Backup) using an Azure Automation runbook.
 
-If you are looking for sample scripts, you can refer to the sample script on GitHub (<https://github.com/Azure-Samples/Use-PowerShell-for-long-term-retention-of-Azure-Files-Backup>) using Azure Automation runbook that enables you to schedule backups on a periodic basis and retain them even up to 10 years.
-
-> [!WARNING]
-> Make sure the PS version is upgraded to the minimum version for 'Az.RecoveryServices 2.6.0' for AFS backups in your automation runbooks. You will have to replace the old 'AzureRM' module with 'Az' module. With this version, the 'friendlyName' filter is available for ```Get-AzRecoveryServicesBackupItem``` command. Pass the azure file share name to friendlyName parameter. If you pass the azure file share name to the 'Name' parameter, this version throws a warning to pass this friendly name to the friendly name parameter.
+>[!NOTE]
+> Azure File share Backup Policy now supports configuring backup with daily/weekly/monthly/yearly retention.
 
 ## Next steps
 

articles/backup/backup-azure-files-faq.md

@@ -13,96 +13,45 @@ To quickly scan the sections in this article, use the links to the right, under
 
 ## Configuring the backup job for Azure Files
 
-### Why can't I see some of my Storage Accounts I want to protect, that contain valid Azure file shares?
+### Why can't I see some of my Storage Accounts that I want to protect, which contain valid Azure file shares?
 
-Refer to the [Support Matrix for Azure file shares backup](afs-support-matrix.md) to ensure the storage account belongs to one of the supported storage account types. It is also possible that the Storage Account you are looking for is already protected or registered with another Vault. [Unregister the storage account](manage-afs-backup.md#unregister-a-storage-account) from the vault to discover the Storage Account in other vaults for protection.
+Refer to the [Support Matrix for Azure file shares backup](afs-support-matrix.md) to ensure the storage account belongs to one of the supported storage account types. It's also possible the Storage Account you're looking for is already protected or registered with another Vault. [Unregister the storage account](manage-afs-backup.md#unregister-a-storage-account) from the vault to discover the Storage Account in other vaults for protection.
 
 ### Why can't I see some of my Azure file shares in the Storage Account when I'm trying to configure backup?
 
 Check if the Azure file share is already protected in the same Recovery Services vault or if it has been deleted recently.
 
 ### Can I protect File Shares connected to a Sync Group in Azure Files Sync?
 
-Yes. Protection of Azure File Shares connected to Sync Groups is enabled and part of Public preview.
+Yes. Protection of Azure File Shares connected to Sync Groups is enabled.
 
-### When trying to back up file shares, I clicked on a Storage Account for discovering the file shares in it. However, I did not protect them. How do I protect these file shares with any other Vault?
+### When trying to back up file shares, I clicked on a Storage Account for discovering the file shares in it. However, I didn't protect them. How do I protect these file shares with any other vault?
 
 When trying to back up, selecting a Storage Account to discover file shares within it registers the Storage Account with the vault from which this is done. If you choose to protect the file shares with a different vault, [unregister](manage-afs-backup.md#unregister-a-storage-account) the chosen Storage Account from this vault.
 
 ### Can I change the Vault to which I back up my file shares?
 
 Yes. However, you'll need to [stop protection on the file share](manage-afs-backup.md#stop-protection-on-a-file-share) from the connected vault, [unregister](manage-afs-backup.md#unregister-a-storage-account) this Storage Account, and then protect it from a different vault.
 
-### In which geos can I back up Azure File shares?
-
-Backup for Azure File shares is currently in Preview and is available only in the following geos:
-
-- Australia East (AE)
-- Australia South East (ASE)
-- Brazil South (BRS)
-- Canada Central (CNC)
-- Canada East (CE)
-- Central US (CUS)
-- East Asia (EA)
-- East US (EUS)
-- East US 2 (EUS2)
-- Japan East (JPE)
-- Japan West (JPW)
-- India Central (INC)
-- India South (INS)
-- Korea Central (KRC)
-- Korea South (KRS)
-- North Central US (NCUS)
-- North Europe (NE)
-- South Central US (SCUS)
-- South East Asia (SEA)
-- UK South (UKS)
-- UK West (UKW)
-- West Europe (WE)
-- West US (WUS)
-- West Central US (WCUS)
-- West US 2 (WUS 2)
-- US Gov Arizona (UGA)
-- US Gov Texas (UGT)
-- US Gov Virginia (UGV)
-- Australia Central (ACL)
-- India West(INW)
-- South Africa North(SAN)
-- UAE North(UAN)
-- France Central (FRC)
-- Germany North (GN)                       
-- Germany West Central (GWC)
-- South Africa West (SAW)
-- UAE Central (UAC)
-- NWE (Norway East)     
-- NWW (Norway West)
-- SZN (Switzerland North)
-
-Write to [[email protected]](mailto:[email protected]) if you need to use it in a specific geo that is not listed above.
-
 ### How many Azure file shares can I protect in a Vault?
 
-During the preview, you can protect Azure file shares from up to 50 Storage Accounts per Vault. You can also protect up to 200 Azure file shares in a single vault.
+You can protect Azure file shares from up to 50 Storage Accounts per Vault. You can also protect up to 200 Azure file shares in a single vault.
 
 ### Can I protect two different file shares from the same Storage Account to different Vaults?
 
 No. All file shares in a Storage Account can be protected only by the same Vault.
 
 ## Backup
 
-### How many scheduled backups can I configure per file share?
-
-Azure Backup currently supports configuring scheduled once-daily backups of Azure File Shares.
-
-### How many On-Demand backups can I take per file share?
+### What should I do if my backups start failing due to the maximum limit reached error?
 
-You can have up to 200 Snapshots for a file share at any point in time. The limit includes snapshots taken by Azure Backup as defined by your policy. If your backups start failing after reaching the limit, delete On-Demand restore points for successful future backups.
+You can have up to 200 Snapshots for a file share at any point in time. The limit includes snapshots taken by Azure Backup as defined by your policy. If your backups start failing after reaching the limit, delete On-Demand snapshots for successful future backups.
 
 ## Restore
 
 ### Can I recover from a deleted Azure file share?
 
-When an Azure file share is deleted, you're shown the list of backups that will be deleted and a confirmation is sought. A deleted Azure file share can't be restored.
+When an Azure file share is deleted, you're shown the list of backups that will be deleted and a confirmation is requested. Currently, a deleted Azure file share can't be restored.
 
 ### Can I restore from backups if I stopped protection on an Azure file share?
 
@@ -116,15 +65,15 @@ If an ongoing restore job is canceled, the restore process stops and all files r
 
 ### Can I use PowerShell to configure/manage/restore backups of Azure File shares?
 
-Yes. Please refer to the detailed documentation [here](backup-azure-afs-automation.md)
+Yes. Refer to the detailed documentation [here](backup-azure-afs-automation.md).
 
-### Can I access the snapshots taken by Azure Backups and mount it?
+### Can I access the snapshots taken by Azure Backups and mount them?
 
-All Snapshots taken by Azure Backup can be accessed by Viewing Snapshots in the portal, PowerShell, or CLI. To learn more about Azure Files share snapshots, see [Overview of share snapshots for Azure Files (preview)](../storage/files/storage-snapshots-files.md).
+All snapshots taken by Azure Backup can be accessed by viewing snapshots in the portal, PowerShell, or CLI. To learn more about Azure Files share snapshots, see [Overview of share snapshots for Azure Files (preview)](../storage/files/storage-snapshots-files.md).
 
 ### What is the maximum retention I can configure for backups?
 
-Backup for Azure file shares offers the ability to configure policies with retention up to 180 days. However, using the ["On-demand backup" option in PowerShell](backup-azure-afs-automation.md#trigger-an-on-demand-backup), you can retain a recovery point even for 10 years.
+Refer to the [support matrix](afs-support-matrix.md) for details on maximum retention. Azure Backup does a real-time calculation of the number of snapshots when you enter the retention values while configuring backup policy. As soon as the number of snapshots corresponding to your defined retention values exceeds 200, it will show a warning requesting that you adjust your retention values. This is so you don’t exceed the limit of maximum number of snapshots supported by Azure Files for any file share at any point in time.
 
 ### What happens when I change the Backup policy for an Azure file share?