dell emc enterprise storage integrator for sap landscape … · 2020-06-10 · dell emc enterprise...

Dell EMC Enterprise Storage Integrator forSAP Landscape ManagementSimplify and Accelerate System Clone, Copy, andRefresh for SAP SystemsFebruary 2019

H13279.3

Deployment Guide

Abstract

This deployment guide describes how to implement the Dell EMC Enterprise StorageIntegrator (ESI) for SAP Landscape Management with SAP Landscape Managementsoftware. ESI storage-based cloning automates the SAP LaMa System operations andprovisioning processes for Dell EMC storage systems in physical and virtualenvironments.

Copyright © 2014-2019 Dell Inc. or its subsidiaries. All rights reserved.

Published February 2019

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 Dell EMC Enterprise Storage Integrator for SAP Landscape Management

Executive Summary 5Purpose of this guide....................................................................................6Business value.............................................................................................. 6Audience...................................................................................................... 6Scope........................................................................................................... 6Terminology..................................................................................................7We value your feedback............................................................................... 8

Solution Overview 9Solution architecture.................................................................................. 10Dell EMC components................................................................................. 11

Solution Prerequisites 13Required software.......................................................................................14Essential reading......................................................................................... 14General prerequisites.................................................................................. 15Storage system prerequisites......................................................................16

VMAX All Flash and PowerMax prerequisites................................. 16VPLEX prerequisites...................................................................... 18Unity prerequisites........................................................................ 20

IBM AIX operating system configuration prerequisites for ESI.................... 21Prerequisites and recommendations for vSphere with ESI ......................... 21Microsoft Windows operating system configuration for ESI....................... 24SAP HANA platform systems installation and configuration tasks.............. 25SAP LaMa installation and configuration tasks........................................... 27EHAC appliance deployment prerequisite tasks..........................................28

Solution Deployment 29Deployment overview................................................................................. 30

Solution Configuration 31Configuration overview...............................................................................32

Status definitions...........................................................................32SAP LaMa operations.................................................................... 33

Configure initial settings.............................................................................34Retrieve host-specific storage properties...................................................35Configure properties for SAP system instances......................................... 36Retrieve mount points for application instances......................................... 37Configure system provisioning....................................................................39

Solution Verification 43Run Mass Stop with Unprepare.................................................................. 44Run Mass Start with Prepare......................................................................47Relocate the SAP system........................................................................... 49

Accelerate SAP LaMa system operations in vSphere vCenter........51Managing snapshots...................................................................................53

Create a snapshot......................................................................... 53

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

Chapter 6

CONTENTS

Dell EMC Enterprise Storage Integrator for SAP Landscape Management 3

Create an online snapshot............................................................. 54View snapshots..............................................................................57Remove a snapshot....................................................................... 58

Using SAP LaMa System Provisioning Processes.......................................58Create a clone............................................................................... 60Copy a system................................................................................61Create a snapshot clone on a remote array....................................63Create a clone from a snapshot..................................................... 64

Running System Destroy............................................................................ 65Destroy partially provisioned systems............................................66

Reference Documentation 69Dell EMC documents.................................................................................. 70Dell EMC links.............................................................................................70VMware documents....................................................................................70SAP documents.......................................................................................... 70

Chapter 7

CONTENTS


CHAPTER 1

Executive Summary

This chapter presents the following topics:

l Purpose of this guide........................................................................................... 6l Business value......................................................................................................6l Audience.............................................................................................................. 6l Scope...................................................................................................................6l Terminology......................................................................................................... 7l We value your feedback....................................................................................... 8

Executive Summary 5

Purpose of this guideThis deployment guide describes the steps that are required to install and configurethe Dell EMC products that enable integration with SAP Landscape Management(LaMa) software.

This document provides the prerequisites and configuration procedures that arerequired to integrate Dell EMC PowerMax, VMAX All Flash, Unity, VPLEX, andXtremIO storage systems with SAP LaMa software. ESI enables automated SAPsystem operations and provisioning processes, such as System Clone, System Copy,and System Refresh.

The objectives of this document are to:

l Provide a predeployment checklist to verify that all prerequisites have been metbefore you install the ESI components

l Introduce the key components of Enterprise Storage Integrator (ESI) for SAPLaMa

l Describe how to install and configure the ESI key components

l Provide the steps to validate the customer deployment

Business valueSAP LaMa software reduces Total Cost of Ownership (TCO) and increases flexibilityand agility to respond to business demands.

SAP LaMa software supports application virtualization and provides management ofSAP systems through a single user interface. This powerful management toolsimplifies and optimizes provisioning, deployment, and management of SAP systemsby using virtualization and cloud technology.

Dell EMC supports SAP LaMa as part of its strategy and direction towardvirtualization and cloud technologies. Integrating SAP LaMa into a Dell EMCinfrastructure enables customers to maximize the value of their infrastructure whileproviding them with a path to virtualization and the cloud.

AudienceThis deployment guide is intended for the Dell EMC Professional Services team that isresponsible for implementing ESI for SAP at the customer site and the Dell EMCCustomer Service team that supports ESI. Partners and customers can also use thisguide as a reference when executing SAP LaMa system operations and provisioningprocesses with ESI.

Technical experience with virtualization, servers, operating systems (OS), networking,and storage solutions is required to fully understand the content described in thisdocument.

ScopeThis deployment guide focuses on the implementation of the components that arerequired for integration of Dell EMC storage systems with SAP LaMa storage-based

Executive Summary


cloning software on SAP systems. ESI for SAP LaMa can clone physical hosts andVMware vSphere virtual hosts.

The document does not cover all the features that are available with SAP LaMasoftware or details on SAP Post Copy Automation (PCA).

TerminologyUnderstand the terms used in this document.

Term Definition

ABAP SAP Central Services(ASCS)

Runs the SAP NetWeaver Advanced Business Application Programming (ABAP) centralqueue and message server services.

Enterprise Library for SAPAdapter (ELSA)

The SAP application shared library (the libsapacosprep_emc.so file) is part of the

Storage Resource Management Suite (SRM) module of the Dell EMC Solutions Enabler(SE) software. ELSA provides integration for the SAP Host Agent and SAP AdaptiveExtensions software. ELSA enables SAP host agent tasks such as mount and unmountSAP file systems and import and export partitions, logical volumes, and volume groups thatare based on distributed file systems (DFS) and are stored on SAN-FC volumes. ELSAattaches and detaches distributed file systems and storage resources.

Java Enterprise Archive (EAR) A file format that is used by Java EE for packaging modules into a single archive forsimultaneous and coherent deployment of the various modules onto an application server.

Network Attached storage (NAS) A file-level storage system that is connected to a network that provides data access to aheterogeneous group of clients. NAS operates as a file server that is specialized for thistask by its hardware, software, or configuration. NAS provides access to files usingnetwork file sharing protocols such as NFS, SMB/CIFS, or AFP.

REST API Representational State Transfer (REST) is an architectural style describing the act oftransferring a state of something by its representation. An application program interface(API) consists of routines, protocols, and tools for building software applications. An APIspecifies how software components should interact. REST API provides a way ofinteracting with an application.

SAP Additional Application Server(SAP AAS)

Formerly called Application Instance, the SAP NetWeaver Additional Application Server isthe scalable component of the SAP software stack for ABAP and Java applications.

SAP Adaptive-enabled (AC-Enabled) systems

SAP systems are installed using the SAP concept of abstracting SAP instances from theunderlying operating system and infrastructure. This abstraction uses virtual IP addresses,virtual host names, and independent file systems. These components are grouped by SAPinstance and stored on dedicated storage volumes on shared central storage systemsaccording to the SAP adaptive design concept.

SAP Advanced BusinessApplication Programming (ABAP)

The programming language SAP uses to describe the SAP system architecture type usedin this solution.

SAP database instance Runs the database software, including traditional disk-based relational databasemanagement systems (RDBMS) such as Oracle, Microsoft SQL Server, DB2, and in-memory database software such as SAP HANA.

SAP Enhancement Package(EHP)

SAP software component that provides highly integrated core functionality encapsulatedin business functions. It simplifies the way customers manage and deploy new softwarefunctionality.

SAP LaMa Prepare, Unprepare,and Relocation operations

These operations can be performed on one instance or a set of instances.

Executive Summary

Terminology 7

Term Definition

l Prepare binds virtual host names of an instance to network interfaces and mountsstorage locations to the local file systems.

l Unprepare reverses the prepare operation tasks.

l Relocation moves an instance or a set of instances from one host to another, eitherphysically or virtually in either direction.

The operation retains the status of the instances. When the SAP instance is running, youcan run the Stop and Unprepare operations. When the SAP instance is not running, youcan run the Prepare and Start operations.

SAP LaMa system operations Group term that includes SAP LaMa System Mass Start with Prepare, Mass Stop withUnprepare, Relocation operations, and single instance operations, such as Start, Stop,Prepare, Unprepare, and Relocation.

SAP LaMa system provisioningprocesses

Group term for the SAP LaMa System Clone, System Copy, System Refresh, SystemRename, and System Destroy processes.

SAP Primary Application Server(SAP PAS)

Formerly called central instance, the SAP NetWeaver Primary Application Server is thecentral foundation for the entire SAP software stack. It also provides a platform for otherNetWeaver components such as Portal, XI, and ABAP and Java applications.

Secure Shell (SSH) A cryptographic network protocol for secure data communication between two networkedcomputers. Using a secure channel over an unsecure network, it connects a server runningSSH server, and a client running SSH client.

Storage Area Network (SAN) A dedicated network that provides access to consolidated, block-level data storage. It isprimarily used to enhance storage devices, such as disk arrays, so that the devices appearlocally attached to the operating system. The SAN Fibre Channel (SAN-FC) is a fast andreliable protocol that is widely used by the Dell EMC storage systems in this solution.

vStorage APIs for ArrayIntegration (VAAI)

A set of APIs that enables communication between VMware vSphere ESXi hosts andstorage devices; also referred to as hardware acceleration or hardware offload APIs.

We value your feedbackDell EMC and the authors of this document welcome your feedback on the solutionand the solution documentation.

Contact the Dell EMC Solutions team by email or provide your comments bycompleting our documentation survey.

Authors: Manoel Silva, Donna Renfro

Note

The following page of the Everything SAP at Dell EMC space on the Dell EMCCommunities website provides links to additional documentation for this solution: SAPInfo Hub for Ready Solutions.

Executive Summary


mailto:[email protected]?subject=Dell%20EMC%20Storage%20Integration%20with%20SAP%20Landscape%20Management%20Software%20Implementation%20Guide%20P/N%20H13279.3

https://www.surveymonkey.com/r/SolutionsSurveyExt

https://community.emc.com/docs/DOC-66864


CHAPTER 2

Solution Overview

Read this chapter to gain an understanding of the key technologies used to integrateDell EMC storage systems with SAP Landscape Management. This chapter presentsthe following topics:

l Solution architecture.......................................................................................... 10l Dell EMC components......................................................................................... 11

Solution Overview 9

Solution architectureThe solution architecture includes several components.

The following figure depicts the architecture of the solution.

Figure 1 Solution architecture

The following table lists the key technologies that you must implement to enable theintegration between SAP LaMa software and ESI in SAN and NAS environments.

Table 1 Key solution components

Component Description Requiredfor SAN

Requiredfor NAS

SAP LaMa server SAP LaMa is an Add-On component for SAP NetWeaver Java Stackserver and is the SAP landscape control block. Also referred to as theSAP LaMa Management server.

Y Y

SAP Hosts SAP Business Suite systems, like ERP, CRM and SCM. Also referred toas SAP LaMa Managed hosts.

Y Y

SAP Host Agent SAP software installed on all SAP hosts to be managed by SAP LaMa. Y Y

ESI plug-in Enterprise storage integrator for SAP LaMa software is a Java plug-inthat is deployed on the SAP NetWeaver Java application server that isrunning the SAP LaMa add-on.

Y Y

Enterprise HLSAdministrationConsole (EHAC)

Enterprise central storage administration tool used to manage all storagesystems that are used by ESI for SAP LaMa.

Y Y

