Hitachi Storage Adapter for the SAP HANA Cockpit · 12 Hardware and Software Requirements Hitachi Storage Adapter for the SAP HANA Cockpit v01.1.0 User’s Guide Supported Hardware

MK-92ADPTR111-01

Hitachi Storage Adapter for the SAP HANA Cockpit

User’s Guide

v01.1.0

Hardware and Software Requirements

Contents

Getting Help

FASTFIND LINKS

©2016 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means,

electronic or mechanical, including copying and recording, or stored in a database or retrieval

system for commercial purposes without the express written permission of Hitachi, Ltd., or Hitachi

Data Systems Corporation (collectively “Hitachi”). Licensee may make copies of the Materials

provided that any such copy is: (i) created as an essential step in utilization of the Software as

licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not make

any other copies of the Materials. “Materials” mean text, data, photographs, graphics, audio, video

and documents.

Hitachi reserves the right to make changes to this Material at any time without notice and assumes

no responsibility for its use. The Materials contain the most current information available at the time

of publication.

Some of the features described in the Materials might not be currently available. Refer to the most

recent product announcement for information about feature and product availability, or contact

Hitachi Data Systems Corporation at https://portal.hds.com.

Notice: Hitachi products and services can be ordered only under the terms and conditions of the

applicable Hitachi agreements. The use of Hitachi products is governed by the terms of your

agreements with Hitachi Data Systems Corporation.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.

AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON,

FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli,

z/OS, z9, z10, z13, z/VM, and z/VSE are registered trademarks or trademarks of International

Business Machines Corporation.

Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo,

Microsoft, the Microsoft Corporate Logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight,

SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo,

Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows

Vista are registered trademarks or trademarks of Microsoft Corporation. Microsoft product screen

shots are reprinted with permission from Microsoft Corporation.

All other trademarks, service marks, and company names in this document or website are properties

of their respective owners.

https://portal.hds.com/

Contents 3

Hitachi Storage Adapter for the SAP HANA Cockpit v01.1.0 User’s Guide

Contents

Preface ............................................................................ 7

Intended Audience .................................................................. 8

Related Document .................................................................. 8

Release Notes ........................................................................ 8

Document Conventions ........................................................... 8

Getting Help ........................................................................ 10

Comments ........................................................................... 10

1 Hardware and Software Requirements................................ 11

Supported Hardware and Software ......................................... 12

Hardware Requirements for Adapter Management Server ........ 12

Software Requirements ....................................................... 12

Operating Systems ............................................................... 12

Adapter Management Server Operating Systems .................... 12

HANA Database Operating Systems ...................................... 12

HANA Volumes ..................................................................... 13

Storage Models .................................................................... 13

Replication Software ............................................................. 13

Maximum Storage Consistency Groups .................................. 14

Host Interface ...................................................................... 14

Volume Type ........................................................................ 14

4 Contents


2 Architecture ................................................................... 15

3 Installation .................................................................... 17

Required Pre-installation on Management Server ..................... 18

Hitachi Command Control Interface (CCI) .............................. 18

Auto_cmddev.py ................................................................ 21

Installing the SAP HANA Windows Client ............................... 22

Java ................................................................................. 23

Distribution Package ............................................................. 23

Installing and Uninstalling ..................................................... 23

Installation Overview .......................................................... 23

Installation Procedure ......................................................... 23

Uninstallation .................................................................... 36

Backing Up the Adapter Configuration Repository ..................... 37

4 Operations ..................................................................... 39

Overview of Features ............................................................ 40

New Features and Important Enhancements .......................... 42

Launching the UI for Hitachi Adapter for SAP HANA Cockpit ....... 43

Registering a HANA Instance ................................................. 44

Input Parameters ............................................................... 45

Registering a HANA Host ....................................................... 46


Registering Hitachi Storage ................................................... 48


Creating a HANA Storage Snapshot with Hitachi Thin Image ...... 49

Prerequisites ..................................................................... 49


Procedure .......................................................................... 50

Verifying HANA Storage Snapshot from HANA Studio ................ 53

Contents 5


Recovering a HANA Database from a HANA Storage Snapshot .... 54

Procedure .......................................................................... 54

Cloning HANA Systems Using Hitachi Thin Image ..................... 63

Prerequisites ...................................................................... 64

Procedure .......................................................................... 64


Cloning HANA Systems Using Hitachi ShadowImage ................. 68

Prerequisites ...................................................................... 69

Procedure .......................................................................... 69


Backing up HANA OS by Using HTI/ShadowImage .................... 73

Prerequisites ...................................................................... 73

Procedure .......................................................................... 74

Deleting Replication Pairs ...................................................... 76

Collecting Storage Data ......................................................... 77

Storage Data Collection Job and Cache .................................. 77

Configure the Time Interval for Scheduled Storage Data Collection Job............................................................................... 78

Storage Data Collection Force Update ................................... 78

5 Reporting ...................................................................... 79

Overview ............................................................................. 80

Filtering............................................................................. 80

Filter Context ..................................................................... 81

Device-Mapping Report ......................................................... 82

Hostgroup Report ................................................................. 84

LUN Performance Report ....................................................... 85

LUN Performance Detail Report ............................................ 86

LUN Performance History Chart ............................................ 86

Port Performance Report ....................................................... 87

6 Contents


Port Performance History Chart ............................................ 87

Replication Report ................................................................ 88

Storage Pool Report .............................................................. 90

Storage Snapshot History Report ........................................... 91

Storage Layout Graph ........................................................... 92

6 Logging, Troubleshooting, and Error Messages .................... 93

Logging ............................................................................... 94

Log Generation and Rotation ............................................... 94

Sample Log Output ............................................................. 95

Troubleshooting ..................................................................100

Changing the Session Timeout ............................................100

Cleaning the Cache When the Delivery Unit Fails to Import .....103

Turn on port 2022 on Windows firewall ................................103

Troubleshooting Diagnostic Steps ........................................109

Error Messages ...................................................................111

Preface 7


Preface

Intended Audience

Related Document

Release Notes

Document Conventions

Getting Help

Comments

8 Preface


Note Your use of the Hitachi Storage Adapter for the SAP HANA Cockpit and all other Hitachi Data Systems products is governed by the

terms of your agreements with Hitachi Data Systems.

Intended Audience

This document is intended for customers of the Hitachi Storage Adapter for the SAP HANA Cockpit: database administrators, storage administrators, and architects implementing backup, recovery, and cloning solutions for SAP HANA

databases. Ideally, readers understand the architecture, administration, and backup and recovery concepts of SAP HANA databases.

Related Document

Name Description

SAP HANA Administration Guide Describes the administrative tasks that SAP HANA system administrators perform regularly and on demand

Release Notes

You can find release notes on the documentation CD. Release notes contain requirements and more recent product information that this manual may not fully describe. Be sure to review the release notes before installation.

Document Conventions

This document uses the following typographic conventions:

Convention Description

Bold Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels Example: Click OK.

Italic Indicates a variable, which is a placeholder for actual text provided by the user or system

Example: copy source-file target-file

Note: Angled brackets (<>) also indicate variables.

screen/code Indicates text on the screen or that you enter Example: # pairdisplay -g oradb

https://help.sap.com/saphelp_hanaplatform/helpdata/en/33/0e5550b09d4f0f8b6cceb14a64cd22/content.htm?current_toc=/en/00/0ca1e3486640ef8b884cdf1a050fbb/plain.htm&show_children=true

Preface 9


Convention Description

<> angled brackets

Indicates a variable, which is a placeholder for actual text provided by the user or system

Example: # pairdisplay -g <group>

Note: Italic font also indicates variables.

[ ] square brackets

Indicates optional values

Example: [a | b] indicates that you can select a, b, or nothing.

{ } braces Indicates required or expected values

Example: { a | b } indicates that you must select either a or b.

| vertical bar Indicates a choice between two or more options or arguments

Examples:

[a | b] indicates that you can select a, b, or nothing.

{ a | b } indicates that you must select either a or b.

This document uses the following icons to draw attention to information:

Icon Label Description

Note Calls attention to important and/or additional information

Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively

Caution Warns the user of adverse conditions and/or consequences (for example, disruptive operations)

WARNING Warns of severe conditions and/or consequences (for example, destructive operations)

10 Preface


Getting Help

The Hitachi Data Systems Support Center staff is available 24 hours a day,

seven days a week. Provisions for patches and fixes are restricted to normal business hours, 8 a.m. to 5 p.m. PST.

To reach us, visit the support website for current telephone numbers and other

contact information: http://www.hds.com/services/support/. If you purchased this product from an authorized HDS reseller, contact that reseller for support.

Before calling the Hitachi Data Systems Support Center, provide as much information about the problem as possible, including:

The circumstances surrounding the error or failure.

The exact content of any error messages displayed on the host systems.

Comments

Please send us your comments on this document: [email protected].

Include the document title, number, and revision, and refer to specific sections and paragraphs if possible. Thank you! (All comments become the property of

Hitachi Data Systems Corporation.)

http://www.hds.com/services/support/

mailto:[email protected]

Hardware and Software Requirements 11


Hardware and Software Requirements

Supported Hardware and Software

Operating Systems

HANA Volumes

Storage Models

Replication Software

Host Interface

Volume Type

12 Hardware and Software Requirements


Supported Hardware and Software

Note This release supports only the hardware and software listed in

this document.

Hardware Requirements for Adapter Management Server

Item Requirements

CPU Pentium 4 or more

Memory 2 gigabytes or more

Graphics 800x600, 16-bit color or more

HDD Capacity 10 gigabytes or more

Supported HBAs All the HBAs certified by Microsoft on the OS are supported.

Software Requirements

Hitachi Command Control Interface (CCI) 01-37-03

SAP HANA Windows Client 1.0.120 or above

Java Runtime Environment version 7 x64 edition or above installed on the same Windows host that is running the Hitachi Windows service

Note The version 7 x64 JRE edition or above is specifically required. The more common 32-bit JRE edition does not

work.

Operating Systems

Adapter Management Server Operating Systems

OS Version Supported

Windows 2012 R2 Yes

HANA Database Operating Systems

OS Version Supported

Redhat Enterprise Linux 6.6-HANA SPS11 Scale-up Dedicated Yes

Redhat Enterprise Linux 7.2-HANA SPS12 Scale-up Dedicated Yes

SuSE Linux 11.3-HANA SPS11 Scale-up Dedicated Yes

SuSE Linux 12.0-HANA SPS12 Scale-up Dedicated Yes

Hardware and Software Requirements 13


Note This release only supports scale-up and dedicated hardware. MDC, MCOD, Virtualized, and MCOS are not supported. Users can get more

information on SAP HANA system configuration types from this link: http://help.sap.com/saphelp_hanaplatform/helpdata/en/64/83b71787f2439c907bd99036559e72/content.htm?frameset=/en/df/16fa40b3dc4

ed3b86e575ad6d1198d/frameset.htm&current_toc=/en/aa/c4bed2390045f59dd8fdeab3ffafb3/plain.htm&node_id=9.

