9.1.1. SAP HANA

9.1.1.1. About This Menu

About This Menu

This menu provides Customers with SAP-regulated TDI (i.e., Tailored Data-center Integration) appliance in one deployment by initializing SAP HANA along with Operating System over the Baremetal Server and Filestorage for standard Enterprise Cloud.
OS License includes to this menu; however, Customers are advised to bring in their own SAP HANA license.
Hardware operability monitoring stays provisioned within respective menus for Baremetal server and Filestorage ; however, OS and SAP HANA monitoring will not be provisioned thus will be assumed within the capacities of Customers’ monitoring.
As with the operability monitoring of OS and SAP HANA, Customers are advised to separately utilize GMOne for SAP HANA suite.
The image of SAP HANA infrastructure with this menu is following:
SAPHANA

Features

<Activate Your “Asset-Less” Business Agility>

  • Customers can utilize the SAP HANA infrastructure without having to purchase various SAP HANA-regulated appliance components and pay metered charge per their use.

  • Customers can utilize the SAP HANA infrastructure without wondering about the minimum use period but both on the developmental phase or on the base of POC (as in point of concept) to utilize within a short term.

  • Customers can start utilizing SAP HANA infrastructure after five (5) days after officially subscribing the menu.

<System Infrastructure That Is Highly Trusted>

  • Customers can take DR measures depending upon the large-scale disasters in scenario by utilizing inter-DC network connectivity.

<System Infrastructure That Is Highly Trusted>

  • Customers can utilize SAP HANA infrastructure specifically aimed at global aspects so that IT architectural cost will be reduced in line by integrating application architectural development.

  • Customers can utilize SAP HANA infrastructure so that they can reduce IT operational cost through integrating OS and SAP HANA-related maintenance procedures in global scale.


9.1.1.2. Available Functions

List of Available Functions

This menu provides the following functions:

Functions

   

Description

Create SAP HANA infrastructure

Subscription

Specify Enterprise Cloud 2.0 Business Portal / Tenant Access Info

  • Customers can request for deploying SAP HANA infrastructure in which they can specify their Tenant info, operation account ID and password when subscription. NTT Com will verify them and access to customers’ tenant when deploying SAPHANA infrastructure by using these information.

   

Specify Baremetal server set info

  • Customer can specify the flavor, OS and Network information of Baremetal server at subscription.

  • For the network connection information, the designation of DataPlane2 segment, Storage1 segment is possible. However, the logical network for Common Function Gateway cannot be specified. Customers need to connect Common Function Gateway on customers’ side. Designation of each segment Tagged or Untagged is possible.

   

Specify Filestorage set info

  • Customers can specify the name of Virtual Storage, network information, volume name and volume size in FileStorage menu.

   

Specify OS Settings’ set info

  • Customers can specify host name, password, disk partition and connected network information on OS which installed on Baremetal server at subscription.

   

Specify SAP HANA Minimal Server info

  • Customers can specify configuration of Database and the version of installed SAPHANA at subscription.

 

Installation

Baremetal Server setting

  • NTTCom will deploy Baremetal server according to subscribe request.

  • Network interface connects two by two each in the data plane and the storage plane.

   

Set OS Installation

  • NTTCom will install OS on Baremetal server according to subscribe request. Network interface will be configured two interface which connected to DataPlane and StoragePlane as bonding.

  • NTTCom will set OS for launching HANA library and HANA installation suite.

   

Create Storage / Volume and mount

  • NTTCom will create volumes on FileStorage accorrding to subscribe request.

  • NTTCom will mount volume over the Operating System accordingly with the request submitted by Customers.

   

Launch to install HANA

  • NTT Com will install SAP HANA according to application.

   

Check TDI appliance deployed suite

  • NTTCom will ensure the deployment of TDI suite by utilizing HWCCT offered by SAP.

Terminate SAP HANA infrastructure

Subscription

Select Tenant, Baremetal Server, Filestorage

  • Customers can terminate SAPHANA by specifying tenant name, access information, Baremetal server, FileStorage deployed as SAPHANA infrastructure via CustomerPortal.

Manage SAP HANA infrastructure

