You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-quickstart-set-up-account-create-volumes.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -395,7 +395,7 @@ When you're done and if you want to, you can delete the resource group. The acti
395
395
>Deleting a resource group also deletes all resources within it. The action can't be undone.
396
396
397
397
>[!IMPORTANT]
398
-
>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 [manually delete the backups](backup-delete.md). If you delete the resource group without deleting all the backups, you can't see those backups anymore but can continue to incur billing for them. In case you're wrongly billed for some backups, open a support case ticket to get this issue resolved.
398
+
>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.
399
399
400
400
1. In the Azure portal's search box, enter **Azure NetApp Files** and then select **Azure NetApp Files** from the list that appears.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/backup-configure-manual.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,10 +30,10 @@ The following list summarizes manual backup behaviors:
30
30
31
31
## Requirements
32
32
33
-
* 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.
33
+
* 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.
34
34
*[!INCLUDE [consideration regarding deleting backups after deleting resource or subscription](includes/disable-delete-backup.md)]
35
35
36
-
## Enable backup functionality
36
+
## Configure backups
37
37
38
38
If you haven’t done so, assign a backup vault to the volume before creating manual backups:
39
39
@@ -43,6 +43,7 @@ If you haven’t done so, assign a backup vault to the volume before creating ma
43
43
4. Select **OK**.
44
44
45
45

46
+
:::image type="content" source="./media/shared/backup-configure-enabled.png" alt-text="Screenshot of backup vault creation.":::
46
47
47
48
## Create a manual backup for a volume
48
49
@@ -61,7 +62,7 @@ If you haven’t done so, assign a backup vault to the volume before creating ma
61
62
62
63
`account1-pool1-vol1-backup1`
63
64
64
-
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.
65
+
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.
65
66
66
67
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.
67
68
@@ -81,7 +82,6 @@ If you haven’t done so, assign a backup vault to the volume before creating ma
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/backup-configure-policy-based.md
+10-11Lines changed: 10 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.author: anfdocs
12
12
13
13
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.
14
14
15
-
This article shows you how to configure policy-based backups. For manual backup configuration, see [Configure manual backups](backup-configure-manual.md).
15
+
This article explains how to configure policy-based backups. For manual backup configuration, see [Configure manual backups](backup-configure-manual.md).
16
16
17
17
## About policy-based backups
18
18
@@ -28,7 +28,7 @@ Assigning a policy creates a baseline snapshot that is the current state of the
28
28
29
29
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).
30
30
31
-
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.
31
+
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.
32
32
33
33
To enable a policy-based (scheduled) backup:
34
34
@@ -64,21 +64,21 @@ The following example configuration has a backup policy configured for daily bac
64
64
Weekly: `Weekly Backups to Keep = 6`
65
65
Monthly: `Monthly Backups to Keep = 4`
66
66
67
-
## Enable backup functionality for a volume and assign a backup policy
67
+
## Assign backup vault and backup policy to a volume
68
68
69
-
Every Azure NetApp Files volume must have the backup functionality enabled before any backups (policy-based or manual) can be taken.
69
+
Every Azure NetApp Files volume must have a backup vault assigned before any backups (policy-based or manual) can be taken.
70
70
71
-
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.)
71
+
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.)
72
72
73
73
>[!NOTE]
74
74
>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.
75
75
76
-
To enable the backup functionality for a volume:
76
+
To configure backups for a volume:
77
77
78
-
1.Go to **Volumes**and select the volume for which you want to enable backup.
79
-
2.Select**Configure**.
80
-
3. In the Configure Backups page, toggle the **Enabled** setting to **On**.
81
-
4. In the **Backup Policy** drop-down menu, assign the backup policy to use for the volume. Click**OK**.
78
+
1.Navigate to **Volumes**then select the volume for which you want to configure backups.
79
+
2.From the selected volume, select **Backup** then**Configure**.
80
+
3. In the Configure Backups page, select the backup vault from the **Backup vaults** drop-down.
81
+
4. In the **Backup Policy** drop-down menu, assign the backup policy to use for the volume. Select**OK**.
82
82
83
83
The Vault information is prepopulated.
84
84
@@ -93,7 +93,6 @@ To enable the backup functionality for a volume:
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/backup-delete.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,21 +14,24 @@ You can delete individual backups that you no longer need to keep for a volume.
14
14
15
15
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.
16
16
17
-
Deleting the latest backup is permitted only when both of the following conditions are met:
17
+
Deleting the latest backup is permitted only when either of the following conditions are met:
18
18
19
19
* The volume has been deleted.
20
20
* The latest backup is the only remaining backup for the deleted volume.
21
21
22
22
If you need to delete backups to free up space, select an older backup from the **Backups** list to delete.
23
23
24
+
> [!NOTE]
25
+
> Deleting the last backup on a volume removes the reference point for future incremental backups.
26
+
24
27
## Steps
25
28
26
29
>[!IMPORTANT]
27
-
>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).
30
+
>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).
28
31
29
-
1. Select **Volumes**.<!-- is this -->
32
+
1. Select **Volumes**.
30
33
2. Navigate to **Backups**.
31
-
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.
34
+
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.
32
35
33
36