See the “Hitachi UCP for the HANA platform in a scale-up configuration”

document for information about HANA installation with Hitachi hardware.

HANA Volumes

Volume Name Volume Type Supported

OS LVM Yes

OS Plain LUN Yes

Data, Log, and Share LVM Yes

Data, Log, and Share Plain LUN No

Storage Models

Model Micro Version Supported

Hitachi Unified Storage VM 73-03-49-00/00 Yes

Virtual Storage Platform-G1000 80-05-00-00/00 Yes

Virtual Storage Platform-G1500 80-05-01-00/00 Yes

Virtual Storage Platform VSP Gx00 (G200/G400/G600/G800)

83-03-24-40/00 Yes

Virtual Storage Platform Gx00 Unified 83-03-20-40/00 Yes

VSP Fx00 83-03-01-40/00 Yes

Replication Software

Replication Software Supported

Hitachi ShadowImage Yes

Hitachi Thin Image Yes

http://help.sap.com/saphelp_hanaplatform/helpdata/en/64/83b71787f2439c907bd99036559e72/content.htm?frameset=/en/df/16fa40b3dc4ed3b86e575ad6d1198d/frameset.htm&current_toc=/en/aa/c4bed2390045f59dd8fdeab3ffafb3/plain.htm&node_id=9




14 Hardware and Software Requirements


Maximum Storage Consistency Groups

Copy Type CTG Range

Hitachi ShadowImage 0-127 (1, 2, 3)1

Hitachi Thin Image 0-2048 (VSP Gx00), 0-255 (HUS-VM)

Host Interface

Interface Supported

FC Yes

Volume Type

Volume Type Supported

HDP/HDT/HRT pools Yes

Parity Group Yes

*1: “CTG IDs are numbers between 0 and FF. CTG IDs 00 to 7F (or 0 to 127) are used for SI, SS, and HTI. CTG IDs 80 to FF (or 128 to 255) are used for HTI only.” (Ref: Hitachi Virtual Storage Platform G1000 Hitachi ShadowImage User Guide, MK-92RD8021)

*2: “CTG IDs are numbers between 0 and FF. CTG IDs 00 to 7F (or 0 to 127) are used for SI and HTI. CTG IDs 80 to FF (or 128 to 255) are used for HTI only.” (Ref: Hitachi ShadowImage® User Guide, MK-94HM8021)

*3: “You can use consistency group numbers 00 to 7F (or 0 to 127) commonly for SI and HTI. Consistency group numbers 80 to FF (or 128 to 255) are exclusively used for HTI.” (Ref: Hitachi Unified Storage VM Block Module Hitachi ShadowImage User Guide, MK-92HM7013)

*4: When creating Thin Image by using this adapter, each CTG is associated with one snapshot group.

Architecture 15


Architecture

The SAP HANA Cockpit is an SAP Fiori Launchpad site that provides you with a

single point of access to a range of web-based applications for the online administration of SAP HANA. You access the SAP HANA Cockpit through a web

browser. The Hitachi Storage Adapter for the SAP HANA Cockpit runs as a cockpit web application. This adapter provides storage configuration, registration, and

additional management functionality for storage management. Specifically, the adapter does the following:

Allows users to register and monitor Hitachi storage subsystems.

Allows users to create and manage HANA storage snapshots by using Hitachi Thin Image (HTI).

Allows users to create and manage replication by using ShadowImage and Hitachi Thin Image.

Generates the following reports:

• Device Mapping

• Host Group

• LUN Performance

• Port Performance

• Replication

• Storage Pool

• Storage Snapshot History

• Storage Layout Graph

16 Architecture


Installation 17


Installation

Required Pre-installation

Distribution Package

Installing and Uninstalling

Backing Up the Adapter Configuration Repository

18 Installation


Required Pre-installation on Management Server

# Item Configuration

1 Hitachi CCI Hitachi CCI must be installed and running on a Windows host to allow you to use this product.

2 SAP HANA Windows Client

The SAP HANA Windows client must be installed and running on a Windows host to allow you to access the HANA database. You can find this on the SAP website.

3 Java Runtime Environment

Java Runtime Environment version 7 x64 edition or above must be installed on the management server to

allow you to use this product.

Hitachi Command Control Interface (CCI)

Before using the adapter with enterprise storage arrays, install Hitachi

Command Control Interface (CCI), and then configure the software.

CCI performs in-band array management on behalf of the adapter workflows.

Note CCI commands run “in-band,” which refers to the method of transferring commands from the server to the command device by

sharing the same data path as the disk I/O. VSP arrays are exceptions and support virtual command devices by using an out-of-

band transfer method. See the sections on command execution by in-band and out-of-band methods in the CCI document for your storage system model.

CCI should exist on the same Windows host that is running the Hitachi Windows service.

CCI supports several scenarios, and its configuration can become complex.

These notes may help you to get started quickly, and they should yield a configuration sufficient for many of this product’s workflows. For in-depth CCI

configuration information, see CCI’s documentation.

To prepare for CCI use, follow the steps below.

1. Install CCI on the Windows host running this product’s Windows service.

2. Edit the Windows TCP/IP services file to define a CCI service associated with UDP port 1000. Add this single line to

C:\Windows\system32\drivers\etc\services.

horcm 1000/udp horcm

3. Choose (or create) an LDEV on the enterprise storage array to act as a command device.

Installation 19


4. Configure the LDEV to be a command device, as shown below.

5. Present the LDEV to the Windows host where the Hitachi Windows service is running.

6. Ask the Windows host to re-scan, and then ensure that the host sees the new LDEV.

7. Create a CCI configuration file named C:\Windows\horcm0.conf that

contains these two lines. Replace \\.\PHYSICALDRIVE1 with the drive

name that corresponds to the command device.

HORCM_CMD

\\.\PHYSICALDRIVE1

Note If it is difficult to determine which PHYSICALDRIVE device name corresponds to the command device LDEV, try this command in a Windows Command Prompt window:

C:\> wmic diskdrive list brief /format:list

8. Start a CCI process (instance). Supplying a zero to horcmstart asks CCI

to create an instance number of zero. The CCI instance number becomes an input to some workflows that this product includes.

C:\HORCM\etc.\horcmstart 0

20 Installation


9. If CCI fails to start, or to determine its status in detail, look at its log files in this folder.

C:\HORCM\log0\curlog\

This procedure is for adding command devices manually. The procedure

described in the next section is for adding command devices automatically.

Installation 21


Auto_cmddev.py

Auto_cmddev.py automatically creates a single command device on the physical machine on which it is being executed.

Auto_cmddev.py is installed when the SAP HANA adapter is installed on the

management server (for example, C:\Program Files\Hitachi\Hitachi HANA Management Service) under the autocreateCMD folder.

To see more information about the steps of this process, navigate to this directory and locate the readme, which contains examples of usage.

Auto_cmddev.py also prints out the current command devices that are mapped

out to the machine that the program is being run on.

The following screenshot shows one example of running auto_cmddev.py to

create a command device.

Example: PS C:\Python27> python.exe auto_cmddev.py --user csultana --ip 172.17.47.55 --port CL4-A -wwns "500008700053bdbc 50

0008700053bdbe"

22 Installation


Installing the SAP HANA Windows Client

Install the SAP HANA Windows Client to enable communication between the HANA management server and the HANA instance. Click the SAP HANA

Windows Client installer. Then select the installation path as it appears below.

Click Next to complete the installation of the SAP Windows client.

Installation 23


Java

Before using this product with Enterprise storage arrays, you must install Hitachi CCI and a specific Java Runtime Environment.

Java Runtime Environment

Install Java Runtime Environment version 7 x64 edition or above on the

management server.

Note

The x64 JRE edition or above is specifically required. The more common 32-bit JRE edition does not work.

Distribution Package

The distribution packages for the Hitachi Storage Adapter for the SAP HANA

Cockpit contain the following:

Hitachi-HANAServerAdapter-setup(01.1.0)-(x64)-01.exe

Installing and Uninstalling

Installation Overview

Installation includes the following items.

Installation Item Location

Hitachi HANA Management Service Windows management server

Delivery unit of Hitachi Storage for SAP HANA Cockpit adapter

Import the delivery unit to the SAP HANA Cockpit

Note

The installer installs the .NET 4.5 framework if this framework is not already installed.

Installation Procedure

1. Installing the HANA Management Service on the Windows

Management Server

On a supported Windows host, install the Hitachi Storage Adapter for the SAP HANA Cockpit by running this program:

24 Installation


Hitachi-HANAServerAdapter-setup(01.1.0)-(x64)-01.exe

The installer adds two main components:

The adapter (for example, located in C:\Program Files\Hitachi\Hitachi HANA Management Service\deliveryunit)

A Windows service named Hitachi HANA Management Service

First, install the Hitachi HANA Management Service by running the installer as

seen in the images beginning on the next page:

Installation 25


26 Installation


Installation 27


Then verify the installation by navigating to Control Panel->Programs and Features. If the program installed successfully, it appears in this list.

To verify that the service is running, navigate to Start->Run->mstsc, and then verify that the status of Hitachi HANA Management Service is Running.

2. Importing the delivery unit to the SAP HANA Cockpit

After you install Hitachi HANA Management Service on the Windows

management server, import the delivery unit to the SAP HANA Cockpit:

This operation requires the following roles for the on the Cockpit (client) side:

sap.hana.admin.roles::Administrator

sap.hana.uis.db::SITE_DESIGNER

sap.hana.xs.admin.roles::HTTPDestAdministrator

sap.hana.xs.lm.roles::Administrator

28 Installation


To import the delivery unit, follow these steps:

1. Log in to Cockpit.

2. Access SAP HANA Application Lifecycle Management->Manage Products and Delivery Units.

3. Click Delivery Units->Import.

4. Select the delivery unit file (HANA_ADAPTER_DU-hds.com.tgz) from

C:\Program Files\Hitachi\Hitachi HANA Management Service\deliveryunit on the HANA management server.

5. After you install the delivery unit, the screen below appears so that you can see the tile that represents the adapter.

Installation 29


3. Configuring the SAP HANA Cockpit

Next, configure the transport service on the SAP HANA Cockpit.

1. Log in to Cockpit->XS Artifact Administration.

2. On the XS Artifact Administration screen, type HitachiHanaService to

find the httpdest file as shown below.

3. Click Edit if you wish to modify the httpdest file by changing the IP

address and port of the Hitachi HANA Management service.

30 Installation


If the name of the target system is not “HIT” (default name), then it is not allowed to edit the http destination directly. In this case, extend the

http destination, and then edit by following the steps below:

1. Click Extend on the bottom right of the screen.

2. If this is the first time that you are installing the adapter, click New Package, and then provide the extension package and the extension

name. Otherwise, select an existing package. Then click Create Extension.

Installation 31


3. Click Edit on the bottom right of the screen that shows the new

extension of the HTTP destination.

32 Installation


4. Changing the Session Timeout