Confirm SAP HANA infrastructure information

 
  • Customers can check detail information of Baremetal Server and Filestorage deployed within SAP HANA infrastructure.

Provision of the OS license

Provision of the license of the Red Hat Enterprise Linux(From here RHEL) for SAP HANA

 
  • A CCP contract (certified cloud provider contract) is provided for the RHEL for SAP HANA license.

  • Customers will be able to use the trouble support, the OS vendor’s software for bug fixing and security patches.

Baremetal Server and Filestorage are certified hardware by SAP as appliance suite for deploying SAP HANA infrastructure.

Description of Each Function

Create SAP HANA infrastructure

NTTCom will create Baremetal Server, FileStorage, OS and SAPHANA installation in proper procedure according to subscribe request.
  • Following are Operating System and SAP HANA Versions appropriately provisioned for Customers:

Product   version

Notes

OS Red Hat Enterprise Linux for SAP HANA 6.7

Red Hat Enterprise Linux (RHEL hereinafter) will be provided with early version Ver.6.7.

SAP HANA SAP HANA Platform Edition 1.0
SPS11
SPS12
SAP HANA will be provided with early version SPS11 (i.e., 1.00.110.00).
SAP HANA will be provided with early version SPS12 (i.e., 1.00.120.00).

  • SAP HANA Modules for Installation are as follows:

SAP HANA Modules

Description

Subjects of Installation

version  
HANA Server HANA Database Engine Y
SPS11
SPS12
1.00.110.00.1447753075
1.00.120.00.1462275491
HANA Client

For HANA: JDBC、ODBC Driver and HDBSQL

Y
SPS11
SPS12
1.00.110.00.1447753075
1.00.120.024.1461933179

  • OS, HANA Settings

The description that have (), will be subject to the appropriate version and plan.

Functions

 

Installation / Setting Items

Set value

OS Installed Packages ※1 OS package groups Base Base
  RHUI packages
rhui-client
gpg-key
rh06-rhui-client01-sap-hana-01-<Region>-ecl-ntt-com-1.0-1.noarch.rpm
RPM-GPG-KEY-rhui-custom
  HANA packages
compat-sap-c++
tuned-profiles-sap-hana
compat-sap-c++-4.8.2-16.el6.x86_64.rpm
tuned-profiles-sap-hana-0.2.19-15.el6.noarch.rpm(SPS11)
tuned-profiles-sap-hana-0.2.19-16.el6.noarch.rpm(SPS12)
  File System xfsprogs xfsprogs-3.1.1-16.el6.x86_64.rpm
  SAP Java Virtual Machine sapjvm sapjvm-8.1.009-linux-x64.rpm
  Tuned Profile tuned
tuned-0.2.19-15.el6.noarch.rpm(SPS11)
tuned-0.2.19-16.el6.noarch.rpm(SPS12)
  Dependencies for SAP HANA ※2
