Enterprise Storage Integrator for SAP Landscape ... This user guide describes how to use Dell EMC...

Enterprise Storage Integrator for SAPLandscape Management Storage AdapterVersion 5.0

User Guide300-014-914

REV 09

Copyright © 2013-2017 Dell Inc. or its subsidiaries. All rights reserved.

Published January 2018

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND

WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.

Published in the USA.

Dell EMCHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.DellEMC.com

2 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

Preface 5Purpose........................................................................................................6Audience...................................................................................................... 6Scope........................................................................................................... 6Related documentation................................................................................ 6Conventions used in this document.............................................................. 6Where to get help......................................................................................... 7Your comments.............................................................................................7

Enterprise Storage Integrator for SAP Landscape ManagementOverview 9Executive summary..................................................................................... 10Product overview........................................................................................10Installation overview.................................................................................... 11

Prerequisites 13Solution prerequisites..................................................................................14Prerequisites for cloning SAP instances in a Windows OS...........................17Prerequisites for cloning SAP instances in an AIX OS................................. 19Setting properties for vSphere environments.............................................20

Installing and Configuring VMware Virtual Hosts 21Enabling the disk UUID in a VMware virtual environment............................22

Configuring the VMDK so that it can respond to a SCSI inquiry.....22Enabling the VMware tools installation option for the virtual machine........ 24

Verifying the VMware Tools installation.........................................24Verifying the SG utility and library package files installation.......... 25

Virtual host configuration script................................................................. 26Configuring VMware virtual machines........................................................ 26Commands for managing the vCenter server..............................................27

Installing ESI for SAP Landscape Management 29Choosing to install the Windows EHAC server............................................30Downloading ESI for SAP LaMa..................................................................30Installing the ESI for SAP LaMa storage adapter........................................ 30

SAP LaMa-ESI Integration: System Provisioning Operations andProcesses 33Adding an ESI storage manager..................................................................34Caching storage information from SAP systems.........................................34Removing SAP systems from a host...........................................................36Mounting SAP systems to a host................................................................37Relocating the SAP system........................................................................ 40

Accelerating relocation operations in vSphere virtual environments..41

SAP LaMa system provisioning prerequisites............................................. 42

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

CONTENTS

Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide 3

Managing snapshots...................................................................................44Creating a snapshot.......................................................................44Verifying Oracle redo logs..............................................................45Creating an online snapshot...........................................................46Viewing snapshots......................................................................... 49Removing a snapshot.....................................................................49

SAP LaMa System Provisioning Processes: System Clone, Copy, andRefresh...................................................................................................... 50

Configuring SAP target servers......................................................51Managing SAP LaMa system provisioning processes with full clones...................................................................................................... 52Creating a clone.............................................................................52Creating a clone from a snapshot.................................................. 54

Destroying volumes.................................................................................... 55Destroying partially provisioned systems....................................................55

Troubleshooting 57Troubleshooting......................................................................................... 58Known limitations and problems................................................................. 59

Chapter 6

CONTENTS


Preface

As part of an effort to improve its product lines, Dell EMC periodically releasesrevisions of its software and hardware. Therefore, some functions described in thisdocument might not be supported by all versions of the software or hardwarecurrently in use. The product release notes provide the most up-to-date informationon product features.

Contact your Dell EMC technical support professional if a product does not functionproperly or does not function as described in this document.

Note

This document was accurate at publication time. To ensure that you are using thelatest version of this document and the release notes, go to Dell EMC Online Support.

Preface 5

http://support.emc.com

PurposeThis user guide describes how to use Dell EMC™ Enterprise Storage Integrator (ESI)for SAP Landscape Management.

AudienceThis user guide is for Dell EMC personnel, partners, and customers. The intendedaudience is an SAP Landscape Management (SAP LaMa) user who wants to manageshared file or block storage by using ESI for SAP LaMa.

ScopeThis user guide is intended to provide an overview of ESI for SAP LaMa and its use inthe SAP LaMa environment. Topics covered include:

l Prerequisites

l Installation, configuration, and storage management procedures

l Troubleshooting information

Related documentationThe following documents, located on Dell EMC Online Support or on EMC.com,provide additional relevant information. Access to these documents is based on yourlogin credentials. If you do not have access to the following documents, contact yourDell EMC representative:

l Enterprise Storage Integrator for SAP Landscape Management Administrator Guide

l Enterprise Storage Integrator for SAP Landscape Management Release Notes

Conventions used in this documentDell EMC uses the following conventions for special notices:

NOTICE

NOTICE is used to address practices not related to personal injury.

Note

A note presents information that is important, but not hazard-related.

Dell EMC uses the following type style conventions in this document:

Table 1 Typographical conventions

Bold Used for names of interface elements, such asnames of windows, dialog boxes, buttons,fields, tab names, key names, and menu paths(what the user specifically selects or clicks).

Preface


Table 1 Typographical conventions (continued)

Italic Used for full titles of publications referencedin text.

MonospaceUsed for:

l System output, such as an error messageor script

l System code

l Path names, filenames, prompts, andsyntax

l Commands and options

Monospace italicUsed for variables.

[ ] Square brackets enclose optional values.

| Vertical bar indicates alternate selections —the bar means “or.”

{ } Braces enclose content that the user mustspecify, such as x or y or z.

... Ellipses indicate nonessential informationomitted from the example.

Where to get helpYou can obtain Dell EMC support, product, and licensing information as follows.

Product informationFor documentation, release notes, software updates, or information about Dell EMCproducts, go to Dell EMC Online Support.

Technical supportGo to Dell EMC Online Support and click Service Center. You will see several optionsfor contacting Dell EMC Technical Support. To open a service request, you must havea valid support agreement. Contact your Dell EMC sales representative for detailsabout obtaining a valid support agreement or with questions about your account.

Your commentsYour suggestions help us continue to improve the accuracy, organization, and overallquality of the user publications. Send your opinions of this document to:

Send your comments about this document to Feedback.

Preface

Where to get help 7



mailto:[email protected]?subject=Enterprise%20Storage%20Integration%20for%20SAP%20Landscape%20Management%20User%20Guide%20P/N%20300-014-914

Preface


CHAPTER 1

Enterprise Storage Integrator for SAPLandscape Management Overview

This chapter presents the following topics:

l Executive summary.............................................................................................10l Product overview............................................................................................... 10l Installation overview............................................................................................11

Enterprise Storage Integrator for SAP Landscape Management Overview 9

Executive summaryESI for SAP LaMa is a software adapter that integrates Dell EMC storage with SAPLaMa. Administrators can use SAP LaMa to manage SAP system copies for non-production testing and development, using the SAP Clone, Copy, Refresh, andRelocate functions. Because SAP environments can have hundreds of testing anddevelopment systems, automating management of SAP system copies by usingtrusted storage-based cloning, saves significant time and effort, reducing the TotalCost of Ownership (TCO) of an SAP Landscape.

ESI for SAP LaMa has the following components:

l ESI for SAP LaMa storage adapter, which is deployed as a storage manager in SAPLaMa

l Enterprise High Level Storage (HLS) Administration Console (EHAC), which is aweb service layer that administrators can use to manage users, storage systems,vCenter servers, Dell EMC Common Object Manager (ECOM) servers, and accesscontrol

ESI for SAP LaMa 5.0 includes support for SAP instance file systems based on block,file, or both block and file, combined on the same SAP system that is monitored bySAP Landscape Management 3.0.

Note

The SAP installation requires that the SAP NetWeaver /sapmnt/SIDand /usr/sap/trans global file systems are based on Network File System (NFS)file systems. This requirement is necessary because the file systems must be sharedacross all the instances of an SAP system that is configured in a distributed or high-availability architecture. On SAP HANA scale-out systems, the /hana/shared/SIDfile system must be based on NFS and shared across all of the HANA nodes.

ESI for SAP LaMa also supports physical and virtual hosts on:

l Dell EMC VMAX3™ arrays that use service level objectives (SLO) storageprovisioning

l Dell EMC XtremIO™ all-flash arraysl Dell EMC VNX™ and VMAX™ block storage systems, which can be used in

combination with VMAX3 eNAS file storage and VNX file storage, respectivelyl Dell EMC VPLEX™ 5.5 systems

Note

Refer to the Enterprise Storage Integrator for SAP Landscape Management ReleaseNotes for a complete list of all new features and changes.

Product overviewThe ESI for SAP LaMa storage adapter is distributed as a Java Enterprise Archive(EAR) file that complies with SAP LaMa specifications.

The storage adapter, which is shown in the following figure, runs in the SAPNetWeaver Java Stack with the SAP LaMa add-on installed.

