Merge pull request #234219 from kalyaninamuduri/patch-42

Update start-stop-sap-systems.md

Author: prmerger-automator[bot]

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

@@ -18,7 +18,10 @@ In this how-to guide, you'll learn to start and stop your SAP systems through th
 
 Through the Azure portal, you can start and stop:
 
-- Application tier instances, which include ABAP SAP Central Services (ASCS) and Application Server instances. You can start and stop instances in the following types of deployments:
+- Entire SAP Application tier in one go, which include ABAP SAP Central Services (ASCS) and Application Server instances.
+- Individual SAP instances, which include Central Services and Application server instances.
+- HANA Database
+- You can start and stop instances in the following types of deployments:
     - Single-Server
     - High Availability (HA)
     - Distributed Non-HA
@@ -28,9 +31,17 @@ Through the Azure portal, you can start and stop:
 ## Prerequisites
 
 - 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).
-- For the start operation to work, all virtual machines (VMs) inside the SAP system must be running. This capability starts or stops the SAP application instances, not the VMs that make up the SAP system resources.
+- 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.
 - The `sapstartsrv` service must be running on all VMs related to the SAP system.
 - 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).
+- 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.
+
+## Supported scenarios
+The following scenarios are supported when Starting and Stopping SAP systems:
+
+- 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.
+- 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.
+- 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.
 
 ## Stop SAP system