avistavkin / sap-hana-arm-andvis-econom

SAP HANA ARM Installation

This ARM template is used to install SAP HANA on a single VM running SUSE SLES 12 SP 3 or SLES 12 SP 2. For documentation on deploying a cluster of linux machines running HANA System Replication and Linux High Availability Extension, please see documentation here: cluster deployment.

This template uses the Linux SKU for SAP. We will be adding additional SKUs and Linux flavors in future Versions. The template takes advantage of Custom Script Extensions for the installation and configuration of the machine. This should be used only for demonstration and sandbox environments. This is not a production deployment.

Machine Info

The template currently deploys HANA on one of the machines listed in the table below with the noted disk configuration. The deployment takes advantage of Managed Disks, for more information on Managed Disks or the sizes of the noted disks can be found on this page.

Machine Size	RAM	Data and Log Disks	/hana/shared	/root	/usr/sap	hana/backup
E16	128 GB	2 x P20	1 x S20	1 x S6	1 x S6	1 x S15
E32	256 GB	2 x P20	1 x S20	1 x S6	1 x S6	1 x S20
E64	432 GB	2 x P20	1 x S20	1 x P6	1 x S6	1 x S30
GS5	448 GB	2 x P20	1 x S20	1 x P6	1 x S6	1 x S30

For the M series servers, this template uses the Write Accelerator feature for the Log disks. For this reason, the log devices are separated out from the data disks:

Machine Size	RAM	Data Disks	Log disks	/hana/shared	/root	/usr/sap	hana/backup
M64s	1TB	4 x P20	2 x P20	1 x P30	1 x P6	1 x P6	2 x P30
M64ms	1.7TB	3 x P30	2 x P20	1 x P30	1 x P6	1 x P6	2 x P30
M128S	2TB	3 x P30	2 x P20	1 x P30	1 x P6	1 x P6	2 x P40
M128ms	3.8TB	5 x P30	2 x P20	1 x P30	1 x P6	1 x P6	5 x P50

Installation Media

Installation media for SAP HANA should be downloaded and placed in the SapBits folder. You will need to provide the URI for the container where they are stored, for example https://yourBlobName.blob.core.windows.net/yourContainerName. For more information on how to upload files to Azure please go here Specifically you need to download SAP package 51053061, which should consist of four files:

51053061_part1.exe
51053061_part2.rar
51053061_part3.rar
51053061_part4.rar

Addtionally, if you wish to install a Windows-based Jumpbox with HANA Studio enabled, create a SAP_HANA_STUDIO folder under your SapBits folder and place the following packages:

IMC_STUDIO2_212_2-80000323.SAR
sapcar.exe
serverjre-9.0.1_windows-x64_bin.tar.gz

If you want to use a newer version of HANA Studio rename your filename to IMC_STUDIO2_212_2-80000323.SAR.

The Server Java Runtime Environment bits can be downloaded here.

There should be a folder inside your storage account container called SapBits:

The following files should be present inside the SapBits folder:

Additionally if you plan on installing the HANA Jumpbox, you should create a folder under the SapBits folder and add the following files:

Deploy the Solution

Deploy from the Portal

To deploy from the portal using a graphic interface you can use the button to bring up the template in your subscription and fill out the parameters.

Deploy from Powershell

New-AzureRmResourceGroup -Name HANADeploymentRG -Location "Central US"
New-AzureRmResourceGroupDeployment -Name HANADeployment -ResourceGroupName HANADeploymentRG `
  -TemplateUri https://raw.githubusercontent.com/AzureCAT-GSI/SAP-HANA-ARM/master/azuredeploy.json `
  -VMName HANAtestVM -HANAJumpbox yes -CustomURI https://yourBlobName.blob.core.windows.net/yourContainerName -VMPassword AweS0me@PW

Deploy from CLI

az login