You can use EHAC to manage one or more Dell EMC file and block storage systems.The Java ESI storage adapter (or ESI storage plug-in) for SAP LaMa communicates

Enterprise Storage Integrator for SAP Landscape Management Overview


with the EHAC server to enable the management of one or more Dell EMC file andblock storage systems, and to enable storage provisioning as part of SAP LaMasystem Clone, Copy, Refresh, and Destroy processes. These processes are also knownas SAP LaMa system provisioning processes.

Figure 1 ESI for SAP LaMa storage adapter

Note

Solutions Enabler is not required for NFS-based file systems.

Installation overviewThe following table contains an ESI for SAP LaMa installation overview with the high-level steps that are required to implement SAP LaMa with ESI for SAP LaMa.

Table 2 Installation overview

Steps Chapter

Verifying the prerequisites 2

Installing and configuring VMware vSphere virtual hosts 3

Installing ESI for SAP LaMa components 4

l Configuring ESI for SAP LaMa adapter in SAP LaMa 5


Installation overview 11

Table 2 Installation overview (continued)

l Running provisioning operations and processes for SAP systems

Troubleshooting 6



CHAPTER 2

Prerequisites


l Solution prerequisites......................................................................................... 14l Prerequisites for cloning SAP instances in a Windows OS.................................. 17l Prerequisites for cloning SAP instances in an AIX OS......................................... 19l Setting properties for vSphere environments.................................................... 20

Prerequisites 13

Solution prerequisitesBefore you install the Enterprise HLS Administration Console (EHAC) and the ESI forSAP LaMa storage adapter, follow these steps:

1. Consult your storage administrator to configure and document the zoning andmasking of the SAP systems based on the Dell EMC storage systems before theconfiguration, as described in the Enterprise Storage Integrator for SAP LandscapeManagement Administrator Guide. The document is available from Dell EMC OnlineSupport.

Note

You must already have login credentials. If you do not, register at Dell EMC OnlineSupport.

2. Install and configure SAP LaMa 3.0 as described in the SAP LaMa 3.0, EnterpriseEdition Support Package 4 in the SAP Help Portal page.The following table lists the required SAP NetWeaver Java Stack and SAP LaMaminimum software versions for the installation.

Software Minimum softwareversion

Installed on

SAP NetWeaver Java Stacka 7.5 SP04 or later SAP LaMa server

SAP LaMab 3.0, SP04 SP2 (Thisresolution is for the end-usercomputer running the webbrowser that connects to theSAP LaMa GUI.)

SAP LaMa server

a. Get the latest version from SAP ONE Support Launchpad. Click Installations andUpgrades > Browse By Category > SAP NetWeaver andcomplementary products > SAP NetWeaver > SAP NETWEAVER 7.x >Installation and Upgrade > Select the OS and database.

b. Get the latest version from SAP ONE Support Launchpad. Click Installations andUpgrades > Browse By Category > SAP NetWeaver andcomplementary products > SAP LANDSCAPE VIRT MGT ENT > SAPLANDSCAPE VIRT MGT ENT 3.0 > INSTALLATION AND UPGRADE .

3. Install Dell EMC Solutions Enabler 8.3 on the SAP hosts with block-based filesystems to be managed by SAP LaMa by using the instructions in the SolutionsEnabler Version 8.3 Installation and Configuration Guide from Dell EMC OnlineSupport.

4. Deploy the EHAC appliance as described in the Enterprise Storage Integrator forSAP Landscape Management Administrator Guide, which is available from Dell EMCOnline Support.

5. From the following prerequisite software table, install and configure SolutionsEnabler, the SAP Host Agent, and browser prerequisite software on the SAPsystem hosts that SAP LaMa 3.0 will manage.

Prerequisites


https://support.emc.com




https://help.sap.com/viewer/c337eb50b9084db6a5207afda95efc19/3.0.3.0/en-US

https://launchpad.support.sap.com/#/softwarecenter


https://support.emc.com/docu78907_Solutions_Enabler_8.3.0_Installation_and_Configuration_Guide.pdf?language=en_US&language=en_US




Table 3 Prerequisite software

Software Minimum softwareversion

Installed on

Solutions Enablera 8.4.0.18 All SAP hosts with block-based file systems

SAP Host Agentb 7.21 with the latest patch All SAP hosts

SAP Adaptive Extensions 1.0 All SAP hosts

Browser Internet Explorer 11 (youcan use other browsers,also)

User desktop with aminimal display resolutionof 1280x1024

a. Download Solutions Enabler from the Dell EMC Online Support Downloads for SolutionsEnabler page.

b. Get the latest version from SAP ONE Support Launchpad. Click Installations andUpgrades, browse your company's download catalog, type in the SAP host agent, andthen select the latest Host Agent for the required OS.

6. Complete all of the SAP LaMa configuration steps before you configure theinfrastructure and the storage managers. These configuration steps are describedin SAP Landscape Management 3.0, Enterprise Edition Configuration and DeploymentInformation in the SAP Help Portal.

7. Install and configure the latest patch for SAP Host Agent 7.21 according to thesteps that are described in Configuring SAP Host Agent on the SAP Help Portal.

8. When working with SAP LaMa and ESI storage-based cloning, the SAP instancefile systems are cloned for using ESI cloning technologies at the storage level. Forthat reason, verify that the SAP instance-specific file systems of your SAPsystems are configured as follows:

l The SAP instance file systems (\usr\sap\SID, oracle\SID\sapdata1,oracle\SID\sapdata2, for example) must be stored in dedicated LUNs/datastores that are separated from the operating system (OS) disk of thesource hosts.

Prerequisites

Solution prerequisites 15

https://support.emc.com/downloads/2071_Solutions-Enabler

https://support.emc.com/downloads/2071_Solutions-Enabler


https://help.sap.com/viewer/e7dead4286c545808b3bd24feee7448c/3.0.3.0/en-US/4e57e8322ace4dabe10000000a42189b.html

https://help.sap.com/viewer/lama_help/4e56df6600c74dabe10000000a42189b.html

Note

n Do one of the following:

– Install and configure the OS, SAP Host Agent, SAP Adaptive Extensions,and Solutions Enabler for the existing physical and virtual target serversin advance.

– Deploy new target hosts from VMware vSphere pre-configuredtemplates containing the OS, SAP Host Agent, SAP AdaptiveExtensions, and Solutions Enabler installed and configured.

n For vSphere virtual machines, the OS disk must be in a dedicated VMwarevirtual machine disk (VMDK) and stored in a shared datastore.

n For physical systems, the OS must use local disks or dedicated LUNs thatwill not be cloned by ESI for SAP LaMa.

n The SAP instance file systems must have dedicated LUNs/datastoresseparated from the OS LUN/datastore. This requirement enables SAP LaMato clone LUNs, with or without datastores at the storage level, that containonly the SAP instance-specific file system mount points. It avoidsduplication of the OS file systems from the source system.

n See Adaptive Computing Concept , also called Adaptive Design, for moreinformation about the design of the source SAP system that follows theSAP recommendations for storage-based cloning.

l If you plan to use the SAP LaMa System Relocation operation, ensure that theSAP source system instances are installed and configured according to theSAP Adaptive Computing concept, also known as SAP Adaptive Design or SAPApplication Virtualization. This concept requires that independent virtual IPaddresses, virtual hostnames, and dedicated instance file systems be installedin a shared central storage system. For more information, refer to AdaptiveComputing Concept on the SAP Community page.

l To facilitate SAP, VMware, and Dell EMC support in a VMware environment,use the following troubleshooting best practices:

n For a specified SAP system, document the vSphere virtual machines that ituses and document which SAP instance file systems are stored in whichdatastores.

n Document the SAP, VMware, and Dell EMC environments for each virtualmachine in detail. Include the masking views being used, physical storagedevice IDs, datastore names, virtual machine settings, SCSI controllernumbers, and ports used by each hard disk. Also, include the guest OSdevice IDs, volume groups, logical volumes, and file systems used for eachdatastore. Use Dell EMC Virtual Storage Integrator (VSI), which is a freeproduct, to collect most of this information.

9. In a VMware environment, if you intend to use VMware VMDKs or raw devicemapping disks (RDM), you must also install and configure the prerequisitesoftware:

Table 4 Prerequisite software for vSphere virtual servers

Software Software version

VMware vCenter Server 5.5 U3b, 6.0U3, or 6.5.

Prerequisites


https://archive.sap.com/documents/docs/DOC-8725

https://help.sap.com/viewer/lama_help/737a99e86f8743bdb8d1f6cf4b862c79.html



Table 4 Prerequisite software for vSphere virtual servers (continued)

Software Software version

