SAP HANA Deployment Guide

This deployment guide shows you how to deploy SAP HANA systems on Compute Engine, which is part of Google Cloud Platform (GCP). The guide helps you configure Compute Engine, persistent disks, and the Linux operating system, to achieve the best performance for your SAP HANA system. The guide incorporates best practices from Compute Engine and SAP.

Deploying SAP HANA on GCP

This section shows you how to deploy an SAP HANA installation on GCP by using the Deployment Manager and editing a configuration file template that defines your installation.

Setting up your Google account

A Google account is required to work with GCP.

  1. Sign up for a Google account if you don't already have one.
  2. Log in to the Google Cloud Platform Console, and create a new project.
  3. Enable your billing account.
  4. Configure SSH keys so that you are able to use them to SSH into your Compute Engine instances. Use the gcloud command-line tool to create a new SSH key, or, if you already have an existing SSH key, use the tool to format your existing SSH keys.
  5. Use the gcloud command-line tool or GCP Console to add the SSH keys to your project metadata. This allows you to access any Compute Engine instance created within this project, except for instances that explicitly disable project-wide SSH keys.

Creating a network

When you create a project, a default network is created for your project. However, for security purposes, you should create a new network and specify firewall rules to control who has access.

To set up networking:

  1. Go to Cloud Shell.

    Go to Cloud Shell

  2. To create a new network in the custom subnetworks mode, run:

    gcloud compute networks create [YOUR_NETWORK_NAME] --subnet-mode custom

    where [YOUR_NETWORK_NAME] is the name of the new network. The network name can contain only lowercase characters, digits, and the dash character (-).

    Make sure to specify the custom flag instead of using an automatic subnetwork. An automatic subnetwork always has the same assigned IP address range, which can cause issues if you have multiple subnetworks and want to use VPN.

  3. Create a subnetwork, and specify the region and IP range:

    gcloud compute networks subnets create [YOUR_SUBNETWORK_NAME]
            --network [YOUR_NETWORK_NAME] --region [YOUR_REGION] --range [YOUR_RANGE]

    where:

    • [YOUR_SUBNETWORK_NAME] is the new subnetwork.
    • [YOUR_NETWORK_NAME] is the name of the network you created in the previous step.
    • [REGION] is the region where you want the subnetwork.
    • [YOUR_RANGE] is the IP address range, specified in CIDR format, such as 10.1.0.0/24. If you plan to add more than one subnetwork, assign non-overlapping CIDR IP ranges for each subnetwork in the network. Note that each subnetwork and its internal IP ranges are mapped to a single region.
  4. Optionally, repeat the previous step and add additional subnetworks.

Setting up a NAT gateway

If you intend to create one or more VMs that will not have public IP addresses, you must create a NAT gateway so that your VMs can access the Internet to download Google's monitoring agent.

If you intend to assign an external public IP address to your VM, you can skip this step.

To create a NAT gateway:

  1. Create a VM to act as the NAT gateway in the subnet you just created:

    gcloud compute instances create [YOUR_VM_NAME] --can-ip-forward \
            --zone [YOUR_ZONE]  --image-family [YOUR_IMAGE_FAMILY] \
            --image-project [YOUR_IMAGE_PROJECT] \
            --machine-type=[YOUR_MACHINE_TYPE] --subnet [YOUR_SUBNETWORK_NAME] \
            --metadata startup-script="sysctl -w net.ipv4.ip_forward=1; iptables \
            -t nat -A POSTROUTING -o eth0 -j MASQUERADE" --tags [YOUR_VM_TAG]

    where:

    • [YOUR_VM_NAME] is the name of the VM you are creating that want to use for the NAT gateway.
    • [YOUR_ZONE] is the zone where you want the VM.
    • [YOUR_IMAGE_FAMILY] and [YOUR_IMAGE_PROJECT] specify the image you want to use for the NAT gateway.
    • [YOUR_MACHINE_TYPE] is any supported machine type. If you expect high network traffic, choose a machine type with that has at least eight virtual CPUs.
    • [YOUR_SUBNETWORK_NAME] is the name of the subnetwork where you want the VM.
    • [YOUR_VM_TAG] is a tag that is applied to the VM you are creating. If you use this VM as a bastion host, this tag is used to apply the related firewall rule only to this VM.
  2. Create a route that is tagged so that traffic passes through the NAT VM instead of the default Internet gateway:

    gcloud compute routes create [YOUR_ROUTE_NAME] \
            --network [YOUR_NETWORK_NAME] --destination-range 0.0.0.0/0 \
            --next-hop-instance [YOUR_VM_NAME] --next-hop-instance-zone \
            [YOUR_ZONE] --tags [YOUR_TAG_NAME] --priority 800

    where:

    • [YOUR_ROUTE_NAME] is the name of the route you are creating.
    • [YOUR_NETWORK_NAME] is the network you created.
    • [YOUR_VM_NAME] is the VM you are using for your NAT gateway.
    • [YOUR_ZONE] is the zone where the VM is located.
    • [YOUR_TAG_NAME] is the tag on the route that directs traffic through the NAT VM.
  3. If you also want to use the NAT gateway VM as a bastion host, run the following command. This command creates a firewall rule that allows inbound SSH access to this instance from the Internet:

    gcloud compute firewall-rules create allow-ssh --network [YOUR_NETWORK_NAME] --allow tcp:22 --source-ranges 0.0.0.0/0 --target-tags "[YOUR_VM_TAG]"

    where:

    • [YOUR_NETWORK_NAME] is the network you created.
    • [YOUR_VM_TAG] is the tag you specified when you created the NAT gateway VM. This tag is used so this firewall rule applies only to the VM that hosts the NAT gateway, and not to all VMs in the network.