34
37
@@ -42,6 +45,5 @@ If you need to delete backups to free up space, select an older backup from the
> After backups are enabled and have taken effect for the scheduled frequency, you cannot change the backup retention count to `0`. A minimum number of `1` retention is required for the backup policy. See [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md) for details.
37
+
> After backups are configured and have taken effect for the scheduled frequency, you can't change the backup retention count to `0`. The backup retention count requires a minimum number of `1` for the backup policy. See [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md) for details.
38
38
39
39
## Suspend a backup policy
40
40
@@ -50,17 +50,15 @@ A backup policy can be suspended so that it does not perform any new backup oper
50
50
51
51
1. Toggle **Policy State** to **Disabled**, enter the policy name to confirm, and click **Save**.
52
52
53
-
<!-- this does NOT work anymore -->
54
-
55
53
### Suspend a backup policy for a specific volume
56
54
57
55
1. Go to **Volumes**.
58
56
2. Select the specific volume whose backups you want to suspend.
59
-
3. Select **Configure**.
60
-
4. In the Configure Backups page, toggle **Policy State** to **Suspend**, enter the volume name to confirm, and click **OK**.
61
-
62
-

57
+
3. From the selected volume, select **Backup** then **Configure**.
58
+
4. In the Configure Backups page, toggle **Policy State** to **Suspend**, enter the volume name to confirm, then select **OK**.
63
59
60
+
:::image type="content" source="./media/backup-manage-policies/backup-modify-policy-suspend.png" alt-text="Screenshot that shows the Configure Backups window with the Suspend Policy State.":::
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/backup-requirements-considerations.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,9 +40,9 @@ Azure NetApp Files backup in a region can only protect an Azure NetApp Files vol
40
40
41
41
* See [Restore a backup to a new volume](backup-restore-new-volume.md) for additional considerations related to restoring backups.
42
42
43
-
*[Disabling backups](backup-disable.md) for a volume will delete all the backups stored in the Azure storage for that volume. If you delete a volume, the backups will remain. If you no longer need the backups, you should [manually delete the backups](backup-delete.md).
43
+
* If you delete a volume, the backups remain. If you no longer need the backups, you should [manually delete the backups](backup-delete.md).
44
44
45
-
* If you need to delete a parent resource group or subscription that contains backups, you should delete any backups first. Deleting the resource group or subscription won't delete the backups. You can remove backups by [disabling backups](backup-disable.md) or [manually deleting the backups](backup-disable.md). If you delete the resource group without disabling backups, backups will continue to impact your billing.
45
+
* If you need to delete a parent resource group or subscription that contains backups, you should delete any backups first. Deleting the resource group or subscription won't delete the backups. You can remove backups [manually deleting the backups](backup-disable.md).
46
46
47
47
* If you use the standard storage with cool access, see [Manage Azure NetApp Files standard storage with cool access](manage-cool-access.md#considerations) for more considerations.
48
48
@@ -55,7 +55,6 @@ Azure NetApp Files backup in a region can only protect an Azure NetApp Files vol
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/backup-restore-new-volume.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Restoring a backup creates a new volume with the same protocol type. This articl
18
18
19
19
* You can restore backups to a different capacity pool within the same NetApp account.
20
20
21
-
* You can restore a backup only to a new volume. You cannot overwrite the existing volume with the backup.
21
+
* You can restore a backup only to a new volume. You cannot overwrite the existing volume with the backup.
22
22
23
23
* The new volume created by the restore operation cannot be mounted until the restore completes.
24
24
@@ -41,7 +41,7 @@ See [Requirements and considerations for Azure NetApp Files backup](backup-requi
41
41
## Steps
42
42
43
43
>[!IMPORTANT]
44
-
>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).
44
+
>All backups must be migrated to backup vaults. You are unable to perform any operation on or with a backup until you have migrated the backup to a backup vault. For more information about this procedure, see [Manage backup vaults](backup-vault-manage.md).
45
45
46
46
1. Select **Backup Vault**. Navigate to **Backups**.
47
47
<!--
@@ -75,7 +75,6 @@ See [Requirements and considerations for Azure NetApp Files backup](backup-requi
0 commit comments