Skip to content

Commit 149fd13

Browse files
authored
Merge pull request #314822 from Xelu86/cedrcomply
[Update] Customer enabled disaster recovery in Azure Center for SAP solutions
2 parents f62b986 + 65a075e commit 149fd13

1 file changed

Lines changed: 66 additions & 59 deletions

File tree

Lines changed: 66 additions & 59 deletions
Original file line numberDiff line numberDiff line change
@@ -1,66 +1,73 @@
11
---
2-
title: Customer enabled disaster recovery in Azure Center for SAP Solutions
3-
description: Find out about Customer enabled disaster recovery in Azure Center for SAP Solutions
2+
title: Configure customer-enabled disaster recovery in Azure Center for SAP solutions
3+
description: Learn how to configure customer-enabled disaster recovery for Virtual Instance for SAP solutions resources in Azure Center for SAP solutions.
44
author: jjaygbay1
55
ms.author: jacobjaygbay
6-
ms.topic: overview
7-
ms.custom: references_regions
6+
ms.topic: how-to
7+
ms.custom: references_regions
88
ms.service: sap-on-azure
99
ms.subservice: center-sap-solutions
10-
ms.date: 05/15/2023
10+
ms.date: 04/16/2026
1111
# Customer intent: As an SAP administrator, I want to configure customer-enabled disaster recovery for my SAP systems in Azure, so that I can ensure cross-region resiliency and minimize downtime during regional outages.
1212
---
13-
# Customer enabled disaster recovery in *Azure Center for SAP solutions*
14-
Azure Center for SAP solutions service is a zone redundant service. So, service may experience downtime because no paired region exists. There will be no Microsoft initiated failover in the event of a region outage. This article explains some of the strategies that you can use to achieve cross-region resiliency for Virtual Instance for SAP solutions resources with customer enabled disaster recovery. It has detailed steps for you to follow when a region in which your Virtual Instance for SAP solutions resource exists is down.
15-
16-
You must configure disaster recovery for SAP systems that you deploy using Azure Center for SAP solutions using [Disaster recovery overview and infrastructure guidelines for SAP workload](/azure/sap/workloads/disaster-recovery-overview-guide).
17-
18-
In case of a region outage, customers will be notified about it. This article has the steps you can follow to get the Virtual Instance for SAP solutions resources up and running in a different region.
19-
20-
## Prerequisites for Customer enabled disaster recovery in Azure Center for SAP solutions.
21-
Configure disaster recovery for your SAP system deployed using Azure Center for SAP solutions or otherwise using the [Disaster recovery overview and infrastructure guidelines for SAP workload](/azure/sap/workloads/disaster-recovery-overview-guide).
22-
23-
## Region Down Scenarios and Mitigation Steps:
24-
25-
| Case # | ACSS Service Region | SAP Workload Region | Scenario | Mitigation Steps |
26-
|--------|-----------------|------------------|--------------------------|------------------------|
27-
| Case 1 | A (Down) | B | ACSS Service region is down | Register the workload with ACSS service available in another region using PowerShell or CLI which allow to select an available service location. |
28-
| Case 2 | A | B (Down) | SAP Workload region is down | 1. Customers should perform workload failover to DR region (outside of ACSS). <br> 2. Register the failed over workload with ACSS using PowerShell or CLI. |
29-
| Case 3 | A (Down) | B (Down) | ACSS Service and SAP workload regions are down | 1. Customers should perform workload failover to DR region (outside of ACSS). <br> 2. Register the failed over workload with ACSS service available in another region using PowerShell or CLI which allow to select an available service location.
30-
31-
## Steps to re-register the SAP system with Azure Center for SAP solutions in case of regional outage:
32-
33-
1. In case the region where your SAP workload exists is down (case 1 and 2 mentioned in the above section), perform workload failover to DR region (outside of ACSS) and have the workload running in a secondary region.
34-
35-
2. In case the Azure Center for SAP solutions service is down (case 1 and 3 mentioned in the above section) in the region where your Virtual Instance for SAP solutions resource exists, register your SAP system with another available region.
36-
37-
```azurepowershell-interactive
38-
New-AzWorkloadsSapVirtualInstance `
39-
-ResourceGroupName 'TestRG' `
40-
-Name L46 `
41-
-Location eastus `
42-
-Environment 'NonProd' `
43-
-SapProduct 'S4HANA' `
44-
-CentralServerVmId '/subscriptions/sub1/resourcegroups/rg1/providers/microsoft.compute/virtualmachines/l46ascsvm' `
45-
-Tag @{k1 = "v1"; k2 = "v2"} `
46-
-ManagedResourceGroupName "acss-L46-rg" `
47-
-ManagedRgStorageAccountName 'acssstoragel46' `
48-
-IdentityType 'UserAssigned' `
49-
-UserAssignedIdentity @{'/subscriptions/sub1/resourcegroups/rg1/providers/Microsoft.ManagedIdentity/userAssignedIdentities/ACSS-MSI'= @{}} `
50-
```
51-
3. Following table has the list of locations where Azure Center for SAP solutions service is available. It is recommended that you choose a region within the same geography where your SAP infrastructure resources are located.
52-
53-
| **Azure Center for SAP solutions service locations** |
54-
| --------------------------------------------------- |
55-
| East US |
56-
| East US 2 |
57-
| West US 3 |
58-
| West Europe |
59-
| North Europe |
60-
| Australia East |
61-
| East Asia |
62-
| Central India |
63-
64-
## Next steps
65-
> [!div class="nextstepaction"]
66-
> [Deploy a new SAP system with Azure Center for SAP solutions](/azure/sap/center-sap-solutions/deploy-s4hana)
13+
14+
# Configure customer-enabled disaster recovery in Azure Center for SAP solutions
15+
16+
Azure Center for SAP solutions is a zone-redundant service. The service might experience downtime because no paired region exists, and there's no Microsoft-initiated failover during a region outage. This article explains strategies to achieve cross-region resiliency for Virtual Instance for SAP solutions resources with customer-enabled disaster recovery (DR). Also, steps to follow when a region where your Virtual Instance for SAP solutions resource exists is down.
17+
18+
You must configure disaster recovery for SAP systems that you deploy by using Azure Center for SAP solutions. For more information, see [Disaster recovery overview and infrastructure guidelines for SAP workload](/azure/sap/workloads/disaster-recovery-overview-guide).
19+
20+
When a region outage occurs, you're notified. The following sections describe the steps you can follow to get the Virtual Instance for SAP solutions resources running in a different region.
21+
22+
## Prerequisites
23+
24+
- An SAP system deployed by using Azure Center for SAP solutions or registered with Azure Center for SAP solutions.
25+
- DR configured for your SAP system by using the [Disaster recovery overview and infrastructure guidelines for SAP workload](/azure/sap/workloads/disaster-recovery-overview-guide).
26+
27+
## Understand region-down scenarios and mitigation steps
28+
29+
| Case | Service region | Workload region | Scenario | Mitigation steps |
30+
|------|----------------|-----------------|----------|------------------|
31+
| 1 | A (down) | B | Azure Center for SAP solutions service region is down. | Register the workload with an Azure Center for SAP solutions service available in another region by using PowerShell or CLI, which allow you to select an available service location. |
32+
| 2 | A | B (down) | SAP workload region is down. | 1. Perform workload failover to the DR region (outside of Azure Center for SAP solutions). <br><br> 2. Register the failed-over workload by using PowerShell or CLI. |
33+
| 3 | A (down) | B (down) | Both the service and SAP workload regions are down. | 1. Perform workload failover to the DR region (outside of Azure Center for SAP solutions). <br><br> 2. Register the failed-over workload with an Azure Center for SAP solutions service available in another region by using PowerShell or CLI. |
34+
35+
## Re-register the SAP system during a regional outage
36+
37+
1. If the region where your SAP workload exists is down (cases 1 and 2), perform workload failover to the DR region outside of Azure Center for SAP solutions and have the workload running in a secondary region.
38+
39+
1. If the Azure Center for SAP solutions service is down (cases 1 and 3) in the region where your Virtual Instance for SAP solutions resource exists, register your SAP system with another available region.
40+
41+
```azurepowershell-interactive
42+
New-AzWorkloadsSapVirtualInstance `
43+
-ResourceGroupName 'TestRG' `
44+
-Name L46 `
45+
-Location eastus `
46+
-Environment 'NonProd' `
47+
-SapProduct 'S4HANA' `
48+
-CentralServerVmId '/subscriptions/sub1/resourcegroups/rg1/providers/microsoft.compute/virtualmachines/l46ascsvm' `
49+
-Tag @{k1 = "v1"; k2 = "v2"} `
50+
-ManagedResourceGroupName "acss-L46-rg" `
51+
-ManagedRgStorageAccountName 'acssstoragel46' `
52+
-IdentityType 'UserAssigned' `
53+
-UserAssignedIdentity @{'/subscriptions/sub1/resourcegroups/rg1/providers/Microsoft.ManagedIdentity/userAssignedIdentities/ACSS-MSI'= @{}}
54+
```
55+
56+
The following table lists the locations where Azure Center for SAP solutions is available. Choose a region within the same geography where your SAP infrastructure resources are located.
57+
58+
| Azure Center for SAP solutions service locations |
59+
|---|
60+
| Australia East |
61+
| Central India |
62+
| East Asia |
63+
| East US |
64+
| East US 2 |
65+
| North Europe |
66+
| West Europe |
67+
| West US 3 |
68+
69+
## Related content
70+
71+
- [Deploy a new SAP system with Azure Center for SAP solutions](deploy-s4hana.md)
72+
- [Register an existing SAP system](register-existing-system.md)
73+
- [Disaster recovery overview and infrastructure guidelines for SAP workload](/azure/sap/workloads/disaster-recovery-overview-guide)

0 commit comments

Comments
 (0)