Skip to content

Commit 806ce83

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #238458 from kalyaninamuduri/patch-57
Update start-stop-sap-systems.md
2 parents 253fa3a + 065ce5c commit 806ce83

File tree

4 files changed

+145
-8
lines changed

4 files changed

+145
-8
lines changed

‎articles/sap/center-sap-solutions/manage-with-azure-rbac.md

Lines changed: 132 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -300,6 +300,138 @@ To stop the SAP system from a VIS resource, a *user* and *user-assigned managed
300300
| `Microsoft.Compute/virtualMachines/extensions/write` |
301301
| `Microsoft.Compute/virtualMachines/instanceView/read` |
302302

303+
## Start SAP Central services instance
304+
To start the SAP Central services instance from a VIS resource, a *user* and *user-assigned managed identity* requires the following role or permissions.
305+
306+
| Built-in roles for *users* |
307+
| ------------------------- |
308+
| **Azure Center for SAP solutions administrator** |
309+
310+
| Minimum permissions for *users* |
311+
| ------------------------------- |
312+
| `Microsoft.Workloads/sapVirtualInstances/centralInstances/start/action` |
313+
314+
| Built-in roles for *user-assigned managed identities* |
315+
| ---------------------------------------------------- |
316+
| **Azure Center for SAP solutions service role** |
317+
318+
| Minimum permissions for *user-assigned managed identities* |
319+
| ---------------------------------------------------------- |
320+
| `Microsoft.Compute/virtualMachines/read` |
321+
| `Microsoft.Compute/virtualMachines/extensions/read` |
322+
| `Microsoft.Compute/virtualMachines/extensions/write` |
323+
| `Microsoft.Compute/virtualMachines/instanceView/read` |
324+
325+
## Stop SAP Central services instance
326+
To stop the SAP Central services instance from a VIS resource, a *user* and *user-assigned managed identity* requires the following role or permissions.
327+
328+
| Built-in roles for *users* |
329+
| ------------------------- |
330+
| **Azure Center for SAP solutions administrator** |
331+
332+
| Minimum permissions for *users* |
333+
| ------------------------------- |
334+
| `Microsoft.Workloads/sapVirtualInstances/centralInstances/stop/action` |
335+
336+
| Built-in roles for *user-assigned managed identities* |
337+
| ---------------------------------------------------- |
338+
| **Azure Center for SAP solutions service role** |
339+
340+
| Minimum permissions for *user-assigned managed identities* |
341+
| ---------------------------------------------------------- |
342+
| `Microsoft.Compute/virtualMachines/read` |
343+
| `Microsoft.Compute/virtualMachines/extensions/read` |
344+
| `Microsoft.Compute/virtualMachines/extensions/write` |
345+
| `Microsoft.Compute/virtualMachines/instanceView/read` |
346+
347+
## Start SAP Application server instance
348+
To start the SAP Application server instance from a VIS resource, a *user* and *user-assigned managed identity* requires the following role or permissions.
349+
350+
| Built-in roles for *users* |
351+
| ------------------------- |
352+
| **Azure Center for SAP solutions administrator** |
353+
354+
| Minimum permissions for *users* |
355+
| ------------------------------- |
356+
| `Microsoft.Workloads/sapVirtualInstances/applicationInstances/start/action` |
357+
358+
| Built-in roles for *user-assigned managed identities* |
359+
| ---------------------------------------------------- |
360+
| **Azure Center for SAP solutions service role** |
361+
362+
| Minimum permissions for *user-assigned managed identities* |
363+
| ---------------------------------------------------------- |
364+
| `Microsoft.Compute/virtualMachines/read` |
365+
| `Microsoft.Compute/virtualMachines/extensions/read` |
366+
| `Microsoft.Compute/virtualMachines/extensions/write` |
367+
| `Microsoft.Compute/virtualMachines/instanceView/read` |
368+
369+
## Stop SAP Application server instance
370+
To stop the SAP Application server instance from a VIS resource, a *user* and *user-assigned managed identity* requires the following role or permissions.
371+
372+
| Built-in roles for *users* |
373+
| ------------------------- |
374+
| **Azure Center for SAP solutions administrator** |
375+
376+
| Minimum permissions for *users* |
377+
| ------------------------------- |
378+
| `Microsoft.Workloads/sapVirtualInstances/applicationInstances/stop/action` |
379+
380+
| Built-in roles for *user-assigned managed identities* |
381+
| ---------------------------------------------------- |
382+
| **Azure Center for SAP solutions service role** |
383+
384+
| Minimum permissions for *user-assigned managed identities* |
385+
| ---------------------------------------------------------- |
386+
| `Microsoft.Compute/virtualMachines/read` |
387+
| `Microsoft.Compute/virtualMachines/extensions/read` |
388+
| `Microsoft.Compute/virtualMachines/extensions/write` |
389+
| `Microsoft.Compute/virtualMachines/instanceView/read` |
390+
391+
## Start SAP HANA Database instance
392+
To start the SAP HANA Database instance from a VIS resource, a *user* and *user-assigned managed identity* requires the following role or permissions.
393+
394+
| Built-in roles for *users* |
395+
| ------------------------- |
396+
| **Azure Center for SAP solutions administrator** |
397+
398+
| Minimum permissions for *users* |
399+
| ------------------------------- |
400+
| `Microsoft.Workloads/sapVirtualInstances/databaseInstances/start/action` |
401+
402+
| Built-in roles for *user-assigned managed identities* |
403+
| ---------------------------------------------------- |
404+
| **Azure Center for SAP solutions service role** |
405+
406+
| Minimum permissions for *user-assigned managed identities* |
407+
| ---------------------------------------------------------- |
408+
| `Microsoft.Compute/virtualMachines/read` |
409+
| `Microsoft.Compute/virtualMachines/extensions/read` |
410+
| `Microsoft.Compute/virtualMachines/extensions/write` |
411+
| `Microsoft.Compute/virtualMachines/instanceView/read` |
412+
413+
## Stop SAP HANA Database instance
414+
To stop the SAP HANA Database instance from a VIS resource, a *user* and *user-assigned managed identity* requires the following role or permissions.
415+
416+
| Built-in roles for *users* |
417+
| ------------------------- |
418+
| **Azure Center for SAP solutions administrator** |
419+
420+
| Minimum permissions for *users* |
421+
| ------------------------------- |
422+
| `Microsoft.Workloads/sapVirtualInstances/databaseInstances/stop/action` |
423+
424+
| Built-in roles for *user-assigned managed identities* |
425+
| ---------------------------------------------------- |
426+
| **Azure Center for SAP solutions service role** |
427+
428+
| Minimum permissions for *user-assigned managed identities* |
429+
| ---------------------------------------------------------- |
430+
| `Microsoft.Compute/virtualMachines/read` |
431+
| `Microsoft.Compute/virtualMachines/extensions/read` |
432+
| `Microsoft.Compute/virtualMachines/extensions/write` |
433+
| `Microsoft.Compute/virtualMachines/instanceView/read` |
434+
303435
## View cost analysis
304436

