Skip to content

Commit 38f394b

Browse files
Merge pull request #291852 from b-ahibbard/file-path-ga-new
File path ga new
2 parents 6e99a6e + 406ef5b commit 38f394b

File tree

2 files changed

+7
-3
lines changed

2 files changed

+7
-3
lines changed

articles/azure-netapp-files/manage-availability-zone-volume-placement.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: b-ahibbard
66
ms.service: azure-netapp-files
77
ms.custom: devx-track-terraform
88
ms.topic: how-to
9-
ms.date: 12/11/2024
9+
ms.date: 12/17/2024
1010
ms.author: anfdocs
1111
---
1212
# Manage availability zone volume placement for Azure NetApp Files
@@ -30,7 +30,7 @@ You can deploy new volumes in the logical availability zone of your choice. You
3030

3131
* VMs and Azure NetApp Files volumes are to be deployed separately, within the same logical availability zone to create zone alignment between VMs and Azure NetApp Files. The availability zone volume placement feature doesn't create zonal VMs upon volume creation, or vice versa.
3232

33-
* <a name="file-path-uniqueness"></a> For volumes in different availability zones, Azure NetApp Files allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol). This feature is currently in preview.
33+
* <a name="file-path-uniqueness"></a> For volumes in different availability zones, Azure NetApp Files allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol).
3434

3535
>[!IMPORTANT]
3636
>It's not recommended that you use availability zones for Terraform-managed volumes. If you do, you must [add the zone property to your volume](#populate-availability-zone-for-terraform-managed-volumes).

articles/azure-netapp-files/whats-new.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: b-hchen
66
ms.service: azure-netapp-files
77
ms.custom: linux-related-content
88
ms.topic: overview
9-
ms.date: 12/11/2024
9+
ms.date: 12/17/2024
1010
ms.author: anfdocs
1111
---
1212

@@ -16,6 +16,10 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
1616

1717
## December 2024
1818

19+
* [Volume enhancement: creating volumes with the same file path, share name, or volume path in different availability zones](manage-availability-zone-volume-placement.md#file-path-uniqueness) is now generally available (GA)
20+
21+
Azure NetApp Files allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol) as long as they are in different availability zones. For more information, see [Create an NFS volume for Azure NetApp Files](azure-netapp-files-create-volumes.md), [Create an SMB volume for Azure NetApp Files](azure-netapp-files-create-volumes-smb.md), or [Create a dual-protocol volume for Azure NetApp Files](create-volumes-dual-protocol.md). This feature is now generally available.
22+
1923
* [Cloud Backup for Virtual Machines on Azure NetApp Files datastores for Azure VMware Solution:](../azure-vmware/install-cloud-backup-virtual-machines.md) enhanced backup capabilities (Preview)
2024

2125
Cloud Backup for Virtual Machines now integrates with [Azure NetApp Files backup](backup-introduction.md), significantly enhancing data protection by offering a fully managed backup solution for long-term recovery, archiving, and compliance. This integration allows you to mount a datastore from a snapshot or Azure NetApp Files backup to restore files. You can [mount the backup](../azure-vmware/configure-cloud-backup-virtual-machine.md) to either the Azure VMware Solution host where it was created or to an alternate host.

0 commit comments

Comments
 (0)