Skip to content

Latest commit

 

History

History
75 lines (56 loc) · 6.39 KB

quickstart-create-high-availability-namecustom.md

File metadata and controls

75 lines (56 loc) · 6.39 KB
Raw
title description ms.service ms.subservice ms.custom ms.topic ms.date ms.author author
Quickstart - Create a distributed highly available SAP system with Azure Center for SAP solutions with Azure CLI
Learn how to create a distributed highly available SAP system in Azure Center for SAP solutions through Azure CLI.
sap-on-azure
center-sap-solutions
devx-track-azurecli
quickstart
05/04/2023
sagarkeswani
sagarkeswani

Quickstart: Use Azure CLI to create infrastructure for a distributed highly available (HA) SAP system with Azure Center for SAP solutions with customized resource names

The Azure CLI is used to create and manage Azure resources from the command line or in scripts.

Azure Center for SAP solutions enables you to deploy and manage SAP systems on Azure. This article shows you how to use Azure CLI to deploy infrastructure for an SAP system with highly available (HA) Three-tier Distributed architecture. You also see how to customize resource names for the Azure infrastructure that gets deployed. Alternatively, you can deploy SAP systems with customized using the Azure PowerShell Module

After you deploy infrastructure and install SAP software with Azure Center for SAP solutions, you can use its visualization, management and monitoring capabilities through the Azure portal. For example, you can:

  • View and track the SAP system as an Azure resource, called the Virtual Instance for SAP solutions (VIS).
  • Get recommendations for your SAP infrastructure, Operating System configurations etc. based on quality checks that evaluate best practices for SAP on Azure.
  • Get health and status information about your SAP system.
  • Start and Stop SAP application tier.
  • Start and Stop individual instances of ASCS, App server and HANA Database.
  • Monitor the Azure infrastructure metrics for the SAP system resources.
  • View Cost Analysis for the SAP system.

Prerequisites

  • An Azure subscription.

  • If you're using Azure Center for SAP solutions for the first time, Register the Microsoft.Workloads Resource Provider on the subscription in which you're deploying the SAP system:

    az provider register --namespace 'Microsoft.Workloads'

  • An Azure account with Azure Center for SAP solutions administrator and Managed Identity Operator role access to the subscriptions and resource groups in which you create the Virtual Instance for SAP solutions (VIS) resource.

  • A User-assigned managed identity which has Azure Center for SAP solutions service role access on the Subscription or atleast all resource groups (Compute, Network,Storage). If you wish to install SAP Software through the Azure Center for SAP solutions, also provide Reader and Data Access role to the identity on SAP bits storage account where you would store the SAP Media.

  • A network set up for your infrastructure deployment.

  • Availability of minimum 4 cores of either Standard_D4ds_v4 or Standard_E4s_v3, SKUS which will be used during Infrastructure deployment and Software Installation

  • Review the quotas for your Azure subscription. If the quotas are low, you might need to create a support request before creating your infrastructure deployment. Otherwise, you might experience deployment failures or an Insufficient quota error.

  • Note the SAP Application Performance Standard (SAPS) and database memory size that you need to allow Azure Center for SAP solutions to size your SAP system. If you're not sure, you can also select the VMs. There are:

    • A single or cluster of ASCS VMs, which make up a single ASCS instance in the VIS.
    • A single or cluster of Database VMs, which make up a single Database instance in the VIS.
    • A single Application Server VM, which makes up a single Application instance in the VIS. Depending on the number of Application Servers being deployed or registered, there can be multiple application instances.

[!INCLUDE cloud-shell-try-it.md]

Right Size the SAP system you want to deploy

Use az workloads sap-sizing-recommendation to get SAP system sizing recommendations by providing SAPS input for application tier and memory required for database tier

az workloads sap-sizing-recommendation --app-location "eastus" --database-type "HANA" --db-memory 1024 --deployment-type "ThreeTier" --environment "Prod" --high-availability-type "AvailabilitySet" --sap-product "S4HANA" --saps 75000 --location "eastus2" --db-scale-method ScaleUp

Create json configuration file with custom resource names

  • Prepare a json file with the configuration (payload) to use for the deployment of SAP system infrastructure. You can make edits in this sample payload or use the examples listed in the Rest API documentation for Azure Center for SAP solutions
  • In this json file, provide the custom resource names for the infrastructure that is deployed for your SAP system

Deploy infrastructure for your SAP system

Use az workloads sap-virtual-instance create to deploy infrastructure for your SAP system with Three tier HA architecture

az workloads sap-virtual-instance create -g <Resource Group Name> -n <VIS Name> --environment NonProd --sap-product s4hana --configuration <Payload file path> --identity "{type:UserAssigned,userAssignedIdentities:{<Managed_Identity_ResourceID>:{}}}"

Next steps

In this quickstart, you deployed infrastructure in Azure for an SAP system using Azure Center for SAP solutions. You used custom resource names for the infrastructure. Continue to the next article to learn how to install SAP software on the infrastructure deployed.

[!div class="nextstepaction"] Install SAP software