Merge pull request #272519 from b-ahibbard/anf-disable-backup

enable/disable backup out of portal

Author: JamesJBarnett

articles/azure-netapp-files/.openpublishing.redirection.azure-netapp-files.json

@@ -24,6 +24,11 @@
             "source_path_from_root": "/articles/azure-netapp-files/azure-netapp-files-faqs.md",
             "redirect_url": "/azure/azure-netapp-files/faq-nfs",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-netapp-files/backup-disable.md",
+            "redirect_url": "/azure/azure-netapp-files/backup-configure-manual",
+            "redirect_document_id": false
         }
     ]
 }

articles/azure-netapp-files/TOC.yml

@@ -367,8 +367,6 @@
         href: backup-search.md 
       - name: Restore a backup
         href: backup-restore-new-volume.md 
-      - name: Disable backup functionality
-        href: backup-disable.md
       - name: Delete backups 
         href: backup-delete.md 	
     - name: Manage replication

articles/azure-netapp-files/azure-netapp-files-quickstart-set-up-account-create-volumes.md

@@ -14,7 +14,7 @@ ms.custom: devx-track-azurecli, subject-armqs, mode-ui, devx-track-azurepowershe
 
 This article shows you how to quickly set up Azure NetApp Files and create an NFS volume. 
 
-In this quickstart, you will set up the following items:
+In this quickstart, you set up the following items:
 
 - Registration for NetApp Resource Provider
 - A NetApp account
@@ -265,13 +265,13 @@ The following code snippet shows how to create a capacity pool in an Azure Resou
 
 4. Select **Protocol**, and then complete the following actions:
     * Select **NFS** as the protocol type for the volume.