By default, the SAP HANA Cockpit only allows 10 minutes as the maximum

timeout value. Many storage-related operations need more than 10 minutes. If you need to increase the maximum timeout value, follow these steps:

1. From HANA Studio, select the HANA system.

2. From system view, choose Open Administration from the Configuration and Monitoring menu.

Installation 33


3. Click the Configuration tab, and then expand xsengine.ini.

4. On httpserver, find or create the max_request_runtime and

sessiontimeout parameters. Then change both parameters to a higher number of seconds, such as 1800 or more.

34 Installation


5. Modify the icm/server_port parameter in the webdispatcher.ini section by changing the value of “PROCTIMEOUT” to 1800 or more if necessary. If

you are using http to access the Cockpit, then you only need to change icm/server_port_0. If you are also using https, then you need to change

icm/server_port_1 as well.

Installation 35


36 Installation


Uninstallation

To uninstall the Windows service, follow these steps:

1. Go to Control Panel>Programs and Features, and then choose

Hitachi HANA Management Service.

2. Right-click, and then select Uninstall.

Installation 37


To uninstall the delivery unit, follow these steps:

1. Go to HANA Cockpit->SAP HANA Application Lifecycle

Management->Manage Products and Delivery Units.

2. Select HANA_Adapter_DU (hds.com), and then click Delete.

Backing Up the Adapter Configuration Repository

The adapter uses the SQlite database to store the history records of HANA storage snapshots, performance information, and scheduler

information. If the SQlite database crashes for any reason, then you can still find the records of the HANA storage snapshot from the HANA database. Backing up the SQLite database is optional. To back up the

SQLite database, follow these steps:

1. Stop the Hitachi HANA Management service.

2. Copy the “HANAStorageSnapshotHistoryDB.db” file from the installation directory to the backup location that you prefer.

3. Restart the Hitachi HANA Management service.

Operations 39


Operations

Overview of Features

Launching the UI for Hitachi Adapter for SAP HANA Cockpit

Registering a HANA Instance

Registering a HANA Host

Registering Hitachi Storage

Creating a HANA Storage Snapshot with Hitachi Thin Image

Verifying HANA Storage Snapshot from HANA Studio

Recovering a HANA Database from a HANA Storage Snapshot

Cloning HANA Systems Using Hitachi Thin Image

Cloning HANA Systems Using Hitachi ShadowImage

Backing up HANA OS by Using HTI/ShadowImage

Deleting Replication Pairs Collecting Storage Data

40 Operations


Overview of Features

Operations 41


To use this adapter, you must first register the HANA instance, the HANA host, and the storage. The following workflow shows the sequence of registration.

Start

Register HANA Instance by using HANA database user

credential

Register HANA Host by using Linux user credential that has

sudo privilege

Register Hitachi Storage that is used by the specified HANA

host

42 Operations


New Features and Important Enhancements

The following features have been added to this release of the Hitachi Storage Adapter for the SAP HANA.

You may now use auto_cmddev.py to create command devices

automatically.

After discovery of Hitachi storage subsystems, the following

operations can be performed using this adapter:

o Select floating device for storage snapshot

o Use the scheduler to create storage snapshots

o Use the scheduler to delete existing jobs

o Use the scheduler for task view (current tasks and task history)

o Perform offline operations such as resync, split, and revert

using a standalone UI

Real-time reports about the specified Hitachi storage subsystem. The

following reports are available in the Hitachi Storage Adapter for the

SAP HANA user interface.

o Host group report

o Storage pool report

o LUN performance chart

o Port performance chart

o Context filter for reports

o Storage layout graph

Operations 43


Launching the UI for Hitachi Adapter for SAP HANA Cockpit

Before you perform any operations, launch the user interface for the Hitachi Adapter for SAP HANA Cockpit by following these steps:

1. After you install the Hitachi Adapter for SAP HANA Cockpit, open the cockpit by navigating to the following link on the Windows management server:

http://172.17.37.142:8010/sap/hana/admin/cockpit (The IP address in this link is an example. Replace it with your own.)

2. Log in as a system user for SAP HANA instance.

3. Once you are logged in, the following screen appears.

http://172.17.37.142:8010/sap/hana/admin/cockpit

44 Operations


Registering a HANA Instance

HANA instance registration registers the provided HANA instance with a HANA

host on the inventory of the management web service. You can perform subsequent management operations by using the results of this registration feature. This operation requires a HANA database account with the following

roles:

sap.hana.admin.roles::Monitoring

sap.hana.backup.roles::Administrator

To register a HANA instance, follow these steps:

1. After you log in to the UI, click the + sign next to HANA Instances on the upper left of the UI.

Operations 45


2. Provide information for the parameters listed below, as shown in the following screenshot.

Input Parameters

Name Description

Master Host Name DNS name or IP of the master host

HANA Instance Number Instance number of this HANA system

HANA User Name User name of this HANA system

HANA Password Password of this HANA system

46 Operations


Registering a HANA Host

Note The host name must be the same as it is presented on the HANA

instance database.

After you register the HANA instance, you can register the hosts of the specified HANA instance. This feature registers the related HANA hosts on the inventory of the management web service.

You can perform subsequent management operations by using the result of this registration feature. Provide the SSH credential that has root privileges. The

adapter can then scan the host and find all the volumes of Logical Volume Management (LVM) on the HANA host.

To add a HANA host, click on the HANA instance that appears under “HANA Instances” on the left. Then click Register Host under Actions, as shown in

the following screenshot.

Operations 47


Enter the correct parameters in the window that appears, as shown in the following screenshot.

Input Parameters

Name Type Description

HANA Host Name

String DNS name or IP address of the master host. This must be the same as the name that is presented to the HANA database.

SSH User Name

String SSH user name of this HANA host. This user account must have sudo privilege by using SSH.

SSH Password

SecureString SSH password of this HANA host. This user account must have sudo privilege by using SSH.

48 Operations


Registering Hitachi Storage

After you register a specified HANA host, you can register the Hitachi storage

systems that the HANA host has used, assuming that each HANA host uses only one Hitachi storage system. This feature registers the related Hitachi storage on the inventory of the management web service.

You can perform subsequent storage management operations (that is, Hitachi Thin Image and ShadowImage) after you register the storage by using the

adapter. Provide the user credentials that provide access to the Hitachi storage. Also provide the IP address and HORCM instance number. The adapter scans

the Hitachi storage according to your input. See the screenshot below.

Input Parameters


Storage Serial Number

String Serial number of the Hitachi storage

Storage Location (IP) String IP of the Hitachi storage

Horcm Instance Number

Integer HORCM instance number for managing the Hitachi storage

Storage User Name String User name for accessing the Hitachi storage

Storage Password String Password for accessing the Hitachi storage

Operations 49


Creating a HANA Storage Snapshot with Hitachi Thin Image

This feature allows you to create a HANA storage snapshot by using Hitachi Thin Image. With this feature, you may either create the HANA storage

snapshot instantly or schedule a specified date/time for automation of the HANA storage snapshot. In addition, you also may choose to use “HTI” or

“floating device” when you create the HANA storage snapshot.

Prerequisites

Before using this feature, create a Hitachi Thin Image (HTI) pool on your

Hitachi storage system.

A HANA storage snapshot is an option of a database backup. It includes all the data that is required to recover the database to a consistent state. A HANA

storage snapshot captures the content of the SAP HANA data area at a particular point in time.

Before you create any HANA storage snapshot, it is strongly recommended that you create a full file system backup of your HANA instance first. SAP does not provide an integrity check for an HANA storage snapshot. Instead, SAP

recommends that you combine storage snapshots with traditional data backups.

Note SAP does not support storage snapshots with SAP HANA if the data resides in multitenant database containers. Use this feature only with

SAP HANA single-database containers. See Create a Storage Snapshot (SAP HANA Studio) for details.

Note Hitachi Thin Image has two options: “HTI” and “floating device”. This adapter supports both of them for creating a HANA storage snapshot. They have the following differences.

1. “Floating device” does not have a V-VOL ID or an LUN name.

Therefore, it cannot be mapped to any host group.

2. Due to the reduction of internal resources of storage (for example, V-VOL ID), the speed of “floating device” is faster.

3. “Floating device” is not available on HUS-VM. It is only available

on VSP G/Fx00 and G/F1000 series.

Input Parameters

Name Description

HTI Pool HTI pool for the storage snapshot

LUNs Selected LUNs for the storage snapshot. Initially, all LUNs in the data volume are selected by default.

https://help.sap.com/saphelp_hanaplatform/helpdata/en/a0/3f8f08501e44d89115db3c5aa08e3f/content.htm?frameset=/en/c5/1a3983bb571014afa0c67026e44ca0/frameset.htm&current_toc=/en/00/0ca1e3486640ef8b884cdf1a050fbb/plain.htm&node_id=591)

https://help.sap.com/saphelp_hanaplatform/helpdata/en/a0/3f8f08501e44d89115db3c5aa08e3f/content.htm?frameset=/en/c5/1a3983bb571014afa0c67026e44ca0/frameset.htm&current_toc=/en/00/0ca1e3486640ef8b884cdf1a050fbb/plain.htm&node_id=591)

50 Operations


Procedure Note This operation may take a while. However, HANA Cockpit by default

allows 300 seconds as the maximum session timeout period. If you

receive a timeout error, change the session timeout by following the steps under Changing the Session Timeout.

1. Select the type of the task. You may either select Execute Now to

create the HANA storage snapshot instantly or select Recurring to create a schedule that automatically and recurrently creates the HANA storage snapshot according to the schedule. If you select to create it

instantly, then go directly to step 3.

2. Define the recurring schedule. Provide a unique schedule name. Also,

select the recurring time of the schedule. You can select a daily, weekly, or monthly schedule and define the start time. The time that you set is relative to the time zone that is set on the adapter management server

that runs the task. See the following screenshot:

Operations 51


After the schedule is created successfully, the following image appears (“dailynoon” is an example of a schedule name):

Note It is recommended that you schedule a few snapshots per day with at least one hour between jobs. This is to ensure that the previous

jobs complete successfully before the next jobs begin.

The Schedule tab displays all schedules that are created by users. It allows

users to view the details of a schedule, as shown below:

The following table describes each property shown in the above screenshot.

Property Description

ScheduleName Schedule name

ScheduleType Schedule type (for example, floating device snapshot, HTI snapshot)

ScheduleSetting Trigger settings of the schedule (for example, every day at 2 PM)

Previous FireTime Local Previous fire time of this schedule (local time zone)

Next FireTime Local Next fire time of this schedule (local time zone)

52 Operations


The Job History section displays the history of all schedules. The history report of schedules allows users to view when each schedule started, how long each

schedule has been running, and the error message if the schedule task has failed. See the following screenshot for an example.

You may manually delete a HANA storage snapshot schedule from the schedule list when you no longer want to run the schedule.

To delete a schedule, follow these steps:

1. Open the list of schedules.

2. Find the schedule that you want to delete.

3. Click the red icon on the “Delete” column.