Solutions Enabler(SE)

Includes the Enterprise storage library for SAP (ELSA) that is used forfile system mount and unmount operations on the SAP hosts.

Y N

Solution Overview


Table 1 Key solution components (continued)

Component Description Requiredfor SAN

Requiredfor NAS

Unisphere for VMAX/PowerMax

A user interface (UI) that provides a common Dell EMC user experienceacross storage platforms. Unisphere enables customers to provision,manage, and monitor storage environments.

Y Y

Dell EMC componentsThis solution uses individual Dell EMC software components to integrate Dell EMCstorage systems with SAP LaMa.

Software integration componentsThe Dell EMC ESI for SAP LaMa components include the following:

l Enterprise Storage Integrator plug-in—A storage plug-in that is distributed as aJava Enterprise Archive (EAR) file (esi_4_sap_lama_plugin.6.0.x.ear).The ESI plug-in complies with SAP LaMa storage manager specifications. The ESIadapter is deployed in the SAP NetWeaver Java stack application server andintegrates with Dell EMC file and block storage systems.

The ESI plug-in provides storage management for SAP LaMa and enables SAPadministrators to manage clones and snapshots of multiple storage volumes thatcontain the SAP instance-specific file systems.

The ESI plug-in supports the following:

n SAP systems in physical, virtual, and mixed environments on PowerMax, VMAXAll Flash, XtremIO, Unity, and VPLEX 5.5 storage systems, that use VirtualMachine Disks (VMDKs) or physical raw device mapping (pRDMs).

n Dell EMC VxBlock converged systems that use PowerMax, VMAX All Flash,XtremIO, and Unity all-flash storage arrays.

l Unisphere REST API—The ESI code contains the Rest API calls for DELL EMCVMAX All Flash, PowerMax, Unity, and VPLEX storage systems.

l Enterprise High Level Storage Administration Console (EHAC)— Apreconfigured Linux-based appliance (EHAC appliance) that provides a gatewayfor the ESI plug-in to access the configured Dell EMC storage systems on theEHAC database. The EHAC web service enables the Dell EMC storage-relatedsteps required for SAP LaMa provisioning operations and processes.

Storage administrators use the EHAC configuration console to:

n Add and remove VMware vCenter and ESXi servers to and from the EHACdatabase.

n Discover and configure storage area network (SAN) storage, such as Dell EMCUnity, Dell EMC PowerMAX, VMAX All Flash, XtremIO all-flash arrays, andVPLEX storage systems.

n Discover and configure network-attached-storage (NAS), such as VMAX AllFlash and PowerMax eNAS, and Unity file storage in the EHAC database.

n Discover and add Dell EMC Unity unified storage system to the EHACdatabase.

n Discover all Dell EMC storage systems and their pools, and set or removeaccess rights.

Solution Overview

Dell EMC components 11

n Create and delete administrator and ESI general users. Grant and revokeaccess to Dell EMC storage systems and storage pools.

l Solutions Enabler (SE)—Software that must be installed on all SAP physical orvirtual hosts that contain SAP instance-specific file systems stored on Dell EMCvolumes that are connected through the SAN-FC protocol. Solutions Enablercontains the Storage Resource Management (SRM) module with the sharedEnterprise Storage Library for SAP (ELSA), libsapacosprep_emc, andprovides the following functions:

n Retrieves and identifies the storage devices, servers, HBAs, partitions, volumegroups, and logical groups that are used by each SAP instance-specific filesystem. SE also mounts and unmounts these entities on the physical hosts orVMware vSphere virtual SAP hosts.

n SE supports command-line entries to perform initial configuration and ongoingcontrol operations to manage SAN-FC-based storage systems used by the SAPhosts.

The SAP Host Agent (SAP HA) and the SAP Adaptive Extensions (SAP AdExt)software are the only OS-specific components in the ESI for SAP solution. Theyintegrate with SE, SRM, and ELSA. SAP file systems are configured as mountpoints inside the SAP LaMa system instances, and the SAP HA, SAP AdExt, andELSA integration is used to retrieve and upload these file systems to SAP LaMaand to mount and unmount them from the SAP hosts.

Note

The Dell EMC Simple Support Matrix document on the Dell EMC support website listsstorage systems that are supported in this solution, their operating environment (OE)releases, and operating system combinations. ESI uses storage-specific REST APIs tomanage Dell EMC storage systems.

Solution Overview


CHAPTER 3

Solution Prerequisites

Ensure that the environment setup complies with the requirements for deployment ofESI components. This chapter presents the following topics:

l Required software.............................................................................................. 14l Essential reading.................................................................................................14l General prerequisites..........................................................................................15l Storage system prerequisites............................................................................. 16l IBM AIX operating system configuration prerequisites for ESI............................21l Prerequisites and recommendations for vSphere with ESI .................................21l Microsoft Windows operating system configuration for ESI...............................24l SAP HANA platform systems installation and configuration tasks......................25l SAP LaMa installation and configuration tasks................................................... 27l EHAC appliance deployment prerequisite tasks................................................. 28

Solution Prerequisites 13

Required softwareEnsure that the environment includes the correct versions of the required software.

Table 2 Required software

Software Minimum softwareversion

Installed on

Browser Chrome 71 End-user desktop

SuSE Linux EnterpriseServer (SLES) for SAP

12 SP13Note

All software described here is pre-installed and configured on theLinux-based EHAC virtual appliance. Both virtual and physical EHACappliances include a software package containing the latest versionof the SAP Host Agent, SAP Adaptive Extensions, DELL EMC SE,Grab, and implementation scripts. The software package must beinstalled or upgraded on the SAP hosts.

Java Runtime Environment jre.8.0.162

Wildfly Application Server 10.1 final

Apache Derby database 10.9.1

ESI for SAP LaMa Webservice

6.0.xx

EHAC Deployment Console 6.0.xx

SAP NetWeaver Java Server 7.5 SP11 Server dedicated to run SAP NetWeaver Java Stack with SAP LaMa

SAP LaMa 3.0, SP07 Patch 4 SAP LaMa server

ESI Java plug-in 6.0.xx SAP LaMa server as a Dell EMC storage manager plug-in

SAP Host Agent 7.21 SP39 or latersupport package

All SAP managed hosts

SAP Adaptive Extensions 1.0 EXT 43 or latersupport package

All SAP managed hosts

DELL EMC Grab 4.7.13 All SAP managed hosts

Dell EMC Solutions Enabler 9.0.0.8 or later patch All SAP managed hosts with instance file systems based on SAN/FCstorage devices

VMware vCenter server 6.5 U2C or 6.0 U3h Intel x86 physical servers

Unisphere for PowerMax 9.0.1 or 9.0.2.5 On VMware vSphere vCenter Server, as a virtual appliance if DellEMC VMAX All Flash storage systems are used with ESI.

Note

The Dell EMC Simple Support Matrix provides the latest software versions that arecompatible with this solution. SAP Product Availability Matrix (PAM) provides SAPsoftware release information. Credentials are required to access these sites.

Essential readingRead these documents for important information about procedures you mustcomplete.

Dell EMC recommends that you read the following documentation, available atSAP.com, SAP Community, Dell EMC Community Network, and Dell EMC Online



https://elabnavigator.emc.com/vault/pdf/EMC_ESI_ESSM.pdf?key=1548824704399

https://apps.support.sap.com/sap/support/pam

Support. If you are unable to access these documents, contact your SAP or Dell EMCrepresentative.

l SAP Landscape Management 3.0, Enterprise Edition - Overview

l Enterprise Storage Integrator for SAP Landscape Management Release Notes on DellEMC Enterprise Storage Integrator for SAP Landscape Management ProductSupport

Required Reference documentation

The following documents contain procedures not duplicated in this guide that you willneed for the deployment. Ensure that you download these documents to your laptop incase you do not have internet access at the customer site.

l Enterprise Storage Integrator for SAP Landscape Management Administrator Guideavailable on Dell EMC Enterprise Storage Integrator for SAP LandscapeManagement Product Support

l Enterprise Storage Integrator for SAP Landscape Management User Guide availableon Dell EMC Enterprise Storage Integrator for SAP Landscape ManagementProduct Support

l Dell EMC Solutions Enabler 9.0 Installation and Configuration Guide

l Dell EMC Virtual Appliance Manager 9.0 Installation Guide

l Dell EMC Knowledgebase article 458145 Symmetrix: Gatekeepers: All you need toknow

General prerequisitesThis guide assumes that all predeployment requirements have been completed.

Before starting the deployment, ensure that all the relevant tasks in this chapter havebeen completed. Failure to complete these tasks can jeopardize the successfuldeployment of this solution.

Table 3 General tasks

Task References and notes

You have access to Dell EMC ESI and Solutions Enablersoftware and SAP software documentation.

Contact your Dell EMC and SAP representatives forcredentials.

You have online access to the ESI web page or you havedownloaded all the required documentation for thedeployment.

Essential reading on page 14

Read and download the SAP Storage-based SystemProvisioning document and ensure that recommendationshave been followed.

Storage-based system provisioning with SAP LandscapeVirtualization Management

Acquire the ESI for SAP LaMa Professional Servicesimplementation service and download all the referencedocuments there.

Dell EMC Service Offering PS-BAS-SAPESI, search forPS-BAS-SAPESI.


General prerequisites 15

https://www.sap.com/products/landscape-management.html

https://support.emc.com/products/28468/Documentation







https://support.emc.com/docu88899

https://support.emc.com/docu88899

https://support.emc.com/kb/458145


https://www.sap.com/documents/2015/07/b4531ebb-5b7c-0010-82c7-eda71af511fa.html

https://www.sap.com/documents/2015/07/b4531ebb-5b7c-0010-82c7-eda71af511fa.html

https://www.emc.com/auth/service-offering-index.htm#search/cPage=1&sort=sortableproductsolutionname:A&q=PS-BAS-SAPESI

Storage system prerequisitesBefore you start the deployment, setup of the required storage systems should havebeen completed according to the guidelines in this section.

Table 4 Dell EMC Storage system installation and configuration prerequisites

Task Steps Notes

Review the DellEMC storagesystemconfigurationwith thecustomerstorageadministrator.

Configure all Dell EMC storage systemsaccording to the recommendations that aredescribed in the storage systemdocumentation.Zone and mask the Dell EMC storage systemsto all source and target SAP physical hosts orto all ESXi servers on the vCenter clusterwhere these VMs are running.

Refer to the appropriate Dell EMC Storage systemdocumentation:

l VMAX / PowerMax Families Documentation

l XtremIO Family Documentation

l Unity Family Documentation

l VPLEX Family Documentation

Ensure that theappropriate DellEMC storagesystem licensesare installed.

To check the licenses for:

l VMAX All Flash and PowerMax: Log in toUnisphere for PowerMax.

l XtremIO: Log in to XMS.

l Unity: Log in to Unisphere for Unity.

l VPLEX: Log in to Unisphere for VPLEX.

Install the following snapshot and clone licenses onthe appropriate Dell EMC storage systems beforeattempting to perform the corresponding operations:

l VMAX All Flash and PowerMax TimeFinder/SnapVX licenses

l Unity Local Copies and Network File System(NFS) licenses

l Unity Unified Snapshots (Consistency Groups,Thin Clones, and VMware vStorage VMFSdatastores) licenses

l XtremIO Virtual Copies (XVC) licenses

l "Masking view" is the term that is used for VMAX All Flash and PowerMax storage systems. This term is equivalentto "storage groups" or "consistency groups" for Unity and "storage views" for VPLEX.

l For XtremIO, create the initiator groups for the target hosts ahead of time for System Clone and System Copy.

l The storage pool must have available space that is at least equal to the size of all the source volumes combined.

VMAX All Flash and PowerMax prerequisitesEnsure that your environment meets the requirements for VMAX All Flash andPowerMax storage systems.

Table 5 Dell EMC VMAX All Flash and PowerMax storage system installation and configurationprerequisites

Task Steps Notes

Be aware of thelimitations forVMAX All Flashand PowerMaxstorage

Login to Unisphere for PowerMax to verify thatthe storage configuration used by the SAPhosts is set up correctly.

