Muokkaa

Jaa

Configure manual backups for Azure NetApp Files

  • Artikkeli

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.

About manual backups

Every Azure NetApp Files volume must have a backup vault assigned before any backups (policy-based or manual) can be taken.

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 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 are cleaned up. You can't delete the snapshot generated for the latest manual backup.

Note

The option to disable backups is no longer available beginning with the 2023.09 API version. If your workflows require the disable function, you can still use an API version earlier than 2023.09 or the Azure CLI.

Register the feature

Azure NetApp Files backup is generally available (GA). You must register for Azure NetApp Files backup before using it for the first time.

  1. Register the feature

    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFBackupPreview

  2. Check the status of the feature registration:

    Note

    The RegistrationState may be in the Registering state for up to 60 minutes before changing to Registered. Wait until the status is Registered before continuing.

    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFBackupPreview

You can also use Azure CLI commands az feature register and az feature show to register the feature and display the registration status.

Requirements

  • 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 for more information.
  • If you need to delete a resource group or subscription that contains backups, you should delete any backups first. Deleting the resource group or subscription doesn't delete the backups. You can remove backups by manually deleting the backups.

Configure 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 configure backups.
  2. Select Configure.
  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. Screenshot of backup vault creation.

Create a manual backup for a volume

  1. Go to Volumes and select the volume for which you want to create a manual backup.

  2. Select Add Backup.

  3. In the New Backup window that appears:

    1. Specify a backup name in the Name field.

      • Manual backup names must be 3 to 256 characters in length.

      • As a best practice, prepend a prefix in the following format before the actual backup name. Doing so helps you identify the manual backup if the volume is deleted (with backups retained).

        NetAppAccountName-CapacityPoolName-VolumeName

        For example, assume that the NetApp account is account1, the capacity pool is pool1, the volume name is vol1. A manual backup can be named as follows:

        account1-pool1-vol1-backup1

        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.

  4. Select Create.

    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's transferred to Azure storage. Once the backup completes, the manual backup entry appears in the list of backups for the volume.

Screenshot that shows the New Backup window.

Next steps