Merge pull request #102340 from dcurwin/support-afs

AFS Support Matrix

Author: ttorble

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.
@@ -33,7 +34,7 @@ Azure file share backup is a native, cloud based backup solution that protects y
 5. Based on the policy specified, the Azure Backup scheduler triggers backups at the scheduled time. As part of that job, the file share snapshot is created using  the File share API. Only the snapshot URL is stored in the metadata store.
 
     >[!NOTE]
-    >The file share data is not transferred to the Backup service, since the Backup service creates and manages snapshots that are part of your storage account.
+    >The file share data is not transferred to the Backup service, since the Backup service creates and manages snapshots that are part of your storage account, and backups are not transferred to the vault.
 
 6. You can restore the Azure file share contents (individual files or the full share) from snapshots available on the source file share. Once the operation is triggered, the snapshot URL is retrieved from the metadata store and the data is listed and transferred from the source snapshot to the target file share of your choice.
 
@@ -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/azure-file-share-support-matrix.md

@@ -0,0 +1,81 @@
+---
+title: Support Matrix for Azure file share backup
+description: Provides a summary of support settings and limitations when backing up Azure file shares.
+ms.topic: conceptual
+ms.date: 1/26/2020
+---
+
+# Support matrix for Azure file share backup
+
+You can use the [Azure Backup service](https://docs.microsoft.com/azure/backup/backup-overview) to back up Azure file shares. This article summarizes support settings when you back up Azure file shares with Azure Backup.
+
+## Supported GEOS
+
+Backup for Azure file shares is available in the following GEOS:
+
+| GA regions | Supported regions but not GA                                                      |
+| ------------------------------------------------------------ | ------------------------------------------------------------ |
+| Australia East (AE), Canada Central (CNC),West Central US (WCUS), India South (INS), North Central US (NCUS), Japan East (JPE), Brazil South (BRS)                                                     |Australia South East (ASE), Canada East (CE),Central US (CUS),East Asia (EA),East US (EUS),East US 2 (EUS2), Japan West (JPW),India Central (INC), Korea Central (KRC),Korea South (KRS) ,North Europe (NE),South Central US (SCUS),South East Asia (SEA),UK South (UKS),UK West (UKW),West Europe (WE),West US (WUS), 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),Norway East (NWE),Norway West (NWW),Switzerland North (SZN), West US 2 (WUS 2)             |
+
+## Supported storage accounts
+
+| Storage  account details | Support                                                      |
+| ------------------------ | ------------------------------------------------------------ |
+| Account  Kind            | Azure  Backup supports Azure file shares in both general-purpose v1 and general-purpose v2 storage accounts |
+| Performance              | Azure  Backup supports file shares in both standard and Premium Storage accounts |
+| Replication              | Azure  files shares in Storage Accounts with any replication type are  supported |
+
+## Supported file shares
+
+| File  share type                                   | Support   |
+| -------------------------------------------------- | --------- |
+| Standard                                           | Supported |
+| Large                                              | Supported |
+| Premium                                            | Supported |
+| File shares connected with Azure File sync service | Supported |
+
+## Protection limits
+
+| Setting                                                      | Limit |
+| ------------------------------------------------------------ | ----- |
+| Maximum  number of file shares that can be protected per day per vault | 200   |
+| Maximum  number of storage accounts that can be registered per vault per day | 50    |
+
+## Backup limits
+
+| Setting                                      | Limit |
+| -------------------------------------------- | ----- |
+| Maximum  number of on-demand backups per day | 4     |
+| Maximum  number of scheduled backups per day | 1     |
+
+## Restore limits
+
+| Setting                                                      | Limit   |
+| ------------------------------------------------------------ | ------- |
+| Maximum number of restores per day                           | 10      |
+| Maximum  number of files per restore                         | 10      |
+| Maximum  recommended restore size per restore for large file shares | 15  TiB |
+
+## Retention limits
+
+| Setting                                                      | Limit    |
+| ------------------------------------------------------------ | -------- |
+| Maximum total recovery points per  file share at any point in time | 200      |
+| Maximum retention of recovery  point created by on-demand backup | 10 years |
+| Maximum retention of daily recovery points (snapshots) per file share| 200 days |
+| Maximum retention of weekly recovery points (snapshots) per file share | 200 weeks |
+| Maximum retention of monthly recovery points (snapshots) per file share | 120 months |
+| Maximum retention of  yearly recovery points (snapshots) per file share | 10 years |
+
+## Supported restore methods
+
+| Restore method     | Details                                                      |
+| ------------------ | ------------------------------------------------------------ |
+| Full Share Restore | You can restore the complete file  share to the original or an alternate location |
+| Item Level Restore | You can restore individual files and folders to the original or an alternate location |
+
+## Next steps
+
+* Learn how to [Back up Azure file shares](backup-afs.md)
+* Learn how to [Restore Azure file shares](restore-afs.md)
+* Learn how to [Manage Azure file share backups](manage-afs-backup.md)

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](azure-file-share-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,18 @@ 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**.
 
+>[!NOTE]
+>Azure Backup locks the storage account when you configure protection for any file share in the corresponding account. This provides protection against accidental deletion of a storage account with backed up file shares.
+
+## Best practices
+
+* Don't delete snapshots created by Azure Backup. Deleting snapshots can result in loss of recovery points and/or restore failures.
+
+* Don't remove the lock taken on the storage account by Azure Backup. If you delete the lock, your storage account will be prone to accidental deletion and if it's deleted, you will lose your snapshots or backups.
+
 ## 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