Skip to content

Commit 085593f

Browse files
Merge pull request #216100 from b-ahibbard/anf-backupvault-2022.09
backup vault 2022.09
2 parents 2644051 + c70557e commit 085593f

21 files changed

+132
-49
lines changed

articles/azure-netapp-files/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -323,6 +323,8 @@
323323
href: backup-configure-policy-based.md
324324
- name: Configure manual backups
325325
href: backup-configure-manual.md
326+
- name: Manage a backup vault
327+
href: backup-vault-manage.md
326328
- name: Manage backup policies
327329
href: backup-manage-policies.md
328330
- name: Search backups

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

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,14 +28,17 @@ This article shows you how to configure manual backups. For policy-based backup
2828

2929
Every Azure NetApp Files volume must have the backup functionality enabled before any backups (policy-based or manual) can be taken.
3030

31-
After you enable the backup functionality, you have the option 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.
31+
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.
3232

3333
The following list summarizes manual backup behaviors:
3434

3535
* 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.
3636

3737
* 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.
3838

39+
## Requirements
40+
41+
* Azure NetApp Files now requires you to create a backup vault before enabling backup functionality. If you have not configured a backup, refer to [Manage backup vaults](backup-vault-manage.md) for more information.
3942
* [!INCLUDE [consideration regarding deleting backups after deleting resource or subscription](includes/disable-delete-backup.md)]
4043

4144
## Enable backup functionality
@@ -45,8 +48,7 @@ If you haven’t done so, enable the backup functionality for the volume before
4548
1. Go to **Volumes** and select the specific volume for which you want to enable backup.
4649
2. Select **Configure**.
4750
3. In the Configure Backup page, toggle the **Enabled** setting to **On**.
48-
The Vault field is prepopulated.
49-
4. Click **OK**.
51+
4. Select **OK**.
5052

5153
![Screenshot that shows the Enabled setting of Configure Backups window.](../media/azure-netapp-files/backup-configure-enabled.png)
5254

@@ -71,9 +73,9 @@ If you haven’t done so, enable the backup functionality for the volume before
7173

7274
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.
7375

74-
4. Click **Create**.
76+
4. Select **Create**.
7577

76-
When you create a manual backup, a snapshot is also created on the volume using the same name you specified for the backup. This snapshot represents the current state of the active file system. It is transferred to Azure storage. When the backup is complete, the manual backup entry will appear in the list of backups for the volume.
78+
When you create a manual backup, a snapshot is also created on the volume using the same name you specified for the backup. This snapshot represents the current state of the active file system. It is transferred to Azure storage. Once the backup completes, the manual backup entry appears in the list of backups for the volume.
7779

7880
![Screenshot that shows the New Backup window.](../media/azure-netapp-files/backup-new.png)
7981

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ This article shows you how to configure policy-based backups. For manual backup
2828

2929
Backups are long-running operations. The system schedules backups based on the primary workload (which is given a higher priority) and runs backups in the background. Depending on the size of the volume being backed up, a backup can run in background for hours. There's no option to select the start time for backups. The service performs the backups based on the internal scheduling and optimization logic.
3030

31-
Assigning a policy creates a baseline snapshot that is the current state of the volume and transfers the snapshot to Azure storage. The baseline snapshot is created with a name starting with `baseline`. This baseline snapshot is deleted automatically when the first scheduled backup is complete (based on the policy). If the backup policy is attached to a volume, the backup list will be empty until the baseline snapshot is transferred. When the backup is complete, the baseline backup entry appears in the list of backups for the volume. After the baseline transfer, the list will be updated daily based on the policy. An empty list of backups indicates that the baseline backup is in progress. If a volume already has existing manual backups before you assign a backup policy, the baseline snapshot isn't created. A baseline snapshot is created only when the volume has no prior backups.
31+
Assigning a policy creates a baseline snapshot that is the current state of the volume and transfers the snapshot to Azure storage. This baseline snapshot is deleted automatically when the first scheduled backup is complete (based on the policy). If the backup policy is attached to a volume, the backup list will be empty until the baseline snapshot is transferred. When the backup is complete, the baseline backup entry appears in the list of backups for the volume. After the baseline transfer, the list will be updated daily based on the policy. An empty list of backups indicates that the baseline backup is in progress. If a volume already has existing manual backups before you assign a backup policy, the baseline snapshot isn't created. A baseline snapshot is created only when the volume has no prior backups.
3232

3333
[!INCLUDE [consideration regarding deleting backups after deleting resource or subscription](includes/disable-delete-backup.md)]
3434

@@ -44,7 +44,7 @@ To enable a policy-based (scheduled) backup:
4444
2. Select your Azure NetApp Files account.
4545
3. Select **Backups**.
4646

