Disaster recovery overview and infrastructure guidelines for SAP workload: Architecture Diagram

[yertaylan67]

[Enter feedback here] Please find below my feedback for the architecture diagram on this page:

• Remove NSG icons from the GatewaySubnets, since NSG on GatewaySubnet is not supported.
• Use the term "Azure Fencing Agent" instead of "Linux fence agent" in the Azure Active Directory tenant
• Remove the subscription (key) icon from the Central Services and Database Servers in the primary region.
• You may consider an Azure Standard Load Balancer in front of SAP Web Dispatchers for a simpler setup. Azure Application Gateway with a public IP address makes more sense for direct inbound Internet connections to SAP. With that, customers see both options.
• The diagram only shows one single global VNet peering across Hub VNets. In this case, SAP HSR and rsync/robocopy traffic would flow over the firewalls in the Hubs. For a more optimal path, I recommend globally peering the SAP Spoke VNets, as well.
• In Storage chapter, you mention Azure Site Recovery's cache storage account. For completeness, I recommend depicting this resource in the diagram, as well, similar to Recovery Services Vault in the DR region.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 7a7c63ec-29d2-c2cf-62a0-3fd1777b5c56
• Version Independent ID: 60dc70b7-571c-e4cd-8cc3-53348152bb45
• Content: Disaster Recovery overview and infrastructure guidelines for SAP workload - Azure Virtual Machines
• Content Source: articles/virtual-machines/workloads/sap/disaster-recovery-overview-guide.md
• Service: virtual-machines-sap
• GitHub Login: @dennispadia
• Microsoft Alias: depadia

[RamanathanChinnappan-MSFT]

@yertaylan67

I've delegated this to content author @dennispadia to review and share his valuable insights.

[yertaylan67]

@dennispadia please review and share your insights for the article. Thanks a lot.

[cynthn]

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing. We are closing this issue for now, but feel free to comment here as necessary. #please-close