az group create --name HANADeploymentRG --location "Central US"
az group deployment create \
    --name HANADeployment \
    --resource-group HANADeploymentRG \
    --template-uri "https://raw.githubusercontent.com/AzureCAT-GSI/SAP-HANA-ARM/master/azuredeploy.json" \
    --parameters VMName=HANAtestVM HANAJumpbox=yes CustomURI=https://yourBlobName.blob.core.windows.net/yourContainerName VMPassword=AweS0me@PW

Monitoring

For your deployment to be supported by SAP the Azure Enhanced Monitoring Extension must be enabled on the Virtual Machine. Please refer to the following blog post for more information on how to enable it.

Parameters

Parameter name	Required	Description	Default Value	Allowed Values
VM Name	Yes	Name of the HANA Virtual Machine.	None	No restrictions
HANA Jumpbox	Yes	Defines whether to create a Windows Server with HANA Studio installed.	None	No Restrictions
VM Size	No	Defines the size of the Azure VM for the HANA server.	Standard_GS5	Standard_GS5, Standard_M64s, Standard_M64ms, Standard_M128s, Standard_M128ms, Standard_E16s_v3, Standard_E32s_v3, Standard_E64s_v3
Write Accelerator	Yes	Whether to enable the M series write accelerator.	no	yes, no
Network Name	No	Name of the Azure VNET to be provisioned	ra-hana-vnet	No restrictions
Address Prefixes	No	Address prefix for the Azure VNET to be provisioned	10.0.0.0/16	No restrictions
HANA Subnet Name	No	Name of the subnet where the HANA server will be provisioned	SAPDataSubnet	No restrictions
HANA Subnet Prefix	No	Subnet prefix of the subnet where the HANA server will be provisioned	10.0.5.0/24	No restrictions
Management Subnet Name	No	Name of the subnet where the HANA jumpbox will be provisioned	SAPMgmtSubnet	No restrictions
Management Subnet Prefix	No	Subnet prefix of the subnet where the HANA jumpbox will be provisioned	10.0.6.0/24	No restrictions
Custom URI	Yes	URI where the SAP bits are stored for Azure use the URI up to the container, excluding the SAPBtis folder	None	No restrictions
VM User Name	No	Username for both the HANA server and the HANA jumpbox	testuser	No restrictions
VM Password	Yes	Password for the user defined above	None	No restrictions
Operating System	No	Linux distribution to use for the HANA server	SLES for SAP 12 SP2	SLES for SAP 12 SP2, RHEL 7.2 for SAP HANA
HANASID	No	HANA System ID	H10	No restrictions
HANA Number	No	SAP HANA Instance Number	00	No restrictions
Existing Network Resource Group	No	This gives you the option to deploy the VMs to an existing VNET in a different Resource Group. The value provided should match the name of the existing Resource Group. To deploy the VNET in the same Resource Group the value should be set to "no"	no	No restrictions
IP Allocation Method	no	Lets you choose between Static and Dynamic IP Allocation	Dynamic	Dynamic, Static
Static IP	No	Allows you to choose the specific IP to be assgined to the HANA server. If the allocation method is Dynamic this parameter will be ignored	10.0.5.6	No restrictions
Subscription Email	No	OS subscription email for BYOS. Leave blank for pay-as-you-go OS image.		No restrictions
Subscription ID	No	OS ID or password for BYOS. Leave blank for pay-as-you-go OS image.		No restrictions
SMT Uri	No	The URI to a subscription management server if used, blank otherwise		No restrictions

Known issues

When clicking on Deploy to Azure you get redirected to an empty directory

The only way to get around this is to save the template to your own template library. Click on "Create a Resource" and choose "Template Deployment". Click "Create".

Select the option of "Build your own template in the editor"

Copy the contents from the azuredeploy.json file and paste them into the template editor, click Save.

The template is now available in your template library. Changes made to the github repo will not be replicated, make sure to update your template when changes to the azuredeploy.json file are made.