Downloading SAP HANA

Unless you have already extracted the SAP HANA binaries to a Cloud Storage bucket, download SAP HANA now:

  1. Log into the SAP support portal.

    If your SAP Support Portal account does not allow access to the software and you believe that you should be entitled to the software, contact the SAP Global Support Customer Interaction Center.

  2. In the left navigation pane, choose Installation and Upgrades.

  3. Choose A – Z index. 0 In the Installations and Upgrades window, choose H.
  4. Choose SAP HANA Platform Edition from the list.
  5. Choose SAP HANA Platform Edit. 1.0 or 2.0.
  6. Choose Installation.
  7. In the Downloads windows, find the Linux x86_64 revision you wish to download, and download all applicable parts directly to your local drive. For example, all 3 parts of SAP HANA Platf.Ed.1.0 SPS12 DSP(SAP HANA DB 1.00.122.6).
  8. Use the GCP Console to create a Cloud Storage bucket for storing the SAP HANA installation files. Note that the bucket name must be unique across GCP.

    • During bucket creation, choose Regional if you plan to create SAP HANA instances in a single region.

      Creating Buckets

    • If you are creating SAP HANA instances in other regions in the same continent, choose Multi-Regional for your storage class. If you are not sure, choose Multi-Regional.

  9. Configure bucket permissions. By default, as owner of the bucket, you have read-write access to the bucket. If you want, you can allow other members in your group or individual users to access your bucket, as shown here:

    Bucket Permissions

  10. In the GCP Console, in the Cloud Storage bucket page, choose Upload Files to upload the software to your bucket from your local media:

    Upload Files

  11. Note the name of the bucket that you uploaded the binaries to. You need to use it later when you install SAP HANA.

Creating a VM with SAP HANA installed