4. In the “Confirm” dialog box, click OK. Then this schedule is

deleted permanently.

3. Select the type of Hitachi Thin Image. You can select “HTI” or “floating

device”. If you select “floating device”, then go directly to step 5.

4. Select the host group. The UI lists all available host groups with the

associated port of the Hitachi storage array. Select the host group that you need to map for the HTI. It is suggested that users create and use a

dummy host group.

5. Select the HTI pool. The UI lists all available HTI pools for selection. Also, the UI lists all LUNs of HANA data volume of the specified HANA instance

for review.

6. Confirm the selection by clicking Confirm on the UI. If the task is an

instant task, the adapter creates the HANA storage snapshot instantly and displays the result. If the task is scheduled, the adapter shows this message: “This schedule has been created successfully.”

Operations 53


Verifying HANA Storage Snapshot from HANA Studio

After the operation, verify the backup status by using the specified backup ID and HANA Studio according to the following steps.

1. Open HANA Studio, and then select the HANA instance. Right-click it, and then choose Backup and Recovery->Open Backup Console.

2. Click the Backup Catalog tab, and then select the backup snapshot and

make sure that the ID that is listed under Backup Details matches the provided backup ID.

54 Operations


Recovering a HANA Database from a HANA Storage Snapshot

Procedure Note It is recommended that you cancel any scheduled snapshots before

beginning the recovery process.

To recover your HANA database from a HANA storage snapshot, follow the steps in the following three sections, Putting the HANA System Offline,

Reverting a HANA Storage Snapshot Using the Standalone GUI, and Recovering the HANA System Using HANA Studio:

Putting the HANA System Offline

1. Use HANA Studio to bring the HANA system offline.

2. Select Backup and Recovery->Recover System. The following screen appears. Select “Recover the database to a specific data backup or storage snapshot,” and then click Next.

Operations 55


3. A list of snapshots appears. Select the snapshot that you wish to recover. Keep this window open, and then proceed to the next step.

4. Use SSH to access your HANA system. Type

umount /hana/data

to let HANA host unmount the data volumes.

Once you finish the steps in this section, proceed to the following section.

56 Operations


Reverting a HANA Storage Snapshot Using the Standalone GUI

1. Navigate to the “StandaloneGUI” folder of the installation directory of

HANA management web service on the adapter management server.

2. Double-click the “StandaloneGUI.exe” file.

3. Provide the required parameters (for example, IP of the management

service, username and password, etc.) for connection of the Hitachi storage.

4. Under Operation Type, select Revert, as shown in the following screenshot.

5. Select SnapshotGroupName, and then type the name of the snapshot that you wish to revert into the “Filter” field, as shown in the following

screenshot. You may search for the name by typing only part of the

Operations 57


name into the field. You also may sort the results by selecting “Sort Ascending” or “Sort Descending.”

6. Select the snapshot that you wish to revert, and then click Step 4 in the

lower left corner of the screen, as shown in the following screenshot.

58 Operations


7. Review the information, and then click Confirm, as shown in the following screenshot.

Once you finish these steps, proceed to the following section.

Operations 59


Recovering the HANA System Using HANA Studio

1. Use SSH to access your HANA system. Type

mount –a

to let HANA remount the recovered data volumes.

2. Return to HANA Studio, and then click Refresh. The snapshot in the screen that you kept open in step 3 should now display green, as shown

in the following example.

60 Operations


3. Click Next and Finish. Wait until HANA Studio displays the success message. The following three screens appear.

Operations 61


62 Operations


Operations 63


Cloning HANA Systems Using Hitachi Thin Image

Note SAP does not support storage snapshots with SAP HANA if the data resides in multitenant database containers. Use this feature only with SAP HANA single-database containers.

If you wish to put a Hitachi Thin Image (HTI) pair on a specified HTI pool, create the pool on your Hitachi storage before using this feature.

This operation can support OS backup and HANA system replication/cloning.

The following figure shows a scenario of support for HANA system replication/cloning.

SAP HANA System

HANA Cockpit

Hitachi Server Adapter for the SAP HANA Cockpit

HANA Database

Management Server(Windows 2012 R2)

Hitachi HANA Management Web Service

CMD DEV

HTTP/SSH/SQL

http/https

Log Volume

Data Volume

Shared Volume

HITACHI Storage

Data

Source Target

Log

Shared

Data

Log

Shared

Consistency GroupP-VOL

Consistency GroupV-VOL

HTI Replication

Hitachi Storage Adapter for the SAP HANA Cockpit Architecture Diagram: Scale-up

configuration

64 Operations


Prerequisites

1. If you plan to place an HTI pair in an HTI pool, first create one on your Hitachi storage.

2. SAP recommends that you select only data, log, and shared volumes.

Procedure

1. List all LDEVs of data, log, and shared volumes of the specified HANA

instance.

2. List all available HTI pools and host groups for selection.

3. Select all LDEVs, HTI pools, and host groups that you listed in the first two steps. Examples are shown in the following screenshot.

4. Confirm the selection by clicking Confirm.

5. Create V-VOLs and HTI pairs for each selected item.

Operations 65


The software places all created HTI pairs in one consistency group and returns the consistency group ID. You may see a “Please wait” screen, and then the following image appears.

Splitting Replication Pairs Using Thin Image

Use the following procedure to split replication pairs.

1. Wait until the status of all HTI pairs of the consistency group is PAIR.

2. (HANA Studio) Bring the HANA system offline.

3. Navigate to the “StandaloneGUI” folder of the installation directory of

HANA management web service on the adapter management server.


66 Operations


5. Provide the required parameters (for example, IP of the management

service, username and password, etc.) for connection of the Hitachi storage.

6. Under Operation Type, select Split, as shown in the following screenshot.

7. Search for a consistency group by selecting ConsistencyGroupId and then typing the consistency group ID into the “Filter” field. You may sort the results by selecting “Sort Ascending” or “Sort Descending.”

8. After you select the consistency group, select Consistency Group under “Selection,” and then click Step 4 in the lower left corner of the screen.

Operations 67


9. Review the information, and then click Confirm.

10. Mount the V-VOLs to the new HANA server, and then use the SAP HANA

utility (hdblcm) to register the new HANA system by following the official

SAP HANA system clone procedure. (See https://help.sap.com/saphelp_hanaplatform/helpdata/en/c6/22d640e47e

4c0ebca8cbe74ff9550a/content.htm.)

11. Follow the SAP HANA system clone procedure in Copy or Clone an SAP

HANA System.

Note The hdblcm may not start and return error messages in some cases (for example, the target host already has a HANA instance that has

the same instance name and number as a HANA system clone). Users can use hdbreg or hdbrename to register or regname the cloned HANA instance on the target host. Users can find hdbreg/hdbrename in the

<installation path>/<SID>/global/hdb/install/bin folder.

