Skip to content

Commit 6f666ba

Browse files
committed
Fix validation
1 parent 09dadb3 commit 6f666ba

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/sap/workloads/high-availability-zones.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ When you deploy Azure VMs across Availability Zones and establish failover solut
6666

6767
## The ideal Availability Zones combination
6868

69-
Unless you configure the business process assignment using SAP functionalities like Logon Groups, RFC Server Groups, Batch Server Groups, and similar, business processes are assigned automatically. They can then be executed in different application instances. These instances can be located across your SAP application layer. These instances can be located across your SAP application layer. The side effect of this is that batch jobs might be executed from any SAP application instance. They can run regardless of whether the instance is in the same zone as the active database instance or not. If the difference in network latency between the difference zones is small compared to network latency within a zone, the difference in run times of batch jobs might not be significant. However, the larger the difference of network latency within a zone compared to across‑zone network traffic, the more the run time of batch jobs can be impacted. This impact occurs if the job is executed in a zone where the database instance isn't active.
69+
Unless you configure the business process assignment using SAP functionalities like Logon Groups, RFC Server Groups, Batch Server Groups, and similar, business processes are assigned automatically. They can then be executed in different application instances. These instances can be located across your SAP application layer. The side effect of this is that batch jobs might be executed from any SAP application instance. They can run regardless of whether the instance is in the same zone as the active database instance or not. If the difference in network latency between the difference zones is small compared to network latency within a zone, the difference in run times of batch jobs might not be significant. However, the larger the difference of network latency within a zone compared to across‑zone network traffic, the more the run time of batch jobs can be impacted. This impact occurs if the job is executed in a zone where the database instance isn't active.
7070

7171
It's on you as a customer to decide what acceptable differences in run time are. And with that what the tolerable network latency for cross zones traffic is for your workload. Purely from a technical point of view, the network latencies between Azure Availability Zones within an Azure region work for the architecture of NetWeaver, S/4HANA, or other SAP applications. It's also on you as a customer to mitigate such differences using SAP concepts such as Logon Groups, RFC Server Groups, Batch Server Groups, and similar. This becomes important when you decide on one of the deployment concepts introduced in this article.
7272

0 commit comments

Comments
 (0)