VMware Tools Use the version that is bundled with the ESXiserver. This software is preinstalled on anewer OS, such as SLES 12 and RHEL 7.2.

When using virtual hosts:

l Multiple paravirtual SCSI (PVSCSI) controllers are supported, which conformsto SAP and VMware best practices. See Configuring disks to use VMwareParavirtual SCSI (PVSCSI) adapters (1010398) in the VMware KnowledgeBase.

l If you use VMware vSphere in a Linux OS, see SAP note 1122388: VMwarevSphere configuration guidelines on the SAP ONE Support Launchpad.

l If you use VMware vSphere in a Windows environment, see SAP note 2161991: VMware vSphere configuration guideline on the SAP ONE Support Launchpad.

l Configure the VMware Virtual Machine Advanced Parameterdisk.enableUUID using the vSphere Web Client. For more details, see Installing and Configuring VMware Virtual Hosts on page 21.

Note

Plan for downtime to add the advanced disk.enableUUID parameter to allSAP systems based on vSphere virtual machines. To install VMware Tools,refer to Installing and Configuring VMware Virtual Hosts on page 21.

l Configure the Virtual Hosts details by running theConfigure_Virtual_v2.sh script that Dell EMC provides. Refer to Installing and Configuring VMware Virtual Hosts on page 21 for details.

Note

For SAP systems with NAS mount points, you must have 1:1 mapping between theNAS file system and the NFS export on the array. Multiple NFS exports on a singleNAS file system (for example, exporting the subdirectories on a single NAS file systemto be mounted to hosts) is not supported.

Prerequisites for cloning SAP instances in a Windows OSThe ESI for SAP LaMa storage adapter has the following prerequisites for cloning SAPinstances in a Windows OS.

l Use only dynamic disks.

l For spanned volumes, you can use multiple dynamic disks, but ensure that disksthat belong to one volume are not shared with another volume.

l Mount volumes only as a mount path on the C drive and do not use other driveletters such as F, G, and H.

Prerequisites

Prerequisites for cloning SAP instances in a Windows OS 17

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398

https://launchpad.support.sap.com/#/notes/2161991



Note

n Use the Disk Management utility and select the Mount Path option. Forexample, the following figure shows SAP mount points (junctions or soft links)mounted as a Windows mount path on the C drive, with MC1 mounted on disk 5in the C:\MC1 folder.

n NAS/NFS file system mount points for SAP instances are not supported bySAP LaMa.

Figure 2 Managing Windows disks

Note

For more information about the design of the source SAP system, which follows theSAP recommendations for storage-based cloning, see SAP LVM Best Practices forSystem Provisioning in the SAP Community page. For additional requirements forWindows network-attached storage (NAS) environments, see Landscape Preparationin the SAP Help Portal.

l Install Solutions Enabler 8.3 on the SAP hosts running SAP systems to bemanaged by SAP LaMa using the instructions in the Solutions Enabler Version 8.3Installation and Configuration Guide in Dell EMC Online Support.

l Install and configure the latest patch for SAP Host Agent 7.21 by using theinstructions in Configuring SAP Host Agent in the SAP Help Portal.

l After you install and configure Solutions Enabler 8.4 and SAP Host Agent 7.21,integrate the Enterprise Storage Library for SAP Adapter (ELSA) , which isdeployed inside Solutions Enabler, with the SAP Host Agent:

Prerequisites


https://scn.sap.com/docs/DOC-56593

https://scn.sap.com/docs/DOC-56593

http://help.sap.com/saphelp_lamaent30/helpdata/en/ad/4e4e34efd54a5d885daf73885c520f/frameset.htm



http://help.sap.com/saphelp_lvment21/helpdata/en/4e/56df6600c74dabe10000000a42189b/content.htm

1. Copy the libsapacosprep_emc.dll file from C:\ProgramFiles\EMC\SYMCLI\shlib\apps\sap to the C:\Program Files\SAP\hostctrl\exe directory.

2. Add to the system environment variable path the value as C:\ProgramFiles\EMC\SYMCLI\bin.

l Run the Virtual Disk Service from services.msc.

l To enable cloning:

n Install the Oracle database software locally on drive C of the target host.

n After you manually install Oracle, check whether the following services arelisted in services.msc. If a service is not listed, copy the missing databaseservice entries from the source to the target machine.SAP recommends the following services for the Oracle client:

– Microsoft SQL Server– OracleJobSchedulerMK1– OracleMK111203ClrAgent– OracleMK111203TNSListener– OracleMTSRecoveryService– OracleServiceMK1– OracleVssWriterMK1

Note

MK1 is the System ID (SID) of the SAP instance and registry entries are basedon the SID.

l Turn off the domain firewall for retrieving the HBA properties.

l Configure port 443 to enable an outgoing OS connection to the physical host busadapter (HBA) on the server. Run the steps from SAP LaMa Configuration >Systems > Instance > Network isolation to enable Solutions Enabler tocommunicate with the ESXi physical HBA. This step is for collecting properties forthe SAP LaMa storage-based system System Clone, System Copy, and SystemRefresh provisioning processes. For more information, see Configuring OutgoingConnections for System Isolation in the SAP Help Portal.

Prerequisites for cloning SAP instances in an AIX OSFor SAP systems running on an AIX OS, configure all SAP file systems to use INLINElogging, which is a requirement for Solutions Enabler and Storage Resource Manager(SRM) operations.

View the contents of the/etc/filesystems file, which shows Log = INLINE foreach mount point if the file system is configured to use INLINE logging.

Note

If any SAP file systems are not configured to use INLINE logging, move the contentsof each file to a new file system that is configured to use INLINE logging. Converting afile system from using outline logging to inline logging corrupts its data. See IBM note Conversion Between Inline and Outline JFS2 Filesystem Logs to verify this statement.

Prerequisites

Prerequisites for cloning SAP instances in an AIX OS 19

http://help.sap.com/saphelp_lvment21/helpdata/en/1b/10b0f9c9764450bc213e1b3574c803/content.htm#loio1b10b0f9c9764450bc213e1b3574c803

http://help.sap.com/saphelp_lvment21/helpdata/en/1b/10b0f9c9764450bc213e1b3574c803/content.htm#loio1b10b0f9c9764450bc213e1b3574c803

http://www-01.ibm.com/support/docview.wss?uid=isg3T1012989

The logname attribute must use the INLINE value to create a file system that usesINLINE logging.

For recommended commands and procedures to create a file system in an AIX OS, seethe AIX documentation. For more information about using the crfs command, see the crfs Command in the IBM Knowledge Center.

Setting properties for vSphere environmentsIn SAP systems that use vSphere HA with VMware vSphere vMotion and Dell EMCstorage arrays, all datastores that are used by SAP source systems must be visible ormasked to all ESXi hosts that are in the vSphere cluster.

Procedure

1. Create masking views for the individual servers with storage groups thatcontain only the dedicated devices that the individual servers need.

2. Create a separate masking view with a storage group that contains the shareddevices, a port group containing the applicable ports, and an initiator group thatcontains the initiator groups of each host that were created in the first step.

Note

For a description of cascaded initiator groups, refer to the EMC SolutionsEnabler Symmetrix Array Controls CLI Product Guide.

3. Optionally, set configuration properties to avoid steps to add or removevolumes from a masking view at the storage level during virtual-to-virtualrelocation operations. These settings save time during the virtual-to-virtualrelocation operation.

Prerequisites


https://www.ibm.com/support/knowledgecenter/en/ssw_aix_72/com.ibm.aix.cmds1/crfs.htm

http://www.emc.com/collateral/TechnicalDocument/docu46981.pdf

http://www.emc.com/collateral/TechnicalDocument/docu46981.pdf

CHAPTER 3

Installing and Configuring VMware Virtual Hosts


l Enabling the disk UUID in a VMware virtual environment................................... 22l Enabling the VMware tools installation option for the virtual machine................24l Virtual host configuration script.........................................................................26l Configuring VMware virtual machines................................................................26l Commands for managing the vCenter server..................................................... 27

Installing and Configuring VMware Virtual Hosts 21

Enabling the disk UUID in a VMware virtual environmentConfigure the virtual machine to force a VMDK respond to a SCSI inquiry from theguest OS to read the Vital Product Data (VPD) page.

Note

When a VMDK is created in a VMware ESXi virtual machine, it is stored in a datastore,which is a storage LUN formatted with a virtual machine file system (VMFS). A uniqueUUID is generated for each VMDK and kept in the virtual disk configuration file andvirtual machine configuration (.vmx) file.

VPD is a collection of configuration data that is associated with a particular set ofhardware or software. The VPD stores information such as engineering change levels.Often SCSI devices attached to a system provide VPD information.