(https://help.sap.com/saphelp_hanaplatform/helpdata/en/c6/ce24c3bb571014bcfdf6abefff1d4f/content.htm)

Input Parameters


HTI Pool String HTI pool for the Thin Image pairs

Hostgroup String Host group for the V-VOLs of the replication pairs

LUNs String Selected LUNs for the Thin Images. All LUNs of the data, log, and shared volumes are selected by default.

https://help.sap.com/saphelp_hanaplatform/helpdata/en/c6/22d640e47e4c0ebca8cbe74ff9550a/content.htm




https://help.sap.com/saphelp_hanaplatform/helpdata/en/c6/ce24c3bb571014bcfdf6abefff1d4f/content.htm


68 Operations


Cloning HANA Systems Using Hitachi ShadowImage

This operation can support OS backup and HANA system replication/cloning.

The following figure shows a scenario of support for HANA system replication/cloning.

SAP HANA System

HANA Cockpit

Hitachi Adapter for the SAP HANA Cockpit

HANA Database

Management Server(Windows 2012 R2)

Hitachi HANA Management Web Service

CMD DEV

HTTP/SSH/SQL

Log Volume

Data Volume

Shared Volume

HITACHI Storage

Data

Source Target

Log

Share

Data

Log

Share

Consistency GroupP-VOL

Consistency GroupS-VOL

ShadowImage Replication

Operations 69


Prerequisites

1. If you plan to place the ShadowImage pair in a DP pool or parity group, first create one on your Hitachi storage.

2. SAP recommends that you select only data, log, and shared volumes.

Procedure

1. List all LDEVs of the data, log, and shared volumes of the specified HANA

instance.

2. List all available DP pools, parity groups, and host groups for selection.

3. Select the LDEVs, DP pool/parity groups, and host groups that you listed

in the first two steps.


5. Create S-VOLs and ShadowImage pairs for each selected item.

70 Operations


The software places all created ShadowImage pairs in one consistency group and returns the consistency group ID. You may see a “Please wait” screen, and

then the following image appears.

Splitting Replication Pairs Using ShadowImage

Use the following procedure to split replication pairs.

1. Wait until the status of all SI pairs of the consistency group is PAIR.

2. (HANA Studio) Bring the HANA system offline.

3. Navigate to the “StandaloneGUI” folder of the installation directory of HANA management web service on the adapter management server.


Operations 71


5. Provide the required parameters (for example, IP of the management service, username and password, etc.) for connection of the Hitachi storage.

6. Under Operation Type, select Split, as shown in the following screenshot.

7. Search for a consistency group by selecting ConsistencyGroupId and

then typing the consistency group ID into the “Filter” field. You may search for the ID by typing only part of the ID into the field. You also may sort the results by selecting “Sort Ascending” or “Sort Descending.”

8. After you select the consistency group, select Consistency Group under “Selection,” and then click Step 4 in the lower left corner of the screen.

Review the information, and then click Confirm.

72 Operations


9. Mount the V-VOLs to the new HANA server, and then use the SAP HANA

utility (hdblcm) to register the new HANA system by following the official

SAP HANA system clone procedure. (See https://help.sap.com/saphelp_hanaplatform/helpdata/en/c6/22d640e47e

4c0ebca8cbe74ff9550a/content.htm.)

Note The hdblcm may not start and return error messages in some cases

(for example, the target host already has a HANA instance that has the same instance name and number as a HANA system clone). Users

can use hdbreg or hdbrename to register or regname the cloned HANA instance on the target host. Users can find hdbreg/hdbrename in the

<installation path>/<SID>/global/hdb/install/bin folder.

(https://help.sap.com/saphelp_hanaplatform/helpdata/en/c6/ce24c3bb571014bcfdf6abefff1d4f/content.htm)

10. Follow the SAP HANA system clone procedure in Copy or Clone an SAP

HANA System.

Input Parameters


DP Pool or Parity Group

String DP pool/parity group for the ShadowImage pairs

Hostgroup String Host group for the S-VOLs of the replication pairs

LUNs String Selected LUNs for the ShadowImages. All LUNs of the data, log, and shared volumes are selected by default.







Operations 73


Backing up HANA OS by Using HTI/ShadowImage

Creating Thin Image and ShadowImage can also support OS backup. The figure below shows a scenario of support for OS backup.

Prerequisites

1. If you plan to place an HTI pair in an HTI pool, first create one on your

Hitachi storage.

2. If you plan to place a ShadowImage pair in an HDP pool, first create one on your Hitachi storage.

74 Operations


Procedure

1. List all LDEVs of the specified HANA instance.

2. List all available HTI pools and host groups for selection.

3. Select the host groups and the LDEV of the OS that you listed in the first two steps. An example is shown in the following screenshot.


5. Create S-VOLs/V-VOLs and SI/HTI pairs for each selected item.

The software places all created SI/HTI pairs in one consistency group and returns the consistency group ID. You may see the following “Please wait” screen.

Operations 75


Then, the following image appears.

1. Wait until the status of all SI/HTI pairs of the consistency group is PAIR.

2. To split replication pairs, follow the steps under Splitting Replication Pairs Using Thin Image or Splitting Replication Pairs Using ShadowImage,

excluding the first step.

3. To recover the OS, shut down the OS, and then use the revert

procedure. See Reverting Replication Pairs by Using Consistency Groups.

76 Operations


Deleting Replication Pairs

This feature deletes the replication pairs and S-VOL/V-VOL on a specified

consistency group or snapshot group created in Creating a HANA Storage Snapshot with Hitachi Thin Image, Cloning HANA Systems Using Hitachi Thin Image, or Cloning HANA Systems Using Hitachi ShadowImage. To execute this

operation, follow these steps:

1. Navigate to the Actions tab on the left panel, and then click Delete

Replication Pairs.

2. Select the group mode and a single replication pair, and then click Next.

Depending on the group type selection, other pairs that reside either in the same snapshot group or consistency group are also selected for reviewing. The default group mode is Snapshot Group.

For example, if the group mode is CTG (consistency group), then this pair and other pairs on the same CTG are selected for reviewing. If the

group mode is SSG (snapshot group), then this pair and other pairs on the same SSG are selected for reviewing.

Note This operation may take a while. However, HANA Cockpit by default allows 300 seconds as the maximum session timeout period. If you receive a timeout error, change the session timeout by following the steps under Changing the Session Timeout.

Operations 77


Collecting Storage Data

Storage Data Collection Job and Cache

This is a pre-defined scheduled job that collects information from registered Hitachi storage. It collects the following information and store for performance

reports and cache.

Hostgroups

Replication Pairs

LUN Performance

Port Performance

LUN Information

Storage Pools

The dates of all updates that have taken place within the last month are used

for performance reports (that is, LUN performance and port performance). The date of the latest update is used as a cache layer. This adapter checks the

cache first when it needs any storage-related information. If it cannot find the required information on the cache or if the data of the cache layer is expired

78 Operations


(default expire value: 2 hours), then it queries the registered Hitachi storage to get the up-to-date information.

The user can check the details of this schedule job from the “Overview” tab, as shown below:

It shows the current scheduled time interval. This job is repeatedly executed on the defined time interval. Also, you may check the previous fire time and next fire time of this job.

Configure the Time Interval for Scheduled Storage Data Collection Job

You may configure the time interval of the scheduled storage data collection job. The default value is 30 minutes. The minimum value is 15 minutes, and the maximum value is 2,880 minutes (two days). Input the time interval value,

and then click Ok. Then this scheduled job is executed with the new time interval.

Storage Data Collection Force Update You may manually kick off a storage data collection. After you click Update Storage Data on the action list in the lower left corner, this adapter starts to run the storage data collection instantly.

Reporting 79


Reporting

Overview

Device-Mapping Report

Hostgroup Report

LUN Performance Report

Port Performance Report

Replication Report

Storage Pool Report

Storage Snapshot History Report

Storage Layout Graph

80 Reporting


Overview

The following sections describe reports that you can generate to retrieve

information about HANA hosts. These reports include device-mapping reports, LUN performance reports, port performance reports, replication reports, and storage snapshot history reports.

To generate reports, first navigate to the Storage tab.

While generating a report, you may see the following “Please wait” message.

Filtering

To filter the results of a report, click the parameter that you wish to filter, and then type a value into the Filter box. The following three screenshots show an

example of filtering the parameter Consistency Group ID. Filtering is only applicable for table-based reports.

Reporting 81


Filter Context

The context filter filters the information and only displays the data related with the specified HANA instance. For example, if a HANA host with an IP address of

172.15.37.143 only uses port CL4-A, then only port CL4-A is displayed in the port performance report when the context filter is turned on. If users turn off the context filter, then all ports of this Hitachi storage array are displayed.

You can turn on or turn off the context filter that is located on left upper corner, as shown below. The context filter is turned on by default. It can help

users to quickly find storage information related with their HANA system.

82 Reporting


The context filter is available for the following reports:

- LUN Performance

- Port Performance

- Replication

- Host Group

- Storage Pool

Device-Mapping Report

After the registration of a specified HANA host and the Hitachi storage, the adapter can generate a device-mapping report that describes the LUNs for the

specified HANA host. It shows the related Hitachi storage on the inventory of the management web service. This report shows information about registered

storage with the HANA host that you specify. The adapter refreshes the data each time you run the report.

To generate a device-mapping report, follow these steps:

1. Click the Storage tab.

Reporting 83


2. Click Overview.

You can perform subsequent storage management operations (that is, HTI and

ShadowImage) by using the result of this registration feature. Provide the user credential that has access permission to the Hitachi storage as well as to the IP address and HORCM instance number for this feature. The adapter uses your

inputs (see below) to scan the Hitachi storage. All the parameters are required.


HANA Host Name of the HANA host

LUN Number Number of the logical unit

LDEV ID ID of the LDEV

Storage Serial Serial number of the storage device that is associated with the HANA host

WWID World Wide Identifier (WWID) of the LUN

Volume Group Name of the LVM volume group of the LUN

Physical Volume Name of the LVM physical volume

Mount Point Mount point to which the LUN belongs

HANA Volume Type

HANA volume type (DATA or LOG) to which the LUN belongs

Logical Volume Name of the LVM logical volume to which the LUN belongs

84 Reporting


Hostgroup Report

This report shows information for all hostgroups of the storage that is

registered with the specified HANA host. This report only shows up-to-time data (the latest list of host groups).

See the following table for the details of this report.


Hostgroup Name Hostgroup name

Hostgroup Id Hostgroup ID

HostMode Host mode information (that is, UNKNOWN, NOT_SPECIFIED, RESERVED, STANDARD, LINUX, VMWARE, HP, OPEN_VMS, TRU64, SOLARIS, NETWARE,

WINDOWS, HI_UX, AIX, VMWARE_EXTENSION, WINDOWS_EXTENSION, UVM)

ResourceGroupId ID of the resource group that this host group belongs to

Port Port that this host group resides on

Paths LUN paths that are mapped to this host group

Reporting 85


LUN Performance Report

LUN performance reports show information about the performance of all LUNs in registered storage with the HANA host that you specify. The adapter

refreshes the data each time you run the report.

To generate a LUN performance report, follow these steps:


2. Click LUN Performance.



LUN Number Logical unit number

ReadRate in KB/s Read rate in KB/s

WriteRate in KB/s Write rate in KB/s

IORate in KB/s IO rate in KB/s (ReadRate + WriteRate)

RandomReadRate in KB/s Random read rate in KB/s

RandomWriteRate in KB/s Random write rate in KB/s

RandomIORate in KB/s Random IO rate in KB/s

SequentialReadRate in KB/s Sequential read rate in KB/s

SequentialWriteRate in KB/s Sequential write rate in KB/s

SequentialIORate in KB/s Sequential IO rate in KB/s

ReadCount (IOPS) Read count (IOPS)

WriteCount (IOPS) Write count (IOPS)

RandomReadCount (IOPS) Number of random reads (IOPS)

RandomWriteCount (IOPS) Number of random writes (IOPS)

SequencialReadCount (IOPS) Number of sequential reads (IOPS)

SequencialWriteCount (IOPS) Number of sequential writes (IOPS)

86 Reporting


LUN Performance Detail Report

Users can click Details on the LUN Performance report to see a chart that summarizes the details of the specified LUN performance.

LUN Performance History Chart

Users also can click History on the LUN Performance report to see a chart that

presents the history (all entries from the last month in the storage data collection) of the specified LUN performance. Users may select “Grouped” or “Stacked” to change the way the data is presented.

Reporting 87


Port Performance Report

This report shows information for the performance of all ports in registered storage with the HANA host that you specify. The adapter refreshes the data

each time you run the report.

To generate a port performance report, follow these steps:


2. Click Port Performance.



Port Name Port name

Average IOPS Average IO per second

Max IOPS Maximum IO per second

Min IOPS Minimum IO per second

Max Port Transfer Maximum port transfer (KB per second)

Average Port Transfer Average port transfer (KB per second)

Min Port Transfer Minimum port transfer (KB per second)

Collection Date Time Timestamp of the performance data taken

Port Performance History Chart

Users also can click History on the Port Performance report to see a chart that

presents the history (all entries from the last month in the storage data collection) of the specified port performance. Users may select “Grouped” or

“Stacked” to change the way the data is presented.

88 Reporting


Replication Report

This report shows information for all replication pairs in registered storage with the HANA host that you specify. The adapter refreshes the data each time you

run the report.

To generate a replication report, follow these steps:


2. Click Replication Report.

Reporting 89




Serial Number Serial number of the storage. If it is -1, the pair is a remote replication pair.

Data Pool ID ID of the data pool that this replication pair uses. If it is -1, then the replication pool does not use any data pool on this storage device.

Consistency Group ID

ID of the consistency group for this replication pair. If it is -1, then this pair does not use any consistency group.

P-VOL LUN number of the P-VOL

S-VOL/V-VOL LUN number of the S-VOL or V-VOL. If the pair type is

TI, then it is the LUN number of the V-VOL. If the pair type is SI, then it is the LUN number of the S-VOL.

Pair Type Type of pair (SI, TI, UR, TC)

Pair Status Status of the pair (that is, SMPL(PD), COPY, PAIR, PFUL, PFUS, PSUS, RCPY, PSUE)

Pair Name Name of the pair

Mirror ID ID of the mirror unit

90 Reporting


Storage Pool Report

This report shows information for all storage pools of the storage that is

registered with the specified HANA host. This report only shows up-to-time data (the latest list of storage pools).



Serial Storage serial

Id Storage pool ID

Name Storage pool name. For parity group, it is blank.

TotalCapacityInMB Total capacity (MB)

FreeCapacityInMB Free capacity (MB)

Type Type of this storage pool (UNKNOWN, HDP, SNAPSHOT, HDT, HTI, DATAPOOL, HDT_AF, PARITYGROUP, RAIDGROUP)

Status Current status of this storage pool (UNKNOWN, NORMAL, OVERTHRESHOLD, SUSPENDED, FAILURE, SHRINKING, REGRESSED)

UtilizationRate Utilization percentage

SubscriptionRate Current subscription percentage. For a non-HDP/HDT pool, this value is blank or -1.

SubscriptionWarningRate

Subscription warning rate. For AMS data pools and RAID devices, this value does not apply and is blank or -1.

WarningThresholdRate

Warning threshold percentage. If no warning threshold is set or if this represents a data pool, this value is -1.

DepletionThresholdRate

Depletion threshold percentage. If no depletion threshold is set, this is -1. This is also known as the high-water mark. For data pools, this value represents the singular

threshold.

VirtualLUCount Virtual LU count. For DP/DT pools, this value represents the number of virtual volumes. For CoW/TI pools, this value represents the number of snapshots. For AMS data

pools, this value is not valid and is set to -1.

Reporting 91


Storage Snapshot History Report

This report shows information about the storage snapshots that the adapter has created since installation.

To generate a storage snapshot history report, follow these steps:


2. Click Storage Snapshot History.



Instance Host Name HANA instance name

Storage Serial Serial number of the storage

Backup ID Backup ID of this storage snapshot

Backup External ID Backup external ID of this storage snapshot

Group ID ID of the group for this storage snapshot

Storage Snapshot Status Status of this storage snapshot (success or fail)

Current Status Whether the snapshot is available

Update On Timestamp of the collection

Details Thin Image pair details of the storage snapshot (that is, P-VOL or V-VOL)

92 Reporting


Storage Layout Graph

The storage layout graph visualizes the hierarchical relationship of storage context of a specified HANA host. It shows the structure of LUNs, hostgroups, storage pool, and ports in the registered Hitachi storage for a specified HANA

host. The graph displays information about the hostgroup that connects the LUNs to the storage port with the external host. This feature automatically

checks the storage layout from collected storage data. If the layout is changed, the layout graph changes as well after the storage cache is updated.

Logging, Troubleshooting, and Error Messages 93


Logging, Troubleshooting, and Error Messages

Logging

Troubleshooting

Error Messages

94 Logging, Troubleshooting, and Error Messages


Logging

Find log files in this location:

[Installed drive]\Program Files\Hitachi\ Hitachi HANA Management Service\Log

The adapter supports the following logging levels:

Fatal

Error

Warn

Info

Debug

Trace

The default logging level is Info. You can change the logging level in the

HiHanaLogConfig.Config file in the installation folder as shown below:

Log Generation and Rotation

Multiple log generation and rotation of the adapter log files create multiple log

files. The active log filename is hiHana.log.

The log generation and rotation of the adapter log files allow you to do the

following:

Log multiple processes to the same file.

Determine the maximum number of consecutive files by using a user-specified parameter or a system default.

Rotate the current or active log file by incrementing the log file name, appending consecutive numbers that start from zero to a user-specified limit or a system default.

Specify a maximum log file size in hiHanaLogConfig.config by editing

the [archiveAboveSize] key as shown below:



If the value of the log file size is greater than the specified [archiveAboveSize] value, then the log file is automatically rotated. The default value of [archiveAboveSize] is 10485760 bytes (10MB). Specify a

maximum backup log file in hiHanaLogConfig.config by editing the

[maxArchiveFiles] key. The default value is 10 as shown below:

Sample Log Output

The default log level is Info. Here is a sample of normal log output.

[4756] [01/08/16-22:47:18] [HiHANA] DBG3 [--------] {StorageManager::ResetSession}:startTime: [1/8/2016 10:47:18 PM].

[4756] [01/08/16-22:47:18] [HiHANA] EXIT [--------] {StorageManager::ResetSession}:

[4756] [01/08/16-22:47:18] [HiHANA] EXIT [--------] {StorageManagerFactory::GetStorageManager}:


[4756] [01/08/16-22:47:18] [HiHANA] ENTER [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:

[4756] [01/08/16-22:47:18] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:sessionId: [22049698-89bf-4f65-b8a1-696c9d2c99a6].

[4756] [01/08/16-22:47:18] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:serialNumber: [210050].

[4756] [01/08/16-22:47:18] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:P-VOL: [267].

[4756] [01/08/16-22:47:18] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:V-VOL: [-1].

[4756] [01/08/16-22:47:18] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:dataPool: [13].

[4756] [01/08/16-22:47:18] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:ctgID: [-1].

[4756] [01/08/16-22:47:18] [HiHANA] ENTER [--------] {StorageManagerFactory::GetStorageManager}:



[4756] [01/08/16-22:47:18] [HiHANA] PARAM [--------] {StorageManagerFactory::GetStorageManager}:guidIdentifierString: [22049698-89bf-4f65-b8a1-696c9d2c99a6].


[4756] [01/08/16-22:47:18] [HiHANA] PARAM [--------] {StorageManagerFactory::GetStorageManager}:identifier: [22049698-89bf-4f65-b8a1-696c9d2c99a6].

[4756] [01/08/16-22:47:18] [HiHANA] ENTER [--------] {StorageManager::ResetSession}:





[4756] [01/08/16-22:47:18] [HiHANA] ENTER [--------] {StorageManager::GetStorageDevice}:

[4756] [01/08/16-22:47:18] [HiHANA] ENTER [--------] {StorageManagerFactory::DumpStorageDeviceRegistration}:

[4756] [01/08/16-22:47:18] [HiHANA] DBG3 [--------] {StorageManagerFactory::DumpStorageDeviceRegistration}:Session ID: [f47d3cdb-ac39-4b88-9a4a-606209fc81d2].

[4756] [01/08/16-22:47:18] [HiHANA] ENTER [--------] {StorageManager::DumpStorageDeviceRegistration}:

[4756] [01/08/16-22:47:18] [HiHANA] EXIT [--------] {StorageManager::DumpStorageDeviceRegistration}:

[4756] [01/08/16-22:47:18] [HiHANA] DBG3 [--------] {StorageManagerFactory::DumpStorageDeviceRegistration}:Session ID: [22049698-89bf-4f65-b8a1-696c9d2c99a6].

[4756] [01/08/16-22:47:18] [HiHANA] ENTER [--------] {StorageManager::DumpStorageDeviceRegistration}:



[4756] [01/08/16-22:47:18] [HiHANA] DBG3 [--------] {StorageManager::DumpStorageDeviceRegistration}:Serial: [210050], Storage device object: [65718035].

[4756] [01/08/16-22:47:18] [HiHANA] EXIT [--------] {StorageManager::DumpStorageDeviceRegistration}:

[4756] [01/08/16-22:47:18] [HiHANA] EXIT [--------] {StorageManagerFactory::DumpStorageDeviceRegistration}:

[4756] [01/08/16-22:47:18] [HiHANA] EXIT [--------] {StorageManager::GetStorageDevice}:

[4756] [01/08/16-22:47:18] [HiHANA] ENTER [--------] {StorageDevice::CreateSnapshotPairWithCTG}:

[4756] [01/08/16-22:47:18] [HiHANA] PARAM [--------] {StorageDevice::CreateSnapshotPairWithCTG}:P-VOL=267 V-VOL=-1 dataPool=13 ctgID=-1: [].

[4756] [01/08/16-22:47:18] [HiHANA] ENTER [--------] {StorageDevice::getFreeLUNumber}:

[4756] [01/08/16-22:47:19] [HiHANA] ENTER [--------] {StorageManager::ValidateResult}:

[4756] [01/08/16-22:47:19] [HiHANA] EXIT [--------] {StorageManager::ValidateResult}:

[4756] [01/08/16-22:47:19] [HiHANA] DBG3 [--------] {StorageDevice::getFreeLUNumber}:Generated Lun Number: 844

[4756] [01/08/16-22:47:19] [HiHANA] EXIT [--------] {StorageDevice::getFreeLUNumber}:



[4756] [01/08/16-22:47:22] [HiHANA] ENTER [--------] {StorageDevice::PresentVirtualVolume}:

[4756] [01/08/16-22:47:22] [HiHANA] PARAM [--------] {StorageDevice::PresentVirtualVolume}:V-VOL: [844].

[4756] [01/08/16-22:47:22] [HiHANA] PARAM [--------] {StorageDevice::PresentVirtualVolume}:hostGroupName: [HITACHI_HG].

[4756] [01/08/16-22:47:22] [HiHANA] PARAM [--------] {StorageDevice::PresentVirtualVolume}:port: [CL1-A].





[4756] [01/08/16-22:47:22] [HiHANA] ENTER [--------] {StorageDevice::Presentlu}:

[4756] [01/08/16-22:47:22] [HiHANA] PARAM [--------] {StorageDevice::Presentlu}:Lu=844, port=CL1-A hostGroupName=HITACHI_HG: [].



[4756] [01/08/16-22:47:37] [HiHANA] EXIT [--------] {StorageDevice::Presentlu}:

[4756] [01/08/16-22:47:37] [HiHANA] EXIT [--------] {StorageDevice::PresentVirtualVolume}:

[4756] [01/08/16-22:47:37] [HiHANA] ENTER [--------] {StorageDevice::CreateLocalConsistencyGroup}:



[4756] [01/08/16-22:47:37] [HiHANA] EXIT [--------] {StorageDevice::CreateLocalConsistencyGroup}:

[4756] [01/08/16-22:47:37] [HiHANA] ENTER [--------] {StorageDevice::GetStoragePool}:



[4756] [01/08/16-22:48:20] [HiHANA] EXIT [--------] {StorageDevice::GetStoragePool}:







[4756] [01/08/16-22:48:20] [HiHANA] ENTER [--------] {ReplicationPair::.ctor}:

[4756] [01/08/16-22:48:20] [HiHANA] EXIT [--------] {ReplicationPair::.ctor}:

[4756] [01/08/16-22:48:20] [HiHANA] EXIT [--------] {StorageDevice::CreateSnapshotPairWithCTG}:

[4756] [01/08/16-22:48:20] [HiHANA] DBG3 [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:Created Snapshot pair with CTG P-VOL = 267, V-VOL = 844, CTG = 13 in DataPool = -1

[4756] [01/08/16-22:48:20] [HiHANA] EXIT [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:

[4756] [01/08/16-22:48:20] [HiHANA] ENTER [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:

[4756] [01/08/16-22:48:20] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:sessionId: [22049698-89bf-4f65-b8a1-696c9d2c99a6].

[4756] [01/08/16-22:48:20] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:serialNumber: [210050].

[4756] [01/08/16-22:48:20] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:P-VOL: [268].

[4756] [01/08/16-22:48:20] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:V-VOL: [-1].

[4756] [01/08/16-22:48:20] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:dataPool: [13].

[4756] [01/08/16-22:48:20] [HiHANA] PARAM [--------] {SnapshotImpl::CreateSnapshotPairWithCTG}:ctgID: [27].




[4756] [01/08/16-22:48:20] [HiHANA] PARAM [--------] {StorageManagerFactory::GetStorageManager}:guidIdentifierString: [22049698-89bf-4f65-b8a1-696c9d2c99a6].


[4756] [01/08/16-22:48:20] [HiHANA] PARAM [--------] {StorageManagerFactory::GetStorageManager}:identifier: [22049698-89bf-4f65-b8a1-696c9d2c99a6].

[4756] [01/08/16-22:48:20] [HiHANA] ENTER [--------] {StorageManager::ResetSession}:





Troubleshooting

Changing the Session Timeout

By default, the SAP HANA Cockpit only allows 10 minutes as the maximum timeout value.

Many storage-related operations need more than 10 minutes. If you need to increase the maximum timeout value, follow these steps:

1. From HANA Studio, select the HANA system.

2. From system view, choose Open Administration from the

Configuration and Monitoring menu.



3. Click the Configuration tab, and then expand xsengine.ini.



4. On httpserver, find or create the max_request_runtime and

sessiontimeout parameters. Then change both parameters to a higher

number of seconds, such as 1800 or more.

5. Modify the icm/server_port parameter in the webdispatcher.ini section by

changing the value of PROCTIMEOUT to 1800 or more if necessary. If you

are using http to access the Cockpit, then you only need to change

icm/server_port_0. If you are also using https, then you need to

change icm/server_port_1 as well.



Cleaning the Cache When the Delivery Unit Fails to Import

Sometimes, the delivery unit fails to import to the HANA Cockpit when you are using SAP HANA Application Lifecycle Management with

your browser. To solve this problem, clean the cache of your browser, and then try again.

Turn on port 2022 on Windows firewall

The error message “error: Internal Server Error HttpClient.request:

request failed: unable to establish connection to <Adapter Management Server IP>:2022 - IPcon: connection to host failed!” means that the

HANA system cannot connect to the adapter management server. To resolve this issue, check and ensure the network connectivity.



Sometimes, the Windows firewall of the adapter management server blocks the http connection on the default port (2022). Enable the

connection of the port by following the steps below:

1. Open Windows Firewall by navigating to Start>Control Panel. In the

search box, type “firewall,” and then click Windows Firewall.

2. In the left pane, click Advanced settings. Administrator permission is required. If you are prompted for an administrator password or

confirmation, type the password or provide confirmation.

3. In left pane of the Windows Firewall with Advanced Security dialog box,

click Inbound Rules. Then, in the right pane, click New Rule….

4. Select “Port,” and then click Next.



5. Select “TCP,” type “2022” into the “Specific local ports” field, and then

click Next.



6. Select ”Allow the connection,” and then click Next.



7. Select the appropriate network types, and then click Next.



8. Provide a name for this rule, and then click Finish.



Troubleshooting Diagnostic Steps

Use the flowchart below and the Troubleshooting tips on the next page.

Error Condition Detected

SAP HANA

Issue?

Investigate HANA

environment. See

Troubleshooting

#1.

Investigate the

adapter logs. See

Troubleshooting

#2.

Gather information and

call technical support

Adapter log

error?

No

HORCM error

Storage error

No

No

No

Investigate the

HORCM logs.

Investigate

Storage and

dump files.

Yes

Yes

Yes

Yes



Troubleshooting #1

Investigate the SAP HANA environment.

If SAP HANA cannot be reached or is experiencing performance problems, open the Administration editor in diagnosis mode to resolve this issue by following the SAP HANA procedure that is explained here:

https://help.sap.com/saphelp_hanaplatform/helpdata/en/95/fc8adf6c5a46e7bc3a0a29b63ec6bb/content.htm)

Troubleshooting #2

Investigate the adapter logs.

Review the log file (hiHana.log) under the log subfolder of the installation

folder. Study the recommended action for resolving the issue from the error message list by checking the error message ID.

https://help.sap.com/saphelp_hanaplatform/helpdata/en/95/fc8adf6c5a46e7bc3a0a29b63ec6bb/content.htm

https://help.sap.com/saphelp_hanaplatform/helpdata/en/95/fc8adf6c5a46e7bc3a0a29b63ec6bb/content.htm



Error Messages

E590001

Error Message ID E5900001

Error Message Text Invalid username or password. Check and try again.

Explanation Error occurred while using the specified username and password.

Recommended Action

Ensure that the username and password are valid.

E5900002


Error Message Text Error occurred while getting the version.

Explanation Error occurred while getting the version number.

Recommended Action

Ensure that version.txt is located on the

installation directory and includes the version number and build number.

E5900003


Error Message Text Error occurred while registering the HANA instance.

Explanation Error occurred while registering the specified HANA instance.

Recommended Action

Ensure that the provided parameters (instance number, IP) of this HANA instance are valid.

E5900004


Error Message Text Error occurred while splitting the snapshot pair from the specified subsystem.

Explanation Error occurred while splitting the COW/HTI snapshot pair.

Recommended Action

Ensure that the storage array is not locked. Check the input parameters and detailed error message

in the HiStor API log.

E5900005


Error Message Text Error occurred while getting HTI pools by storage

serial.



Explanation Error occurred while splitting the HTI pool.

Recommended Action

Ensure that the storage array is not locked. Check the input parameters and detailed error message in the HiStor API log.

E5900006


Error Message Text Error occurred while creating storage snapshot by using HTI.

Explanation Error occurred while creating the storage snapshot by using HTI.

Recommended Action

Ensure that the storage array is not locked. Check

the input parameters and detailed error message in the HiStor API log.

E5900007


Error Message Text Error occurred while registering the HANA host.

Explanation Error occurred while registering the HANA host

Recommended Action

Ensure that the storage array is not locked. Check that the input parameters (host name, SSH

username, and password) are valid.

E5900008


Error Message Text Error occurred while saving the HCSM config.

Explanation Error occurred while saving the HCSM config.

Recommended Action

Ensure that the input parameters (HCSM IP, port, username, password, protocol) are valid.

E5900009


Error Message Text Error occurred while creating storage replication by using ShadowImage.

Explanation Error occurred while creating storage replication by using ShadowImage.

Recommended Action





E5900010


Error Message Text Error occurred while reverting the storage snapshot.

Explanation Error occurred while reverting the storage snapshot.

Recommended Action



E5900011


Error Message Text Error occurred while getting server by serial.

Explanation Error occurred while getting server by serial.

Recommended Action

Check whether the server has been managed by HCSM.

E5900012


Error Message Text Error occurred while getting chassis by server serial.

Explanation Error occurred while getting chassis by server serial.

Recommended Action Check whether HCSM is managing the server.

E5900013


Error Message Text Error occurred while getting switch by server serial.

Explanation Error occurred while getting switch by server serial.

Recommended Action Check whether HCSM is managing the server.

E5900014


Error Message Text Error occurred while getting power supply by server serial.

Explanation Error occurred while getting power supply by server serial.



Recommended Action

Check whether HCSM is managing the server.

E5900015


Error Message Text Error occurred while getting server serial.

Explanation Error occurred while getting server serial.

Recommended Action

Ensure that the account used for registering the host has root privileges.

E5900016


Error Message Text Error occurred while getting HANA instances.

Explanation Error occurred while getting HANA instances.

Recommended Action

Check the network connection/environment between the management server and the HANA instance. Ensure that the HANA instances are up.

E5900017


Error Message Text Error occurred while getting HANA hosts.

Explanation Error occurred while getting HANA hosts.

Recommended Action

Check the network connection/environment between the management server and the HANA host. Ensure that the HANA hosts are up and that

the DNS name for the HANA host registration is correct.

E5900018


Error Message Text Error occurred while getting the LUNs of a specified HANA host.

Explanation Error occurred while getting the LUNs of a specified HANA host.

Recommended Action

Ensure that the account used for registering the host has root privileges.

E5900019


Error Message Text Error occurred while getting the storage snapshots by instance host name.



Explanation Error occurred while getting storage snapshots by instance host name.

Recommended Action

Check the log for the HANA management web service for the details. If the data store is damaged, repair the installation.

E5900020


Error Message Text Error occurred while getting the storage by hana host.

Explanation Error occurred while getting the storage by HANA host.

Recommended Action

Ensure that the storage for the specified HANA host is first.

E5900021


Error Message Text Error occurred while getting the server by hana host.

Explanation Error occurred while getting the server by HANA host.

Recommended Action

Ensure that the account used for registering the host has root privileges and that HCSM is available.

E5900022


Error Message Text Error occurred while getting the DP pools and parity group by storage.

Explanation Error occurred while getting the DP pools and parity group by storage.

Recommended Action



E5900023


Error Message Text Error occurred while getting the parity group by storage.

Explanation Error occurred while getting the parity group by storage.



Recommended Action


E5900024


Error Message Text Error occurred while getting the host names by querying hana database with the instance name.

Explanation Error occurred while getting the host names by querying HANA database with the instance name.

Recommended Action

Ensure that your HANA instance and the network connection/environment of your management server are available.

E5900025


Error Message Text Error occurred while getting the workload by using the host names to query hana database.

Explanation Error occurred while getting the workload by using the host names to query the HANA database.

Recommended Action

Ensure that your HANA instance and the network connection/environment of your management

server are available.

E5900026


Error Message Text Error occurred while getting server report info by server serial.

Explanation Error occurred while getting server report info by server serial.

Recommended Action

Ensure that HCSM and the network connection/environment of your management server are available.

E5900027


Error Message Text Error occurred while getting the ports by storage.

Explanation Error occurred while getting the ports by storage.

Recommended Action




E5900028


Error Message Text Invalid HCSM IP or port. Check your input again and if that is correct then your HCSM is not available at this time.

Explanation Invalid HCSM IP or port. Check your input again,

and if that is correct, then your HCSM is not available at this time.

Recommended Action

Ensure that the storage array is not locked. Also ensure that the provided HCSM IP or port are valid

and the network connection is available.

E5900029


Error Message Text Unable to connect to HCSM. Check the management server's network and proxy settings,

and try again.

Explanation Unable to connect to HCSM. Check the management server network and proxy settings, and then try again.

Recommended Action

Check the network connection and/or DNS settings on your management server.

E5900030


Error Message Text Invalid HCSM username, password, or wrong protocol for hcsm configuration.

Explanation Invalid HCSM username, password, or wrong protocol for HCSM configuration.

Recommended Action

Ensure that the HCSM username, password, and protocol are valid.

E5900031


Error Message Text Invalid SSL cert.

Explanation Invalid SSL cert for HCSM connection.

Recommended Action



E5900032




Error Message Text Error occurred while getting the ports by storage.

Explanation Error occurred while getting the ports by storage.

Recommended Action


E5900033


Error Message Text Error occurred while getting the performance data of ports by storage.

Explanation Error occurred while getting the performance data of ports by storage.

Recommended Action



E5900034


Error Message Text Error occurred while getting replication groups by

storage.

Explanation Error occurred while getting replication groups by storage.

Recommended Action


E5900035


Error Message Text The parameter is null or invalid.

Explanation Error occurred while one of the input parameter is null or invalid.

Recommended Action

Check the input parameters. Ensure that they are not null or invalid.



E5900036


Error Message Text Error occurred while getting the storage information by host.

Explanation Error occurred while getting the storage information by host.

Recommended Action



E5900037


Error Message Text Error occurred while getting the hostgroup, DP pool

and parity group.

Explanation Error occurred while getting the hostgroup, DP pool and parity group.

Recommended Action


E5900038


Error Message Text Error occurred while creating replication with CTG by Thin image.

Explanation Error occurred while creating replication with CTG via thin Image.

Recommended Action


E5900039


Error Message Text Error occurred while deleting the replication pairs by CTG ID.

Explanation Error occurred while deleting the replication pairs by CTG ID.

Recommended Action

Ensure that the storage array is not locked. Check the input parameters and detailed error message in

the HiStor API log.



E5900040


Error Message Text Error occurred while this argument is invalid.

Explanation Error occurred while this argument is invalid.

Recommended Action

Ensure that the storage array is not locked. Check the input parameters and ensure that they are valid. (That is, some parameters, such as the CTG

ID, must be integers.)

E5900041


Error Message Text Error occurred while removing the replication pairs and unmapping the S/V-VOL.

Explanation Unable to remove the replication pairs and unpresent them from the hostgroups.

Recommended Action Ensure that the storage array is not locked.

E5900042


Error Message Text Invalid Pair Status. The TI pair cannot be restored. This P-VOL has a SI pair that is not PSUS/PSUE. Change the SI pair status to PSUS or PSUE first.

Explanation The P-VOL has another SI pair that is not PSUS/PSUE.

Recommended Action

Check the P-VOL and change the SI pair that is not PSUS/PSUE to PSUE or PSUE. Then re-run this operation.

E5900043


Error Message Text Error occurred while resyncing the CTG.

Explanation Cannot resync this CTG.

Recommended Action

Ensure that the storage array is not locked. Also, check whether this CTG has any replication pairs

and check the status of the pairs.

E5900044


Error Message Text Error occurred while removing the HANA instance.

Explanation Cannot delete the HANA instance.



Recommended Action

Restart the Hitachi HANA management service if needed.

E5900045


Error Message Text Error occurred while creating SnapshotPair in new CTG with auto V-VOL.

Explanation Cannot create the HTI pairs in a new CTG.

Recommended Action

Ensure that the storage array is not locked. Also, Check whether it has any available CTG (CTG range: 0-255 for HTI).

E5900046


Error Message Text Error occurred while creating Shadow Image pair in new CTG and HDP with auto S-VOL.

Explanation Cannot create the ShadowImage pairs in a new CTG.

Recommended Action

Ensure that the storage array is not locked. Also, check whether it has any available CTG (CTG

range: 0-127 for ShadowImage). In addition, ensure that the HDP pool has enough free space.

E5900047


Error Message Text Error occurred while using a CTG. No valid CTG is available for the replication. Valid CTG range: ShadowImage (0-127) Thin Image (0-255).

Explanation No valid CTG is available.

Recommended Action

Remove some unused CTGs from the storage array. Then re-run this operation.

E5900048


Error Message Text Error occurred while creating ShadowImage pair in new CTG and Parity Group with auto S-VOL.

Explanation Cannot create the ShadowImage pairs in a new CTG.

Recommended Action

Ensure that the storage array is not locked. Also, check whether it has any available CTG (CTG

range: 0-127 for ShadowImage). In addition, ensure that the parity group has enough free

space.



E5900049


Error Message Text Error occurred with SAPUI5 on client's browser.

Explanation Error occurred on SAPUi5 side.

Recommended Action

Check the error message on the log. Ensure that the status of the HANA cockpit is normal.

E5900050


Error Message Text Error occurred while save the JS client error message to log.

Explanation Cannot save the error message from javascript to the log.

Recommended Action

Ensure that the adapter management server has free space.

E5900051


Error Message Text Error occurred while this argument has an illegal character.

Explanation The input parameter has an illegal character.

Recommended Action

Remove the illegal character (for example, *, %) from the input parameter.

E5900052


Error Message Text Error occurred while splitting the CTG.

Explanation Cannot split the CTG.

Recommended Action

Ensure that the storage array is not locked. Also, check the status of all replication pairs of this CTG.

E5900053


Error Message Text Error occurred while getting the hostgroup.

Explanation Error occurred while getting the hostgroup.

Recommended

Action

Ensure that the storage array is not locked.

E5900054




Error Message Text Invalid value for storage cache interval.

Explanation Invalid value for storage cache interval.

Recommended Action

Check the input parameters and ensure that they are valid (that is, the interval time should be

between 15 and 2,880 minutes).

E5900055


Error Message Text Error occurred while setting the cache update interval value for storage devices.

Explanation Error occurred while setting the cache update interval value for storage devices.

Recommended Action

Check the input parameters and ensure that they are valid (that is, the interval time should be between 15 and 2,880 minutes).

E5900056


Error Message Text Error occurred while getting the performance history data of a specified LUN by storage.

Explanation Error occurred while getting the performance history data of a specified LUN by storage.

Recommended Action

Check whether the DB files on the installation directory are opened by any other processes.

E5900057


Error Message Text Error occurred while getting the performance history data of a specified port by storage.

Explanation Error occurred while getting the performance history data of a specified port by storage.

Recommended Action


E5900058


Error Message Text Error occurred while getting the storage pools.

Explanation Error occurred while getting the storage pools.




E5900059


Error Message Text Error occurred while creating storage snapshot by using floating device.

Explanation Error occurred while creating storage snapshot by using floating device.


E5900060


Error Message Text Error occurred while getting the job instance history.

Explanation Error occurred while getting the job instance history.

Recommended Action


E5900061


Error Message Text Error occurred while creating the scheduled HANA snapshot job with floating device.

Explanation Error occurred while creating the scheduled HANA snapshot job with floating device.

Recommended Action


E5900062


Error Message Text Error occurred while creating the scheduled HANA snapshot job with regular HTI.

Explanation Error occurred while creating the scheduled HANA snapshot job with regular HTI.

Recommended Action


E5900063


Error Message Text Error occurred while getting the user defined schedules.

Explanation Error occurred while getting the user defined schedules.



Recommended Action


E5900064


Error Message Text Invalid schedule description.

Explanation Invalid schedule description.

Recommended Action

Check the schedule name, recurring time string, and description.

E5900065


Error Message Text Error occurred while saving the IPMI config.

Explanation Error occurred while saving the IPMI config.

Recommended Action


E5900066


Error Message Text Error occurred while getting the server event log.

Explanation Error occurred while getting the server event log.

Recommended Action

Ensure that the server is accessible.

E5900067


Error Message Text Error occurred while getting the storage layout.

Explanation Error occurred while getting the storage layout.

Recommended Action Update the storage cache.

E5900068


Error Message Text Error occurred while getting the firmware information.

Explanation Error occurred while getting the firmware information.

Recommended Action




E5900069


Error Message Text Error occurred while getting the sensor information.

Explanation Error occurred while getting the sensor information.

Recommended Action Ensure that the server is accessible.

E5900070


Error Message Text Error occurred while getting the FRU information.

Explanation Error occurred while getting the FRU information.

Recommended Action


E5900071


Error Message Text Error occurred while getting the server IPMI information.

Explanation Error occurred while getting the server IPMI information.

Recommended Action Ensure that the server is accessible.

E5900072


Error Message Text Error occurred while checking if the server is quanta.

Explanation Error occurred while checking if the server is quanta.

Recommended Action


E5900073


Error Message Text Error occurred while getting the storage by using the provided information.

Explanation Error occurred while getting the storage by using the provided information.

Recommended Action

Ensure that the storage array is not locked and accessible.



E5900074


Error Message Text Error occurred while getting replication groups with CTG by storage.

Explanation Error occurred while getting replication groups with CTG by storage.

Recommended Action


Check the input parameters and ensure that they are valid (that is, some parameters, such as the

CTG ID, must be an integer).

E5900075


Error Message Text Error occurred while getting replication pairs of a CTG by using P-VOL and mirror ID.

Explanation Error occurred while getting replication pairs of a CTG by using P-VOL and mirror ID.

Recommended Action




E5900076


Error Message Text Error occurred while geting the replication pairs of a snapshot group.

Explanation Error occurred while geeting the replication pairs

of a snapshot group.

Recommended Action

Ensure that the storage array is not locked. Check the input parameters and ensure that they are valid.

E5900077


Error Message Text Error occurred while split paris by using snapshot group.

Explanation Error occurred while split paris by using snapshot group.

Recommended Action


Check the input parameters and ensure that they are valid.



E5900078


Error Message Text Error occurred while resync the pairs by using snapshotgroup.

Explanation Error occurred while resync the pairs by using snapshotgroup.

Recommended Action


Check the input parameters and ensure that they

are valid.

E5900079


Error Message Text Error occurred while split the CTG pairs by using P-VOL and MU ID.

Explanation Error occurred while split the CTG pairs by using P-VOL and MU ID.

Recommended Action


Check the input parameters and ensure that they are valid (that is, some parameters, such as the CTG ID, must be an integer).

E5900080


Error Message Text Error occurred while resync the CTG pairs by using P-VOL and MU ID.

Explanation Error occurred while resync the CTG pairs by using P-VOL and MU ID.

Recommended Action


Check the input parameters and ensure that they

are valid (that is, some parameters, such as the CTG ID, must be an integer).

E5900081


Error Message Text Error occurred while revert the CTG pairs by using P-VOL and MU ID.

Explanation Error occurred while revert the CTG pairs by using P-VOL and MU ID.

Recommended Action






E5900082


Error Message Text Error occurred while delete the replication pairs of a snapshot group.

Explanation Error occurred while delete the replication pairs of a snapshot group.

Recommended Action


E5900083


Error Message Text Error occurred while delete the replication pairs of a consistency group by using P-VOL and MU ID.

Explanation Error occurred while delete the replication pairs of a consistency group by using P-VOL and MU ID.


E5900084


Error Message Text Error occurred while execute the schedule job for creating HANA snapshot with floating device.

Explanation Error occurred while execute the schedule job for creating HANA snapshot with floating device.

Recommended Action


E5900085


Error Message Text Error occurred while executing the schedule job for creating HANA snapshot with HTI.

Explanation Error occurred while executing the schedule job for creating HANA snapshot with HTI.

Recommended Action


E5900086


Error Message Text

Error occurred while executing the schedule job for updating storage cache.



Explanation Error occurred while executing the schedule job for updating storage cache.

Recommended Action



MK-92ADPTR111-01

Hitachi Data Systems

Corporate Headquarters 2845 Lafayette Street

Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000

www.hds.com [email protected]

Asia Pacific and Americas

2845 Lafayette Street Santa Clara, California 95050-2627

U.S.A. Phone: 1 408 970 1000

[email protected]

Europe Headquarters

Sefton Park Stoke Poges Buckinghamshire SL2 4HD

United Kingdom Phone: + 44 (0)1753 618000

[email protected]

http://www.hds.com/




Documents

Hitachi Storage Adapter for the SAP HANA Cockpit · 12 Hardware and Software Requirements Hitachi Storage Adapter for the SAP HANA Cockpit v01.1.0 User’s Guide Supported Hardware