The following instructions install SAP HANA on one or more VM instances with all of the persistent disks that SAP HANA requires. You define the values for the installation in a Deployment Manager configuration file template. The instructions use the Cloud Shell, but are generally applicable to the Cloud SDK.

  1. Confirm that your current quotas for resources such as persistent disks and CPUs are sufficient for the SAP HANA system you are about to install. If your quotas are insufficient, deployment fails. For the SAP HANA quota requirements, see Pricing and quota considerations for SAP HANA.

    Go to the quotas page

  2. Open the Cloud Shell or, if you installed the Cloud SDK on your local workstation, open a terminal.

    Go to the Cloud Shell

  3. Download the template.yaml configuration file template to your working directory by entering the following command in the Cloud Shell or GCP SDK:

    wget https://storage.googleapis.com/sapdeploy/dm-templates/sap_hana/template.yaml
    
  4. Open the template.yaml file in Cloud Shell code editor or, if you are using the GCP SDK, the text editor of your choice.

    To open the Cloud Shell code editor, click the pencil icon in the upper right corner of the Cloud Shell terminal window.

  5. In the template.yaml file, update the following property values by replacing the brackets and their contents with the values for your installation.

    Some of the property values that you specify for the SAP HANA system, such as [SID] or [PASSWORD], are subject to rules that are defined by SAP. For more information, see the Parameter Reference in the SAP HANA Server Installation and Update Guide.

    If you want to create a VM instance without installing SAP HANA, delete all of the lines that begin with sap_hana_.

    • instanceName: [VM_NAME] is the name of the VM instance for the SAP HANA master node. The name must be specified in lowercase letters, numbers, or hyphens. The VM instances for any worker nodes use the same name with a "w" and the node number appended to the name.
    • instanceType: [MACHINE_TYPE] is the type of Compute Engine virtual machine that you want to run HANA on.
    • zone: [ZONE] is the zone in which you are deploying your SAP HANA systems to run. It must be in the region that you selected for your subnet.
    • subnetwork: [SUBNETWORK] is the name of the subnetwork you created in a previous step.
    • linuxImage: [IMAGE_FAMILY] is the operating-system image family that contains the RHEL or SLES image that you are using with SAP HANA. For example, rhel-7-sap-hana or sles-12-sp2-sap. For the list of available image families, see the Images page in the Cloud console.
    • linuxImageProject: [IMAGE_PROJECT] is the project that contains the image you are going to use. This project might be your own project or a GCP image project, such as rhel-sap-cloud or suse-sap-cloud. For a list of GCP image projects, see the Images page in the Compute Engine documentation.
    • sap_hana_deployment_bucket: [MEDIA_BUCKET] is the name of the GCP storage bucket in your project that contains the SAP HANA installation files that you uploaded in a previous step.
    • sap_hana_sid: [SID] is the SAP HANA system ID.
    • sap_hana_instance_number: [INSTANCE_NUMBER] is the instance number of the SAP HANA system.
    • sap_hana_sidadm_password: [PASSWORD] is the password for the operating system administrator.
    • sap_hana_system_password: [PASSWORD] is the password for the database superuser.
    • sap_hana_scaleout_nodes: [NUMBER_OF_WORKER_NODES] is the number of additional SAP HANA worker nodes that you need. The worker nodes are in addition to the primary SAP HANA instance. For example, if you specify 3, four SAP-HANA instances are deployed in a scale-out cluster.

    The following example shows a completed configuration file, which directs the Deployment Manager to deploy an n1-highmem-96 virtual machine with a scale-out HANA system that includes a master SAP HANA instance with three worker nodes. SAP HANA is running on a SLES 12 SP2 operating system.

     imports:
     - path: https://storage.googleapis.com/saphana/dm-templates/sap_hana/sap_hana.py
    
     resources:
     - name: sap_hana
       type: https://storage.googleapis.com/saphana/dm-templates/sap_hana/sap_hana.py
       properties:
         instanceName: example-vm
         instanceType: n1-highmem-96
         zone: us-central1-f
         subnetwork: default
         linuxImage: family/sles-12-sp2-sap
         linuxImageProject: suse-sap-cloud
         sap_hana_deployment_bucket: mybucketname
         sap_hana_sid: ABC
         sap_hana_instance_number: 00
         sap_hana_sidadm_password: Google123
         sap_hana_system_password: Google123
         sap_hana_scaleout_nodes: 3
    
  6. Create the instances:

    gcloud deployment-manager deployments create [DEPLOYMENT-NAME] --config
    template.yaml
    

    The above command invokes the Deployment Manager, which deploys the VMs, downloads the SAP HANA software from your storage bucket, and installs SAP HANA, all according to the specifications in your template.yaml file. The process takes approximately 10 to 15 minutes to complete. To check the progress of your deployment, follow the steps in the next section.

Verifying deployment

  1. Open Stackdriver Logging to check for errors and monitor the progress of the installation.

    Go to Stackdriver logging

  2. On the Resources tab, select Global as your logging resource.

    • If "INSTANCE DEPLOYMENT COMPLETE" is displayed, Deployment Manager processing is complete and you can proceed to the next step.
    • If you see a quota error:
    • Increase any of your quotas on the Quotas page in the console that do not meet the SAP HANA requirements that are listed in the SAP HANA Planning Guide.
    • Cleanup the VMs and persistent disks from the failed installation.
    • Rerun the Deployment Manager.

    Stackdriver logging display.

  3. After the Deployment Manager completes without errors, from your Cloud Shell window, SSH into the VM and change to the root user.

    gcloud compute ssh [YOUR_VM_NAME] --zone [YOUR_ZONE]

    sudo su -

  4. At the command prompt, enter df -h. Ensure that you see output similar to the following, such as the /hana/data directory.

    Data volumes created by the script.

  5. Change to the SAP admin user. Replace [SID] with the [SID] value that you specified in the configuration file template.

    su - [SID]adm

  6. Ensure that SAP HANA services are running on the instance.

    HDB info
    