-    * Enter **myfilepath1** as the file path that will be used to create the export path for the volume.
+    * Enter **myfilepath1** for the file path used to create the export path for the volume.
     * Select the NFS version (**NFSv3** or **NFSv4.1**) for the volume.
       See [considerations](azure-netapp-files-create-volumes.md#considerations) and [best practice](azure-netapp-files-create-volumes.md#best-practice) about NFS versions.
 
     ![Screenshot of NFS protocol for selection.](./media/azure-netapp-files-quickstart-set-up-account-create-volumes/azure-netapp-files-quickstart-protocol-nfs.png)
 
-5. Select **Review + create** to display information for the volume you are creating.  
+5. Select **Review + create** to display information for the volume you're creating.  
 
 6. Select **Create** to create the volume. 
     The created volume appears in the Volumes blade.
@@ -389,14 +389,13 @@ The following code snippets show how to set up a VNet and create an Azure NetApp
 
 # [Portal](#tab/azure-portal)
 
-When you are done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
+When you're done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
 
 > [!IMPORTANT]
-> All resources within the resource groups will be permanently deleted and cannot be undone.
-
+>Deleting a resource group also deletes all resources within it. The action can't be undone.  
 
 >[!IMPORTANT]
->Before you delete a resource group, you must first delete the backups. Deleting a resource group will not delete the backups. You can preemptively delete backups on volumes by [disabling the backup policy](backup-disable.md) or you can [manually delete the backups](backup-delete.md). If you delete the resource group without disabling backups, backups will continue to impact your billing.  
+>Before you delete a resource group, you must first delete the backups. Deleting a resource group doesn't delete the backups. You can preemptively delete backups on volumes by [manually delete the backups](backup-delete.md). If you delete the resource group without deleting all the backups, you lose the ability to see the backups. The backups, however, can continue to incur costs. If you're wrongly billed for some backups, open a support case ticket to get this issue resolved. 
 
 1. In the Azure portal's search box, enter **Azure NetApp Files** and then select **Azure NetApp Files** from the list that appears.
 
@@ -409,18 +408,18 @@ When you are done and if you want to, you can delete the resource group. The act
 
     ![Screenshot that highlights the Delete resource group button.](./media/azure-netapp-files-quickstart-set-up-account-create-volumes/azure-netapp-files-azure-delete-resource-group.png)
 
-    A window opens and displays a warning about the resources that will be deleted with the resource group.
+    A window opens and displays a warning about the resources to be deleted with the resource group.
 
 4. Enter the name of the resource group (myRG1) to confirm that you want to permanently delete the resource group and all resources in it, and then select **Delete**.
 
     ![Screenshot showing confirmation of deleting resource group.](./media/azure-netapp-files-quickstart-set-up-account-create-volumes/azure-netapp-files-azure-confirm-resource-group-deletion.png)
 
 # [PowerShell](#tab/azure-powershell)
 
-When you are done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
+When you're done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
 
 > [!IMPORTANT]
-> All resources within the resource groups will be permanently deleted and cannot be undone.
+>Deleting a resource group also deletes all resources within it. The action can't be undone.  
 
 1. Delete resource group by using the [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup) command.
 
@@ -430,10 +429,10 @@ When you are done and if you want to, you can delete the resource group. The act
 
 # [Azure CLI](#tab/azure-cli)
 
-When you are done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
+When you're done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
 
 > [!IMPORTANT]
-> All resources within the resource groups will be permanently deleted and cannot be undone.
+>Deleting a resource group also deletes all resources within it. The action can't be undone.  
 
 1. Delete resource group by using the [az group delete](/cli/azure/group#az-group-delete) command.
 

articles/azure-netapp-files/backup-configure-manual.md

@@ -10,39 +10,40 @@ ms.author: anfdocs
 ---
 # Configure manual backups for Azure NetApp Files 
 
-Azure NetApp Files backup supports *policy-based* (scheduled) backups and *manual* (on-demand) backups at the volume level. You can use both types of backups in the same volume. During the configuration process, you enable the backup feature for an Azure NetApp Files volume before policy-based backups or manual backups can be taken. 
+Azure NetApp Files backup supports *policy-based* (scheduled) backups and *manual* (on-demand) backups at the volume level. You can use both types of backups in the same volume. During the configuration process, you need to assign a backup vault to Azure NetApp Files volume before policy-based backups or manual backups can be created. 
 
 This article shows you how to configure manual backups. For policy-based backup configuration, see [Configure policy-based backups](backup-configure-policy-based.md).  
 
 ## About manual backups  
 
-Every Azure NetApp Files volume must have the backup functionality enabled before any backups (policy-based or manual) can be taken.   
+Every Azure NetApp Files volume must have a backup vault assigned before any backups (policy-based or manual) can be taken.   
 
-After you enable the backup functionality, you can choose to manually back up a volume. A manual backup takes a point-in-time snapshot of the active file system and backs up   that snapshot to the Azure storage account.
+After you assign a backup vault, you can choose to manually back up a volume. A manual backup takes a point-in-time snapshot of the active file system and backs up that snapshot to the Azure storage account.
 
 The following list summarizes manual backup behaviors:  
 
-* You can create manual backups on a volume even if the volume is already backup-enabled and configured with backup policies.  However, there can be only one outstanding manual-backup request for the volume. If you assign a backup policy and if the baseline transfer is still in progress, then the creation of a manual backup will be blocked until the baseline transfer is complete.
+* You can create manual backups on a volume even if the volume is already assigned to a backup vault and configured with backup policies.  However, there can be only one outstanding manual-backup request for the volume. If you assign a backup policy and if the baseline transfer is still in progress, then the creation of a manual backup is blocked until the baseline transfer is complete.
 
-* Unless you specify an existing snapshot to use for a backup, creating a manual backup automatically generates a snapshot on the volume. The snapshot is then transferred to Azure storage. The snapshot created on the volume will be retained until the next manual backup is created. During the subsequent manual backup operation, older snapshots will be cleaned up. You can't delete the snapshot generated for the latest manual backup. 
+* Unless you specify an existing snapshot to use for a backup, creating a manual backup automatically generates a snapshot on the volume. The snapshot is then transferred to Azure storage. The snapshot created on the volume will be retained until the next manual backup is created. During the subsequent manual backup operation, older snapshots are cleaned up. You can't delete the snapshot generated for the latest manual backup. 
 
 [!INCLUDE [Backup registration heading](includes/backup-registration.md)]
 
 ## Requirements
 
-* Azure NetApp Files now requires you to create a backup vault before enabling backup functionality. If you haven't configured a backup, see [Manage backup vaults](backup-vault-manage.md) for more information.
+* Azure NetApp Files requires you to assign a backup vault before allowing backup creation on a volume. To configure a backup vault, see [Manage backup vaults](backup-vault-manage.md) for more information.
 * [!INCLUDE [consideration regarding deleting backups after deleting resource or subscription](includes/disable-delete-backup.md)]
 
-## Enable backup functionality
+## Configure backups
 
-If you haven’t done so, enable the backup functionality for the volume before creating manual backups: 
+If you haven’t done so, assign a backup vault to the volume before creating manual backups: 
 
-1. Go to **Volumes** and select the specific volume for which you want to enable backup.
+1. Go to **Volumes** and select the specific volume for which you want to configure backups.
 2. Select **Configure**.
-3. In the Configure Backup page, toggle the **Enabled** setting to **On**.   
+3. In the Configure Backup page, select the backup vault from the dropdown menu.  
 4. Select **OK**.   
 
 ![Screenshot that shows the Enabled setting of Configure Backups window.](./media/shared/backup-configure-enabled.png)
+:::image type="content" source="./media/shared/backup-configure-enabled.png" alt-text="Screenshot of backup vault creation.":::
 
 ## Create a manual backup for a volume
 
@@ -61,7 +62,7 @@ If you haven’t done so, enable the backup functionality for the volume before
 
             `account1-pool1-vol1-backup1`   
 
-            If you're using a shorter form for the backup name, ensure that it still includes information that identifies the NetApp account, capacity pool, and volume name for display in the backup list.
+            If you're using a shorter form for the backup name, ensure that it includes information that identifies the NetApp account, capacity pool, and volume name for display in the backup list.
 
     2. If you want to use an existing snapshot for the backup, select the **Use Existing Snapshot** option.  When you use this option, ensure that the Name field matches the existing snapshot name that is being used for the backup. 
 
@@ -81,7 +82,6 @@ If you haven’t done so, enable the backup functionality for the volume before
 * [Manage backup policies](backup-manage-policies.md)
 * [Search backups](backup-search.md)
 * [Restore a backup to a new volume](backup-restore-new-volume.md)
-* [Disable backup functionality for a volume](backup-disable.md)
 * [Delete backups of a volume](backup-delete.md)
 * [Volume backup metrics](azure-netapp-files-metrics.md#volume-backup-metrics)
 * [Azure NetApp Files backup FAQs](faq-backup.md)

articles/azure-netapp-files/backup-configure-policy-based.md

@@ -12,7 +12,7 @@ ms.author: anfdocs
 
 Azure NetApp Files backup supports *policy-based* (scheduled) backups and *manual* (on-demand) backups at the volume level. You can use both types of backups in the same volume. During the configuration process, you'll enable the backup feature for an Azure NetApp Files volume before policy-based backups or manual backups can be taken. 
 
-This article shows you how to configure policy-based backups. For manual backup configuration, see [Configure manual backups](backup-configure-manual.md).  
+This article explains how to configure policy-based backups. For manual backup configuration, see [Configure manual backups](backup-configure-manual.md).  
 
 ## About policy-based backups    
 
@@ -28,7 +28,7 @@ Assigning a policy creates a baseline snapshot that is the current state of the
 
 A backup policy enables a volume to be protected on a regularly scheduled interval. It does not require snapshot policies to be configured. Backup policies will continue the daily cadence based on the time of day when the backup policy is linked to the volume, using the time zone of the Azure region where the volume exists. Weekly schedules are preset to occur each Monday after the daily cadence.  Monthly schedules are preset to occur on the first day of each calendar month after the daily cadence. If backups are needed at a specific time/day, consider using [manual backups](backup-configure-manual.md). 
 
-You need to create a backup policy and associate the backup policy to the volume that you want to back up. A single backup policy can be attached to multiple volumes. Backups can be temporarily suspended either by disabling the policy or by disabling backups at the volume level. Backups can also be completely disabled at the volume level, resulting in the clean-up of all the associated data in the Azure storage. A backup policy can't be deleted if it's attached to any volumes.
+You need to create a backup policy and associate the backup policy to the volume that you want to back up. A single backup policy can be attached to multiple volumes. Backups can be temporarily suspended by disabling the policy. A backup policy can't be deleted if it's attached to any volumes.
 
 To enable a policy-based (scheduled) backup: 
 
@@ -64,21 +64,21 @@ The following example configuration has a backup policy configured for daily bac
     Weekly: `Weekly Backups to Keep = 6`   
     Monthly: `Monthly Backups to Keep = 4`   
 
-## Enable backup functionality for a volume and assign a backup policy
+## Assign backup vault and backup policy to a volume
 
-Every Azure NetApp Files volume must have the backup functionality enabled before any backups (policy-based or manual) can be taken. 
+Every Azure NetApp Files volume must have a backup vault assigned before any backups (policy-based or manual) can be taken. 
 
-After you enable the backup functionality, you need to assign a backup policy to a volume for policy-based backups to take effects. (For manual backups, a backup policy is optional.)
+After you assign a backup vault to the volume, you need to assign a backup policy to the volume for policy-based backups to take effects. (For manual backups, a backup policy is optional.)
 
 >[!NOTE]
 >The active and most current snapshot is required for transferring the backup. As a result, you may see 1 extra snapshot beyond the number of snapshots to keep per the backup policy configuration. If your number of daily backups to keep is set to 2, you may see 3 snapshots related to the backup in the volumes the policy is applied to.
 
-To enable the backup functionality for a volume:  
+To configure backups for a volume:  
 
-1. Go to **Volumes** and select the volume for which you want to enable backup.
-2. Select **Configure**.
-3. In the Configure Backups page, toggle the **Enabled** setting to **On**.
-4. In the **Backup Policy** drop-down menu, assign the backup policy to use for the volume. Click **OK**.
+1. Navigate to **Volumes** then select the volume for which you want to configure backups.
+2. From the selected volume, select **Backup** then **Configure**.
+3. In the Configure Backups page, select the backup vault from the **Backup vaults** drop-down.
+4. In the **Backup Policy** drop-down menu, assign the backup policy to use for the volume. Select **OK**.
 
     The Vault information is prepopulated.  
 
@@ -93,7 +93,6 @@ To enable the backup functionality for a volume:
 * [Manage backup policies](backup-manage-policies.md)
 * [Search backups](backup-search.md)
 * [Restore a backup to a new volume](backup-restore-new-volume.md)
-* [Disable backup functionality for a volume](backup-disable.md)
 * [Delete backups of a volume](backup-delete.md)
 * [Volume backup metrics](azure-netapp-files-metrics.md#volume-backup-metrics)
 * [Azure NetApp Files backup FAQs](faq-backup.md)

articles/azure-netapp-files/backup-delete.md

@@ -10,25 +10,28 @@ ms.author: anfdocs
 ---
 # Delete backups of a volume 
 
-You can delete individual backups that you no longer need to keep for a volume. Deleting backups will delete the associated objects in your Azure Storage account, resulting in space saving.  
+You can delete individual backups that you no longer need to keep for a volume. Deleting backups deletes the associated objects in your Azure Storage account, resulting in space saving.  
 
-By design, Azure NetApp Files prevents you from deleting the latest backup. If the latest backup consists of multiple snapshots taken at the same time (for example, the same daily and weekly schedule configuration), they are all considered as the latest snapshot, and deleting those is prevented.
+By design, Azure NetApp Files prevents you from deleting the latest backup. If the latest backup consists of multiple snapshots taken at the same time (for example, the same daily and weekly schedule configuration), they're all considered as the latest snapshot; deleting the snapshots with the same time is prevented.
 
-Deleting the latest backup is permitted only when both of the following conditions are met:
+Deleting the latest backup is permitted only when either of the following conditions are met:
 
 *    The volume has been deleted.
 *    The latest backup is the only remaining backup for the deleted volume.
 
 If you need to delete backups to free up space, select an older backup from the **Backups** list to delete.
 
+> [!NOTE]
+> Deleting the last backup on a volume removes the reference point for future incremental backups.
+
 ## Steps
 
 >[!IMPORTANT]
->You will not be able to perform any operations on a backup until you have migrate to backup vaults. For more information about this procedure, see [Manage backup vaults](backup-vault-manage.md).
+>For volumes with existing backups, you can't perform any operations with a backup until you migrate the backups to a backup vault. For more information about this procedure, see [Manage backup vaults](backup-vault-manage.md).
 
-1. Select **Volumes**. <!-- is this -->
+1. Select **Volumes**.
 2. Navigate to **Backups**.
-3. From the backup list, select the backup to delete. Click the three dots (`…`) to the right of the backup, then click **Delete** from the Action menu.
+3. From the backup list, select the backup to delete. Select the three dots (`…`) to the right of the backup then **Delete** from the Action menu.
 
     ![Screenshot that shows the Delete menu for backups.](./media/backup-delete/backup-action-menu-delete.png)
 
@@ -42,6 +45,5 @@ If you need to delete backups to free up space, select an older backup from the
 * [Manage backup policies](backup-manage-policies.md)
 * [Search backups](backup-search.md)
 * [Restore a backup to a new volume](backup-restore-new-volume.md)
-* [Disable backup functionality for a volume](backup-disable.md)
 * [Volume backup metrics](azure-netapp-files-metrics.md#volume-backup-metrics)
 * [Azure NetApp Files backup FAQs](faq-backup.md)