By default, the VMware ESXi host does not respond to a SCSI inquiry from the guestOS to read the VPD that is associated with the virtual disk. However, SolutionsEnabler requires the VPD information that is associated with the VMDK.

Procedure

1. Add the disk.enableUUID advanced parameter set to TRUE in the virtualmachine (.vmx) configuration file.

2. Verify that the utility and library files are installed and available for the guestOS, as follows:

vmfs/volumes/5200af41-812305ce-812c-60735c68a5da/SAPSource/SAPSource_2.vmdk 1The unique ID associated with the virtual disk is shown as a line in thisconfiguration file:

ddb.uuid = "60 00 C2 91 f0 3d 87 83-33 72 4a 1a 7b ea 0a66"

Configuring the VMDK so that it can respond to a SCSI inquiryConfigure the VMDK to enable it to respond to a SCSI inquiry.

Procedure

1. Log in to the VMware ESXi server or log in to vCenter, which manages the SAPhost.

2. Select the SAP host virtual machine, power it off, and then select Edit virtualmachine settings, as shown in the following figure.



Figure 3 Configuring the VMDK

3. From the Virtual Machine Properties dialog box, select Options > General >Configuration Parameters as shown in the following figure.

Figure 4 Clicking Configuration Parameters

4. Click Add Row, as shown in the following figure.

5. Type the following details for the new row:

l Name = disk.enableUUIDl Value = TRUE


Configuring the VMDK so that it can respond to a SCSI inquiry 23

6. Click OK to save the new configuration parameters and then power on thevirtual machine.

Figure 5 Adding a new row

Enabling the VMware tools installation option for the virtualmachine

To enable VMware tools to be installed on a specified virtual machine, use theprocedure from How to install VMware Tools (1014294) in the VMware KnowledgeBase.

Note

Newer versions of Linux are provided natively with Open VM Tools (OVT), so it is notnecessary to install Linux manually on the hosts. For more information, see VMwaresupport for Open VM Tools (2073803) in the VMware Knowledge Base.

Verifying the VMware Tools installationVerify that VMware Tools have been successfully installed.

Procedure

1. Log in to the ESXi server with the vSphere or vCenter credentials.

2. Select VM > Summary.

3. In the General pane, as shown in the following figure, check that VMware Toolsis running.



https://kb.vmware.com/kb/1014294



Note

This figure shows the status of VMware Tools installed on an older operatingsystem. The page is different for virtual machines with newer guest operatingsystems that use OVT.

Figure 6 Checking that VMware Tools is running

Verifying the SG utility and library package files installationVerify that the Linux SG utility and library package files are installed on the SAP host.

Procedure

1. Log in as root to the guest OS of the SAP virtual machine.

2. Type the rpm -qa | grep sg3* command.

The SG utility and library package files are installed on the host if the sg3utils and sg3 utils-libs files are displayed.

3. If the files are not installed, do one of the following:

l Mount the ISO of the Linux OS installer.

l Download the binaries and install them on the host.

Note

You can type the rpm -qa command to find all rpm packages that are installedon the host.


Verifying the SG utility and library package files installation 25

Virtual host configuration scriptThe ConfigureVirtualHost_v2 script registers the virtual host inside theSolutions Enabler SYMAPI database.

The script does the following:

l Adds a vCenter entry to the Solutions Enabler SYMAPI database

l Deletes the vCenter entry that was previously added to the Solutions EnablerSYMAPI database

l Lists entries of the Solutions Enabler SYMAPI database

Solutions Enabler uses vCenter host connection information to gain access to thestorage array data. The script automatically performs the following operations:

l Updates the Solutions Enabler SYMAPI database with the vCenter IP address,username, and password by running the following command:

symcfg auth add -vmware -host <IP_Address> -username <UserName> -password <Password> -vmport 5988 -namespace vmware/vc

l Confirms that the vCenter certificate is available on the vCenter server at /etc/vmware/ssl and that the vCenter certificate file name is rui.crt.The script then copies the vCenter rui.crt certificate to the /var/symapi/config/ directory and renames it to viclient_cert.pem for use by SolutionsEnabler.

l Copies the virtual machine certificate to the following location:

/var/symapi/config/viclient_cert.peml Runs the discover command for Solutions Enabler to connect to the ESXi server

and gets details of the underlying storage array:

n /opt/emc/SYMCLI/bin/symcfg scan (VMAX and VNX)n /opt/emc/SYMCLI/bin/symcfg discover (VMAX, VPLEX, XtremIO)n /opt/emc/SYMCLI/bin/symcfg discover -clariion (VNX)

Configuring VMware virtual machinesDownload and run the ConfigureVirtualHost_v2 script to configure the virtualmachine.

Before you begin

Solutions Enabler must be installed and configured.

Procedure

1. Download the Configure_VirtualHost_v2.sh script from the Dell EMCOnline Support Storage Integrator for SAP Landscape Management page, andthen copy the script to both the source and target virtual machines.

2. Grant execute permission to the script:

chmod 755 Configure_VirtualHost_v2.sh



https://support.emc.com/products/28468_ESI-for-SAP-LVM

3. Collect the vCenter IP address, hostname, and login credentials of thededicated ESI for SAP LaMa user with admin rights to the vSphere cluster ofwhich the SAP virtual machine is part.

4. Enable the Secure Shell (SSH) on the ESXi server on which the virtual machineresides.

5. Run the script:

./Configure_VirtualHost_v2.sh

6. Type the v option to add the vCenter server IP and credentials to registervCenter in the Solutions Enabler database.

7. After you add vCenter, type the l option to list the vCenter details.

If vSphere HA restarts the virtual machine or if vMotion moves it to anotherESXi server, the Solutions Enabler SYMAPI database can still communicate aslong as vMotion is in the same vCenter domain. When the ESXi server on whichthe virtual machine is running changes, the HBA information that is retrieved bySolutions Enabler also changes. If necessary, perform these steps:

a. In SAP LaMa, go to Configuration > Hosts > Select Host > Edit > HostProperties.

b. Click Retrieve from Host in Host-Specific Storage Properties to updatethe HBA information inside SAP LaMa.

ESI dynamically updates this information before any storage-relatedoperation. Performing this step manually is only necessary to update theHBA information in the SAP LaMa GUI.

8. As a best practice, create a new user in vCenter with administrator rights to runall the ESI-required activities. Type a vCenter username that has theadministrative permission and password.

This best practice enables you to see the specific vCenter activities that are runby ESI for SAP LaMa on vCenter and when you go to Monitoring > Tasks inthe SAP LaMa GUI.

Commands for managing the vCenter serverOptionally, you can use the following commands to manage the vCenter server:

l To check which vCenter server is configured:

symcfg auth list -vmware

l To manually remove a vCenter server that is no longer running, but has an entryfrom the virtual machine Solutions Enabler SYMAPI database:

symcfg auth delete -host <IP Address> -user -namspace vmware/vc


Commands for managing the vCenter server 27

l To manually add a vCenter server entry on the Solutions Enabler SYMAPIdatabase of the virtual machine:

symcfg auth add -vmware -host <IP_Address> -username <UserName> -password <Password> -vmport 5988 -namespace vmware/vc

Note

l You must use the Configure_VirtualHost_v2.sh script on every SAP virtualmachine to be used with ESI for SAP LaMa.

l This script adds an entry for the vCenter server in the SYMAPI database of thevirtual machine.



CHAPTER 4

Installing ESI for SAP Landscape Management

This chapter presents the following topic:

l Choosing to install the Windows EHAC server................................................... 30l Downloading ESI for SAP LaMa......................................................................... 30l Installing the ESI for SAP LaMa storage adapter................................................30

Installing ESI for SAP Landscape Management 29

Choosing to install the Windows EHAC serverIf you choose to install the Windows-EHAC server, you must install the ESI WebService and ESI Deployment Console.

Because the ESI Web Service and ESI Deployment Console are installed andconfigured on the Linux-based EHAC virtual appliance, you only download them whenyou install the Windows-EHAC server.

Deploy the Linux-based EHAC virtual appliance as described in the Enterprise StorageIntegrator for SAP Landscape Management Administrator Guide, and then deploy the ESIfor SAP LaMa storage adapter.

Downloading ESI for SAP LaMaESI for SAP LaMa is distributed as a Java EAR file and can be downloaded from DellEMC Online Support.

You can download and use the ESI for SAP LaMa storage adapter and EHACseparately. This might be necessary if the user is not also the storage administrator.

Procedure

1. Go to the Downloads for Storage Integrator for SAP Landscape Managementpage.

2. Click Downloads to download the Storage Integrator for plug-in.