cairo
compat-libstdc++-33
expect
gcc
glib
glibc
glibc-devel
glib-devel
graphviz
gtk2
iptraf
kernel-devel
krb5-libs.i686
krb5-workstation
libcanberra-gtk2
libicu
libnuma-devel
libssh2
libstdc++-devel
libtool-ltdl
lm_sensors
nfs-utils
ntp
numactl
openssl
openssl098e
PackageKit-gtk-module
redhat-rpm-config
rpm-build
rsyslog
sudo
tcsh
xauth
xulrunner
zlib-devel
compat-openldap
krb5
cairo-1.8.8-6.el6_6.x86_64.rpm
compat-libstdc++-33-3.2.3-69.el6.x86_64.rpm
expect-5.44.1.15-5.el6_4.x86_64.rpm
gcc-4.4.7-16.el6.x86_64.rpm
glib2-2.28.8-4.el6.x86_64.rpm
glibc-2.12-1.166.el6.x86_64.rpm
glibc-devel-2.12-1.166.el6.x86_64.rpm
glib2-devel-2.28.8-4.el6.x86_64.rpm
graphviz-2.26.0-10.el6.x86_64.rpm
gtk2-2.24.23-6.el6.x86_64.rpm
iptraf-3.0.1-14.el6.x86_64.rpm
kernel-devel-2.6.32-573.el6.x86_64.rpm
krb5-libs-1.10.3-42.el6.i686.rpm
krb5-workstation-1.10.3-42.el6.x86_64.rpm
libcanberra-gtk2-0.22-1.el6.x86_64.rpm
libicu-4.2.1-12.el6.x86_64.rpm
numactl-devel-2.0.9-2.el6.x86_64.rpm
libssh2-1.4.2-1.el6_6.1.x86_64
libstdc++-devel-4.4.7-16.el6.x86_64.rpm
libtool-ltdl-2.2.6-15.5.el6.x86_64.rpm
lm_sensors-3.1.1-17.el6.x86_64.rpm
nfs-utils-1.2.3-64.el6.x86_64.rpm
ntp-4.2.6p5-5.el6.x86_64
numactl-devel-2.0.9-2.el6.x86_64.rpm
openssl-1.0.1e-42.el6.x86_64
openssl098e-0.9.8e-18.el6_5.2.x86_64.rpm
PackageKit-gtk-module-0.5.8-25.el6.x86_64.rpm
redhat-rpm-config-9.0.3-44.el6.noarch.rpm
rpm-build-4.8.0-47.el6.x86_64.rpm
rsyslog-5.8.10-10.el6_6.x86_64
sudo-1.8.6p3-19.el6.x86_64
tcsh-6.17-25.el6_6.x86_64
xorg-x11-xauth-1.0.2-7.1.el6.x86_64.rpm
xulrunner-17.0.10-1.el6_4.x86_64.rpm
zlib-devel-1.2.3-29.el6.x86_64.rpm
compat-openldap-2.3.43-2.el6.x86_64.rpm(SPS12)
krb5-server-1.10.3-42.el6.x86_64.rpm(SPS12)
OS Started Services NTPD /etc/rc*.d ntpd
  NTPDATE /etc/rc*.d ntpdate
OS Stopped Services SE Linux /etc/sysconfig/selinux SELINUX=disabled
  Kdump /etc/rc*.d kdump
  ABRT(Bug report) /etc/rc*.d
abrtd
abrt-ccpp
OS Kernel parametar setting HANA /etc/sysctl.conf
kernel.shmmax=1073741824
kernel.shmall=1073741824(GP2)
kernel.shmall=8589934592(GP3)
  NFS /etc/sysctl.conf
net.ipv4.tcp_slow_start_after_idle=0
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.core.rmem_default = 16777216
net.core.wmem_default = 16777216
net.core.optmem_max = 16777216
net.core.netdev_max_backlog = 300000
net.ipv4.tcp_rmem = 65536 16777216 16777216
net.ipv4.tcp_wmem = 65536 16777216 16777216
net.ipv4.tcp_no_metrics_save = 1
net.ipv4.tcp_moderate_rcvbuf = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_sack = 1
OS Setting Timezone /etc/sysconfig/clock ZONE=”Etc/UTC”
  Language /etc/sysconfig/i18n LANG=”en_US.UTF-8”
  Keyboard /etc/sysconfig/keyboard
KEYTABLE=”us”
MODEL=”pc105+inet”
LAYOUT”us”
  SSH /etc/ssh/sshd_config
Port 22
Protocol 2
PubkeyAuthentication yes
HostbasedAuthentication no
PasswordAuthentication yes
  Network Setting (Data plane I/F) /etc/sysconfig/network-scripts/ifcfg-[Data Plane I/F]
ONBOOT=yes
BOOTPROTO=static
MASTER=bond0
MASTER=bond0
    /etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
BONDING_OPTS=”mode=1 primary=<Data Plane I/F (eth number)> miimon=100”
    /etc/sysconfig/network-scripts/ifcfg-bond0.<vlan id>
DEVICE=bond0.<vlan id>
BOOTPROTO=static
IPADDR=<IP Address>
PREFIX=<Prefix>
ONBOOT=yes
VLAN=yes
  Network Setting (Storage plane I/F) /etc/sysconfig/network-scripts/ifcfg-[Storage Plane I/F]
ONBOOT=yes
BOOTPROTO=static
MASTER=bond1
MASTER=bond0
MTU=9000
    /etc/sysconfig/network-scripts/ifcfg-bond1