If any of the above validation steps show that the installation failed, resolve any errors, delete the VM instances and the disks, and then re-run the create command.

    gcloud deployment-manager deployments create [DEPLOYMENT-NAME] --config
    template.yaml

Completing the NAT gateway installation

If you created a NAT gateway, complete the following steps.

  1. Add tags to all instances, including the worker nodes:

    export INSTANCE_NAME="[YOUR_VM_NAME]"
    export NETWORK_NAME="[YOUR_NETWORK_NAME]"
    export ZONE="[YOUR_ZONE]"
    export TAG="[YOUR_TAG_TEXT]"

    gcloud compute instances add-tags "$INSTANCE_NAME" --tags="$TAG" --zone=$ZONE
    gcloud compute instances add-tags "$INSTANCE_NAME"w1 --tags="$TAG" --zone=$ZONE
    gcloud compute instances add-tags "$INSTANCE_NAME"w2 --tags="$TAG" --zone=$ZONE
    gcloud compute instances add-tags "$INSTANCE_NAME"w3 --tags="$TAG" --zone=$ZONE

  2. Delete external IPs:

    gcloud compute instances delete-access-config "$INSTANCE_NAME" --access-config-name "external-nat" --zone=$ZONE
    gcloud compute instances delete-access-config "$INSTANCE_NAME"w1 --access-config-name "external-nat" --zone=$ZONE
    gcloud compute instances delete-access-config "$INSTANCE_NAME"w2 --access-config-name "external-nat" --zone=$ZONE
    gcloud compute instances delete-access-config "$INSTANCE_NAME"w3 --access-config-name "external-nat" --zone=$ZONE

Creating a Windows VM for SAP HANA Studio

  1. Use the Cloud Shell to invoke the following commands.

    OPEN THE CLOUD SHELL

    export NETWORK_NAME="[YOUR_NETWORK_NAME]"
    export REGION="[YOUR_REGION]"
    export ZONE="[YOUR_ZONE]"
    export SUBNET="[YOUR_SUBNETWORK_NAME]"

    gcloud compute instances create "saphanastudio" --zone $ZONE --machine-type "n1-standard-2" --subnet $SUBNET --metadata "tag1=hanastudio" --image "windows-server-2012-r2-dc-v20170117" --image-project "windows-cloud" --boot-disk-size "100" --boot-disk-type "pd-standard" --boot-disk-device-name "saphanastudio"

    gcloud compute firewall-rules create ${NETWORK_NAME}-allow-rdp --network $NETWORK_NAME --allow tcp:3389 --source-ranges 0.0.0.0/0 --target-tags "hanastudio"

    The above commands create a Windows server in the subnetwork you created earlier, with a firewall rule to allow access to the instance through Remote Desktop Protocol (RDP). Although not shown in this guide, you can whitelist your customer IP address range in the firewall rules.

  2. Install SAP HANA Studio on this server.

Setting up Google's monitoring agent for SAP HANA

Optionally, you can set up Google's monitoring agent for SAP HANA, which collects metrics from SAP HANA and sends them to Stackdriver Monitoring. Stackdriver Monitoring allows you to create dashboards for your metrics, set up custom alerts based on metric thresholds, and more. For more information on setting up and configuring Google's monitoring agent for SAP HANA, see the SAP HANA Monitoring Agent User Guide.

Connecting to SAP HANA

Note that because these instructions don't use an external IP for SAP HANA, you can only connect to the SAP HANA instances through the bastion instance using SSH or through the Windows server through SAP HANA Studio.

  • To connect to SAP HANA through the bastion instance, connect to the bastion host, and then to the SAP HANA instance(s) by using an SSH client of your choice.

  • To connect to the SAP HANA database through SAP HANA Studio, use a remote desktop client to connect to the Windows Server instance. After connection, manually install SAP HANA Studio and access your SAP HANA database.

Performing post-deployment tasks

Before using your SAP HANA instance, we recommend that you perform the following post-deployment steps. For more information, see SAP HANA Installation and Update Guide.

  1. Update the SAP HANA software with the latest patches.

  2. Install any additional components such as Application Function Libraries (AFL) or Smart Data Access (SDA).

  3. Configure and backup your new SAP HANA database. For more information, see the SAP HANA operations guide.

What's next

Send feedback about...