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
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
5
5
author: b-hchen
6
6
ms.service: azure-netapp-files
7
7
ms.topic: conceptual
8
-
ms.date: 08/09/2024
8
+
ms.date: 12/31/2024
9
9
ms.author: anfdocs
10
10
---
11
11
# Resource limits for Azure NetApp Files
@@ -31,7 +31,7 @@ The following table describes resource limits for Azure NetApp Files:
31
31
| Maximum size of a single regular volume | 100 TiB | No |
32
32
| Minimum size of a single [large volume](large-volumes-requirements-considerations.md)| 50 TiB | No |
33
33
| Large volume size increase | 30% of lowest provisioned size | Yes |
34
-
| Maximum size of a single [large volume](large-volumes-requirements-considerations.md)| 1,024 TiB |No|
34
+
| Maximum size of a single [large volume](large-volumes-requirements-considerations.md)| 1,024 TiB |Yes**|
35
35
| Maximum size of a single large volume on dedicated capacity (preview) | 2,048 TiB | No |
36
36
| Maximum size of a single file | 16 TiB | No |
37
37
| Maximum size of directory metadata in a single directory | 320 MB | No |
@@ -52,6 +52,10 @@ The following table describes resource limits for Azure NetApp Files:
52
52
53
53
\*[!INCLUDE [Limitations for capacity pool minimum of 1 TiB](includes/2-tib-capacity-pool.md)]
54
54
55
+
56
+
57
+
\** 2-PiB [large volume](large-volumes-requirements-considerations.md) large volumes are available on request depending on regional dedicated capacity availability. To request 2-PiB large volumes, contact your account team.
58
+
55
59
For more information, see [Capacity management FAQs](faq-capacity-management.md).
56
60
57
61
For limits and constraints related to Azure NetApp Files network features, see [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md#considerations).
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/large-volumes-requirements-considerations.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
@@ -6,7 +6,7 @@ author: b-ahibbard
6
6
ms.service: azure-netapp-files
7
7
ms.custom: references_regions
8
8
ms.topic: conceptual
9
-
ms.date: 10/07/2024
9
+
ms.date: 12/31/2024
10
10
ms.author: anfdocs
11
11
---
12
12
# Requirements and considerations for large volumes
@@ -18,7 +18,7 @@ This article describes the requirements and considerations you need to be aware
18
18
The following requirements and considerations apply to large volumes. For performance considerations of *regular volumes*, see [Performance considerations for Azure NetApp Files](azure-netapp-files-performance-considerations.md).
19
19
20
20
* A regular volume can’t be converted to a large volume.
21
-
* You must create a large volume at a size of 50 TiB or larger. A single volume can't exceed 1 PiB.
21
+
* You must create a large volume at a size of 50 TiB or larger. The maximum size of a large volume is 1,024 TiB, though 2-PiB large volumes are available on request depending on regional dedicated capacity availability. To request 2-PiB large volumes, contact your account team.
22
22
* You can't resize a large volume to less than 50 TiB.
23
23
A large volume cannot be resized to more than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits).
24
24
* Large volumes are currently not supported with Azure NetApp Files backup.
Copy file name to clipboardExpand all lines: articles/load-balancer/load-balancer-troubleshoot-backend-traffic.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Using source persistence distribution mode can cause an uneven distribution of t
29
29
30
30
Clients that run behind proxies might be seen as one unique client application from the load balancer's point of view.
31
31
32
-
## VMs behind a load balancer aren't responding to traffic on the configured data port
32
+
## Virtual machines behind a load balancer aren't responding to traffic on the configured data port
33
33
34
34
If a backend pool VM is listed as healthy and responds to the health probes, but is still not participating in the load balancing, or isn't responding to the data traffic, it may be due to any of the following reasons:
35
35
@@ -109,6 +109,11 @@ The symptom for this scenario is intermittent connection timeouts when the flow
109
109
110
110
You can combine an internal load balancer with any third-party proxy or use internal [Application Gateway](../application-gateway/overview.md) for proxy scenarios with HTTP/HTTPS. While you could use a public load balancer to mitigate this issue, the resulting scenario is prone to [SNAT exhaustion](load-balancer-outbound-connections.md). Avoid this second approach unless carefully managed.
111
111
112
+
## Virtual machines removed from a load balancer are receiving traffic
113
+
114
+
It is by design that existing TCP connections will continue to a virtual machine even after a backend is removed from a load balancer. Once a connection is routed to a backend instance by the load balancer, traffic is established directly between the client and the backend instance. Connections will continue untl the virtual machine is stopped or deallocated.
115
+
116
+
112
117
## Next steps
113
118
114
119
If the preceding steps don't resolve the issue, open a [support ticket](https://azure.microsoft.com/support/options/).
Copy file name to clipboardExpand all lines: articles/network-watcher/traffic-analytics.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: halkazwini
6
6
ms.author: halkazwini
7
7
ms.service: azure-network-watcher
8
8
ms.topic: concept-article
9
-
ms.date: 12/29/2024
9
+
ms.date: 12/31/2024
10
10
ms.custom: references_regions
11
11
12
12
#CustomerIntent: As an Azure administrator, I want to use Traffic analytics to analyze Network Watcher flow logs so that I can view network activity, secure my networks, and optimize performance.
@@ -93,13 +93,11 @@ To use traffic analytics, you need the following components:
> <sup>2</sup> Only required when using traffic analytics to analyze virtual network flow logs.
101
-
>
102
-
> If none of the preceding built-in roles are assigned to your account, assign a [custom role](../role-based-access-control/custom-roles.md?toc=/azure/network-watcher/toc.json) that supports the actions listed in [Traffic analytics permissions](required-rbac-permissions.md#traffic-analytics).
100
+
> If none of the preceding built-in roles are assigned to your account, assign a [custom role](../role-based-access-control/custom-roles.md?toc=/azure/network-watcher/toc.json) that supports the actions listed in [Flow logs](required-rbac-permissions.md#flow-logs) and [Traffic analytics](required-rbac-permissions.md#traffic-analytics) permissions.
103
101
104
102
## How traffic analytics works
105
103
@@ -115,7 +113,7 @@ Reduced logs are enhanced with geography, security, and topology information and
115
113
116
114
The following tables list the supported regions where you can enable traffic analytics for your flow logs and the Log Analytics workspaces that you can use.
117
115
118
-
####[North America / South America](#tab/Americas)
Copy file name to clipboardExpand all lines: articles/oracle/oracle-db/oracle-database-regions.md
+25-30Lines changed: 25 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,50 +12,45 @@ ms.author: jacobjaygbay
12
12
13
13
# Region availability for Oracle Database@Azure
14
14
15
-
Learn what Azure regions and corresponding Oracle Cloud Infrastructure (OCI) regions support Oracle Database@Azure in standard business regions across the globe.
15
+
Learn what Azure regions and corresponding Oracle Cloud Infrastructure (OCI) regions support Oracle Database@Azure in standard business regions across the globe.
16
+
17
+
The list below mentions the Azure and corresponding OCI regions with the regional availability for Oracle Database@Azure:
18
+
- Dual – Minimum two Azure zones are available in this region
19
+
- Single – One Azure zone available with a corresponding paired DR region
20
+
- DR - Disaster recovery only region
16
21
17
22
## Asia Pacific (APAC)
18
23
19
-
The following table lists Azure regions and corresponding OCI regions that support Oracle Database@Azure in the APAC business region:
24
+
| Azure region | OCI region | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure | Regional Availability |
| Canada Central | Canada Southeast (Toronto) | ✓ | ✓ | Single |
53
+
| West US | US West (San Jose) | ✓ | ✓ | Single |
59
54
60
55
> [!NOTE]
61
56
> To provision Oracle Database@Azure resources in a supported region, your tenancy must be subscribed to the target region. Learn how to [manage regions](https://docs.oracle.com/iaas/Content/Identity/regions/managingregions.htm#Managing_Regions) and [subscribe to an infrastructure region](https://docs.oracle.com/iaas/Content/Identity/regions/To_subscribe_to_an_infrastructure_region.htm#subscribe).
0 commit comments