The following limitations exist for ESI on VMAX AllFlash and PowerMax storage arrays:

l Do not manually modify or delete the snapshotscreated by ESI directly on the storage array by



https://support.emc.com/products/42836_PowerMax/Documentation

https://support.emc.com/products/31109_XtremIO-Family/Documentation/

https://support.emc.com/products/39949_Dell-EMC-Unity-Family/Documentation/

https://support.emc.com/products/29384_VPLEX-Series/Documentation/

Table 5 Dell EMC VMAX All Flash and PowerMax storage system installation and configurationprerequisites (continued)

Task Steps Notes

systems onESI.

using SYMCLI commands or Unisphere forPowerMax. Snapshots created by ESI on VMAXAll Flash or PowerMax and manually deleted fromthe storage array still appear in the SAP LaMaGUI and could cause confusion.

l Do not create snapshots of an existing SNAPVXsnapshot session on VMAX All Flash orPowerMax eNAS devices.

l The SAP instance-specific file systems that arebased on NAS mount points must have 1:1mapping between the NAS file system and thestorage-based Network File System (NFS)export on the storage array. Multiple NFSexports on a single NAS file system (for example,exporting the subdirectories on a single NAS filesystem to be mounted to hosts) is not currentlysupported.

Prepare VMAXAll Flashstoragesystems.

1. Deploy Unisphere for PowerMax 9.01(U4PMAX9) virtual appliance (vApp).

2. Provision six Dell EMC gatekeeper devicesand add them as pRDM disks to theUnisphere for PowerMax 9.01 vApp.

Note

Do not try to mount these disks to theGuest OS.

Refer to the following documentation:

l Virtual Appliance Manager 9.0 Installation Guide,Chapter 3: Installing Unisphere for PowerMaxVirtual Appliance.

l Dell EMC Knowledgebase article 458145.

Prepare VMAXAll Flash orPowerMaxstoragesystems.

1. In Unisphere for PowerMax 9.0, confirm(and adjust if necessary) that storagegroups and masking views are configuredfor the source and target SAP hosts andtheir contained instances and respectivededicated LUNs on physical and virtualenvironments.

2. Ensure that all SAP instance-specificdedicated LUNs are stored in one storagegroup and that all the instances of an SAPsystem are child storage groups of a parentstorage group that is assigned to a maskingview that grants access to all source hosts.

3. Ensure that at least one masking view iscreated for the target hosts initiators(HBAs).

Note

ESI creates its own storage groups andcorresponding masking views for the cloned LUNs byusing an existing Parent Host Group and Port Groupon the storage system. Masking views and storagegroups that are created by ESI are deleted when thecloned system is destroyed in the LaMa UI.

Prepare VMAXAll Flash or

Log in to the U4PMAX9 and ensure that thefollowing are complete:

l PowerMax and VMAX All-Flash documentation


VMAX All Flash and PowerMax prerequisites 17

https://support.emc.com/docu88899_Virtual_Appliance_Manager_9.0_Installation_Guide.pdf?language=en_US&language=en_US%20


https://www.dellemc.com/en-us/documentation/vmax-all-flash-family.htm

Table 5 Dell EMC VMAX All Flash and PowerMax storage system installation and configurationprerequisites (continued)

Task Steps Notes

PowerMaxstoragesystems withSRDFreplication.

l Both the local and remote VMAX All Flasharrays are compliant with the bestpractices listed in the SRDF InterfamilyConnectivity Information documentation.

l All SAP instance-specific file systems andthe storage volumes on which they arestored are part of a storage group.

l All SAP instances of an SAP system arepart of a parent storage group and theparent storage group is protected usingSRDF Mode Synchronous.

l The volume pairs in the remote VMAX AllFlash/PowerMax storage array are alreadyestablished and fully synchronized.

l The SAP target physical host(s) or ESXihost(s) running the SAP VM are alreadyzoned and masked to the remote VMAX AllFlash/PowerMax storage array and it isrunning without any problems.

l VMAX-Remote-Replication documentation

VPLEX prerequisitesIf you are using VPLEX with ESI, confirm that the system is set up correctly.

Table 6 Dell EMC VPLEX storage system installation and configuration prerequisites

Task Steps Notes

PrepareVPLEXstorage forESI.

Confirm that the following steps havebeen completed.

1. The VPLEX storage system andthe underlying storage arrays arealready installed and configuredaccording to the VPLEX bestpractices.

2. A VPLEX extent has been createdwith an SAP instance-specific filesystem for each storage deviceyou want to claim in both VPLEXclusters.

3. Devices have been created toform a one-to-one mappingbetween extents and devices.

4. Distributed devices have beencreated to mirror across clusters.

When ESI creates a full clone of a virtual volume, it is visible onthe target host only after it is automatically added to a previouslycreated storage view containing the target host's initiators.

Storage view requirements:

l A unique initiator port has been registered and then added ineach storage view and has not been added to other storageviews.

l Storage views for the target SAP hosts that are used in thecloning process have been created. The storage views are onthe same cluster where the target host resides.

l The cloned virtual volume has not been added to otherstorage views separate from the target host storage views,as this would cause an ESI error.

Virtual volume requirements

l Ensure that all SAP system instance-specific mount pointsare based on virtual volumes (distributed or not) and based



https://support.emc.com/docu88908_SRDF-Interfamily-Connectivity-Information.pdf?language=en_US

https://support.emc.com/docu88908_SRDF-Interfamily-Connectivity-Information.pdf?language=en_US

https://support.emc.com/products/32067_VMAX-Remote-Replication/Documentation

Table 6 Dell EMC VPLEX storage system installation and configuration prerequisites (continued)

Task Steps Notes

5. Virtual volumes, consistencygroups, and storage views havebeen created, which VPLEXpresents to hosts using storageviews.

on supported Dell EMC storage systems that VPLEXmanages.

l Ensure that virtual volumes have one-to-one VPLEX elementconstraints and that all volumes come from a single VPLEXsystem Local or Metro.

l Ensure that a single SAP instance does not span multipleVPLEX systems and that volumes from different VPLEXclusters have not been combined.

l Ensure that each VPLEX Metro distributed virtual volume orlocal volume uses a single device that completely uses theclaimed storage volume. Distributed virtual volumes must beof equal size. The mirror of each virtual volume (local ordistributed) must lie entirely on one back-end array volumeand must be in an OK state before any cloning process isattempted. The back-end array volumes corresponding toeach mirror must be the exact size of the virtual volume.

l Ensure that the target hosts for the clone reside on the samecluster as the local virtual volume.

l Do not manually change the name of the cloned virtualvolume, because ESI will be unable to locate it.

l Do not populate the SAP host VMDK mount points in SAPLaMa that are stored on the VMware ESXi host internalstorage disks.

l Consider that if the local volume has two mirrors, the clonedlocal volume has only one mirror. If the distributed volumehas three mirrors, the cloned distributed volume has onlytwo mirrors with one in each cluster. The cloned virtualvolume also has two mirrors: one mirror in an array that isattached to cluster1 and the other mirror in an array that isattached to cluster2.

l You must unregister the initiators of a Host Bus Adapter(HBA) on the cluster that uses that HBA before you canremove a VPLEX cross-connected HBA from a VPLEX.

l Ensure that the source system virtual volumes have validmirrors in an OK state and they are residing in the samecluster as the target host before the clone is started.

VPLEX does not support the Managed Snapshot and Clone froma Managed Snapshot operations. SAP systems that use VPLEXstorage do not support System Clone and System Copy using theProvision New Host option.

Be aware ofVPLEXlimitations.

The following limitations exist for ESI on VPLEX:

l Heterogeneous VPLEX storage environments (using non-Dell EMC storage arrays) are not supportedby ESI.


VPLEX prerequisites 19

Table 6 Dell EMC VPLEX storage system installation and configuration prerequisites (continued)

Task Steps Notes

l The SAP instance-specific file systems must be stored either on direct storage devices for a storagearray or on VPLEX virtual devices.

l All VPLEX virtual volumes must be created with a one-to-one VPLEX element constraint, must haveunique names, and must come from a single VPLEX system. Do not combine virtual volumes from twoor more different VPLEX systems.

l When adding a new initiator to an SAP host, register the initiator in VPLEX and add it to a VPLEXstorage view before you use it. Register at least one initiator for each cluster. You can register onlyone initiator for a storage view from each cluster. The initiator ports that you add and use in onestorage view should be unique, and should not be added to or reused for any other storage views.

l Create each VPLEX distributed virtual volume or local volume using a single device that completelyuses the claimed storage volume. VPLEX distributed virtual volumes must be of equal size. The mirrorof each virtual volume (local or distributed) must lie entirely on one back-end array volume. Theback-end array volumes corresponding to each mirror must be exactly the same size as the virtualvolume.

l A storage administrator must manually create storage views for the target hosts that will be used inan SAP LaMa System Clone, System Copy, or System Refresh before starting any of theseprocesses.

l Ensure that the target hosts for the cloned devices reside on the same VPLEX cluster as the localvirtual volume.

l Snapshots and cloning from snapshots are not supported.

l Cloning is only supported by the native cloning technology of the VPLEX-managed storage array inuse.

Note

l For more information about using array-based and native copy technologies with VPLEX, refer to the EMC VPLEX: Leveraging Array-Based and Native Copy Technologies White Paper.

Unity prerequisitesEnsure that your system meets the requirements for Unity storage systems.

Table 7 Storage configuration for Unity storqage systems

Prerequisites for Unity Notes

Before you start any SAP LaMa system provisioning processes, log in toUnisphere for Unity and ensure that:

l All consistency groups containing SAP-instance-specific file systems,VMDKs, and dedicated datastores from Unity SAN/FC Block-basedLUNs are stored in separate consistency groups and have host accessto all ESXi hosts in the vSphere vCenter cluster.

l For SAP systems on Unity, after youcreate clones or snapshots (by usingSAP LaMa or directly on the storagesystem), you cannot modifyconfigured consistency groups.



https://www.emc.com/collateral/white-papers/h12642-wp-emc-vplex-leveraging-native-and-array-based-copy-technologies.pdf

Table 7 Storage configuration for Unity storqage systems

Prerequisites for Unity Notes

l All source SAP-instance-specific file systems that are based on UnityNAS or file-based NFS shares have host access to all ESXi hosts in thevSphere vCenter cluster.

l The default access is set to Read/Write, allow Root.

l All SAP instance LUNs reside in a single consistency group.

l Ensure that the only LUNs in the consistency group are the LUNs thatare used for the SAP instances.

l You can extend existing LUNs in theconsistency groups to increasestorage space for the SAP hosts.

IBM AIX operating system configuration prerequisites forESI

If you are using IBM AIX operating systems, ensure that the prerequisites have beenmet.

Table 8 ESI prerequisites and recommendations for IBM AIX-based SAP hosts


Ensure that all SAP systems that are running onIBM AIX operating systems are configured to useINLINE logging. This setting is a requirement forSolutions Enabler and Storage Resource Manager(SRM) operations.View the contents of the /etc/filesystemsfile, which shows Log = INLINE for each mount

point if the file system is configured to use INLINElogging. The logname attribute must use the

INLINE value to create a file system that usesINLINE logging.

l Conversion between Inline and Outline JFS2 Filesystem Logs

l For recommended commands and procedures to create a filesystem in an AIX operating system, see the AIX documentation.

l For more information about using the crfs command, see the

crfs Command in the IBM Knowledge Center.

Note

If any SAP file systems are not configured to use INLINE logging,move the contents of each file to a new file system that isconfigured to use INLINE logging. Converting a file system fromusing outline logging to inline logging corrupts its data.

Prerequisites and recommendations for vSphere with ESIEnsure that the your vSphere environment meets the requirements for deploying ESI.

Table 9 Storage configuration for VMware vSphere environment

Prerequisites, recommendations, and limitations for vSpherewith ESI

References and Notes

Ensure that you are running a fully configured VMware vCenter Serverversion 6.0U3h, 6.5 U1g, or U2d or later and that remote access usingthe VMware SDK is enabled.