DEVICE=bond1
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
BONDING_OPTS=”mode=1 primary=<Storage Plane I/F (eth number)> miimon=100”
MTU=9000
    /etc/sysconfig/network-scripts/ifcfg-bond1.<vlan id>
DEVICE=bond1.<vlan id>
BOOTPROTO=static
IPADDR=<IP Address>
PREFIX=<Prefix>
ONBOOT=yes
VLAN=yes
MTU=9000
  Gateway /etc/sysconfig/network
GATEWAY=<Gateway IP Address>
Configured only when customers specify at subscription
  Static Route /etc/sysconfig/network-scripts/route-<Interface Name>
<network address> via <gateway address>
Configured only when customers specify at subscription
  NTP /etc/ntp.conf server 169.254.127.1 iburst
  DNS /etc/resolve.conf
nameserver <DNS IP Address>
Configured only when customers specify at subscription
  RHUI(CDS) FQDN /etc/yum.repos.d/rhui-load-balancers
<CDS-FQDN-#1>
<CDS-FQDN-#2>
    /etc/hosts
169.254.127.18 <CDS-FQDN-#1>
169.254.127.19 <CDS-FQDN-#2>
  Hosts /etc/hosts
<IP Address> <hostname>
Configured IPaddress(Data 1) and hostname specified by Customer.
OS Setting (for SAP HANA) Symlink /usr/lib64/libss
/usr/lib64/libssl.so.0.9.8 -> /usr/lib64/libssl.so.0.9.8e
/usr/lib64/libssl.so.1.0.1 -> /usr/lib64/libssl.so.1.0.1e
  Symlink /usr/lib64/libcrypto
/usr/lib64/libcrypto.so.0.9.8 -> /usr/lib64/libcrypto.so.0.9.8e
/usr/lib64/libcrypto.so.1.0.1 -> /usr/lib64/libcrypto.so.1.0.1e
  SAP Tuned Profile /etc/tune-profiles/sap-hana tuned-adm profile sap-hana
  pam_limits /etc/security/limits.d/99-sapsys.conf @sapsys soft nproc unlimited
    /etc/security/limits.conf
* soft core 0
* hard core 0
  C-State /boot/efi/EFI/redhat/grub.conf
intel_idle.max_cstate=0
processor.max_cstate=1
  transparent_hugepage /boot/efi/EFI/redhat/grub.conf transparent_hugepage=never
  TCP Setting /etc/modprobe.d/sunrpc-local.conf options sunrpc tcp_max_slot_table_entries=128
    /etc/rc.local
ethtool -K [Storage Plain ethernet I/F] lro off gro off
ethtool -K [Storage Plain Bonding I/F] lro off gro off
  NFSv3 Mount Option /etc/fstab
・/hana/data、/hana/log
rw,bg,vers=3,hard,timeo=600,rsize=65536,wsize=65536,intr,actimeo=0,noatime,nolock
・/hana/shared
rw,bg,vers=3,hard,timeo=600,rsize=65536,wsize=65536,intr,noatime,nolock
  NTPDATE /etc/ntp/step-tickers 169.254.127.1
SAP HANA Setting HDB Parameter hdbparam
max_parallel_io_requests: 128
async_read_submit: on
async_write_submit_active: on
async_write_submit_blocks: all

Image Save

