From c88affc5b80858d899f5d1d3694e391b62c42d28 Mon Sep 17 00:00:00 2001 From: Naoki Igarashi <57655797+NaokiIgarashi@users.noreply.github.com> Date: Thu, 11 Jan 2024 16:42:59 +0900 Subject: [PATCH] Update sap_checklist.en.json --- checklists/sap_checklist.en.json | 27 ++++++++++++++++++--------- 1 file changed, 18 insertions(+), 9 deletions(-) diff --git a/checklists/sap_checklist.en.json b/checklists/sap_checklist.en.json index e5c9e9d2b..8ce5f5e26 100644 --- a/checklists/sap_checklist.en.json +++ b/checklists/sap_checklist.en.json @@ -107,20 +107,29 @@ "training": "https://learn.microsoft.com/training/modules/configure-virtual-machine-availability/?source=recommendations", "link": "https://learn.microsoft.com/azure/virtual-machines/availability-set-overview" }, - - - - - - { "category": "Business Continuity and Disaster Recovery", - "subcategory": " ", + "subcategory": "High availability", + "text": "When you use Azure proximity placement groups in an availability set deployment, all three SAP components (central services, application server, and database) should be in the same proximity placement group.", + "guid": "ae4ecb95-b70f-428f-8b9a-4c5b7e3478a2", + "severity": "High", + "link": "https://learn.microsoft.com/azure/sap/workloads/proximity-placement-scenarios" + }, + { + "category": "Business Continuity and Disaster Recovery", + "subcategory": "High availability", "text": "Use one proximity placement group per SAP SID. Groups don't span across Availability Zones or Azure regions", "guid": "5d2fa56c-56ad-4484-88fe-72734c486ba2", - "severity": "Medium", - "link": "https://learn.microsoft.com/azure/security-center/" + "severity": "High", + "link": "https://learn.microsoft.com/azure/sap/workloads/proximity-placement-scenarios" }, + + + + + + + { "category": "Business Continuity and Disaster Recovery", "subcategory": " ",