VMware Knowledge Base article Buildnumbers and versions of VMware vCenter(2143838)


IBM AIX operating system configuration prerequisites for ESI 21

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

https://kb.vmware.com/s/article/2143838



Table 9 Storage configuration for VMware vSphere environment (continued)



l Ensure that all SAP vSphere virtual machines in the SAP landscapeare configured to take advantage of features like VMware vSpherevMotion, VMware High Availability (HA), and VMware DistributedResource Scheduler (DRS).

l Ensure that Storage DRS is disabled for all SAP VMs, because SAPLaMa with ESI does not support Storage DRS.

Configure all SAP virtual machine disks to use VMware PVSCSIadapters.

Configuring Disks to Use VMware ParavirtualSCSI (PVSCSI) adapters (1010398) in theVMware Knowledge Base

Ensure that existing SAP VMs with VMware Virtual raw device mapping(vRDM) disks are migrated to VMware physical raw device mapping(pRDM) disks or vSphere virtual machine disks (VMDKs), because ESIdoes not support vRDM disks.

Ensure that all SAP VM Guest OS file systems are stored on virtualmachine disks (VMDKs) that are separated from the SAP-instance-specific file system VMDKs.

Guest OS VMDKs must be stored on largeshared datastores with other SAP VMs withthe exact same configuration to enable theVMware HA Datastore Heartbeatfunctionality.

Ensure that the VMware vSphere virtual environment supporting theSAP Landscape is configured according to the SAP Note 2161991VMware vSphere configuration guidelines and the SAP on VMwarevSphere web page.

SAP Note 2161991 VMware vSphereconfiguration guidelinesSAP on VMware vSphere web page

l Ensure that SAP VMs with SAP file systems that are stored on NASor file-based NFS shares (such as VMAX All Flash or PowerMaxeNAS or Unity NAS) are mounted directly to the Guest OS of theSAP VM and that a central DNS server can resolve the NAS hostnames.If not, ensure that all /etc/hosts files on the SAP LaMa server,

source, and target servers are maintained with the same exactcontents.

l Ensure that each SAP-instance-specific file system is storeduniquely in one NFS share, because ESI does not support storingmultiple file systems on the same NFS share.

Ensure that the following requirements are in place for virtual SAPsystems with SAN/Block-FC connected volumes:

l SAP-instance-specific file systems on all VMs are stored onVMDKs.

l All SAP-instance-specific VMDKs are stored on datastores that arededicated to that specific SAP VM and are not shared with anyother VMs in the vCenter.

l All SAP-instance-specific VMDKs and datastores (LUNs formattedwith VMFS) are stored in the same storage groups (VMAX All Flashor PowerMax) or consistency groups (Unity).

SAP LaMa storage-based cloning provisioningprocesses invoke ESI to clone SAP-instance-specific file systems that are stored in largedatastores (LUNs or storage volumes at thestorage level) without the Guest OS filesystem. ESI calls the Dell EMC storage-specific cloning and replication technologiesto quickly and consistently create snapshotsor full clones of the LUNs/datastores andpresent them to the target SAP VMs. Thiscloning method offloads the CPU workload






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


https://wiki.scn.sap.com/wiki/display/VIRTUALIZATION/SAP+on+VMware+vSphere





Table 9 Storage configuration for VMware vSphere environment (continued)



from vCenter and ESXi hosts to the Dell EMCstorage systems.

l Ensure that for each SAP source system, all instance-specific filesystems, VMDKs, and dedicated datastores are stored in one parentstorage group, which is assigned to a VMAX All Flash or PowerMaxmasking view that grants access to all ESXi hosts in the vSpherecluster.

l Ensure that all ESXi hosts on the vCenter cluster are part of acascading or parent host group on Unisphere for PowerMax 9.0.

Ensure that the SAP-instance-specific file system VMDKs to be clonedby ESI are stored in dedicated datastores on the SAP VM where theinstance is running.

To prevent cloning by ESI, backup directoriesand other nonessential file systems should notbe stored in same datastores as the SAPinstance file systems.

Ensure that VMware tools are installed in the Guest OS of all SAP VMs.If the Guest OS is SLES 12, RHEL 7.2 or newer, the Open VM Tools(OVT) is installed as part of the operating system.

VMware Knowledge Base article 1014294 Howto Install VMware Tools

Document the zoning and masking of the VMware vSphere ESXi hosts,source, and target SAP systems and dedicated datastores on Dell EMCstorage system volumes.

This documentation provides before and afterconfiguration settings with all the requiredchanges, enabling you to minimize downtimeif reconfiguration becomes necessary.

Enabling the VMware VM advanced parameter disk.enableUUIDrequires that the all SAP VMs involved with SAP LaMa storage-basedsystem operations and provisioning processes are temporarily poweredoff and then restarted.Plan accordingly with the SAP and VMware administrators to minimizedisruption.

Ensure that the number of devices that will be cloned is not greaterthan 128 on vSphere 6.0 and not greater than 256 on vSphere 6.5.Avoid using numerous small LUNs or datastores because the vSphereESXi server is limited to 256 LUNs on vSphere 6.0 and 512 LUNs onvSphere 6.5.

ESI clones the source LUNs during thestorage-based cloning processes, and thenduplicates them. This cloning process couldexceed this limit and fail.

Ensure that the total of all paths is not greater than 512 on vSphere 6.0and not greater than 1,024 on vSphere 6.5. Because the vSphere ESXiServer has a limitation of 1,024 paths on vSphere 6.0 and 2,048 onvSphere 6.5, avoid using more than four paths for each LUN. If theLUNs being cloned have multiple paths, remember that the new LUNsthat ESI creates have the same number of paths, duplicating them.

For more information about vSphere storagemaximums see the following documents onthe VMware website: VMware ConfigurationMaximums for VMware vSphere 6.0 and VMware Configuration Maximums for vSphere6.5.


Prerequisites and recommendations for vSphere with ESI 23



https://www.vmware.com/PDF/VSPHERE6/R60/VSPHERE-60-CONFIGURATION-MAXIMUMS.PDF

https://www.vmware.com/PDF/VSPHERE6/R60/VSPHERE-60-CONFIGURATION-MAXIMUMS.PDF

https://www.vmware.com/pdf/vsphere6/r65/vsphere-65-configuration-maximums.pdf

https://www.vmware.com/pdf/vsphere6/r65/vsphere-65-configuration-maximums.pdf

Microsoft Windows operating system configuration for ESIIf you are using Windows, ensure that your environment meets the prerequisites.

Table 10 Microsoft Windows OS prerequisite tasks


Ensure that SAP supports the Microsoft Windows 2012 and2016 OS version and edition.

l SAP Community website > SAP on Windows

l SAP Note 1709155 System Provisioning with SAPLandscape Management

Ensure that all SAP hosts running on Windows Server 2012and 2016 and all SAP instance file systems are configuredaccording to the following ESI cloning requirements:

l Use only dynamic disks.

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

l Mount volumes only as junctions using the commandmklin to mount paths to additional disks from the C:drive.

l Do not use other drive letters such as F, G, and H.

l Use the Disk Management utility and select theMount Path option. For example, use SAP mountpoints as junctions or soft links mounted as aWindows mount path on the C: drive, with an

additional MC1 mount from disk 5 mounted in the C:\MC1 folder.

l SAP LaMa does not support NAS or NFS file-systemmount points for SAP instances on Windows.

The following steps should be completed on all Windowshosts that are running SAP systems, are managed by SAPLaMa, and will participate in the storage-based systemoperations and provisioning processes:

l Install Solutions Enabler 9.0.

l Install and configure the SAP Host Agent 7.21 latestpatch.

l Configure SE, SRM, and ELSA to integrate with theSAP Host Agent.

l Test the SAP Host Agent and SE, SRM, and ELSAintegration.

Refer to the ESI User Guide, Chapter 3: Configuring SAPHosts.

Turn off the firewall for retrieving the HBA properties andconfigure port 443 to enable an outgoing OS connection tothe physical host bus adapter (HBA) on all the Windows SAPhosts.



https://wiki.scn.sap.com/wiki/display/ATopics/SAP+on+Windows



SAP HANA platform systems installation and configurationtasks

Confirm with the SAP administrator, network administrator, and storage administratorthat SAP HANA prerequisites have been met.

Table 11 SAP HANA platform systems installation and configuration prerequisite tasks

Confirmwith:

Task Reference

SAPAdministrator

l All SAP HANA platform systems and instancesare installed on officially certified and supportedhardware and software.

l Operating system versions are configuredaccording to the stringent SAP requirements.

l All systems are running supported compute,network, and storage platforms.

SAP HANA Platform 2.0 > Installation andUpgrade > SAP HANA Server Installation andUpdate Guide.

The SAP HANA deployment option is an on-premises deployment with a tailored datacenterintegration (TDI) delivery approach.

SAPAdministrator

l SAP Host Agent (SAP HA) software version7.21 is installed on all SAP hosts.

l A password is set for the sapadm user.

l The /usr/sap/hostctrl is separate from

any of the SAP instance-specific mount pointslike /usr/sap/SID to guarantee that the SAP

LaMa Unprepare operation does not unmount it.

SAP Help Portal - SAP LaMa Enterprise Edition >type SAP Host Agent > click Search > Select

SAP Host Agent > SAP Host Agent Installation.

SAPAdministrator

All SAP HANA platform edition systems andinstances meet the following requirements:

l Installed and configured according to the SAPAdaptive Design concept (AC-Enabled) withvirtual IPs, host names, and SAP-instance-specific file systems that are stored on sharedcentral Dell EMC storage volumes.

l Every SAP NW instance was installed with thefollowing SAP SWPM command: sapinstSAPINST_USE_HOSTNAME=pasxxx or

ascsxxx or dbxxx or scsxx, where xxx is the

SAP System ID (SID).

SAP Help Portal - SAP LaMa Enterprise Edition >Application Help > SAP LaMa 3.0 EnterpriseEdition > SAP Landscape PreparationSAP Help Portal - SAP LaMa Enterprise Edition >Application Help > SAP LaMa 3.0 EnterpriseEdition > SAP Landscape Preparation > AdaptiveDesign

SAP Help Portal - SAP LaMa Enterprise Edition >Application Help > Managing SAP Landscapes >Provisioning

SAPAdministrator

l All SAP HANA platform instances are installedaccording to the SAP Adaptive Design conceptusing the hdblcm - h command to specify a

virtual hostname and corresponding virtual IP.

l All instances are decoupled from the operatingsystem of the hosts where the HANA platformsoftware is installed.

l An additional virtual IP address has beencreated for each tenant.

SAP Help Portal - SAP HANA Platform Edition >Administration > SAP HANA Administrator Guide> SAP HANA Lifecycle Management > SAP HANAPlatform Lifecycle Management.Refer to the following SAP official documentationif you are planning to use HANA as the databasepersistence for SAP NetWeaver:

l SAP Help Portal - SAP HANA PlatformEdition > Administration > SAP HANAAdministrator Guide > Availability and


SAP HANA platform systems installation and configuration tasks 25

https://help.sap.com/viewer/p/SAP_HANA_PLATFORM

https://help.sap.com/viewer/p/SAP_LANDSCAPE_MANAGEMENT_ENTERPRISE




https://help.sap.com/viewer/product/SAP_HANA_PLATFORM/2.0.03/en-US



Table 11 SAP HANA platform systems installation and configuration prerequisitetasks (continued)

Confirmwith:

Task Reference

l A third IP address was created for the SAPNetWeaver remote connection from the HANAclient, if SAP HANA will be used as a primarypersistence for SAP NetWeaver applicationsand SAP LaMa will automate SAP HANAreplication and high-availability use cases.

Note

When using SAP HANA as a databasepersistence and SAP NetWeaver (SAP NW) asthe application servers, the HANA clientinstallation is different than the standardstandalone SAP HANA client installationdescribed in the SAP HANA platformdocumentation. In this case, the SAP SoftwareProvisioning Manager tool (SAP SWPM) installsthe HANA client, which can be done using twoautomated methods:

n Local installation of the HANA client onevery SAP NW application server on thedirectory /usr/sap/SID/hdbclient