RHEL6.7 rhel-server-6.7-x86_64-dvd.iso /root/images/
※1 Package of dependent packages are also installed.
※2 For the Extra Packages for Enterprise Linux (EPEL), it has been described as a dependent package of SAP HANA to the document offered by SAP [Red Hat Enterprise Linux (RHEL) 6.x Configuration Guide for SAP HANA(SAP HANA Platform SPS 12)] for “iptraf-ng”will not be installed. Installation of EPEL is performed by the customers in their responsibility.
For more information please check the Red Hat’s official site: (https://access.redhat.com/solutions/3358)

  • SAP HANA Directory Deployment

Disk Type Directory Description
External Disk





/hana/data
└ <SID>
 └ mnt00001
  ├ hdb00001
  ├ hdb00002
  └ hdb00003
SAP HANA DATA area (specified by NTT Com)
<SID>(defined by the customer)

SAP HANA NameServer DATA area
SAP HANA IndexServer DATA area
SAP HANA XS Engine DATA area
External Disk





/hana/log
└ <SID>
 └ mnt00001
  ├ hdb00001
  ├ hdb00002
  └ hdb00003
SAP HANA LOG area (defined by NTT Com)
<SID>(defined by the customer)

SAP HANA NameServer LOG area
SAP HANA IndexServer LOG area
SAP HANA XS Engine LOG area
External Disk











/hana/shared
└ <SID>
 ├ exe
 ├ global
 ├ hdblcm
 ├ hdbclient
 ├ lm_structure
 ├ profile
 └ HDB<instance number>
  ├ backup
  ├ <host name>
  └ work
SAP HANA Installation area (defined by NTT Com)
<SID>(defined by the customer)

SAP HANA configuration files
SAP HANA SAP HANA LifeCycle Management tools
SAP HANA Client Installtaion(defined by this company)
SAP HANA Installation information
SAP HANA Start-up profile of an instance
<instance number>(defined by the customer)
SAP HANA default backup destination (recommended setting change)
<host name>(defined by the customer)
Local Disk





/usr/sap
├hostctrl
└ <SID>
 ├ SYS
 ├ home
 └ HDB<instance number>


<SID>(defined by the customer)

<sid>adm user’s home directory setting (Default fixed)
/hana/shared/HDB<instance number> for Symlink

Terminate SAP HANA infrastructure

NTTCom will delete Baremetal Server, FIleStorage, OS and SAPHANA deployed as SAPHANA infrastructure in proper procedure according to terminate request.

Manage SAP HANA infrastructure

Baremetal Server and FileStorage deployed as SAPHANA infrastructure can be managed via API and Customer Portal.

Provision of the OS license

Licensed (shown again)
Product   version

Notes

OS Red Hat Enterprise Linux for SAP HANA 6.7

Red Hat Enterprise Linux (RHEL hereinafter) will be provided with early version Ver.6.7.

※For the RHEL for SAP HANA that is provided in this menu, the customer will need to implement the activation of the license . For the activation of the license, a connect through a common function gateway is necessary to connect the baremetal server to the license authentication server that is available in NTT Com.
Provided Repository
  • In this menu, it is provided your own repository server. As initial settings, the installation of the client’s certificate (rpm, GPG key) and the specification of the FQDN of RHUI (CDS) server for the host.

  • Software maintenance(bug fixes and security patches) provided by RedHat through yum (Linux-based distribution package management system) is provided. Execution of yum must be carried out by the customer himself.

  • Repository requires the following 7, in order to provide the RHEL for SAP HANA ver6.7. Channel is a package that can be provided from Red Hat, in the CCP license range, “Base”, “Optional”, “RH Common”, and only for custom channel for SAP HANA. Only for type “RPM”, “Debug”.

Repository Name

Red Hat Enterprise Linux 6 Server from RHUI (RPMs) (6Server-x86_64)
Red Hat Enterprise Linux 6 Server from RHUI - Optional (Debug RPMs)(6Server-x86_64)
Red Hat Enterprise Linux 6 Server from RHUI - Optional (RPMs)(6Server-x86_64)
Red Hat Enterprise Linux 6 Server from RHUI - RH Common (Debug RPMs)(6Server-x86_64)
Red Hat Enterprise Linux 6 Server from RHUI - RH Common (RPMs)(6Server-x86_64)
Red Hat Enterprise Linux 6 Server from RHUI (Debug RPMs) (6Server-x86_64)
RHEL for SAP HANA (for RHEL 6 Server) from RHUI (RPMs)
Major version support
Major version support is as following:

OS Version

Start Support

End of Support

6.7 2015/7/22 2020/11/30
※About features and information that RHEL OS itself provides, please refer to the Web site:

https://www.redhat.com/ja/technologies/linux-platforms/enterprise-linux


9.1.1.3. Menu

Menu List

  • SAP HANA menu

Menu

 

Plan

Detail

SAP HANA SAP HANA Deployed TDI with Red Hat Enterprise Linux for SAP HANA
General Purpose 2
General Purpose 3
NTTCom will deploy Baremetal Server, FileStorage and install OS and SAPHANA according to subscribe request, then operate TDI configuration check.
Red Hat Enterprise Linux for SAP HANA will be provisioned at Service Provider License.

  • Concurrent Subscription Menu

Menu

Plan

 

Detail

Baremetal Server

Standard Plan
General Purpose 2
General Purpose 3
RAM 256GB
RAM 512GB

Filestorage (Premium)

400MBps Capped
256GB or 512GB
Use: data volume
Mount point: /hana/data
The plan General Purpose 3 will use 512GB.
  250MBps Capped 256GB or 512GB
Use: log volume
Mount point: /hana/log
  100MBps Capped 256GB or 512GB
Use: shared volume
Mount point: /hana/shared
The plan General Purpose 3 will use 512GB.

Types And Methods of Subscription

Integrated additions / deletions will be available for Baremetal Server, Filestorage and OS upon request submitted by the Customers via CustomerPortal.

Subscription Types

Subscription Methods

Estimated Time of Delivery

Add (or Create anew)

Customers can apply for addition via customer portal.

5 business days after NTTCom verify that Order Sheet has been filled properly.
NTTCom will make a remand if there is any incompleteness in the application contents.
Customers should reapply after correcting inadequacy of application.

Cancellation of contract

Customers can apply cancellation via customer portal.

Immediate


Special Notice at Subscription

Customers are required to the following preliminary work at placing additional subscriptions.
  • Customers are advised to create Logical Network connective to Baremetal Server and Filestorage.

Total of two (2) Logical Networks will be required to be created: One (1) for Data Plane; one (1) for Storage Plane.

9.1.1.4. Terms And Conditions

Conditions of the Use in Combination with Other Menus

Menu

Sub - Menu

Contract

Terms And Conditions

Network

Logical Network

Required

Customers are required to create Logical Networks preliminarily before adding subscription(s).

Network

Common Function Gateway

Required

A common function gateway is needed in order to implement the OS license authentication. In addition, the OS license of RHEL is in a authenticated condition, so if you removed the common function gateway, the repository server will be no longer available.

Storage

Block Storage (Provisioned I/O Performance)

Recommended

For the area of Backup, we recommend to use any of the other menu such as the block storage, etc.

Server

Virtual server (Data Volume)

Recommended

For the area of Backup, we recommend to use any of the other menu such as a virtual server of the data volume.

Operations

GMOne for SAP HANA

Recommended

For the OS, SAP HANA operation monitoring, it is recommended the use of GMOne for SAP HANA.


Minimum Use Period

This menu does not set a minimum use period.

Special Notice for The Customers Prior to the Use of This Menu

Using this menu, customers can use configuration and functions as follows:

SAP HANA Deployment Functions

 

Feasibility for Deployment

Notes

HA / HANA Scale-Out

VMHA N

VM HA is not available for this menu is not accommodated with virtual infrastructure.

  SAP HANA Host Auto-Failover (Scale out) N

SAP HANA Host Automatic fail-over (scale-out) is not available due to SAP regulations.

  HANA System Replication Y

HANA System Replication is available for this menu to deploy by subscribing this menu multiply.

Scale-Up

Server (CPU、Memory)

Y

Scaling up General Purpose 2 to General Purpose 3 is available.

 

Storage

N

Scaling up Filestorage Volume is not available.

DR VM Site Recovery Manager N

Deploying VM Site Recovery Manager is not really available as this menu does not accommodate to virtual infrastructure.

  HANA System Replication N

Deploying DR sites through HANA System Replication is scheduled to be available with the multiplying points of deployments.

  Storage Replication N

Deploying DR sites through Storage Replication is not available.

 

Backup (remote storage)

Y

DR sites’ deployment utilizing Backup (remote storage) is available with Customers if they can subscribe other points.

Backup
Backup Solution
(OS)

Dump commands

Y

OS Backup through Dump Command is possible for Customers to deploy.

  Backup Software Y

OS Backup through Backup Software is possible for Customers to deploy if they prepare their optional backup software.

  VM Snapshot N

OS Backup through VM Snapshot upload is not available as this menu does not accommodate to virtual infrastructure.

Backup
Backup Solution
(DB領域)
HANA Studio Y

Database Backup through HANA Studio is available for Customers to deploy.

  Backint+BackupSoftware Y

Database Backup through Backint + Backup Software can be accommodated to deploy if Customers can prepare optional backup software and backup server and destination storage and such. However, Customers are advised that some backup software cannot be accommodated depending upon the systematic procedures of the third party software.

  StorageBackup(snapshot/Mirror) N

Database Backup through Storage Backup (Snapshot / Mirror) is not available.

Infra-Intensive
(Multitenancy)
MCOD Y

MCOD (i.e., Multiple Components One Database) is available for Customers to deploy if Customers are willing to create the schema after specifying their Database Mode in single container when subscribing.

  MCOS Y

MCOS (i.e., Multiple Components One System) is available for Customers to deploy if Customers are willing to create the database after specifying their Database Mode in single container when subscribing.

  MDC Y

MDC (i.e., Multitenant Database Container) is available for Customers if Customers are willing to create Tenant Database after specifying Database Mode in Multiple Containers.

 

Virtual Multi-Tenant (vHANA)

N

Virtual Multitenant (vHANA) is not available for this menu does not accommodate to virtual infrastructure.


Restricted Items

Following are itemized as restrictions specified in this menu:
  • SAP HANA infrastructure deployed in this menu is ensured to satisfy SAP-regulated TDI deployment standard at the time of initial setup.
  • After Customers start utilizing the infrastructure, logical network, filestorage and such appliance (equipments for SAP HANA infrastructure) is facilitated shared publicly. Therefore, efficiency depends upon the capacities of the use of each appliance.
    For example, in-memory database specifications require extraordinarily storage access at HANA launch / HANA stop. If multiple HANA infrastructures are either launched or stopped concurrently, such process might take extraordinary length of time.
  • OS and SAP HANA settings and modification of such deployed in this menu will depend thoroughly upon the Customers’ decision and plants. NTTCom thereby does not assume any responsibilities when the menu has been modified by the Customers’ decisions.
  • RHEL6.7 that is provided in this menu, is forbidden to be used in other than the SAP HANA platform that is configured in this menu. Also, please use it only to start in rescue mode.
  • Restrictions on OS licenses provided in this menu are as follows.
    Customers are prohibited from utilize RHUI (CDS) server for anything other than this menu.
    The delivery of the OS between Baremetal server and the virtual server is prohibited.
    NTT Com does not support the OS version that Red Hat support is expired. And NTT Com does not extend such expiration dates.
    When Red Hat announces the end of support, or if any of Server/Solution Package is going to be end its support, NTT Com will announce the notification on end of support to Customers in advance.
    In writing or any other means, the information needed for the installation such as activation key, subscription number, etc can not be disclosed directly to the customer.
    Customers are prohibited that they activate KVM on their Baremetal Server, and create RHEL virtual machine on it.
  • Baremetal Server and Filestorage deployed in this menu need to be deleted by termination request in this menu.
  • In case the Customers proceeded to delete appliance or terminate the menu, Red Hat Enterprise Linux for SAP HANA will continue to bill Customers as the billing continues.
    Customers are also advised that Red Hat Enterprise Linux for SAP HANA refund is not really available until the request is appropriately made by the Customers in such duration.
  • In the case the customer uses the General Purpose 3 Plan, /Hana/data, /hana /shared file storage premium will use 512GB.

9.1.1.5. Pricing

Initial Fee

There is no initial fee required in this menu.

Monthly Charges

Menu

 

Plan

RHEL Version

Billing Structures

Billed Items

SAP HANA SAP HANA Deployed TDI with Red Hat Enterprise Linux for SAP HANA
General Purpose 2
General Purpose 3
6.7

Monthly Fixed Billing

Every unit of Baremetal Server utilized more than once a month

  • Baremetal Server and Filestorage deployed in this menu will be calculated for usage billing.

  • Usage billing appropriates the billing to be adjusted so that the start-up of the menu is duly coincided with the exact date that the menu is officially put through(UTC 0:00).

  • The adjusting of usage billing will be terminated when Baremetal server, FileStorage and OS are deleted.

  • Utilizing this menu will allow the Customers to utilize their SAP HANA Usage Discount.


9.1.1.6. Qualities of Provisioned Menu

Support Coverage

Customers are required to read the following preliminary operations and cautions required for the Customers to implement before the menu officially starts:
 

Actions to be taken by Customers

Special Notes

Sizing/Design
  • The configuration information specified at subscription need to be decided on Customers’ side.

Procurement
  • SAP HANA license is required to be prepared by Customers.

  • Customers are advised Red Hat Enterprise Linux for SAP HANA License is provided within the range of this menu.

  • Customers are advised also SAP HANA Software will be provided within the range of this menu.

Installation/Configuration
  • Customers are required to deploy logical network within the on-premises tenants preliminarily.

  • Customers are required to create SAP HANA schema and tables and such.

  • Customers are advised to apply permanent Licensing Key within the effective dates.

  • Customers are required to install HANA Studio and such appliance software.

  • Customers are required to deploy System Replication and HA functions.

  • RHEL licensing authentication is to be implemented by the Customers themselves based upon the specifications made by NTTCom.

  • NTTCom will deploy SAPHANA infrastructure on tenant and logical network on specified by customer at suscription request.

  • The user password of OS and SAPHANA will be configured according to subscription request.

  • Database will be at the initial installation status. In case Customers prefer MDC Deployment, User Database will not be installed.

  • SAP Hana license at the start of Customers’ use will be provided as temporary license key.

  • Customers are notified that deploying SAP HANA infrastructure by installing SAP application server is not supported by the coverage specified by NTT Com.

Monitoring
  • Customers are recommended that concurrently utilizing GMOne for operation monitoring of SAP HANA OS、SAP HANA infrastructure.

  • Customers are advised that Baremetal Server and Filestorage deploying SAP HANA infrastructure provides HW Operations Monitoring Service which accommodates to each menu.

Maintenance / Operation

  • Customers are requested that they make any inquiry about SAP HANA Software at SAP support contact.

  • Customers are advised that they assume thorough responsibilities of OS and Database patch-up, updates and backups.

  • Customers are advised that they assume thorough responsibilities in isolating whatever the issue may be when there is any fail-over issues or troubleshooting inquiries or reports they would like to make in terms of application, middleware, cloud and such appliance units which are not really provided by NTT Com.

  • Customers are notified that at the time of repairs of their hardware when there is such time as repair is needed to take place, NTT Com will operate the repairs accordingly as required, then the Customers are required to restore database or other necessary actions depending upon what they are required to do.

  • Customers are advised that inquiries concerning Baremetal Server, Filestorage and OS deploying SAP HANA infrastructure can be made at Enterprise Cloud Support Center and that they are appropriately provided with the support that is corresponded with the service that they are accommodated with.

  • Customers are recommended that backup storage can be deployed with the other storage menus (such as Block Storage with I/O Performance).

  • SAP HANA infrastructure is combined in deployment with Baremetal Server and Filestorage. For any work or repairs concerned to the respective menus, Customers are recommended that they check out each menu’s repair notice.


Quality of Operation

  • Support is available for this menu respectively with SAP HANA infrastructure deployed with Baremetal Server, Filestorage and OS and their initial settings, initial server log-in and OS licensing certification.

  • NTTCom will not assume the role in giving support (covering the actions such as investigating causes, troubleshooting support or advising how to eliminate such reported fail-overs or troubles in terms of installation, setups, basic or minimal functions and such) to any issues arising or being reported with Customers’ licensing products.

  • When you use the OS license, customers will be able to use the functions of the “software access”, “software maintenance” of the Red Hat Enterprise Linux software subscription. For access method of this features, please follow NTT Com’s instructions.

  • Operations in details of appliance such as Baremetal Server and Filestorage deployed within SAP HANA infrastructure will thoroughly corresponds to each menu.


SLA

SLA as for Baremetal Server and Filestorage in terms of deploying SAP HANA infrastructure will correspond thoroughly to the respective menus.