47-
:::image type="content" source="../media/azure-netapp-files/backup-navigate.png" alt-text="Screenshot that shows how to navigate to Backups option." lightbox="../media/azure-netapp-files/backup-navigate.png":::
47+
<!-- :::image type="content" source="../media/azure-netapp-files/backup-navigate.png" alt-text="Screenshot that shows how to navigate to Backups option." lightbox="../media/azure-netapp-files/backup-navigate.png"::: -->
4848

4949
4. Select **Backup Policies**.
5050
5. Select **Add**.
@@ -85,7 +85,7 @@ To enable the backup functionality for a volume:
8585
3. In the Configure Backups page, toggle the **Enabled** setting to **On**.
8686
4. In the **Backup Policy** drop-down menu, assign the backup policy to use for the volume. Click **OK**.
8787

88-
The Vault information is pre-populated.
88+
The Vault information is prepopulated.
8989

9090
:::image type="content" source="../media/azure-netapp-files/backup-configure-window.png" alt-text="Screenshot showing Configure Backups window." lightbox="../media/azure-netapp-files/backup-configure-window.png":::
9191

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

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
1212
ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.topic: how-to
15-
ms.date: 03/01/2022
15+
ms.date: 10/27/2022
1616
ms.author: anfdocs
1717
---
1818
# Delete backups of a volume
@@ -30,7 +30,10 @@ If you need to delete backups to free up space, select an older backup from the
3030

3131
## Steps
3232

33-
1. Select **Volumes**.
33+
>[!IMPORTANT]
34+
>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).
35+
36+
1. Select **Volumes**. <!-- is this -->
3437
2. Navigate to **Backups**.
3538
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.
3639

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

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
1212
ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.topic: how-to
15-
ms.date: 09/27/2021
15+
ms.date: 10/27/2022
1616
ms.author: anfdocs
1717
---
1818
# Disable backup functionality for a volume
@@ -26,12 +26,15 @@ If a volume is deleted but the backup policy wasn’t disabled before the volume
2626

2727
## Steps
2828