n Central installation of the SAP HANA clienton the SAP NW ASCS global shareddirectory /sapmnt/xxx/exe/uc/linuxx86_64/hdbclient, where xxx is

the SAP SID.

The latest versions of the SAP SWPM provide achoice between these two options during theinitial installation of the SAP NetWeaver PASinstance.

Scalability > High Availability for SAP HANA >Setting Up Host Auto-Failover > ConfiguringApplication Servers for Failover

l Stefan Seeman's blog https://blogs.sap.com/2015/04/14/sap-hana-client-software-different-ways-to-set-the-connectivity-data/

l Michael Healy's blog https://blogs.sap.com/2016/08/15/troubleshooting-hdbuserstore-key-issues/

Refer to the following SAP Notes:

l https://launchpad.support.sap.com/#/notes/1943235 - SAP HANA client installation

l https://launchpad.support.sap.com/#/notes/1930853 - HdbUserStore contains toomany SAP HANA nodes

l https://launchpad.support.sap.com/#/notes/2120226 - SAP HANA client softwareand entries in hdbuserstore when using virtualhost names for SAP application servers

l https://launchpad.support.sap.com/#/notes2250144/ - TroubleshootingHdbuserstore issues

l https://launchpad.support.sap.com/#/notes/1828028 - DBCON connection toremote HANA database cannot be established

SAPAdministrator

l All SAP HANA instance-specific file systems /hana/log/HSID, /hana/log/HSID are

based on SAN-FC/Block.

l The /hana/shared file is block-based for

HANA scale-up systems and NAS/NFS-basedfor HANA scale-out models that are sharedacross all SAP HANA system worker nodes.

SAP Help Portal - SAP HANA Platform Edition >Installation and UpgradeSAP Help Portal - SAP LaMa Enterprise Edition >Application Help > SAP LaMa 3.0 EnterpriseEdition > SAP Landscape Preparation

SAPAdministratorStorageAdministrator

SAP systems on physical hosts to be managed bySAP LaMa using storage-based cloning areconfigured as follows:

l The operating system file systems reside onlocal disks that are directly attached to theserver or on SAN dedicated LUNs for that host.

SAP Help Portal - SAP LaMa Enterprise Edition >Application Help > SAP LaMa 3.0 EnterpriseEdition > SAP Landscape Preparation.SAP Help Portal - SAP LaMa Enterprise Edition >Application Help > SAP LaMa 3.0 EnterpriseEdition > SAP Landscape Preparation > AdaptiveDesign.



HTTPS://BLOGS.SAP.COM/2015/04/14/SAP-HANA-CLIENT-SOFTWARE-DIFFERENT-WAYS-TO-SET-THE-CONNECTIVITY-DATA/




HTTPS://BLOGS.SAP.COM/2016/08/15/TROUBLESHOOTING-HDBUSERSTORE-KEY-ISSUES/



https://launchpad.support.sap.com/#/NOTES/NOTENR,














Table 11 SAP HANA platform systems installation and configuration prerequisitetasks (continued)

Confirmwith:

Task Reference

l The SAP instance-specific file system mountpoints are stored in dedicated SAN-FC LUNsseparated from the operating system LUNs orlocal disks in all SAP hosts, because ESI onlyclones the dedicated LUNs with the SAP-instance-specific file system mount points. Thisseparation avoids duplication of the operatingsystem file systems when cloning.

l The SAN-FC LUNs used by the SAP instance-specific file systems of the source systems areused only by these SAP systems.


Confirm that all SAP source and target systemhosts are configured to use a central user-management server, such as the LightweightDirectory Access protocol (LDAP).If not, ensure that all the SAP operating system userand group IDs are synchronized across the hosts.

Refer to the SAP hosts documentation for theappropriate operating system.


NetworkAdministrator

l All SAP target hosts are set up.

l Operating system is installed, configured, andrunning.

l Administrators can access all the other SAPservers in the network, especially SAP LaMa.

l Administrators have R/W access to the DellEMC central shared storage systems and theSAP Host Agent 7.21 is installed, configured,and running without errors.

Refer to the SAP hosts OS-specificdocumentation.Refer to the network documentation.

Refer to the Dell EMC storage-specificdocumentation.

Refer to the SAP Help Portal - SAP LaMaEnterprise Edition > Application Help > SAP LaMa3.0 Enterprise Edition > SAP LandscapePreparation.

SAPAdministrator

SAP Adaptive Extensions 1.0 is installed on all SAPhosts in the SAP Host Agent localdirectory /usr/sap/hostctrl/ and it is running

without any errors.

SAP Help Portal > SAP Adaptive Extensions >Installation.SAP Note 1759181 - Installation ofSAPACEXT:SAR

SAP LaMa installation and configuration tasksEnsure that your environment meets the required prerequisites for SAP LaMa.

Table 12 SAP LaMa installation and configuration tasks


Ensure that the SAP NetWeaver 7.5 Java Stack ApplicationServer with SP11 on Linux is already installed and correctlyconfigured according to the SAP NetWeaver Java and SAPHANA official documentation.

SAP NetWeaver 7.50 > Installation and Upgrade >Installation Guides > Install new system > Java > SAPHANA database > Installation Guide: SAP systems


SAP LaMa installation and configuration tasks 27



https://help.sap.com/viewer/index

https://launchpad.support.sap.com/#/NOTES/1759181

https://launchpad.support.sap.com/#/NOTES/1759181

https://help.sap.com/viewer/p/SAP_NETWEAVER_750

Table 12 SAP LaMa installation and configuration tasks (continued)


Based on the SAP Application Server Java of SAPNetWeaver on UNIX: SAP HANA database

SAP LaMa 3.0 SP7 P4 or higher is installed and configuredwith the SAP Landscape Management official documentation.

SAP Help Portal - SAP LaMa Enterprise Edition >Installation and Upgrade

SAP LaMa is configured correctly. SAP Help Portal - SAP LaMa Enterprise Edition >Application Help > SAP LaMa 3.0 Enterprise Edition >SAP Landscape Configuration

SAP LaMa is running without any problems and with all SAPsystems and hosts discovered, configured, and without anyvalidation errors or warnings.

SAP Help Portal - SAP LaMa Enterprise Edition >Application Help > SAP LaMa 3.0 Enterprise Edition >Managing System Landscapes

EHAC appliance deployment prerequisite tasksEnsure that the EHAC appliance is set up correctly.

Table 13 EHAC prerequisite tasks

Task Reference

Ensure that the Dell EMC storage systems that host the SAP systemsmanaged by SAP LaMa are zoned and masked according to the requirementsdescribed in Storage system prerequisites on page 16.

Refer to the appropriate Dell EMCstorage system documentation.

Ensure that the required storage-system replication licenses to createsnapshots and clones were installed before deploying the EHAC appliance.

Refer to the appropriate Dell EMCstorage system documentation andrequest the required licenses from theDell EMC support team.

Ensure that networking connectivity exists between the EHAC appliance, theDell EMC storage systems, VMware vCenter, physical and virtual SAP hosts,and a DNS server.


Ensure that a firewall is not blocking the following network ports: 22 SFTP,SSH, 8080 HTTP, and HTTPS.


Ensure that the customer or partner data center where the physical EHACappliance Dell PowerEdge R640 rack mount server will be installed has acompatible rack, power outlets, PDUs and switches, and network cablesworking and available for connection to the EHAC appliance server and thecustomer/core network.

l Refer to the Dell EMC PowerEdgeR640 rack mount serverdocumentation.

l Contact your Dell EMCrepresentative before the ESIImplementation service is acquiredto help you to plan yourinfrastructure accordingly.






CHAPTER 4

Solution Deployment


l Deployment overview.........................................................................................30

Solution Deployment 29

Deployment overviewFollow the steps in the ESI Administration Guide, the ESI User Guide, and thefollowing chapters to deploy the solution.

Note

Ensure that you have completed all the prerequisites in Solution Prerequisites on page13 before attempting to deploy the solution. These prerequisites help ensure asuccessful deployment.

The following table describes the high-level steps that are required to implement theESI for SAP LaMa solution with references to detailed instructions in the solutiondocumentation set.

Step Task Reference

1 Install and configure the EHACAppliance.

ESI for SAP LaMa Administration Guide, Chapters3–8

2 Configure SAP Hosts for SAP LaMastorage-based integration.

ESI for SAP LaMa User Guide, Chapter 3,Configure SAP Hosts

3 Configure SAP LaMa to integratewith ESI.

Chapter 5, Solution Configuration

4 Run SAP LaMa system operationsand provisioning process.

Chapter 6, Solution Verification

Solution Deployment


CHAPTER 5

Solution Configuration


l Configuration overview...................................................................................... 32l Configure initial settings.................................................................................... 34l Retrieve host-specific storage properties.......................................................... 35l Configure properties for SAP system instances................................................. 36l Retrieve mount points for application instances.................................................37l Configure system provisioning........................................................................... 39

Solution Configuration 31

Configuration overviewAfter SAP LaMa software is installed, you must configure it to work with ESI.

This chapter describes the advanced configurations that are required to enablestorage-based cloning of Dell EMC storage in SAP LaMa.

Ensure that the following steps have been completed as described in SolutionPrerequisites on page 13 and Solution Deployment on page 29:

l SAP LaMa is installed and running.

l The EHAC service on the EHAC server is started, and an SAP LaMa user wascreated and granted storage access.

l The SAP systems are adaptively installed and discovered in SAP LaMa with novalidation warnings or errors.

l The SAP Host Agent with SAP Adaptive Extensions are installed, configured, andstarted on all SAP hosts.

l Solutions Enabler is installed and configured on each SAP host using instance-specific file systems that are stored on SAN/FC block storage volumes fromsupported Dell EMC storage arrays.

l The vCenter and ESXi hosts that are running virtual SAP systems are configuredon the EHAC Administrator Console (EHAC Console).

Status definitionsSAP LaMa monitors all system, instance, and operating system hosts and reports thestatus of each.

SAP LaMa monitoring displays the status for SAP instances. Status values anddefinitions are listed in the following table.

Table 14 SAP instance status definitions

Status Definition

Initial Instance file systems are not mounted and the instance virtual hostname isnot active.

Partiallyprepared

l Instance file systems are mounted, but the virtual hostname is notactive.

l Virtual hostname is active, but instance file systems are not mounted.

Prepared Instance file systems are mounted and the virtual hostname is active.

Not running Instance file systems are mounted, the virtual hostname is active, but theSAP services are not running.

Not runningwith issues

Instance file systems are mounted, the virtual hostname is active, butvalidation issues exist.

Running Instance file systems are mounted, the virtual hostname is active, and theSAP instance services are running.



Table 14 SAP instance status definitions (continued)

Status Definition

Running withissues

Instance file systems are mounted, its virtual hostname is active, and theSAP instance services are running, but the SAP host the instance is runningon or the instance services have validation issues.

SAP LaMa operationsThe Stop, Start, Unprepare, Prepare, and Relocation operations can be run on a singleSAP instance or as a mass operation that affects more than one instance or a wholeSAP system.

The Start and Stop operations can be run simultaneously for multiple SAP systems orsequentially for multiple instances of the same SAP system that are distributed onmultiple hosts.

For example, the SAP LaMa administrator can run a Mass Stop of several SAPsystems to power them down for electrical maintenance on the data center.

Operation definitionsThe following table lists the SAP LaMa operations:

Table 15 SAP LaMa operation prerequisites and results

Operation Result Prerequisite Notes

Prepare l Mounts the SAP instance filesystems to a selected host

l Activates the virtual hostname

l Sets the instance state to"Prepared"

SAP instance was installed AC -Enabled and has dedicated SAPinstance file systems from sharedcentral storage systems and avirtual hostname.

The SAP instance file systems aredefined by using the RetrieveMount points operation duringSAP LaMa implementation andconfiguration.

Unprepare l Unmounts the SAP instance filesystems from the host

l Deactivates the virtual hostname

l Sets the instance state to "Initial"

The instance is in a "Not running"state.

Use this operation with the Stopoperation to perform systemmaintenance. You can thenprepare the system again whenmaintenance is completed.