Installing the ESI for SAP LaMa storage adapterInstall the ESI for SAP LaMa storage adapter on the SAP NetWeaver Java stackserver where SAP LaMa is running. The ESI for SAP LaMa storage adapter must bedeployed inside the SAP NetWeaver Java Stack server where the SAP LaMa add-on isrunning.

Before you begin

SAP NetWeaver administrator privileges are required to run this step.

Note

Run the Telnet commands locally on the SAP LaMa server. Do not run the commandsremotely.

Procedure

1. Copy the esi_sap_lvm_plugin.5.0.x.ear file to the server by using atool such as FileZilla or WinSCP.

2. Log in to SAP Java Stack using the Telnet localhost 50008 administratorpassword, as shown in the following figure.



https://support.emc.com/downloads/28468_Storage-Integrator-for-SAP-Landscape-Virtualization-Management

Figure 7 Logging in to SAP Java Stack

3. Run the following command to determine if the adapter is already installed:

list_app | grep plugin4. Undeploy any older versions of the adapter by using the following command:

undeploy name=esi_sap_lvm_plugin.4.6.8.2 vendor=JavaEE5. Deploy the ESI for SAP LaMa storage adapter. For example:

deploy /Binaries/esi_sap_lvm_plugin.5.0.earversion_rule=all

6. Confirm that the ESI for SAP LaMa storage adapter was deployed, as shown inthe following figure.

Figure 8 Adapter is deployed


Installing the ESI for SAP LaMa storage adapter 31

CHAPTER 5

SAP LaMa-ESI Integration: System ProvisioningOperations and Processes


l Adding an ESI storage manager..........................................................................34l Caching storage information from SAP systems................................................ 34l Removing SAP systems from a host.................................................................. 36l Mounting SAP systems to a host....................................................................... 37l Relocating the SAP system................................................................................40l SAP LaMa system provisioning prerequisites..................................................... 42l Managing snapshots.......................................................................................... 44l SAP LaMa System Provisioning Processes: System Clone, Copy, and Refresh

...........................................................................................................................50l Destroying volumes............................................................................................55l Destroying partially provisioned systems........................................................... 55

SAP LaMa-ESI Integration: System Provisioning Operations and Processes 33

Adding an ESI storage managerSAP LaMa needs a storage manager to communicate with the underlying physicalstorage arrays where the SAP instance file systems are stored.

ESI and its associated libraries send queries to the storage system to manage relevantinformation, such as storage pools, mount paths, and snapshots, and provides SAPLaMa support for the system provisioning processes such as System Clone, SystemCopy, and System Refresh.

Procedure

1. Open the SAP Landscape Management GUI web page.

2. Type your username and password, and then click Log On.

3. Select Infrastructure > Storage Managers and click Add.

4. In the list of supported storage manager types, select Dell EMCCorp ESI forSAP NW LaMa and click Next.

5. Type the Basic Properties for the storage manager, as shown in the followingfigure.

a. In Label, type a name that identifies this storage manager.

b. Type the username and password of a registered EHAC user.The Enterprise Storage Integrator for SAP Landscape ManagementAdministrator Guide provides details. Only the storage arrays added by thisuser will be visible to the adapter on the SAP LaMa server.

c. In URL, type the IP address and port number of the EHAC server.

d. In Monitoring Interval (Seconds), add the monitoring interval for storagecaching while configuring the adapter in SAP LaMa 3.0.

6. To test the configuration before adding it, click Test Configuration on thebottom of the page.

7. After you receive confirmation that the configuration is correct, click Next.

8. Click Save.

The storage manager is installed and a list of storage systems assigned to thisuser appears in the Storage Systems section of the SAP LandscapeManagement window. Click Reload Storage Systems to see an updated list ofstorage systems assigned to this user.

9. Confirm that the list of supported storage shows the added storage manager asESI version 5.0.x and the ELSA as version 8.4 or later.

Caching storage information from SAP systemsWith SAP LaMa 3.0, you can use the storage cache feature to retrieve storageinformation from VNX, VMAX, VPLEX, and XtremIO storage arrays. This featurespeeds up the storage-related operations.

The cache information also shows the volume group and logical volume information. uses the cached information during the system provisioning processes, such as the:

l System Clone, System Copy, and System Refresh processes

SAP LaMa-ESI Integration: System Provisioning Operations and Processes


l Mass Unprepare, Mass Prepare, and System Relocation operations

The following figure shows a VMAX3 eNAS storage cache tree with block storagesystem, pool, and volume details at Advanced Operations > Storage > StorageOverview. The same format is used for VMAX and VNX storage arrays.

Figure 9 Storage caching for VNX and VMAX block storage arrays

The following figure shows storage caching for XtremIO and VNX file storage arrays.

Figure 10 Storage caching for XtremIO and VNX file storage arrays

The following figure shows storage caching for volume groups on a host. Duringcloning, the volume group information about the SAP hosts is retrieved and populatedin the Storage tab.


Caching storage information from SAP systems 35

Figure 11 Storage caching for volume groups on a host

Removing SAP systems from a hostUse the Mass Unprepare operation to remove SAP systems from a specified host.

The operation stops the running SAP system, and unmounts and detaches the SAPinstance file systems and volumes from the OS and the host. Use this operation whenyou want to run OS maintenance or hardware upgrades on hosts, where you canprepare the system again after the maintenance activities are completed. You canremove the SAP system from the specified host indefinitely or move the SAP instanceusing the SAP LaMa System Relocation operation to prepare to another host.

Procedure

1. Click Infrastructure > Storage Managers to ensure that Storage Manager wasadded.

2. Click Operations > Storage to confirm that all volumes and volume groupinformation are cached.

3. If all volumes and volume group information are not cached, click MonitoringData to cache the information.

4. Click Operations > Hosts to check that all source hosts are in a correct state,with hosts assigned to their respective instances.

5. Ensure that storage caching has been updated in Storage > Storage Overviewand that the NFS export files for this operation are listed; otherwise theoperation fails.

6. Select Operations > Systems > Mass Operations, then select the files for theUnprepare operation, and then click Execute, as shown in the following figure.

Note

The operation fails if any service or program is running and locking the SAPinstance-specific file systems on the SAP host where the Mass Unprepareoperation is being executed. For example, a user, who is logged in to the hostthorough SSH, in one of the directories that belongs to the mount point beingunmounted, can cause the Unprepare operation to fail.



Figure 12 Selecting files and starting the Mass Unprepare operation

7. Click Monitoring > Logs, select a log, and view its details in the Detailswindow.

Note

Logs show the details and status of the operation and show details of allactivities performed by each component in each operation step.

Mounting SAP systems to a hostUse the Mass Prepare operation to mount the SAP instance-specific file systems to anew target host during the Prepare steps of the System Relocation operation, andduring the System Clone, System Copy, and System Refresh processes.

Before you begin

All source systems must be in an unprepared state without any mounted volumes.

In a VMware environment, before you can use Prepare, Unprepare, Relocation, orClone, you must add all of the SAP source and target ESXi hosts to the EHACdatabase by using the EHAC configuration console. For more information, see theEnterprise Storage Integrator for SAP Landscape Management Administrator Guide.

Procedure

1. Click Infrastructure > Storage Managers, and then perform the followingsteps:

a. Confirm that the storage manager was added with the correct EHAC usercredentials.

b. Test the storage manager connection and retrieve all arrays associated withthe EHAC user.

c. Confirm that all arrays associated to the SAP system are assigned to theEHAC user. If the arrays are not assigned, use the EHAC administrationconsole to assign the required access.


Mounting SAP systems to a host 37

2. Click Advanced Operations > Storage.

Note

If the storage information is not cached, click Monitoring Data to cache theinformation.

3. Click Advanced Operations > Hosts and verify that all source hosts are in acorrect state, with no hosts assigned to their respective instances, as shown inthe following figure.

Figure 13 Checking that hosts are in a correct state

4. Click Advanced Operations > Systems > Mass Operations and perform on ofthe following steps:

l Click Auto Assign

l Manually select the host from the available hosts, as shown in the followingfigure.

5. Select the instances and click Execute.

Figure 14 Selecting a host during a Mass Prepare operation



Note

l During the Prepare operation on VMware environments, ESI performs thefollowing steps for the SAP system instance-specific storage volumes:

n Adds storage volumes to their respective storage groups on the storagearray

n Rescans, discovers, attaches and mounts datastores to the ESXi host

n Adds VMDKs that are associated with the datastores to the virtualmachine

l SAP LaMa then calls the SAP Host Agent and runs the following steps:

n The SAP instances file systems are mounted by the SAP Host Agentsapacosprep command, which calls the ELSA(libsapacosprep_emc.so) that is part of Solutions Enabler software.

n The SAP instances are then started in order.

l Detailed ESI for SAP LaMa logs that confirm the results of the operation aregenerated in the configured {WILDFLY_HOME}/standalone/log folderin the EHAC server.

l Detailed SAP Host Agent logs that confirm the results of the operation aregenerated in the /usr/sap/hostctrl/work directory in the SAPhost.

6. Click Monitoring > Logs and select a log to view its details in the Detailswindow, as shown in the following figure.

Note

Logs show the details and status of the operation and show details of allactivities performed by each component in each operation step.


Mounting SAP systems to a host 39

Figure 15 Viewing log details after the Mass Prepare operation

Relocating the SAP systemThe SAP System Relocation operation enables the SAP system to be moved from anexisting host to another host, which is previously discovered and configured on SAPLaMa.

Before you begin

If you are relocating an SAP instance of an SAP system, the SAP system must beinstalled as Adaptive Enabled.

ESI for SAP LaMa supports all relocation options:

l Physical-to-physical relocation (P2P)

l Physical-to-virtual relocation (P2V), which is supported for physical volumescopied to vSphere using pRDM disks on the target

l Virtual-to-virtual relocation (V2V)

l Virtual-to-physical relocation (V2P), which is only supported for vSphere virtualmachines that use pRDM disks to be copied to physical volumes

Procedure

1. Click Infrastructure > Storage Managers, and then do the following:

l Ensure that the storage manager is added with EHAC user credentials.

l Test the storage manager connection and retrieve all arrays associated withthe EHAC user.

l Ensure that all arrays associated to the SAP system are assigned to theEHAC user.

l If arrays are not assigned, use the EHAC configuration console to getaccess.



2. Click Advanced Operations > Storage, and confirm that all volumes andvolume group information is cached.

Note

If the information is not cached, click Monitoring Data to cache it.

3. Click Operations > Hosts and confirm that all source hosts are in a correctstate, which is indicated by the green icon next to the host names.

4. Click Operations > Systems > Mass Operations, and then select MassRelocate All in State running.

5. Click Auto Assign or manually select the host from the listed hosts, as shown inthe following figure.

Figure 16 Performing a System Relocation

WARNING

In Linux/Unix systems, SAP does not persist in the changed mount optionsof the relocated system, but only uses it once during the Prepare step ofthe System Relocation operation. For that reason, any further operationson the relocated system require refreshing the export path entries in SAPLaMa. Changes are reflected in SAP LaMa only if the SAP LaMaadministrator clicks Retrieve Mount List for the relocated system atConfiguration > System > Select the instance > Edit > Mount Points.

Accelerating relocation operations in vSphere virtual environmentsFor VMware cluster-based virtual environments, ESI for SAP LaMa Version 5.0includes configuration properties that the storage administrator sets on the EHACserver before you perform ESI for SAP LaMa system relocation operations to provideeasy and efficient relocation of SAP systems from source hosts to target virtual hosts.These configuration properties save time during virtual-to-virtual relocation operationsby avoiding the storage layer operations of unmasking and masking LUNs to ESXihosts.

ESI for SAP LaMa supports System Relocation, Unprepare, and Prepare operations onvSphere cluster environments without these configuration properties. However, to


Accelerating relocation operations in vSphere virtual environments 41

complete these operations in considerably less time, add the following configurationproperties to ESI_application.properties, which is available in the WildFlyHome directory:

l UnprepareWithNoVolumes=Truel PrepareWithNoVolumes=TrueUse these configuration properties only during a Mass Unprepare, Prepare, or virtual-to-virtual (V2V) System Relocation operation in a vSphere cluster-based environment.

NOTICE

For all other operations, such as System Clone, System Copy, System Destroy, andSystem Refresh, use the default values for the configuration properties:

l UnprepareWithNoVolumes=Falsel PrepareWithNoVolumes=False

SAP LaMa system provisioning prerequisitesComplete the prerequisites and configuration steps in this section before you managesnapshots and clone a system.

1. Create a masking view for each target. ESI for SAP LaMa discovers each maskingview and adds the SAP instance-relevant storage volumes to the first availablemasking view that it finds. This discovery process makes the volume available tothe target server. The operation fails if no masking views are found.

Note

“Masking view” is the term used for VMAX. This is equivalent to “storage groups”for VNX and “storage views” for VPLEX. For XtremIO, create the initiator groupsfor the target hosts ahead of time for System Clone and System Copy.

2. Ensure that you have appropriate access rights to the storage pool that you selectand the storage pool has available space that is at least equal to the size of thesource file system.

3. Confirm that you have appropriate access rights to the storage pool that youselect. The storage pool must have available space that is at least equal to the sizeof the source volumes.

4. Run all the SAP LaMa configure hosts steps:

l Install the SAP Host Agent on all SAP source and target virtual machines andinstall Solutions Enabler.

l Create a symbolic link in the SAP Host Agent directory pointing to ELSA.

l For Linux environments, run the following command:ln -s /opt/emc/SYMCLI/shlib/apps/SAP/libsapacosprep_emc.solibsapacosprep_emc.so

l For AIX environments, run the following command:ln -s /opt/emc/SYMCLI/shlib/apps/SAP/libsapacosprep_emc.olibsapacosprep_emc.o



l For Windows environments, refer to Prerequisites for cloning SAP instances ina Windows OS on page 17.

5. Verify and configure all of the SAP LaMa Setup menu tabs, especially the timeoutfor operations involving SAP instances operations. This will avoid timeout ofSystem Clone, System Copy, and System Refresh processes.

6. Configure the SAP LaMa Infrastructure menu tabs, especially the Network, UserManagement, Name Management, and Storage Managers configuration.See SAP LaMa Infrastructure Configuration instructions on the SAP LandscapeManagement 3.0, Enterprise Edition page in the SAP Help Portal, and then go toConfiguration and Deployment Information > Landscape Configuration >Managing System Landscapes > Provisioning Systems.

7. Configure the SAP LaMa Configuration menu Host tabs to discover and add thesource and target SAP virtual machines, networks, and HBAs.

Note

l In a VMware environment, the HBAs must match HBAs of the ESXi serverwhere the virtual machine is running.

l To view the HBA ESXi details in a vSphere client, click ESX host > Go toconfiguration > Select Storage Adapters. The details list all the ESXi HBAsand you can check for the Fibre Channel-type HBAs

l You can also retrieve HBA details on a host by running the following SYMCLIcommand:

/opt/emc/SYMCLI/bin/syminq hbaIf this command does not work, there is a Solutions Enabler configuration issue.Review the previous configuration steps in Installing and Configuring VMwareVirtual Hosts on page 21.

8. Configure the Systems tab in the SAP LaMa Configuration menu to discover andadd the SAP instances to be managed by SAP LaMa:

a. Configure all the SAP settings to allow System Clone, System Copy, SystemRename, and System Refresh processes. See SAP LaMa mount pointsinstructions on the SAP Landscape Management 3.0, Enterprise Edition page inthe SAP Help Portal.

b. Configure the network isolation settings to allow open communication at alltimes with the ESXi hosts, the EHAC server, and any central NFS, DomainName System (DNS), and Lightweight Directory Access Protocol (LDAP)servers being used by the SAP LaMa source and target systems. In addition toVMware, this can also be configured with other environments, such as bare-metal or IBM AIX logical partition.

c. Configure the mount points for each of the instances associated with a sourcesystem.

9. In the SAP LaMa Advanced Operations menu, run all the instances and hostsvalidations and confirm that they are green to show that the hosts and instancesare in a correct state.

10. Verify with your storage administrator that the licenses and configuration arecorrect, and that enough space is available in the Dell EMC storage pool for clonesand snapshots.


SAP LaMa system provisioning prerequisites 43

http://help.sap.com/lamaent30



Managing snapshotsAfter you have installed a storage manager and verified all of the provisioningprerequisites, click Provisioning to provision the storage system. Refer to thefollowing procedures to create, remove, and view snapshots.

Snapshots of all the source volumes for a specified instance are triggered in a singlecall to maintain storage consistency. The snapshots are named with an SAP InstanceID and followed by a unique ID, abbreviated if necessary to fit the 64-characterlimitation on snapshot naming.

Note

You cannot create or manage snapshots for VPLEX systems.

NOTICE

All snapshot operations, including Manage Snapshots, Snap-Clones, and Snap-Copieson VMAX3, use the Symmetrix VxSnap technology. Dell EMC TimeFinder™ VP Snapand TFSnaps, for the source volumes taken outside of ESI for SAP LaMa, result infailure, as they are mutually exclusive snapshot technologies.

