Skip to content

Commit 0d04e7c

Browse files
authored
Merge pull request #2 from rvandenbedem/rvandenbedem-patch-1-1
Added service limits link to stretched clusters FAQ.
2 parents b943a7b + 10f330d commit 0d04e7c

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

articles/azure-netapp-files/azure-netapp-files-solution-architectures.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -121,6 +121,7 @@ This section provides references to SAP on Azure solutions.
121121
* [SAP S/4HANA in Linux on Azure - Azure Architecture Center](/azure/architecture/reference-architectures/sap/sap-s4hana)
122122
* [Run SAP BW/4HANA with Linux VMs - Azure Architecture Center](/azure/architecture/reference-architectures/sap/run-sap-bw4hana-with-linux-virtual-machines)
123123
* [SAP HANA Azure virtual machine storage configurations](../virtual-machines/workloads/sap/hana-vm-operations-storage.md)
124+
* [SAP on Azure NetApp Files Sizing Best Practices](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/sap-on-azure-netapp-files-sizing-best-practices/ba-p/3895300)
124125
* [Optimize HANA deployments with Azure NetApp Files application volume group for SAP HANA](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/optimize-hana-deployments-with-azure-netapp-files-application/ba-p/3683417)
125126
* [Using Azure NetApp Files AVG for SAP HANA to deploy HANA with multiple partitions (MP)](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/using-azure-netapp-files-avg-for-sap-hana-to-deploy-hana-with/ba-p/3742747)
126127
* [NFS v4.1 volumes on Azure NetApp Files for SAP HANA](../virtual-machines/workloads/sap/hana-vm-operations-netapp.md)

articles/azure-vmware/deploy-vsan-stretched-clusters.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Deploy vSAN stretched clusters
33
description: Learn how to deploy vSAN stretched clusters.
44
ms.topic: how-to
55
ms.service: azure-vmware
6-
ms.date: 06/24/2023
6+
ms.date: 08/16/2023
77
ms.custom: references_regions
88
---
99

@@ -123,7 +123,7 @@ No. A stretched cluster is created between two availability zones, while the thi
123123
### What are the limitations I should be aware of?
124124

125125
- Once a private cloud has been created with a stretched cluster, it can't be changed to a standard cluster private cloud. Similarly, a standard cluster private cloud can't be changed to a stretched cluster private cloud after creation.
126-
- Scale out and scale-in of stretched clusters can only happen in pairs. A minimum of 6 nodes and a maximum of 16 nodes are supported in a stretched cluster environment.
126+
- Scale out and scale-in of stretched clusters can only happen in pairs. A minimum of 6 nodes and a maximum of 16 nodes are supported in a stretched cluster environment. For more details, refer to [Azure subscription and service limits, quotas, and constraints](https://learn.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-vmware-solution-limits).
127127
- Customer workload VMs are restarted with a medium vSphere HA priority. Management VMs have the highest restart priority.
128128
- The solution relies on vSphere HA and vSAN for restarts and replication. Recovery time objective (RTO) is determined by the amount of time it takes vSphere HA to restart a VM on the surviving AZ after the failure of a single AZ.
129129
- Currently not supported in a stretched cluster environment:

0 commit comments

Comments
 (0)