Start Moves the selected SAP instancefrom a "Not running" to a "Running"state.

The instance is in the "Prepared"state.

This operation can be run on oneor more SAP instances.

Stop Stops the selected SAP instance andsets its status from "Running" to"Not Running."

The instance is in a "Running"state.

This operation can be run on oneor more SAP instances of an SAPsystem or on the entire SAPsystem.

ESI with SAP LaMa operations on VMware vSphere hostsWhen ESI is integrated with SAP LaMa, ESI can execute the following Unprepareactivities for vSphere SAP virtual hosts:

l Identify the VMDK disks that are attached to the SAP VM and store thisinformation in the EHAC database for later use (in a Prepare operation, forexample).


SAP LaMa operations 33

l Remove the unmounted VMDK disks containing the SAP instance file systemsfrom the SAP VM.

l Unmount all SAP VM datastores from ESXi servers in the vCenter cluster.

l Detach all unmounted SAP VM-dedicated datastores from ESXi servers in thevCenter cluster.

l Rescan the vCenter storage to guarantee that the unmounted datastores aredetached from all ESXi hosts in the vCenter cluster.

ESI with SAP LaMa operationsWhen SAP LaMa is integrated with ESI on vSphere virtual or physical hosts, it can alsoremove the SAP instance storage volumes from the storage group (on VMAX All Flashand PowerMax) or Consistency Group (on Unity).

Configure initial settingsConfigure the parameters required to integrate SAP LaMa with Dell EMC components.

Procedure

1. From the SAP LaMa UI, click Setup.

2. Under Settings, customize the following parameters as required: UserInterface, Notification, Engine, Monitoring, and ACM.

For our solution verification testing, we selected the following Engine settings:

l Allow Multiple Instances on Same Host

l Automatic Mountpoint Creation

l Automatic Mountpoint Deletion

l Show Advanced Shutdown Options when Stopping Operations

The Expert mode, shown in the following figure, provides more customizablesettings, such as Timeouts. For the solution verification tests, we used thedefault settings for all Timeout parameters.



Figure 2 Configuring settings in SAP LaMa

3. Verify and configure all SAP LaMa Setup menu tabs. Ensure that the timeoutfor operations that involve SAP instance operations is set to zero. This settingavoids timeout of System Clone, System Copy, and System Refresh processes.

Retrieve host-specific storage propertiesConfigure the newly discovered hosts.

Procedure

1. Select Configuration > Hosts, select the host, and edit as required.

2. Review and confirm the Basic Configuration.

3. Click Retrieve from Host to retrieve the storage properties of the host, whichis the HBA of the physical server.

Note

If you plan to use the host for system provisioning, select Isolation Ready.

4. Configure the SAP LaMa Configuration menu Host tabs to discover and addthe source and target SAP hosts, networks, and HBAs.


Retrieve host-specific storage properties 35

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 hba -fibreIf this command does not work, there is an issue with the Solutions Enablerconfiguration. The Dell EMC Solutions Enabler 9.0 Installation andConfiguration Guide provides more information.

Results

The hosts are configured as shown in the following figure.Figure 3 Configuring SAP LaMa host properties

Configure properties for SAP system instancesConfigure SAP properties for each application instance associated with a system.

Procedure

1. From Configuration, select your system and, for each instance, click Edit tomodify the configuration, as shown in the following figure.



Figure 4 Configuring SAP system instance properties

2. Select 1 to display the Basic configurations screen and set the requiredparameters.

3. Select 2 to display the Instance properties screen.

4. Under Adaptive Enablement, select AC-Enabled, and accept the settings forVirtual Hostnames and Networks and Required Host Type, as shown in thefollowing figure.

Figure 5 SAP LaMa instance properties

Retrieve mount points for application instancesAdd mount points to enable operations on the system.

Before you begin

Before you start any SAP LaMa provisioning processes, ensure that all SAP instance-specific mount points are not local operating system directories of the SAP host. AllSAP instance-specific mount points must be verified, adjusted, and approved by theSAP administrator who supports the SAP LaMa implementation at the customer site.


Retrieve mount points for application instances 37

Procedure

1. Select 3 to display the Mount points screen.

2. Clear OS managed Mounts (Automounter).

3. Click Retrieve Mount list to populate the mount list with all mount points onthe resource or server.

Using this method to automatically retrieve mount points avoids errors.

4. Select the mount points that do not pertain to this SAP instance and clickRemove.

The following figure shows an example of an Oracle database instance, whichcontains SAN-FC block-based mount points, volume groups, their logicalvolumes, and physical LUNs (VMAX device IDs) where they are stored.Figure 6 SAP LaMa Oracle Database Instance configuration mount points

5. Repeat these steps for each application instance in the system.

Example 1 SAP PAS instance

The following figure shows a sample SAP Primary Application Server instance, whichcontains NAS-NFS file-based mount points, volume groups, their logical volumes, andphysical LUNs (VMAX eNAS device IDs) where they are stored.



Example 1 SAP PAS instance (continued)

Figure 7 SAP PAS Instance configuration mount points

After you finish

After the configuration of all instances and hosts of every system in the landscape, runan SAP LaMa validation. After the validation runs successfully, the hosts andinstances are ready for SAP LaMa operations, as shown in the following figure.

Figure 8 SAP System Instances and host configured for operations

Configure system provisioningTo enable SAP LaMa system clone, copy, or refresh processes, the SAP administratorat the customer site must configure the SAP systems.

Before you begin

l Ensure that Dell EMC personnel have completed the configuration steps in Configure initial settings on page 34, Retrieve host-specific storage properties onpage 35, Configure properties for SAP system instances on page 36, and Retrievemount points for application instances on page 37.

l Configure the Systems tab in the SAP LaMa Configuration menu to discover andadd the SAP instances that SAP LaMa manages:


Configure system provisioning 39

n Configure all the SAP settings to enable 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.

n Configure the network isolation settings to always enable open communicationwith the ESXi hosts, the EHAC server, and any central NFS, Domain NameSystem (DNS), and Lightweight Directory Access Protocol (LDAP) serversthat the SAP LaMa source and target systems use. You can configure thesesettings for VMware virtual, physical, or IBM AIX logical partition environments.

n Configure the mount points for each of the instances associated with a sourcesystem. Confirm with your SAP, database, operating system, and storageadministrators that all the SAP instance-specific file systems are stored in thestorage volumes that are identified in the Export Paths.

n Configure the SAP LaMa Infrastructure menu tabs, especially the Network,User Management, Name Management, and Storage Managers tabs.

See SAP LaMa Infrastructure Configuration instructions on the SAP LandscapeManagement 3.0, Enterprise Edition page in the SAP Help Portal, and then goto Configuration and Deployment Information > Landscape Configuration >Managing System Landscapes > Provisioning Systems.

l In the SAPLaMa Operations menu, run all the instance and host validations andconfirm that they are in the correct state (green).

Dell EMC personnel should work with the SAP administrator to ensure that thefollowing tasks are completed. The SAP administrator should refer to the SAPdocumentation for help on these tasks.

Procedure

1. Set a system flag for cloning and copying:

a. Select Configuration > Systems and select the system.

b. Click Edit > Provisioning & RFC.

c. Select Cloning and Copying, as shown in the following figure.



http://help.sap.com/lamaent30



Figure 9 Enabling the system for online system clone, system copy, and systemrefresh

d. For Oracle only: In the Provisioning and RFC step, configure a transfermount for redo logs. When the SAP system on the source is running andusing an Oracle database, configure an NFS share to transfer the redo logsfrom the source to the target system.

2. Configure Remote Function Call (RFC) for system copy/refresh.

For System Copy and System Refresh operations, RFC defines connections torun Post Copy Automation (PCA). Confirm with the customer's SAPadministrator that the RFC destinations are configured to communicate to theSAP systems involved in the SAP LaMa system provisioning processes.

Note

For more information about the SAP LaMa 3.0 Enterprise Edition, refer to Provisioning and Remote Function Call (RFC) Application Help > SAPLandscape Management 3.0, Enterprise Edition > Landscape Preparation >

Initial Entities Configuration > Configuring Systems > Provisioning andRemote Function Call (RFC).

3. Ensure that the UUID parameter is set.

SAP requires that the source SAP system/UUID profile parameter is set for theSAP systems that are involved in an SAP LaMa system provisioning process.


Configure system provisioning 41

https://help.sap.com/viewer/p/SAP_LANDSCAPE_MANAGEMENT_ENTERPRISE%20

Confirm with the customer's SAP administrator that the UUID parameter isconfigured correctly.

Note

For more information about the SAP LaMa 3.0 Enterprise Edition, refer to Provisioning and Remote Function Call (RFC)Application Help > SAPLandscape Management 3.0, Enterprise Edition > Landscape Preparation >

Initial Entities Configuration > Configuring Instances > BasicConfiguration > Configuring Advanced Instance Settings.

4. Define the path to SAP Software Provisioning Manager (SWPM) for SAP LaMasystem Copy and Refresh.

For the SAP LaMa system Copy and Refresh processes, the SWPM must bemade available to SAP LaMa. The System Copy and System Refresh processesrun a system rename process for the storage-based cloned volumes to thetarget SID and host names.

Refer to the SAP documentation for more information about this task.

Confirm with the customer's SAP administrator that the path to SAP SWPM isconfigured correctly in the SAP LaMa system-provisioning processes.

Note

As a best practice, use a central NFS server to define the Export Path andshare the SAP SWPM software to all SAP hosts.

5. Confirm with the SAP system administrator that the following configurationsare in place in accordance with SAP documentation:

l Central NFS server for software distribution

l Central NTP server synchronization

l Central DNS configuration

l Central SAP user management configuration

6. Configure and prepare the target hosts in the same manner as the sourceserver. Ensure that the prerequisites have been completed, which are the sameas for the source hosts.




CHAPTER 6

Solution Verification

Verify the deployment by running the operations in this chapter:

l Run Mass Stop with Unprepare..........................................................................44l Run Mass Start with Prepare............................................................................. 47l Relocate the SAP system...................................................................................49l Managing snapshots.......................................................................................... 53l Using SAP LaMa System Provisioning Processes.............................................. 58l Running System Destroy....................................................................................65

Solution Verification 43

Run Mass Stop with UnprepareMass Stop with Unprepare stops the selected SAP instances from a Running state.Unprepare removes the instances from the host and sets the instances state to Initial.

Before you begin

Use the SAP LaMa UI to:

l Ensure that Storage Manager was added. Select Infrastructure > StorageManagers.

l Confirm that all volumes and volume group information are cached. SelectOperations > Storage to confirm. Select Monitoring Data to cache any uncachedinformation.

l Ensure that the SAP system is running and that hosts are assigned to the correctinstances. Select Operations > Hosts.

l To prevent the operation from failing, ensure that the SAP LaMa storage cache isupdated and that any NFS export files are listed. Select Storage > StorageOverview.

Success criteria:

l The SAP LaMa Mass Stop with Unprepare process runs successfully withouterrors.

l The SAP instance-specific virtual host names and virtual IP addresses aredeactivated.

l All the SAP instance-specific file systems are unmounted and removed from theSAP System virtual host.

Note

Do not manually execute an Unprepare operation for an SAP instance outside of SAPLaMa, because ESI is unable to store the layout of the vSphere VM VMDK disks. Thelayout is required to perform a subsequent prepare operation on the same or anotherSAP host.

Procedure

1. From the SAP LaMa GUI, select Operations > Systems.

2. Select the SAP system on which to perform the Mass Stop with Unprepareoperation.



Figure 10 Selecting the SAP system for the Unprepare operation

3. Under Mass Operations, select each instance of the selected SAP system, andclick Stop (including unprepare if possible), as shown in the following figure.

Figure 11 Selecting instances and starting the Mass Unprepare operation

Note

The operation fails if any SAP instance service or dependent program is runningand locks any of the file systems on the SAP host where the Mass Unprepareoperation is running. For example, if a user is logged in to the host through SSHand issues a cd command to an SAP file system, such as /usr/sap/SID,which is one of the directories that belongs to the mount point beingunmounted, the Unprepare operation is likely to fail. The most common error forthe Unprepare step is: The specified file system could not beinterrogated.