Creating a snapshotYou can create a VNX or VMAX snapshot, or a checkpoint in time, for a selected file orblock storage system.

Procedure

1. Click Provisioning.

2. Click System and AS.

3. Click Manage System Snapshots.

4. In the Manage Snapshots of System dialog box, click Take Snapshot, asshown in the following figure.



Figure 17 Creating a snapshot

5. In the Description dialog box, type a meaningful description for the purpose ofthe snapshot, and then click Next.

The snapshot appears in the Manage Snapshots of System dialog box.

6. Select the Online/Offline option for Database consistency, and then clickNext.

7. Click Take Snapshot.

Verifying Oracle redo logsBefore creating an online snapshot, verify that the Oracle redo logs are configured andactively generating new online redo logs.

The following procedure uses an Oracle database example.

Procedure

1. Click Configuration > Systems > System Details > Edit, as shown in thefollowing figure.


Verifying Oracle redo logs 45

Figure 18 Checking configuration details for a snapshot

2. If the basic configuration is complete, click Provisioning & RFC to performSAP LaMa Online System Clone, System Copy, and System Refresh processes,to ensure that the Oracle redo log is configured for the SAP system, as shownin the following figure.

Click Cancel to exit this screen.

Figure 19 Reviewing the basic configuration and provisioning and RFC details

Creating an online snapshotYou can create a VNX or VMAX snapshot, or a checkpoint in time, for a selected SAPsystem when a database is online or offline.

Before you begin

Ensure that you verified the Oracle redo logs.



Procedure

1. Click Provisioning, and then click Manage System Snapshots > Take SystemSnapshots, as shown in the following figure.

Figure 20 Taking System Snapshots

2. In Basic > Basic Data of System Snapshot, type the snapshot description, andthen click Next, as shown in the following figure.

Figure 21 Selecting data for a snapshot

3. Click Provisioning > System and AS > Consistency, select the default OnlineBackup, type the Timeout [seconds] value, and click Next, as shown in thefollowing figure.


Creating an online snapshot 47

Figure 22 Selecting snapshot consistency details

4. Click Take Snapshot to open the Monitoring > Activities screen that displaysthe high-level details and status of the operation steps of the snapshot, asshown in the following figure.

Figure 23 Viewing snapshot details and operation status

5. In the Logs pane, select a Log ID to view the details and status of the operationand show details of all activities performed by each component, as shown in thefollowing figure.



Figure 24 Viewing snapshot log details

Viewing snapshotsWhen you view snapshots in the SAP LaMa GUI, you only see the storage snapshotscreated from the SAP LaMa Provisioning Manage Snapshots functionality, not anyother snapshots created at the storage-array level with Dell EMC Unisphere™ orSYMCLI commands.

Procedure

1. Click Provisioning > Manage System Snapshots.

2. View the snapshots in the Manage Snapshots of System pane, as shown in thefollowing figure.

Figure 25 Viewing snapshots

Removing a snapshotRemove a snapshot.


Viewing snapshots 49

Procedure

1. Click Provisioning > Manage System Snapshots.

2. In the Manage Snapshots of System pane, select a snapshot from the list.

3. Click Remove Snapshot, and then click Remove Snapshot again to confirmyour action, as shown in the following figure.

Note

Do not delete snapshots in Unisphere that were created in SAP LaMa throughESI for SAP LaMa because doing so causes data errors.

Figure 26 Removing a snapshot

SAP LaMa System Provisioning Processes: System Clone,Copy, and Refresh

You can create system clones either from a snapshot directly from a live system, or byusing an existing SAP LaMa snapshot created at an earlier point in time. The availablestorage replication options depend on the type of storage system. The following tableprovides details.

Table 5 Storage systems and storage replication options

Storage system Storage replication options

VMAX l TimeFinder Snap or VP Snap

l Time Finder Snap or VP Snap from full clone

Note

VP Snap is the default snapshot technology used for VMAX, althoughTime Finder Snap can also be used.

VMAX3 Dell EMC TimeFinder SnapVX™ snapshots and clones



Table 5 Storage systems and storage replication options (continued)

Storage system Storage replication options

SAN VNX l SAN copy full clone

l VNX Snapshot Enabler snapshot or new snapshot

l Full clone from VNX Snapshot Enabler snapshot

Dell EMC VblockSystems

l SAN copy full clone

l VNX Snapshot Enabler snapshot or new snapshot

l Full clone from VNX Snapshot Enabler snapshot

Note

A full clone cannot be used with XtremIO. The cloning process inXtremIO creates a snapshot on the array, and mounts it on the targetmachine. The snapshots created on the array are named with prefixes

of ESISnap and ESIClone and are based on the type of cloningprocess that you use.

NAS VNX l SnapView clone

l SnapView snapshot

VPLEX Full clones using storage layer replication techniques are supported byunderlying VPLEX storage arrays.

XtremIO l Snap clone

l Full clone

For information about the prerequisites and configuration steps that must becompleted before you can clone a system, refer to SAP LaMa system provisioningprerequisites on page 42.

Note

When cloning using a file or block storage system, do not change the name of eitherthe source or the target file systems. You must have sufficient disk space in a targetpool to clone the source.

Configuring SAP target serversConfirm with the storage administrator that storage views are created for the targetservers before you start SAP LaMa system provisioning processes.

The ESI for SAP LaMa storage adapter can expose storage volumes to SAP LaMatargets only by using existing zoning and masking views.

Note

“Masking view” is the term used for VMAX. This is equivalent to “storage groups” forVNX and “storage views” for VPLEX. For XtremIO, create the initiator groups for thetarget hosts ahead of time for system cloning/copy.


Configuring SAP target servers 51

Managing SAP LaMa system provisioning processes with full clonesCreating a full clone causes the storage manager to perform a full copy of thevolumes, instead of only taking snapshots. Confirm that the storage system hasenough space to perform this operation.

Full cloning is supported for both file and block storage systems. Making full copies ofstorage volumes might take a long time, depending on the size of the volume. Forinformation about the limitations of full cloning, refer to Known limitations andproblems on page 59.

Note

When you perform a system clone, the target system is network-isolated by thesettings configured in SAP LaMa Configuration > Instances > Network Isolation. Ifyou forgot to maintain an existing outgoing connection, you can add the connection inthe isolation step.

Creating a cloneYou can create a clone to cause the storage manager to perform a full copy of thevolumes.

Procedure


2. From System Landscape, select the source system that you want to clone.

3. Click Clone System.

Note

If you want to use the SAP Online Cloning option, be sure to select a sourcesystem that contains the mount configuration for database online redo logs.

4. See the SAP LaMa online help and follow the first three System Cloning steps:(1) Basic; (2) Hosts; and (3) Host Names.

5. Click Next when you are finished.

6. In Storage, select the Full Copy checkbox for all storage volumes for a fullclone, as shown in the following figure.

Note

For snap clones, clear the checkbox for all storage volumes.



Figure 27 Creating a Full Copy for all storage volumes

7. From the Storage Pool field, select a storage pool from the list and close thedialog box.

Note

l You must have appropriate access rights to the storage pool that you select,and the storage pool must have available space that is at least equal to thesize of the source volumes. For VPLEX systems, you do not need to select astorage pool, because ESI automatically selects the storage pool based onaccess rights and the maximum space that is available on the storage pool.

l For XtremIO volumes-based SAP systems:

n For an XtremIO RDM/physical volume, the storage system componentname is displayed in the Storage System column.

n For virtual environments or VMDKs, the VMWARE_vmdk token isdisplayed in the Storage System tab.

8. Click Next.

9. See the SAP LaMa online help and follow step (5) Consistency. Select one ofthe following options:

l Online: Backup/Suspend IO Mode to create an online clone

Note

Type 600 in the Timeout [seconds] field to avoid any timeout issues.

l Offline to create an offline clone

10. Click Next.

11. Follow System Cloning steps (6) Isolation and (7) Summary. See SAP LaMaProvisioning instructions in the SAP Landscape Management 3.0, EnterpriseEdition page on the SAP Help Portal, and then navigate to Configuration andDeployment Information > Landscape Configuration > Managing SystemLandscapes > Provisioning Systems.


Creating a clone 53



Creating a clone from a snapshotYou can clone from snapshots on VNX systems. you cannot clone from snapshots onVMAX or VPLEX systems.

Procedure


2. From System Landscape, select the source system that you want to clone.

3. Click System Clone.

4. See theSAP LaMat online help and follow the first three System Cloning steps:(1) Basic; (2) Hosts; and (3) Host Names.

5. Click Next when you are finished.

6. In the Storage step, select the Full Copy checkbox for all storage volumes.