305437
To view the cost analysis, a *user* requires the following role or permissions.

‎articles/sap/center-sap-solutions/quick-stop-start-sap-cli.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,11 +24,12 @@ Through the Azure CLI, you can start and stop:
2424
- Single-Server
2525
- High Availability (HA)
2626
- Distributed Non-HA
27-
- SAP systems that run on Windows and Linux operating systems (OS).
28-
- SAP HA systems that use Linux Pacemaker clustering software and Windows Server Failover Clustering (WSFC). Other certified cluster software isn't currently supported.
27+
- SAP systems that run on Windows and, RHEL and SUSE Linux operating systems.
28+
- SAP HA systems that use SUSE and RHEL Pacemaker clustering software and Windows Server Failover Clustering (WSFC). Other certified cluster software isn't currently supported.
2929

3030
## Prerequisites
3131
- An SAP system that you've [created in Azure Center for SAP solutions](prepare-network.md) or [registered with Azure Center for SAP solutions](register-existing-system.md) as a *Virtual Instance for SAP solutions* resource.
32+
- Check that your Azure account has **Azure Center for SAP solutions administrator** or equivalent role access on the Virtual Instance for SAP solutions resources. You can learn more about the granular permissions that govern Start and Stop actions on the VIS, individual SAP instances and HANA Database [in this article](manage-with-azure-rbac.md#start-sap-system).
3233
- For the start operation to work, the underlying virtual machines (VMs) of the SAP instances must be running. This capability starts or stops the SAP application instances, not the VMs that make up the SAP system resources.
3334
- The `sapstartsrv` service must be running on all VMs related to the SAP system.
3435
- For HA deployments, the HA interface cluster connector for SAP (`sap_vendor_cluster_connector`) must be installed on the ASCS instance. For more information, see the [SUSE connector specifications](https://www.suse.com/c/sap-netweaver-suse-cluster-integration-new-sap_suse_cluster_connector-version-3-0-0/) and [RHEL connector specifications](https://access.redhat.com/solutions/3606101).

‎articles/sap/center-sap-solutions/quick-stop-start-sap-powershell.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,13 +24,14 @@ Through the Azure PowerShell module, you can start and stop:
2424
- Single-Server
2525
- High Availability (HA)
2626
- Distributed Non-HA
27-
- SAP systems that run on Windows and Linux operating systems (OS).
28-
- SAP HA systems that use Linux Pacemaker clustering software and Windows Server Failover Clustering (WSFC). Other clustering software solutions aren't currently supported.
27+
- SAP systems that run on Windows and, RHEL and SUSE Linux operating systems.
28+
- SAP HA systems that use SUSE and RHEL Pacemaker clustering software and Windows Server Failover Clustering (WSFC). Other certified cluster software isn't currently supported.
2929

3030
## Prerequisites
3131

3232
The following are prerequisites that you need to ensure before using the Start or Stop capability on the Virtual Instance for SAP solutions resource.
3333
- An SAP system that you've [created in Azure Center for SAP solutions](prepare-network.md) or [registered with Azure Center for SAP solutions](register-existing-system.md) as a *Virtual Instance for SAP solutions* resource.
34+
- Check that your Azure account has **Azure Center for SAP solutions administrator** or equivalent role access on the Virtual Instance for SAP solutions resources. You can learn more about the granular permissions that govern Start and Stop actions on the VIS, individual SAP instances and HANA Database [in this article](manage-with-azure-rbac.md#start-sap-system).
3435
- For the start operation to work, the underlying virtual machines (VMs) of the SAP instances must be running. This capability starts or stops the SAP application instances, not the VMs that make up the SAP system resources.
3536
- The `sapstartsrv` service must be running on all VMs related to the SAP system.
3637
- For HA deployments, the HA interface cluster connector for SAP (`sap_vendor_cluster_connector`) must be installed on the ASCS instance. For more information, see the [SUSE connector specifications](https://www.suse.com/c/sap-netweaver-suse-cluster-integration-new-sap_suse_cluster_connector-version-3-0-0/) and [RHEL connector specifications](https://access.redhat.com/solutions/3606101).

‎articles/sap/center-sap-solutions/start-stop-sap-systems.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ author: lauradolan
1212

1313
# Start and stop SAP systems
1414

15-
16-
1715
In this how-to guide, you'll learn to start and stop your SAP systems through the *Virtual Instance for SAP solutions (VIS)* resource in *Azure Center for SAP solutions*.
1816

1917
Through the Azure portal, you can start and stop:
@@ -25,20 +23,25 @@ Through the Azure portal, you can start and stop:
2523
- Single-Server
2624
- High Availability (HA)
2725
- Distributed Non-HA
28-
- SAP systems that run on Windows and Linux operating systems (OS).
29-
- SAP HA systems that use Linux Pacemaker clustering software and Windows Server Failover Clustering (WSFC). Other certified cluster software isn't currently supported.
26+
- SAP systems that run on Windows and, RHEL and SUSE Linux operating systems.
27+
- SAP HA systems that use SUSE and RHEL Pacemaker clustering software and Windows Server Failover Clustering (WSFC). Other certified cluster software isn't currently supported.
3028

3129
## Prerequisites
3230

3331
- An SAP system that you've [created in Azure Center for SAP solutions](prepare-network.md) or [registered with Azure Center for SAP solutions](register-existing-system.md).
32+
- Check that your Azure account has **Azure Center for SAP solutions administrator** or equivalent role access on the Virtual Instance for SAP solutions resources. You can learn more about the granular permissions that govern Start and Stop actions on the VIS, individual SAP instances and HANA Database [in this article](manage-with-azure-rbac.md#start-sap-system).
3433
- For the start operation to work, the underlying virtual machines (VMs) of the SAP instances must be running. This capability starts or stops the SAP application instances, not the VMs that make up the SAP system resources.
3534
- The `sapstartsrv` service must be running on all VMs related to the SAP system.
3635
- For HA deployments, the HA interface cluster connector for SAP (`sap_vendor_cluster_connector`) must be installed on the ASCS instance. For more information, see the [SUSE connector specifications](https://www.suse.com/c/sap-netweaver-suse-cluster-integration-new-sap_suse_cluster_connector-version-3-0-0/) and [RHEL connector specifications](https://access.redhat.com/solutions/3606101).
3736
- For HANA Database, Stop operation is initiated only when the cluster maintenance mode is in **Disabled** status. Similarly, Start operation is initiated only when the cluster maintenance mode is in **Enabled** status.
3837

38+
> [!NOTE]
39+
> When you deploy an SAP system using Azure Center for SAP solutions, RHEL and SUSE cluster connector for highly available systems is already configured on them as part of the SAP software installation process.
40+
3941
## Supported scenarios
4042
The following scenarios are supported when Starting and Stopping SAP systems:
4143

44+
- SAP systems that run on Windows and, RHEL and SUSE Linux operating systems.
4245
- Stopping and Starting SAP system or individual instances from the VIS resource only stops or starts the SAP application. The underlying VMs are **not** stopped or started.
4346
- Stopping a highly available SAP system from the VIS resource gracefully stops the SAP instances in the right order and does not result in a failover of Central Services instance.
4447
- Stopping the HANA Database from the VIS resource results in the entire HANA instance to be stopped. In case of HANA MDC with multiple tenant DBs, the entire instance is stopped and not the specific Tenant DB.

0 commit comments

Comments
 (0)