4. Select Monitoring > Activities, select the Stop and unprepare entry, and viewthe details in the Log Details window, as shown in the following figure.


Run Mass Stop with Unprepare 45

Figure 12 Monitoring the Mass Stop and Unprepare operations

5. Select Advanced Operations > Systems, select the EC1 System entry andview its details.

Figure 13 SAP LaMa advanced operations after Mass Stop with Unprepare

6. Log in to the vSphere vCenter Web Client to verify that all the datastores forthe eccsrc VM are detached from the host, as shown in the following figure.



Figure 14 vSphere vCenter server, VM datastores before and after Mass Stop withUnprepare

Run Mass Start with PrepareThe SAP LaMa Mass Start with Prepare operation mounts and starts the selectedSAP instances from a central storage system to an assigned virtual SAP host.

Before you begin

l Ensure that the SAP systems are in an Unprepared state with no SAP instance-specific file systems mounted.

l Select Infrastructure > Storage Managers and check the following:

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

n Test the storage manager connection and retrieve all arrays that are associatedwith the EHAC user.

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

l Select Operations > Storage to verify that the storage information is cached. If itis not, click Monitoring Data to refresh the information about the SAP LaMastorage cache.

Select Operations > Hosts to verify that the SAP hosts have no errors or validationissues.

The success criteria are as follows:

l The SAP LaMa Mass Start with Prepare operation runs without errors.

l The SAP virtual host names and virtual IP addresses are activated in the operatingsystem of the selected host.

l All SAP file systems for the selected instance are mounted and added to the SAPhost.


Run Mass Start with Prepare 47

Procedure

1. From the SAP LaMa GUI, select Operations and Maintenance > Operations >Systems > Mass Operations, and then perform one of the following steps:

l Click Auto Assign.

l Manually select the host from the available hosts.

2. Select the instances on which to perform the Mass Start with Prepareoperation and click Start (including prepare if possible), as shown in thefollowing figure.

Figure 15 Selecting the Start operation

3. Confirm the Host Assignment and click Execute, as shown in the followingfigure.

Figure 16 Executing the Mass Prepare operation for an instance



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

Figure 17 Viewing log details after the Mass Prepare operation

Results

The datastores are attached and mounted to all ESXi servers in the vSphere clusterand the SAP virtual host is prepared and started after a successful Mass Start withPrepare operation, as shown in the following figure.Figure 18 Verifying the Mass Start with Prepare operation

Relocate the SAP systemThe SAP System Relocation operation enables the SAP system to be moved from anexisting host to another host that 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.


Relocate the SAP system 49

ESI for SAP LaMa supports all relocation options:

l Physical-to-physical relocation

l Physical-to-virtual relocation, which is supported for physical volumes that arecopied to vSphere using pRDM disks on the target

l Virtual-to-virtual relocation

l Virtual-to-physical relocation, which is supported only for vSphere virtualmachines that use pRDM disks and are copied to physical volumes

Success criteria:

The SAP LaMa System Relocation operation runs successfully without errors orretries, and moves the SAP system from SAP host A to SAP host B.

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 that areassociated with the EHAC user.

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

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

2. Click Operation and Maintenance > Operations > Storage, and confirm thatall volumes and volume 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 the green icon next to the host names indicates.

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 19 Performing a System Relocation

WARNING

In Linux/Unix systems, SAP uses the relocated system mount options onceduring the Prepare step of the System Relocation operation and thesettings are not saved. For that reason, any further operations on therelocated system require that the administrator refresh the export pathentries in SAP LaMa, as follows: Select Configuration > System, select theinstance and click Edit > Mount Points > Retrieve Mount List.

Accelerate SAP LaMa system operations in vSphere vCenterOn VMware cluster-based virtual environments, the storage administrator (or SAPadministrator with an EHAC appliance account) can set an ESI-specific configurationproperty on the EHAC server to accelerate the SAP LaMa Mass Unprepare, Prepare,or virtual-to-virtual System Relocation operations in a vSphere cluster-basedenvironment.

This optional configuration property:

l Provides fast and efficient relocation of SAP systems from source to target virtualhosts

l Saves time during vSphere virtual-to-virtual relocation operations by removing thestorage layer operations of unmasking and masking LUNs to ESXi hosts

l Moves only the SAP instance-specific file systems that are stored in VMDKs fromthe source to the target SAP virtual machines


Accelerate SAP LaMa system operations in vSphere vCenter 51

Note

For all other SAP LaMa system provisioning processes, such as System Clone, SystemCopy, System Destroy, and System Refresh, keep the default value in the /opt/wildfly/ESI_application.properties file, which isRelocationWithNoVolumes=False. If you change the setting for System Clone,Copy, or Refresh processes, ESI skips the physical storage operations and theoperation fails during the Prepare steps. If you have this problem, set theconfiguration property RelocationWithNoVolumes=True and retry the SystemClone, Copy, or Refresh process that failed in the Prepare step.The following procedure uses the bash shell scriptmain_esi60_4_saplama30_MMMYY.sh to activate and deactivate the acceleration,where MMMYY is the month and year of the last update of the script.

Procedure

1. Complete all running Mass or instance-specific Prepare, Unprepare, andRelocate operations and hold the execution of new ones.

2. Complete all running System Clone, Copy, Refresh, and System Destroyprocesses and hold the execution of all new ones.

3. Use SSH to log in to the EHAC appliance and go to the directory /var/binaries.

4. Run the main_esi60_4_saplama30_MMMYY.sh script.

5. Under CONFIGURATION OPTIONS, type a to activate the EHAC configurationparameter RelocationWithNoVolumes=True. This setting skips the ESIstorage system commands and enables ESI to move VMware VMDKs from oneSAP virtual machine to another. The following figure shows the availableconfiguration options.

Figure 20 ESI appliance main configuration script

6. Perform the System Relocation on VMware vSphere Virtual environments. Donot run any System Clone, Copy, Refresh, or Destroy processes.



7. After you have completed all system relocations in virtual environments, goback to the EHAC appliance SSH session and run themain_esi60_4_saplama30_MMMYY.sh script again and type d to deactivatethe accelerated System Relocation on VMware vSphere virtual environments.

8. Resume the System Clone, Copy, Refresh, and Destroy system provisioningprocesses.

Managing snapshotsAfter you have installed a storage manager and verified all provisioning prerequisites,you can provision new SAP system 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 followed by a unique ID, abbreviated if necessary to fit the 64-character limitationon snapshot naming.

Note

You cannot create or manage snapshots for VPLEX systems.

NOTICE

All snapshot operations on VMAX All Flash, including Manage Snapshots, Snap-Clones, and Snap-Copies, use the SnapVX technology. Any snapshots for the sourcevolumes that are taken outside of ESI for SAP LaMa cannot be used in SAP LaMa. Anyattempt to rename snapshots to the ESI convention results in failure, as they aremutually exclusive snapshot creation methods, even if they use the same SnapVXtechnology.

Create a snapshotCreate a snapshot, or a checkpoint in time, for SAP systems on any supported file orblock storage system.

Procedure

1. Select Provisioning > System and AS > Manage System Snapshots.

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


Managing snapshots 53

Figure 21 Creating a snapshot

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

The snapshot is displayed in the Manage Snapshots of System dialog box.

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

5. Click Take Snapshot.

Create an online snapshotCreate a snapshot or a checkpoint in time, for a selected SAP system when a databaseis online or offline.

Before you begin

Ensure that you have verified the Oracle redo logs.

Procedure

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



Figure 22 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 23 Selecting data for a snapshot

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


Create an online snapshot 55

Figure 24 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 25 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 that each component performs, as shown in thefollowing figure.



Figure 26 Viewing snapshot log details

View snapshotsWhen you view snapshots in the SAP LaMa UI, you see only the storage snapshotsthat were created from the SAP LaMa Provisioning Manage Snapshots functionality.Other snapshots that were created at the storage-array level with Dell EMC Unisphereor SYMCLI commands do not appear.

Procedure

1. Click Provisioning > Manage System Snapshots.

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

Figure 27 Viewing snapshots


View snapshots 57

Remove a snapshotDelete a snapshot that is no longer needed.

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. SAP compares the number of volumes to that of the numberof snapshots ESI for SAP LaMa returns from the storage, which causesinconsistencies.

Figure 28 Removing a snapshot

Using SAP LaMa System Provisioning ProcessesThe SAP LaMa system provisioning processes are System Clone, System Copy, andSystem Refresh.

PrerequisitesConfirm with the storage administrator that storage host access or masking views arecreated for the target servers before you run SAP LaMa system provisioningprocesses. The ESI plugin can expose storage volumes to SAP LaMa targets using onlynew storage groups and masking views. For additional details, see Storage systemprerequisites on page 16.

Provisioning process optionsYou can create system clones or copies either from the live system or by using anexisting SAP LaMa snapshot that was created at an earlier point in time. The availablestorage replication options depend on the storage system type, as shown in thefollowing table. The default cloning processes for VMAX All Flash, PowerMax,



XtremIO, and Unity create space-efficient snapshots of the source volumes from thindevices.

For the Clone, Copy, and Refresh processes, you can also create a full clone or copyfor both file and block storage systems. Creating a full clone creates a full copy of thevolumes, which is different from taking snapshots. Confirm that the storage systemhas enough space to perform the full clone operation. Refer to the following table forresults of selecting this option.

Table 16 Storage systems and storage replication options

Storagesystem

Default storage replication options Full clone/copy option

VMAX AllFlash/PowerMax

l Dell EMC TimeFinder SnapVXsnapshots and clones

l SnapVX snapshot on a remote storagesystem in a synchronous SRDFreplication environment

The Full Clone option on VMAXAll Flash or PowerMax systemscopies all contents of the sourcevolumes to the new volumes. Theprocess can take longer and mightconsume double the storage spaceresources of the source system,depending on deduplication results.We recommend that you avoid thisoption, if possible.

VPLEX VPLEX storage arrays support only fullclones that use storage layer replicationtechniques.

Full clone is the only option forVPLEX.

XtremIO l Snap clone A full clone cannot be created withXtremIO. The cloning process inXtremIO creates a snapshot on thearray and mounts it on the targetmachine. The snapshots that arecreated on the array are namedwith prefixes of ESISnap and

ESIClone and depend on the type

of cloning process that you use.

Unity l Thin Clones for SAN

l Unified Snapshot for NAS and SAN

For Unity, thin clones are created

whether the Full Clone option isselected or not.

Important notes

l When creating a clone on a file or block storage system, do not change the nameof either the source or the target file systems.

l You must have sufficient disk space in a target pool to create a full clone of thesource.

l When you perform a system clone, the target system is isolated on the network bythe settings that are configured in SAP LaMa Configuration > Instances >Network Isolation.


Using SAP LaMa System Provisioning Processes 59

Create a cloneYou can create a clone to perform a full copy of the selected volumes.

Procedure

1. Click Provisioning.

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, ensure that you select asource system that contains the mount configuration for database online redologs in SAP LaMa > Configuration > Select System > Edit > Provisioning &RFC.

4. Follow the first three System Cloning steps: (1) Basic; (2) Hosts; and (3) HostNames.

5. Click Next.

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

Note

To use snapshots for attaching to host, which is the space saving approach tocloning, clear the check box for all storage volumes.

l For VMAX All Flash arrays, cloning creates a SnapVx snapshot session, linksthe snapshot session to target storage volumes, presents them to the SAPtarget host, and mounts the instance-specific file systems to the operatingsystem.

l A full clone sets the copyEnabled flag to True when you create theSnapVX. If the flag is not set, ESI takes a nocopy SnapVx.

l For Unity, both full clone and snap clone create the Unity Thin Clones forSAN and snapshots for the NAS.

Figure 29 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.

l For VPLEX systems, the storage pool is automatically selected based onaccess rights and the maximum space that is available on the storage pool.

l For SAP instances on XtremIO volumes:

n The Storage System column displays RDM and physical volume names.