7. Select Clone from System Snapshot and select the previous snapshotcreated, as shown in the following figure.

Figure 28 Selecting a snapshot

8. Select a snapshot from the Clone from system snapshot list.

9. From Storage Pool, select a storage pool from the list, and then click Go.

10. Click Next.

11. See the SAP LaMa online help and follow step (5), Consistency. Select one ofthe following options:

l Online: Backup/Suspend IO Mode to create an online clone

Note

Type 600 in the Timeout [seconds] field to avoid timeout issues.

l Offline to create an offline clone

12. Click Next.

13. See the SAP LaMa online help and follow System Cloning steps (6) Isolationand (7) Summary.



Destroying volumesThe System Destroy process, as shown in the following figure, destroys all of thevolumes that were automatically created at the storage level during a previous SystemClone or System Copy process.

Procedure

1. Confirm that the SAP System that you want to destroy is unprepared.


3. Select a cloned system from the list of systems.

Note

The SAP instances file systems of an SAP clone must be unprepared before theSystem Destroy process can take place.

4. Click Destroy System.

5. Select all volumes to be deleted, and then click Next.

Figure 29 Destroying a cloned system

Note

The SAP LaMa System Destroy process destroys all the volumes that wereautomatically created in the storage level during the System Cone or Copyprocesses.

Destroying partially provisioned systemsIf a previous SAP LaMa System Clone or Copy process fails after the cloning volumesprocedure, SAP LaMa enables the System Destroy option on partially provisionedsystems. This process runs a Mass Unprepare operation before the storage volumescreated during the provisioning process are deleted. The operation also removes the


Destroying volumes 55

target SAP systems from SAP LaMa Infrastructure > Configuration > Hosts if theywere created during the provisioning process.

Procedure


2. Select a cloned system from the list of systems.

3. Click Destroy System > Destroy Partially Provisioned System.

4. Select all volumes to be deleted, and then click Next until finished, as shown inthe following figure.

Figure 30 Destroying a partially provisioned system



CHAPTER 6

Troubleshooting


l Troubleshooting................................................................................................. 58l Known limitations and problems.........................................................................59

Troubleshooting 57

TroubleshootingThe following table provides troubleshooting information for ESI for SAP LaMa.

Note

ESI for SAP LaMat maintains log files on the EHAC server that are separate from theSAP LaMa server. If you need support, contact the storage administrator to collect logfiles.

Table 6 Troubleshooting

Symptom Prevention, resolution, or workaround

During cloning, when you go

from Hostnames to Storage,volume retrieval operations arenot triggered.

Click Monitoring Data, which sends a request to ESI forvolume retrieval.

A No Parent Found error

occurs during cloning.l Verify whether the cache contains the volume ID. If the

ID is not included, click Monitoring Data to retrievevolume information.

l If the ID is included in the cache, run the cloningoperation to resolve the issue.

After you run an Unprepareoperation, the SAP centralinstance (CI) is in an ERRORstate, despite the operationbeing successful.

The error might be caused by the virtual network interfacecard (NIC) not being brought down during the operation.After the virtual IP is brought down, SAP instances return tothe proper state.

The Unprepare or Prepareoperation failed with this error:Individual devicescannot be added to orremoved from a SG thatcontains other SG(s).

Advanced storage configuration is not enabled for theSymmetrix VMAX array:

l Verify the advanced configuration for the array in EHAC

at SAN > StorageSystem > Retrieve the storagesystem.

l Click Configuration > Enable advancedconfiguration for the array.

During P2V or V2V relocation,the mount operation fails with aCould not find OSphysical device error

message in a VMwareenvironment.

Check whether the target virtual machine's ESXi host detailis added to EHAC. If the EHAC database was upgraded fromESI 3.0 to 4.0, add ESXi details to the database again.

Issue 443878: The systemdestroy failed during a full cloneor an offline clone due tostorage hanging locks.

Verify with the storage administration team that storagesystem locks are cleared, and restart the system.

Troubleshooting


Table 6 Troubleshooting (continued)

Symptom Prevention, resolution, or workaround

Cloning a system from asnapshot fails.

l Confirm that you are cloning from a VNX system.Cloning from snapshots does not work on VMAXsystems.

l When you clone a system from a snapshot, ESI for SAPLaMat makes a full copy. Confirm that the selectedstorage pool has enough free space to store the full sizeof the source file system.

l Confirm that you selected a storage pool in the cloningprocess.

l Confirm that the storage system is accessible and is notoffline.

l Ensure that pools with enough capacity are assigned tothe user in the EHAC console.

l Confirm that you have a SAN copy, and that VNXSnapshot Enabler, and Time Finder Clone and Snap areenabled. The ESI for SAP LaMa system cloningfunctionality requires the software to perform cloningand snapshot operations.

Taking a snapshot is successful,but no snapshots are found onthe array.

Confirm that a storage adapter is added in SAP LaMa. See Adding an ESI storage manager on page 34.

The ESI for SAP LaMa adapterfails to retrieve informationfrom a storage array.

l Click Reload in SAP LaMa to reload the storage systeminformation or to remove the storage manager and re-add it.

l Confirm that the storage system is accessible and is notoffline.

l If the storage array information is not displayed in theSAP LaMa configuration even after reloading, checkthat the web server is running and is accessible.

SAP Host agent commandsapacosprep -aListFileSystems does not

list the devices on VPLEXvirtual disks.

Add a pRDM gatekeeper device to the host, and then runthe symcfg disco command to have SAP

ListFileSystems fetch the devices.

Multiple virtual disks with VMAX backed LUNs and VPLEXor XtremIO disks may not work unless a dummy VMAXgatekeeper/RDM is mapped to a virtual machine. Thislimitation is due to the absence of the gatekeeper. As aresult, information is not updated for discovered XtremIOand VPLEX devices, and the SRM is not able to mapXtremIO and VPLEX LUNs directly.

Known limitations and problemsThe following limitations and problems are for cloning and snapshots. Refer to theEnterprise Storage Integrator for SAP Landscape Management Release Notes for a

Troubleshooting

Known limitations and problems 59

complete list of known problems and limitations and ways to prevent, resolve, or workaround them.

l When cloning a system, taking snapshots, or cloning from snapshots, do notrename the source or target file systems. This includes snapshots taken before orafter a system is cloned and applies even after cloning is complete. Otherwise,SAP LaMa features such as system destroy and volume retrieval might beaffected. You cannot override file systems and system snapshots that are used inESI for SAP LaMa system provisioning processes.

l When cloning a system, SAP LaMa may time out after 10 minutes if a sourcesystem contains many volumes. The snapshot operation will run in the background.

Note

In the SAP LaMat Setup > Engine > Expert mode, you can set the maximum timeoutto 120 minutes or to 0 for an unlimited time, as a workaround.

l Cloning from snapshots is not supported for VMAX storage systems.

l During full cloning, you must select all of the storage volumes.

l System cloning of a cloned system is not supported.

l ESI operations are supported only for masking views

l ESI does not support the following configurations:

n Combination of host initiators and cascaded initiator groups in the sameinitiator group

n Multiple masking views with same initiator group and one or more storagegroups

n Multiple levels of cascading within the initiator group

l In a VMware environment, you must retrieve the HBAs in the SAP LaMaConfiguration > Hosts > Edit > Host profile storage settings after a virtualmachine is moved by vMotion or powered on by vSphere HA in a different ESXiserver from where it was originally discovered, added, or configured on SAP LaMa.If FT is enabled, ESI for SAP LaMa enables SAP operations to stay intact only ifthe FT is disabled and enabled before and after the process, respectively.

l In a VMware environment, ESI creates a new datastore on the ESXi host duringthe snapshot-based clone and full-clone processes. Datastores created by ESIhave a Snap-xxxxxxxx-OriginalDSName naming convention during snapshot-based clones. Datastores created during a full-clone operation have a Clone-xxxxxxxx-OriginalDSName naming convention. Do not change the ESI datastorename, because a renamed datastore affects functionalities supported by ESI forSAP LaMa.

Note

For a cross-platform relocation, using P2V or V2P, SAP LaMa does not persist thechanged mount options, but only uses it once for the next System Prepare. Anyfurther operations on the relocated system modifications made in export paths by theSAP Host Agent invoking the sapacosprep command invoking the Solutions EnablerELSA are reflected only if the SAP LaMa administrator selects Retrieve Mount Listfor the relocated system.

Troubleshooting


Enterprise Storage Integrator for SAP Landscape ... This user guide describes how to use Dell EMC...

Documents

Transcript of Enterprise Storage Integrator for SAP Landscape ... This user guide describes how to use Dell EMC...