29+
>[!IMPORTANT]
30+
>Existing backups not assigned to a backup vault must be migrated. You cannot perform any operations on a backup until it has been migrated to a backup vault. To learn how to migrate, see [Manage backup vaults](backup-vault-manage.md#migrate-backups-to-a-backup-vault).
31+
2932
1. Select **Volumes**.
3033
2. Select the specific volume whose backup functionality you want to disable.
3134
3. Select **Configure**.
3235
4. In the Configure Backups page, toggle the **Enabled** setting to **Off**. Enter the volume name to confirm, and click **OK**.
3336

34-
![Screenshot that shows the Restore to with Configure Backups window with backup disabled.](../media/azure-netapp-files/backup-configure-backups-disable.png)
37+
<!-- ![Screenshot that shows the Restore to with Configure Backups window with backup disabled.](../media/azure-netapp-files/backup-configure-backups-disable.png) -->
3538

3639
## Next steps
3740

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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,19 @@ Azure NetApp Files backup is supported for the following regions:
5656
* West US 2
5757
* West US 3
5858
59+
## Backup vault
60+
61+
Backup vaults are organizational units to manage backups. You must create a backup vault before you can create a backup.
62+
63+
>[!IMPORTANT]
64+
>If you have existing backups on Azure NetApp Files, you must migrate the backups to a backup vault before you can perform any operation with the backup. To learn how to migrate, see [Manage backup vaults](backup-vault-manage.md#migrate-backups-to-a-backup-vault).
65+
66+
<!-- You can have multiple backup vaults in an Azure NetApp Files subscription. Most deployments, however, will only require one backup vault. -->
67+
5968
## Cost model for Azure NetApp Files backup
6069
6170
Pricing for Azure NetApp Files backup is based on the total amount of storage consumed by the backup. There are no setup charges or minimum usage fees.
71+
6272
Backup restore is priced based on the total amount of backup capacity restored during the billing cycle.
6373
6474
As a pricing example, assume the following situations:

articles/azure-netapp-files/backup-manage-policies.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -21,19 +21,22 @@ After you have set up Azure NetApp Files backups using [a backup policy](backup-
2121

2222
Manual backups are not affected by changes in the backup policy.
2323

24+
>[!IMPORTANT]
25+
>All backups require a backup vault. If you have existing backups, you must migrate backups to a backup vault before you can perform any operation with a backup. For more information about this procedure, see [Manage backup vaults](backup-vault-manage.md).
26+
2427
## Modify a backup policy
2528

26-
You can modify an existing Azure NetApp Files backup policy as needed to ensure that you have proper backup coverage for Azure NetApp Files volumes. For example, if you need to change the number of retained backups that are protected by the service, you can modify the Azure NetApp Files backup policy for the volume to revise the number of restores to keep.
29+
You can modify an existing Azure NetApp Files backup policy as needed to ensure that you have proper backup coverage for Azure NetApp Files volumes. For example, if you need to change the number of retained backups that are protected by the service, you can modify the Azure NetApp Files backup policy for the volume to revise the number of backups to keep.
2730

2831
To modify the backup policy settings:
2932

30-
1. Navigate to **Backups**.
33+
1. Navigate to **Backups**.
3134

32-
2. Select **Backup Policies**, click the three dots (``) to the right of a backup policy, then click **Edit**.
35+
2. Select **Backup Policies** then select the three dots (``) to the right of a backup policy. Select **Edit**.
3336

3437
![Screenshot that shows context sensitive menu of Backup Policies.](../media/azure-netapp-files/backup-policies-edit.png)
3538

36-
3. In the Modify Backup Policy window, update the number of restores you want to keep for daily, weekly, and monthly backups. Enter the backup policy name to confirm the action. Click **Save**.
39+
3. In the Modify Backup Policy window, update the number of backups you want to keep for daily, weekly, and monthly backups. Enter the backup policy name to confirm the action. Click **Save**.
3740

3841
![Screenshot that shows the Modify Backup Policy window.](../media/azure-netapp-files/backup-modify-policy.png)
3942

@@ -48,9 +51,11 @@ A backup policy can be suspended so that it does not perform any new backup oper
4851

4952
1. Navigate to **Backups**.
5053

51-
2. Select **Backup Policies**, click the three dots (``) to the right of a backup policy, and click **Edit**.
54+
1. Select **Backup Policies**.
55+
56+
1. Select the three dots (``) to the right of the backup policy you want to modify, then select **Edit**.
5257

53-
3. Toggle **Policy State** to **Disabled**, enter the policy name to confirm, and click **Save**.
58+
1. Toggle **Policy State** to **Disabled**, enter the policy name to confirm, and click **Save**.
5459

5560
![Screenshot that shows the Modify Backup Policy window with Policy State disabled.](../media/azure-netapp-files/backup-modify-policy-disabled.png)
5661

@@ -76,6 +81,3 @@ A backup policy can be suspended so that it does not perform any new backup oper
7681
* [Delete backups of a volume](backup-delete.md)
7782
* [Volume backup metrics](azure-netapp-files-metrics.md#volume-backup-metrics)
7883
* [Azure NetApp Files backup FAQs](faq-backup.md)
79-
80-
81-

articles/azure-netapp-files/backup-requirements-considerations.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,9 @@ This article describes the requirements and considerations you need to be aware
2323

2424
You need to be aware of several requirements and considerations before using Azure NetApp Files backup:
2525

26+
>[!IMPORTANT]
27+
>All backups require a backup vault. If you have existing backups, you must migrate backups to a backup vault before you can perform any operation with a backup. For more information about this procedure, see [Manage backup vaults](backup-vault-manage.md).
28+
2629
* Azure NetApp Files backup is available in the regions associated with your Azure NetApp Files subscription.
2730
Azure NetApp Files backup in a region can only protect an Azure NetApp Files volume located in that same region. For example, backups created by the service in West US 2 for a volume located in West US 2 are sent to Azure storage also located in West US 2. Azure NetApp Files doesn't support backups or backup replication to a different region.
2831

articles/azure-netapp-files/backup-restore-new-volume.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -45,15 +45,17 @@ See [Requirements and considerations for Azure NetApp Files backup](backup-requi
4545

4646
## Steps
4747

48-
1. Select **Volumes**. Navigate to **Backups**.
48+
>[!IMPORTANT]
49+
>All backups must be migrated to backup vaults. You will not be able to perform any operation on or with a backup until you have migrated the backup to a vault. For more information about this procedure, see [Manage backup vaults](backup-vault-manage.md).
4950
51+
1. Select **Backup Vault**. Navigate to **Backups**.
52+
<!--
5053
> [!NOTE]
51-
> If a volume is deleted but the backup policy wasn’t disabled before the volume deletion, all the backups related to the volume are retained in the Azure storage, and you can find them under the associated NetApp account. See [Search backups at NetApp account level](backup-search.md#search-backups-at-netapp-account-level).
52-
54+
> If a volume is deleted but the backup policy wasn’t disabled before the volume deletion, all the backups related to the volume are retained in the Azure storage, and you can find them under the associated NetApp account. -->
5355

5456
2. From the backup list, select the backup to restore. Select the three dots (``) to the right of the backup, then select **Restore to new volume** from the Action menu.
5557

56-
![Screenshot that shows the option to restore backup to a new volume.](../media/azure-netapp-files/backup-restore-new-volume.png)
58+
<!-- ![Screenshot that shows the option to restore backup to a new volume.](../media/azure-netapp-files/backup-restore-new-volume.png) -->
5759

5860
3. In the Create a Volume page that appears, provide information for the fields in the page as applicable, and select **Review + Create** to begin restoring the backup to a new volume.
5961

0 commit comments

Comments
 (0)