Single-instance Implementations (2-tier or 3-tier)

By Ashwin Venugopal -

 

Overview

If you want go for a NetWeaver AnyDB deployment, then you can readily follow the standard (2-tier) or distributed (3-tier) NetWeaver installation options in SAP Software Provisioning Manager (SWPM). But, for the HANA-based ones, you will have to choose from one of the following methods:
  1. Use SAP Software Provisioning Manager (SWPM) as a part of the standard (2-tier) or distributed (3-tier) NetWeaver installation, followed by HANA installation.
  2. Use the SAP HANA database lifecycle manager (HDBLCM) tool, and then install NetWeaver.

The installation can start by an ASCS instance and the /sapmnt share, which have the SAP profile directory, should be shared with the SAP DB server VM. Depending on the OS of the DB server, the best way to provide access is via either SMB or NFS. 

The /sapmnt is shared via NFS while using Linux OS with the help of rw and no_root_squash options which may lead to problems while installing the database instance. Finally, the installation provisions the primary application server instance and after this is installed, you can easily use the tools like SAP GUI to verify that the installation finished correctly or not.

Key steps for SAP HANA installation when you use SAP SWPM

The following are the key steps for manual, single-instance SAP HANA installation when you use SAP SWPM to perform a distributed SAP NetWeaver 7.5 installation:
  1. Create an Azure virtual network.
  2. Deploy two Azure VMs with the help of Azure Resource Manager deployment model.
  3. Attach standard or premium data disks to the application server VM.
  4. Attach premium data disks to the HANA DB server VM.
  5. Create striped volumes using the attache disk. You can use either Logical Volume Management (LVM) or the multiple-devices administration (mdadm) tool inside the VM at the OS level.
  6. Create XFS file system on the attached disk or logical volumes.
  7. Mount the new volumes at the OS level by using separate volumes for the SAP binaries, /sapmnt directory, and backups. You should mount the XFS file systems on the premium storage disks as /hana and /usr/sap on the SAP HANA DB server which would prevent the filling up of root file system that isn't large on Linux AzureVMs.
  8. Add entries representing Azure VMs to the /etc/hosts file.
  9. Add the nofail parameter to the /etc/fstab file.
  10. Set Linux kernel parameters according to the Linux OS release you use.
  11. Add swap space.
  12. Optionally, install a graphical desktop on the test VMs or use a remote SAPinst installation.
  13. Download the SAP software from the SAP Service Marketplace.
  14. Install the SAP ASCS instance on the app server VM.
  15. Share the /sapmnt directory using  NFS whose server is the application server VM.
  16. Install the database instance by using SWPM on the DB server VM.
  17. Install the Primary Application Server (PAS) on the application server VM.
  18. Start SAP Management Console (SAP MC) and connect it with SAP GUI or HANA studio.  


Key steps for SAP HANA installation using HD-BLCM

The following are the key steps for manual, single-instance SAP HANA installation when you use SAP HDBLCM to perform a distributed SAP NetWeaver 7.5 installation:
  1. Create an Azure virtual network.
  2. Deploy two Azure VMs with the help of Azure Resource Manager deployment model.
  3. Attach standard or premium data disks to the application server VM.
  4. Attach premium data disks to the HANA DB server VM.
  5. Create striped volumes using the attache disk. You can use either Logical Volume Management (LVM) or the multiple-devices administration (mdadm) tool inside the VM at the OS level.
  6. Create XFS file system on the attached disk or logical volumes.
  7. Mount the new volumes at the OS level by using separate volumes for the SAP binaries, /sapmnt directory, and backups. You should mount the XFS file systems on the premium storage disks as /hana and /usr/sap on the SAP HANA DB server which would prevent the filling up of root file system that isn't large on Linux AzureVMs.
  8. Add entries representing Azure VMs to the /etc/hosts file.
  9. Add the nofail parameter to the /etc/fstab file.
  10. Set Linux kernel parameters according to the Linux OS release you use.
  11. Add swap space.
  12. Optionally, install a graphical desktop on the test VMs or use a remote SAPinst installation.
  13. Download the SAP software from the SAP Service Marketplace.
  14. Create a group, sapsys, with group ID 1001, on the HANA DB server VM.
  15. Install SAP HANA on the DB server VM with the help of HANA database lifecycle manager.
  16. Install the SAP ASCS instance on the app server VM.
  17. Share the /sapmnt directory using  NFS whose server is the application server VM.
  18. Install the database instance by using SWPM on the DB server VM.
  19. Install the Primary Application Server (PAS) on the application server VM.
  20. Start SAP Management Console (SAP MC) and connect it with SAP GUI or HANA studio.  

Implementing SAP HANA Scale-out

If you want to install a scale-out SAP HANA, you have to perform the following steps:
  1. Create new or use an existing Azure Vnet.
  2. Deploy VMs with managed Sremium storage disks.
  3. Deploy new or use an existing highly available NFS cluster.
  4. Validate that intra-node communication as well as traffic between the VMs and highly available NFS cluster is not routed through an NVA.    
  5. Install the SAP HANA master node according to the SAP's documentation.
  6. After the installation, you can add the parameter 'basepath_shared = no' to the global.ini file which allows SAP HANA to run in scale-out without 'shared' /hana/data and /hana/log volumes between the nodes.
  7. After changing the global.ini parameter, you can restart the SAP HANA instance.
  8. Add additional worker nodes.  

The scale-out configuration will use non-shared disks for running /hana/data and /hana/log while the /hana/shared volume will be placed on the highly available NFS share. 



Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more