n The Storage System tab displays VMWARE_vmdk tokens for virtualenvironments or VMDKs.

8. Click Next.

9. Follow step (5) Consistency in the SAP LaMa online help. Select one of thefollowing options:

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

Note

Type 900 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.

Follow the SAP LaMa Provisioning instructions on the SAP Help Portal.

Copy a systemThe System Copy process creates a copy of an existing SAP system. The SAP systemID (SID) instance host names or IP addresses are renamed, and post copy activitiesare conducted.

Success criteria:SAP LaMa System Copy runs without errors and the copied system runs on the targetsystem.

Note

SAP LaMa System Clone and System Copy processes are identical from an ESIperspective, because the cloning process is the same for both at the storage level.The difference is that for System Copy, after the new storage devices are created andmasked to the target system, the file systems are renamed with the target SAP SID. Inthe System Clone process, the SID remains the same.

Procedure

1. Select Provisioning > System and AS.

2. Under System Landscape, select the system on which to perform the SystemCopy operation.


Copy a system 61

https://help.sap.com/viewer/e7dead4286c545808b3bd24feee7448c/3.0.9.0/en-US/bf87fac514b549c190ff319863157f90.html?q=provisioning%20systems

3. Click Copy System.

4. Follow the screen instructions to complete the System Copy workflow.

a. For 1 Basic, type the new system ID, select the pool for the target system inSAP LaMa, and type the master password.

b. For 2 Hosts, select Use existing host and type the target hostname.

For 3 Host Names, the virtual host names and virtual IP addresses are listedfor each application instance as defined on the central DNS server.

c. To validate the entries, click Check Step, as shown in the following figure.

d. For 4 Instance Number, type the selected target instance numbers for theCentral instance and Central services.

e. For 5 Storage:

l Under Storage Volumes, select Copy Target Selection > Copy targetselection to all volumes of storage manager.

l Do one of the following:

n Select Full Copy to create storage-based full clones.

n Clear the checkbox to create space-saving snapshots.

Note

You cannot mix full copy and snap volumes.

l Under Mount Data, select the logical volumes to view the target MountPoint.

For 7 Users, SAP LaMa verifies whether the required target system users existand are configured on the Central User Manager system or on the target host.If users do not exist and if SAP LaMa is configured to use SAP SWPM for theUser Management instead of a Central User Management system (like LDAP),SAP LaMa calls SAP SWPM to create the users and groups on the targetsystem.

For 8 Rename, SAP LaMa tests the preconfigured SAP SWPM access locationthat will be used for the SAP SID system rename, ensures that the sourcedatabase schema is correct, and displays the source and target SIDs that will beused.

For 9 Isolation, the cloned system is fenced off from the system landscape untilit has been renamed.

5. Configure any hosts or ports that must be excluded from the fencing. LeavePort 443 open to enable SE to communicate with the physical HBA on the ESXiserver.

6. (Optional) For 10 ABAP PCA, select a variant to use.

This step is required only if the customer wants to call ABAP post-copyautomation during the copy process. The customer's SAP administrator mustprovide the SAP PCA task list and task list variants to be used on each client.



7. For 11 Summary, review the summary of selections. Select Save Template andExecute or Start System Copy.

Saving opens a dialog box to name the System Copy template and add apassword so you can run it again.

8. Select Monitoring > Activities to track the progress of the System Copy.

The System Copy activity is finished successfully when the Status showsCompleted and the Progress bar shows 100%.

9. Select Operations > Systems to verify that the copied system is available andrunning.

Create a snapshot clone on a remote arrayCreate a clone of an SAP system from a local VMAX All Flash or PowerMax storagearray to a remote VMAX All Flash or PowerMax storage array. On the remote storagearray, ESI creates TimeFinder SnapVX snapshot sessions of the replicated volumes,links these snapshot sessions to local volumes in the remote array, and then presentsthe remote array volumes to the target SAP system hosts.

Before you begin

l SAP instance-specific file systems on SAN-FC storage devices to be cloned mustbe SRDF-paired before starting this workflow.

l All storage devices of the same SAP instance or system must be in the samestorage group.

l All SAP instance-specific file systems that are based on SAN-FC storage devicesusing SRDF must be in "Ready" status to make use of the remote clone feature.

Procedure




Note

If you want to use the SAP Online Cloning option, ensure that you select asource system that contains the mount configuration for database online redologs.

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 the Storage step, ensure that the Full Copy check boxes for all storagevolumes are cleared and not selected.

7. Select a storage system and its storage pool.

Ensure that the target selected storage system is different than the sourcesystem. Otherwise, the snapshot is taken on the local storage system where thesource system is located.


Create a snapshot clone on a remote array 63

Figure 30 Selecting a snapshot on a remote array

Viewing a SnapVX snapshot sessionUse Unisphere for PowerMax to view a SnapVX snapshot session that is linked to anSRDF/S R2 volume on the remote storage system.

Procedure

1. Log in to Unisphere for PowerMax and select the local storage system.

2. On the remote storage system, select the SAP system storage group and selectData Protection > Storage Groups and select the SnapVX.

3. On the right side of the screen, click Number of Snapshots.

4. From the list of attached remote snapshots, select a snapshot and click SourceVolumes.

5. Select a volume and click linked volumes to view details of the remote linkedvolumes.

Create a clone from a snapshotYou can create a snapshot from a snapshot on Unity and XtremIO storage systems.On VMAX All Flash and PowerMax systems, you can create a TimeFinder SnapVXsnapshot at a certain point in time and use it as the source for a linked clone storagedevice.

Procedure




4. Follow the first three System Cloning steps: (1) Basic; (2) Hosts; and (3) HostNames.

5. Click Next when you are finished.

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

7. Click Clone from System Snapshot and select the last snapshot that wascreated, as shown in the following figure.



Figure 31 Selecting a snapshot

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

9. From the Storage Pool field, select a storage pool from the list, and then clickGo.

10. Click Next.

11. Follow step (5) Consistency. Select one of the following options:

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

Note

Also type 900 in the Timeout [seconds] field to avoid timeout issues.

l Offline to create an offline clone.

12. Click Next.

13. Follow System Cloning steps (6) Isolation and (7) Summary.

14. Click Start System Clone.

Running System DestroyUse System Destroy to remove systems that are no longer required, delete theirassociated storage volumes, and remove the system configuration within SAP LaMa.

Before you begin

Ensure that the system is cloned, copied, or refreshed by SAP LaMa, and the systemstatus is Stopped and Unprepared.

The success criteria is as follows:

l The System Destroy operation runs without errors.

l All storage volumes are deleted.

l The system configuration is removed.

l ESI storage groups and masking views for cloned storage volumes are deleted.

Procedure

1. From the SAP LaMa GUI, select Configuration > Systems > EC2 > Systemdatabase System ID > Edit.

2. Select 3 Mount points.


Running System Destroy 65

3. Under Export Path, identify the physical device IDs to destroy.

4. Use Unisphere to identify and confirm the volumes to destroy.

5. Select Advanced Operations.

6. Select the system to destroy and run the Mass Stop and Unprepare operationon all instances.

7. Select Provisioning > Systems and AS Provisioning, select the system thatyou want to destroy, and click Destroy System.

8. Follow the instructions on the screen to complete the System Destroyworkflow.

l For 1 Delete Storage Volumes, the storage volumes are selected by defaultfor deletion.

l For 2 Delete Host Names, virtual host names with virtual IP addresses areselected for deletion.

l For 3 Summary, review the selections and click Start System Destroy.

9. Select Monitoring > Activities to track the progress of the System Destroyoperation.

10. Use Unisphere to verify at the storage level that the volumes have beendeleted.

Destroy 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 previously createdstorage volumes are deleted. If the target SAP systems were created during theprovisioning process, the operation also removes them from SAP LaMaInfrastructure > Configuration > Hosts.

Note

This process can only be executed if the SAP LaMa system Clone, Copy, or Refreshoperation executed the prepare steps and storage volumes were presented to thespecified SAP hosts.

Procedure


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

3. Click Destroy System > Destroy Partially Provisioned System.

4. Select all volumes to delete, and then click Next until finished, as shown in thefollowing figure.



Figure 32 Destroying a partially provisioned system


Destroy partially provisioned systems 67

CHAPTER 7

Reference Documentation


l Dell EMC documents..........................................................................................70l Dell EMC links.................................................................................................... 70l VMware documents........................................................................................... 70l SAP documents..................................................................................................70

Reference Documentation 69

Dell EMC documentsFor more information, see the following Dell EMC documents which are available onDell EMC Community Network (ECN) and on Dell EMC Online Support.

l Enterprise Storage Integrator for SAP Landscape Management: Administrator Guideon the ESI for SAP product support site.

l Enterprise Storage Integrator for SAP Landscape Management: User Guide on the ESIfor SAP product support site.

l VPLEX: Leveraging Array Based and Native Copy Technologies

l Using VMware vSphere with EMC VPLEX Best Practices Planning

l Dell EMC ESI Support matrix

Dell EMC linksThe following links provide more information.

l Enterprise Storage Integrator for SAP Landscape Management product support

l Solutions Enabler product support

l SAP Info Hub for Ready Solutions

VMware documentsThe following VMware documents provide more information.

l Oracle Databases on VMware Best Practices Guide

l SAP Solutions on VMware Best Practices Guide

l Virtualizing Business-critical Applications with Confidence Technical Papers

l VMware vSphere vMotion - Architecture, Performance and Best Practices inVMware vSphere 5

l VMware vSphere 6.0 Documentation Center

l VMware vSphere Documentation

SAP documentsFor more information, see the following SAP documents, available at SAP SupportPortal.

l SAP Landscape Management product page

l SAP Landscape Management FAQ

l SAP Support Notes:

n SAP Note 1380654 - SAP support in public cloud environments

n SAP Note 2350235 - SAP Landscape Management 3.0 - Enterprise edition

n SAP Note 1709155 - System Provisioning with SAP Landscape VirtualizationManagement






https://www.emc.com/collateral/white-papers/h12642-wp-emc-vplex-leveraging-native-and-array-based-copy-technologies.pdf

https://www.emc.com/collateral/hardware/white-papers/h7118-using-vmware-virtualization-platforms-vplex.pdf

https://elabnavigator.emc.com/vault/pdf/EMC_ESI_ESSM.pdf


https://support.emc.com/products/2071


https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/solutions/vmware-oracle-databases-on-vmware-best-practices-guide.pdf

https://www.vmware.com/files/pdf/solutions/sap/sap-solutions-on-vmware-best-practices-guide.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vsp4-virtualize-biz-critical-apps-white-paper.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-vsphere51-vmotion-performance-white-paper.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-vsphere51-vmotion-performance-white-paper.pdf

https://pubs.vmware.com/vsphere-6-0/index.jsp?topic=%2Fcom.vmware.vddk.pg.doc%2FvddkDataStruct.5.5.html

https://docs.vmware.com/en/VMware-vSphere/index.html

https://www.sap.com/products/landscape-management.html

https://blogs.sap.com/2016/10/21/sap-landscape-management-faq-lvmlama/





n SAP Note 1492000 - General Support Statement for Virtual Environments

n SAP Note 2363128 - SAP Host Agent operation fail

n SAP Note 0611361 - Hostnames of SAP servers

n SAP Note 0962955 - Use of virtual TCP/IP host names

n SAP Note 0171356 - SAP software on Linux: Essential information

n SAP Note 1972803 - SAP on AIX: Recommendations

n SAP Note 1680045 - Release Note for Software Provisioning Manager 1.0

n SAP Note 1031096 - Installing Package SAPHOSTAGENT

n SAP Note 1759181 - Installation of SAPACEXT.SAR

n SAP Note 2050537 - Support for SAP HANA in SAP Landscape Management

n SAP Note 1732161 - SAP Systems on Windows Server 2012 (R2)

n SAP Note 2384179 - SAP Systems on Windows Server 2016

n SAP Note 1564275 - Install SAP Systems Using Virtual Host Names onWindows


SAP documents 71















dell emc enterprise storage integrator for sap landscape … · 2020-06-10 · dell emc enterprise...

Documents