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-resource-limits.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,11 +130,11 @@ You can create an Azure support request to increase the adjustable limits from t
130
130
2. For **Subscription**, select your subscription.
131
131
3. For **Quota Type**, select **Storage: Azure NetApp Files limits**.
132
132
133
-
133
+
134
134
135
135
3. Under the **Additional details** tab, select **Enter details** in the Request Details field.
136
136
137
-
137
+
138
138
139
139
4. To request limit increase, provide the following information in the Quota Details window that appears:
140
140
1. In **Quota Type**, select the type of resource you want to increase.
@@ -148,7 +148,7 @@ You can create an Azure support request to increase the adjustable limits from t
148
148
149
149
3. Enter a value to request an increase for the quota type you specified.
150
150
151
-
151
+
152
152
153
153
5. Select **Save and continue**. Select **Review + create** to create the request.
* In Example 1, a volume from an auto QoS capacity pool with the Premium storage tier that is assigned 2 TiB of quota will be assigned a throughput limit of 128 MiB/s (2 TiB * 64 MiB/s). This scenario applies regardless of the capacity pool size or the actual volume consumption.
45
45
@@ -58,7 +58,7 @@ For example, for an SAP HANA system, this capacity pool can be used to create th
58
58
59
59
The following diagram illustrates the scenarios for the SAP HANA volumes:
60
60
61
-
61
+
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Creating a capacity pool enables you to create volumes within it.
37
37
38
38
1. Go to the management blade for your NetApp account, and then, from the navigation pane, click **Capacity pools**.
39
39
40
-
40
+
41
41
42
42
2. Select **+ Add pools** to create a new capacity pool.
43
43
The New Capacity Pool window appears.
@@ -87,7 +87,7 @@ Creating a capacity pool enables you to create volumes within it.
87
87
```
88
88
You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status.
89
89
90
-
:::image type="content" source="../media/azure-netapp-files/azure-netapp-files-new-capacity-pool.png" alt-text="Screenshot showing the New Capacity Pool window.":::
90
+
:::image type="content" source="./media/shared/azure-netapp-files-new-capacity-pool.png" alt-text="Screenshot showing the New Capacity Pool window.":::
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-smb-performance.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,21 +35,21 @@ With SMB Multichannel disabled on the client, pure 4 KiB read and write tests we
35
35
36
36
The command `netstat -na | findstr 445` proved that additional connections were established with increments from `1` to `4` to `8` and to `16`. Four CPU cores were fully utilized for SMB during each test, as confirmed by the perfmon `Per Processor Network Activity Cycles` statistic (not included in this article.)
37
37
38
-
38
+
39
39
40
40
The Azure virtual machine does not affect SMB (nor NFS) storage I/O limits. As shown in the following chart, the D32ds instance type has a limited rate of 308,000 for cached storage IOPS and 51,200 for uncached storage IOPS. However, the graph above shows significantly more I/O over SMB.
41
41
42
-
42
+
43
43
44
44
#### Sequential IO
45
45
46
46
Tests similar to the random I/O tests described previously were performed with 64-KiB sequential I/O. Although the increases in client connection count per RSS network interface beyond 4’ had no noticeable effect on random I/O, the same does not apply to sequential I/O. As the following graph shows, each increase is associated with a corresponding increase in read throughput. Write throughput remained flat due to network bandwidth restrictions placed by Azure for each instance type/size.
47
47
48
-
48
+
49
49
50
50
Azure places network rate limits on each virtual machine type/size. The rate limit is imposed on outbound traffic only. The number of NICs present on a virtual machine has no bearing on the total amount of bandwidth available to the machine. For example, the D32ds instance type has an imposed network limit of 16,000 Mbps (2,000 MiB/s). As the sequential graph above shows, the limit affects the outbound traffic (writes) but not multichannel reads.
51
51
52
-
52
+
53
53
54
54
## SMB Signing
55
55
@@ -61,7 +61,7 @@ SMB Signing is supported for all SMB protocol versions that are supported by Azu
61
61
62
62
SMB Signing has a deleterious effect upon SMB performance. Among other potential causes of the performance degradation, the digital signing of each packet consumes additional client-side CPU as the perfmon output below shows. In this case, Core 0 appears responsible for SMB, including SMB Signing. A comparison with the non-multichannel sequential read throughput numbers in the previous section shows that SMB Signing reduces overall throughput from 875MiB/s to approximately 250MiB/s.
63
63
64
-
64
+
65
65
66
66
67
67
## Performance for a single instance with a 1-TB dataset
@@ -70,35 +70,35 @@ To provide more detailed insight into workloads with read/write mixes, the follo
70
70
71
71
The following chart shows the results for 4k random I/O, with a single VM instance and a read/write mix at 10% intervals:
72
72
73
-
73
+
74
74
75
75
The following chart shows the results for sequential I/O:
76
76
77
-
77
+
78
78
79
79
## Performance when scaling out using 5 VMs with a 1-TB dataset
80
80
81
81
These tests with 5 VMs use the same testing environment as the single VM, with each process writing to its own file.
82
82
83
83
The following chart shows the results for random I/O:
84
84
85
-
85
+
86
86
87
87
The following chart shows the results for sequential I/O:
88
88
89
-
89
+
90
90
91
91
## How to monitor Hyper-V ethernet adapters
92
92
93
93
One strategy used in testing with FIO is to set `numjobs=16`. Doing so forks each job into 16 specific instances to maximize the Microsoft Hyper-V Network Adapter.
94
94
95
95
You can check for activity on each of the adapters in Windows Performance Monitor by selecting **Performance Monitor > Add Counters > Network Interface > Microsoft Hyper-V Network Adapter**.
96
96
97
-
97
+
98
98
99
99
After you have data traffic running in your volumes, you can monitor your adapters in Windows Performance Monitor. If you do not use all of these 16 virtual adapters, you might not be maximizing your network bandwidth capacity.
100
100
101
-
101
+
102
102
103
103
## SMB encryption
104
104
@@ -142,7 +142,7 @@ With SMB Multichannel enabled, an SMB3 client establishes multiple TCP connectio
142
142
To see if your Azure virtual machine NICs support RSS, run the command
143
143
`Get-SmbClientNetworkInterface` as follows and check the field `RSS Capable`:
144
144
145
-
145
+
146
146
147
147
148
148
## Multiple NICs on SMB clients
@@ -151,7 +151,7 @@ You should not configure multiple NICs on your client for SMB. The SMB client wi
151
151
152
152
As the output of `Get-SmbClientNetworkInterace` below shows, the virtual machine has 2 network interfaces--15 and 12. As shown under the following command `Get-SmbMultichannelConnection`, even though there are two RSS-capable NICS, only interface 12 is used in connection with the SMB share; interface 15 is not in use.
153
153
154
-
154
+
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-solution-architectures.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
@@ -22,7 +22,7 @@ Azure NetApp Files’ integration with Azure native services like Azure Kubernet
22
22
The following diagram depicts the categorization of reference architectures, blueprints and solutions on this page as laid out in the above introduction:
In summary, Azure NetApp Files is a versatile and scalable storage service that provides an ideal platform for migrating various workload categories, running specialized workloads, and integrating with Azure native services. Azure NetApp Files’ high-performance, security, and scalability features make it a reliable choice for businesses looking to run their applications and workloads in Azure.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/backup-configure-manual.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ If you haven’t done so, enable the backup functionality for the volume before
44
44
3. In the Configure Backup page, toggle the **Enabled** setting to **On**.
45
45
4. Select **OK**.
46
46
47
-
47
+
48
48
49
49
## Create a manual backup for a volume
50
50
@@ -71,7 +71,7 @@ If you haven’t done so, enable the backup functionality for the volume before
71
71
72
72
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.
73
73
74
-
74
+
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/backup-configure-policy-based.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,15 +38,15 @@ To enable a policy-based (scheduled) backup:
38
38
2. Select your Azure NetApp Files account.
39
39
3. Select **Backups**.
40
40
41
-
<!-- :::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"::: -->
41
+
<!-- :::image type="content" source="./media/backup-configure-policy-based/backup-navigate.png" alt-text="Screenshot that shows how to navigate to Backups option." lightbox="./media/backup-configure-policy-based/backup-navigate.png"::: -->
42
42
43
43
4. Select **Backup Policies**.
44
44
5. Select **Add**.
45
45
6. In the **Backup Policy** page, specify the backup policy name. Enter the number of backups that you want to keep for daily, weekly, and monthly backups. Select **Save**.
46
46
47
47
The minimum value for **Daily Backups to Keep** is 2.
48
48
49
-
:::image type="content" source="../media/azure-netapp-files/backup-policy-window-daily.png" alt-text="Screenshot that shows the Backup Policy window." lightbox="../media/azure-netapp-files/backup-policy-window-daily.png":::
49
+
:::image type="content" source="./media/backup-configure-policy-based/backup-policy-window-daily.png" alt-text="Screenshot that shows the Backup Policy window." lightbox="./media/backup-configure-policy-based/backup-policy-window-daily.png":::
50
50
51
51
### Example of a valid configuration
52
52
@@ -84,7 +84,7 @@ To enable the backup functionality for a volume:
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/backup-delete.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
@@ -31,7 +31,7 @@ If you need to delete backups to free up space, select an older backup from the
31
31
2. Navigate to **Backups**.
32
32
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.
33
33
34
-
34
+
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/backup-disable.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
@@ -28,7 +28,7 @@ If a volume is deleted but the backup policy wasn’t disabled before the volume
28
28
3. Select **Configure**.
29
29
4. In the Configure Backups page, toggle the **Enabled** setting to **Off**. Enter the volume name to confirm, and click **OK**.
30
30
31
-
31
+
0 commit comments