Enterprise Storage Integrator for SAP Landscape Management Administrator … · 2019-11-10 · deployed inside the SAP NetWeaver Java Stack where the SAP LaMa add-on is already installed

Enterprise Storage Integrator for SAPLandscape ManagementVersion 5.0

Administrator Guide300-014-915

REV 09

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

Published November 2017

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

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

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

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

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

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

Published in the USA.

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

2 Enterprise Storage Integrator for SAP Landscape Management 5.0 Administrator Guide

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

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

Prerequisites 13System prerequisites...................................................................................14VPLEX configuration prerequisites..............................................................15

Installing and Deploying the EHAC Server 19Using the Linux-based EHAC appliance...................................................... 20

Deploying the Linux-based EHAC appliance...................................20Logging in and verifying the EHAC appliance deployment............. 22

Installing the Windows-based EHAC server ............................................... 22Installing the Java Development Kit (JDK).....................................23Installing the Java Cryptography Extension................................... 23Installing the Apache database...................................................... 23Installing and configuring WildFly as a Windows service................ 23

Configuring the EHAC Server 27Configuring EHAC...................................................................................... 28

Enabling the EHAC Console to discover and configure storage..... 28Configuring the database and updating the WildFly configurationfiles................................................................................................28

Configuring the EHAC web service to run in HTTPS mode.........................29Configuring residue cleanup....................................................................... 30Configuring manually installed SMI-S Provider............................................31Starting the EHAC server............................................................................31

Logging in to EHAC 33Logging in to EHAC for the first time......................................................... 34Logging in to EHAC with administrative credentials................................... 34

Configuring Storage and Virtual Systems in EHAC 37Configuring file/NAS storage..................................................................... 38

Preface

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

Chapter 6

CONTENTS

Enterprise Storage Integrator for SAP Landscape Management 5.0 Administrator Guide 3

Adding file/NAS storage systems.................................................. 38Updating file storage systems........................................................38Removing file storage systems...................................................... 39

Configuring block/SAN storage..................................................................39Adding WBEM servers...................................................................39Updating or removing WBEM servers............................................40Adding WBEM-managed block storage systems............................40Enabling advanced configuration for VMAX and VMAX3 arrays..... 41Viewing WBEM-managed block storage systems pools..................41Viewing WBEM-managed block storage systems volumes.............42Adding an XtremIO array............................................................... 42Adding VPLEX storage details....................................................... 42

Changing the global access level................................................................ 44Adding VMware vCenter virtual systems and ESXi hosts............................44

Managing User Accounts 47Adding and removing users.........................................................................48

Adding a user.................................................................................48Updating a user password..............................................................48Updating an administrator password..............................................48Removing a user............................................................................ 49

Configuring access control......................................................................... 49Granting access to file storage systems and pools.........................49Revoking access to file storage systems and pools........................50Granting access to block storage systems and pools.....................50Granting access to XtremIO storage systems................................ 51Revoking access to XtremIO storage systems...............................52

Securing user data......................................................................................52

Utilities 53Starting and stopping the EHAC service.................................................... 54Changing EHAC Deployment Console settings........................................... 54Using EHAC appliance aliases ....................................................................54Configuring WildFly by restoring the database from a backup....................55Backing up and restoring an Apache Derby database..................................57Using logs to monitor EHAC server activities............................................. 58Configuring ESI logs................................................................................... 58Collecting SRM, ViClient, and SAPACOSPREP logs...................................59Upgrading the ESI web service and applying hotfixes.................................60

Troubleshooting and Cleaning up Storage 61Troubleshooting......................................................................................... 62Cleaning up VMAX storage manually after a failed operation......................65Automatically cleaning up storage after a clone fails.................................. 70

Chapter 7

Chapter 8

Chapter 9

CONTENTS


Preface

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

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

Note

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

PurposeThis document describes how storage administrators can manage user accounts,assign storage systems to users, and manage storage assigned to users by using read/write access for storage system pools.

AudienceThis document is for internal Dell EMC personnel, partners, and customers. Theintended audience is SAP Landscape Management (SAP LaMa) administrators andstorage administrators who want to manage user accounts, assign storage space tousers, and manage storage space access for individual users.

ScopeThis storage administrator guide is intended to provide an overview of Dell EMC™

Enterprise Storage Integrator (ESI) for SAP Landscape Management and includes thefollowing information:

l Product overview

l Prerequisites

l Installation and deployment

l ESI database configuration

l User account management

l Troubleshooting

Related documentationThe following documents, located on Dell EMC Online Support and on Dell EMC.com,provide additional relevant information. Access to these documents is based on your


http://support.emc.com

login credentials. If you do not have access to the following documents, contact yourrepresentative:

l Enterprise Storage Integrator for SAP Landscape Management Storage Adapter UserGuide

l Enterprise Storage Integrator for SAP Landscape Management Release Notes

l Enterprise Storage Integration with SAP Landscape Management SoftwareImplementation Guide

l Enterprise Storage Integration with SAP Landscape Management Software DesignGuide

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

NOTICE

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

Note

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

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

Table 1 Typographical conventions

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

Italic Used for full titles of publications referencedin text.

MonospaceUsed for:

l System output, such as an error messageor script

l System code

l Path names, filenames, prompts, andsyntax

l Commands and options

Monospace italicUsed for variables.

[ ] Square brackets enclose optional values.

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

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

Preface


Table 1 Typographical conventions (continued)

... Ellipses indicate nonessential informationomitted from the example.

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

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

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

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

Send your comments about this document to Feedback.

Preface




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

Preface


CHAPTER 1

Enterprise Storage Integrator for SAPLandscape Management Overview

This chapter presents the following topics:

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

Enterprise Storage Integrator for SAP Landscape Management Overview 9

Executive summaryESI for SAP LaMa is an adapter for SAP LaMa. ESI for SAP LaMa has the followingmain components:

l ESI for SAP LaMa storage adapter (or ESI for SAP LaMa plug-in).

l Enterprise High-Level Storage (HLS) Administration Console (EHAC) server,which is the single point of management for storage administrators. The EHACserver contains the ESI deployment utility, the ESI web service, and the EHACconfiguration console.

l Enterprise Storage Library for SAP Adapter (ELSA), which is distributed in the DellEMC Solutions Enabler product.

You can use the EHAC configuration console to:

l Add VMware vCenter servers to and remove from the EHAC database

l Configure storage area network (SAN) storage, such as Dell EMC VNX™, Dell EMCVMAX™, and Dell EMC VMAX3™ arrays, and Dell EMC XtremIO™ all-flash arrays, inthe EHAC database

l Discover and configure network-attached-storage (NAS), such as VMAX3 eNASand VNX file storage in the EHAC database

l Discover and add Dell EMC VPLEX™ systems to the EHAC database

l Discover storage systems and their pools

l Provide a gateway for the ESI adapter to access configuredDell EMC systems

l Create users and grant them access to Dell EMC storage systems and storagepools to be used later by SAP LaMa

Using EHAC, administrators can grant or revoke storage systems assigned toindividual users by controlling read/write access to the storage pools for each storagesystem.

The ESI for SAP LaMa adapter provides storage management capabilities for SAPLaMa and enables SAP administrators to manage clones and snapshots of multipleSAP systems that are managed by SAP LaMa stored on Dell EMC storage systems.

The ESI for SAP LaMa storage adapter/plug-in supports the following:

l SAP systems in both physical and virtual environments based on XtremIO 4.0,VMAX3, VMAX, and VNX storage arrays, and VPLEX 5.5 storage systems, usingVirtual Machine Disks (VMDKs) or physical raw device mapping (pRDMs)

l Dell EMC Vblock System and Dell EMC VxBlock System converged systems usingXtremIO, VNX, VMAX, and VMAX3 storage arrays

l IBM PowerVM server virtualization with AIX operating systems

Note

SAP instance-specific file systems must be stored in LUNs/datastores that are eitherfully on VPLEX virtual devices (distributed or not) or on direct storage.Heterogeneous storage configurations, that is using both VPLEX virtual devices anddirect storage, are not supported.

Enterprise Storage Integrator for SAP Landscape Management Overview


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

The adapter, which is shown in the following figure, runs as an application that isdeployed inside the SAP NetWeaver Java Stack where the SAP LaMa add-on isalready installed.

The ESI for SAP LaMa storage adapter communicates frequently with the EHACserver to manage one or more Dell EMC file or block storage systems and providesusers with access controls to use these storage systems from the SAP LaMainterface. This enables SAP LaMa to perform storage provisioning also as part of theSystem Provisioning processes: System Clone, System Copy, System Refresh, andSystem Destroy.

Figure 1 ESI for SAP LaMa adapter

Note

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


Product overview 11



CHAPTER 2

Prerequisites

This chapter presents the following topic:

l System prerequisites.......................................................................................... 14l VPLEX configuration prerequisites..................................................................... 15

Prerequisites 13

System prerequisitesBefore you deploy the EHAC appliance, verify that the Dell EMC storage arrays thatyou plan to use are zoned and masked correctly to the SAP systems to be part of theSAP LaMa system provisioning processes.

Note

The Enterprise Storage Integrator for SAP Landscape Management Release Notesprovides detailed environment and system requirements for different types of storage.

The following table lists the software prerequisites for the EHAC server on a Linuxsystem.

Table 2 EHAC server prerequisites on a Linux system

Software Minimum software version

EHAC appliance 5.0 (contains SLES 12 SP2 and SMI-S 8.4)

SMI-S Provider 4.6.2.x (for a VNX SAN)

VMware vCenter Server 6.5, 6.0, or 5.5

The following table lists the software prerequisites for the EHAC server on a Windowssystem with physical or virtual machines.

Table 3 EHAC server prerequisites on a Windows system

Software Minimum software version

Microsoft Windows Server 2012 R2 x64 SP1

SMI-S Provider 4.6.2.x (for a VNX SAN);

8.4.x (for a VMAX or VMAX3 SAN)

Java Development Kit (JDK) 1.8

Java Cryptography Extension (JCE) JCE-8 for Java 1.8 with Unlimited StrengthJurisdiction Policy Files 8

WildFly Application Server 10.1.0

Apache Derby database 10.12

If you use block storage, the following table lists the software that you must install andset up.

Table 4 Prerequisite software for block storage

Software Minimum softwareversion

Delivery Method

Solutions Enabler 8.4.x Install on all SAP hosts.

Prerequisites


Table 4 Prerequisite software for block storage (continued)

Software Minimum softwareversion

Delivery Method

Note

For information about how to installSolutions Enabler, see to the SolutionsEnabler documentation page on DellEMC Online Support.

SMI-S Provider for VNXBlock

4.6.2.31 Deploy the virtual appliance.

Note

SMI-S Provider 4.6.2.31 is the latestsupported version for VNX blockstorage. To download the SMI-S virtualappliance, click this link.

SMI-S Provider forVMAX3 Block

8.4.0.18 Deploy Linux-based EHAC appliance.

Note

Dell EMC SMI-S Array Provider 8.4uses an ECOM account. This SMI-Sversion can be used to manage VMAXand VMAX3 storage systems. Forinformation about how to install SMI-SProvider, refer to the SMI-S Providerpage on Dell EMC Online Support

Dell EMC Enginuity™ forVMAX systems

5876 Install or upgrade customer VMAXsystem.

Dell EMC OE for VNXsystems

32 Install or upgrade customer VNXsystem.

If you use VMDK disks or RDM disks, install and set up VMware vCenter Server(virtual environments) version 6.5, 6.0 U3, or 5.5 U3. Install the following snapshotand clone licenses on the corresponding storage arrays:

l Dell EMC VNX Snapshot Enabler and a SAN Copy license for VNX arrays

l Dell EMC TimeFinder™/Snap and TimeFinder/Clone license for VMAX arrays

VPLEX configuration prerequisitesThe following prerequisites apply to VPLEX storage systems:

l Add and use a unique initiator port in each storage view. Do not add and reuse itfor other views.

l Do not manually change the name of the cloned virtual volume.

l Do not manually add the cloned virtual volume to other views separate from thetarget host views.

l Do not populate the host VMDK mount point in SAP LaMa that is on the hostinternal storage. Populate only the SAP instance-specific mount points that are

Prerequisites

VPLEX configuration prerequisites 15

https://support.emc.com/products/2071_Solutions-Enabler/Documentation/

https://support.emc.com/products/2071_Solutions-Enabler/Documentation/

https://download.emc.com/downloads/DL66632_SMI-S_Provider_4.6.2.29_for_SMI-S_1.5_for_Virtual_Appliance.ova?source=OLS

https://support.emc.com/products/5587_SMI-S-Provider

based on Dell EMC storage systems. If a VPLEX system is in use, the mount pointsare based on virtual volumes (distributed or not).

Note

SAP mount points are recognized by ESI for SAP LaMa only when they are carvedfrom Dell EMC storage arrays. Mount points carved from the virtual machine'sinternal storage are not handled by ESI for SAP LaMa.

When using VPLEX virtual systems:

l Ensure that virtual volumes have one-to-one VPLEX element constraints and thatall volumes come from a single VPLEX system. Do not combine volumes from twoseparate VPLEX clusters. A single SAP instance cannot span multiple VPLEXsystems; all volumes must come from a single VPLEX Local or VPLEX Metrosystem.

Create each VPLEX Metro distributed virtual volume or local volume using a singledevice that completely uses the claimed storage volume. Distributed virtualvolumes must be of equal size. The mirror of each virtual volume (local ordistributed) must lie entirely on one back-end array volume. The back-end arrayvolumes corresponding to each mirror must be the exact size of the virtual volume.

l When you add a new initiator to the VPLEX environment, you must first registerthe initiator in VPLEX and add it to a VPLEX storage view before it can be used.

l Register at least one initiator on each cluster.

For VPLEX systems, you can register initiators either through a command-lineinterface or through Dell EMC Unisphere™ for VPLEX.

l If you have a VPLEX cross-connected host bus adapter (HBA) to remove,unregister the initiators on the cluster that uses the HBA.

l Create storage views on the cluster where target hosts reside.

An administrator must manually create storage views for the target hosts that areused in cloning before a clone is attempted. When a clone of a virtual volume iscreated by ESI, it is visible on the target host only after it is automatically added toa view containing the target host’s initiators.

l Ensure that the target hosts for the clone reside on the same cluster as the localvirtual volume.

If the local volume has two mirrors, then the cloned local volume will have only onemirror.

l If the VPLEX virtual volume is distributed, then the cloned VPLEX virtual volume isa distributed virtual volume. The target host can reside anywhere on cluster1 or oncluster2.

If the distributed volume has three mirrors, then the cloned distributed volumeswill have only two mirrors with one on each cluster. The cloned virtual volume willalso have two mirrors—one mirror on an array attached to cluster1 and the othermirror on an array attached to cluster2.

l Clone only if the virtual volume is in an OK state and if the source virtual volumehas a valid mirror residing on the same side as the target host.

The mirror that resides on the cluster for which the target host has visibility playsa critical role in the cloning. Before cloning can proceed, this mirror must be in anOK state.

Prerequisites


l The snap clone and manage snapshot operations are not supported for VPLEX.System Clone and System Copy, using the Provision New Host option, are notsupported in SAP systems that use VPLEX storage.

Prerequisites

VPLEX configuration prerequisites 17

Prerequisites


CHAPTER 3

Installing and Deploying the EHAC Server


l Using the Linux-based EHAC appliance..............................................................20l Installing the Windows-based EHAC server .......................................................22

Installing and Deploying the EHAC Server 19

Using the Linux-based EHAC applianceESI for SAP LaMa provides an easy EHAC deployment option that uses the EHACappliance. Storage administrators can use the appliance to set up the EHAC serviceand the SMI-S 8.4 provider.

Install the EHAC appliance to avoid the cost of providing a dedicated physical serveror the overhead of setting up and maintaining a virtual machine for EHAC. If you installthe appliance, you do not need to install an operating system or required softwaresuch as Application Server and SMI-S Provider, and you do not need to deploy EHACbinaries. You must subscribe to an online SLES maintenance service to keep the SLESOS updated and secured, as you do for your own servers that run SLES OS.

The EHAC appliance includes the following software:

l SLES 12 SP2 with the latest security updates

l Java 1.8 SDK

l WildFly Application Server 10.1.0

l SMI-S Array Provider 8.4.x

l ESI web service v5.0

l ESI Deployment Console v5.0

l Apache Derby database v10.12

Deploying the Linux-based EHAC applianceUse this procedure to deploy the Linux-based EHAC appliance if you are a new ESI forSAP LaMa customer.

Before you begin

Ensure that the environment includes the following prerequisites before using theEHAC appliance:

l vCenter 6.5, 6.0.x or 5.5 U3

l At least 50 GB of available ESXi storage

Procedure

1. Open the Storage Integrator for SAP Landscape Management page on DellEMC Online Support and download the EHAC template.

2. Log in to vCenter where the EHAC Open Virtual Appliance (OVA) must bedeployed, using the vSphere Client.

3. Perform either of these steps:

l From the vSphere Desktop client, select File > Deploy OVF Template.

l From the vSphere Web client, select Actions > Deploy OVF Template.

4. On the Select template screen, specify the location where the OpenVirtualization Format (OVF) file is saved, and then click Next.

Note

You can type the location or browse to find it, either on the Internet or on yourcomputer, network, or CD/DVD.



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

5. On the Select name and location screen, perform the following steps:

a. In the Name field, type a name for the virtual machine appliance.

b. Select a datacenter or folder from the list.

c. Click Next.

6. On the Select a resource screen, select the host or cluster location on which todeploy the template, and then click Next.

7. On the Specify a Specific Host screen, select the ESXi host on which thevirtual machine will be created, and then click Next.

8. Review the details and click Next.

9. On the Select storage screen, select the provisioning type, select thedatastore on which to store virtual machine files, and then click Next.

Ensure that there is enough disk space to deploy the virtual machine.

Note

We recommend that you deploy EHAC in a storage system and not in a localdatastore.

10. On the Select networks screen, select a destination network.

11. On the Customize template screen, type IP addresses for the Domain NameSystem (DNS), Gateway, IP address, and NetMask properties of the virtualmachine that you are creating, and then click Next.

Note

Values are required for all of the properties. Check them carefully to ensure thatthe deployment is successful.

12. On the Ready to Complete screen, review your selections, and click Finish.

Note

Wait until the virtual machine deployment is completed and the IP addressassigned to the virtual machine is running, as shown in the next two figures.

Figure 2 Starting the deployment


Deploying the Linux-based EHAC appliance 21

Figure 3 Finishing the deployment

Logging in and verifying the EHAC appliance deploymentLog in to the operating system and then verify the EHAC appliance is deployed.

NOTICE

Do not change the host name of the EHAC appliance server after you deploy theappliance. Otherwise, after a restart, the ECOM server will not start and the EHACconsole used for configuration will not be available.

Procedure

1. Open the EHAC appliance virtual machine console on vCenter.

2. Log in to the guest operating system using the following username andpassword:

root/Password!

3. Type the following command to verify that the EHAC appliance deployment logserrors:

more /opt/emc/ehac/logs/ehac_init_logs/init.log

4. Search for Deployed in the WildFly server log by typing the followingcommand:

more /usr/local/wildfly-10.1.0.Final/server.log

Installing the Windows-based EHAC serverUse the following procedures only if you are an existing ESI for SAP LaMa customer orprefer to use a Windows-based EHAC server.

Otherwise, follow the steps in Deploying the Linux-based EHAC appliance on page 20



Installing the Java Development Kit (JDK)Install the JDK.

Procedure

1. Download and install JDK version 1.8 from the Java SE Downloads page on theOracle website.

2. Set the JAVA_HOME directory to the JDK1.8 installation directory. Forexample:

C:\Program Files\Java\jdk1.8.0_131\

Installing the Java Cryptography ExtensionInstall the Java Cryptography Extension.

Procedure

1. Download the software and follow the installation instructions from the JavaCryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8Download page.

2. Unzip the UnlimitedJCEPolicyJDK8.zip file to the applicable temporary folderor directory.

3. Copy the local_policy.jar and the US_export_policy.jar files to the%JAVA_HOME%\jre\lib\security folder

Installing the Apache databaseInstall the Apache database.

Procedure

1. Navigate to the Apache Derby Downloads page.

2. Go to the latest 10.12.* version link and download the db-derby-10.12*-lib.zip file.

3. Extract the derby.jar file and copy it to a location on the EHAC server.

Installing and configuring WildFly as a Windows serviceInstall WildFly Application Server version 10.1.0, or later, and configure as a Windowsservice.

Procedure

1. Download the wildfly-10.1.0.Final.zip file from the WildFly Downloadspage.

2. Create the c:\wildfly directory. Extract the contents of thewildfly-10.1.0.Final.zip file into the directory.

3. Put the service folder, which is in the docs\contrib\ directory, into thebin\ directory in the WildFly Installation folder.

4. Under the bin\services directory, open the service.bat file and confirmthat the following modifications have been made and saved:


Installing the Java Development Kit (JDK) 23

http://www.oracle.com/technetwork/java/javase/downloads/index.html

http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html



https://db.apache.org/derby/derby_downloads.html

http://wildfly.org/downloads/

a. Replace set JAVA_OPTS=-Xrs with REM set JAVA_OPTS=-Xrs.

b. Replace all occurrences of standalone.bat with standalone.bat -b="<IP-Address of Server>."

5. Open a command line window as administrator.

a. Select Run, type cmd, and press Enter.

b. Change the location to the WildFly service directory at<wildfly_home_directory>.For example: C:\Eclipse\wildfly-10.1.0.Final\wildfly-10.1.0.Final\bin\service

6. Run the service.bat install command in the command prompt.

The following figure shows the expected results.

Figure 4 Result of service.bat install command

7. After the WildFly service is installed, select Services and Application >Computer Management > WildFly.

8. Right-click WildFly, and then select Properties.

9. Select a Startup Type of Automatic.

10. Click Start, and then click OK, as shown in the following figure.



Figure 5 Starting the WildFly service

WildFly troubleshooting tipsThe following information describes how to address WildFly errors.

l If you see a Failed installing WildFly, Access is denied error, openthe command line prompt as an administrator:

1. Select Run to open the command line prompt as an administrator.

2. Type cmd, and then press Ctrl+Shift+Enter.

l If an Out of Memory error occurs, increase the memory allocated by editing the-Xms and -Xmx values in JAVA_OPTS in thestandalone.conf file in the bindirectory in WildFly.For example, at C:\Program Files\wildfly-10.1.0.Final\bin:

if [ "x$JAVA_OPTS" = "x" ]; then JAVA_OPTS="-Xms128m -Xmx512m -XX:MaxPermSize=512m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000" JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true" JAVA_OPTS="$JAVA_OPTS -Djboss.server.default.config=standalone.xml"


Installing and configuring WildFly as a Windows service 25



CHAPTER 4

Configuring the EHAC Server


l Configuring EHAC..............................................................................................28l Configuring the EHAC web service to run in HTTPS mode................................ 29l Configuring residue cleanup...............................................................................30l Configuring manually installed SMI-S Provider................................................... 31l Starting the EHAC server................................................................................... 31

Configuring the EHAC Server 27

Configuring EHACUse the following procedures to enable the EHAC Console to find the storage to beconfigured and to configure the database and update the WildFly configuration files.

Enabling the EHAC Console to discover and configure storageAs part of configuring EHAC, you can enable the EHAC Console to find the storage tobe configured.

This procedure is applicable to both a Windows-based or a Linux-based EHAC server.

Note

If using a Windows-based EHAC server, storage administrators must configure a Web-Based Enterprise Management (WBEM) infrastructure, the ECOM account, and setthe administrator role to allow full access. For detailed information about ECOM, seethe ECOM Deployment and Configuration Guide, which is available on Dell EMC OnlineSupport.

Procedure

1. Add six gatekeepers (pRDMs in the vSphere virtual appliance).

2. Run TestSmisProvider, which is available in<ECOM_installation_Directory>/bin, to perform a discovery.

3. Run the TestSmisProvider display version option.

4. If you deployed a Linux-based EHAC virtual appliance, go to Logging in to EHACwith administrative credentials on page 34. Otherwise continue to the nextsection.

Configuring the database and updating the WildFly configuration filesAs part of configuring EHAC, you can configure the database and update the WildFlyconfiguration files.

Note

The database is already configured in Linux EHAC appliances. The following steps areapplicable for:

l The Linux appliance if you upgrade form a previous release

l All Windows EHAC servers

Procedure

1. Download the EHAC_DeploymentConsole_ESISAPLaMa.jar file from the Storage Integrator for SAP Landscape Management page on Dell EMC OnlineSupport.

2. Double-click EHAC_DeploymentConsole_ESISAPLaMa.jar.

3. In the Configuration Utility, click Configure Server.

4. Click Download to download the JCE files from the Oracle website.

5. In the Downloaded (Unzipped) Location of the JCE files field, click Select toselect the downloaded JCE files in the displayed location.



https://support.emc.com/docu43613_ECOM-Deployment-and-Configuration-Guide.pdf?language=en_US


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

Note

If you are deploying EHAC for the first time, select the downloaded JCE filesand also click Configure JCE Files. This replaces the local_policy.jar andthe US_export_policy.jar files in the %JAVA_HOME%\jre\lib\security folder. You receive a Configured JCE Files Successfullymessage to confirm the JCE configuration.

6. In the WildFly Location field, type the location where WildFly is installed orclick Select and browse to find the location.

Note

You can click Check Whether Configured to confirm whether WildFly isalready configured. You will receive a WildFly is already configuredmessage if WildFly is configured.

7. Select Configure using Remote Database Backup if the WildFly Server needsto be configured using a remote database backup.

Note

For detailed instructions, refer to Configuring WildFly by restoring the databasefrom a backup on page 55.

8. Type the applicable database name.

9. If you selected Configure using Remote Database Backup, then type theabsolute path of the Remote Database backup directory.

10. In the Path Where Database needs to be created field, type the applicablepath or click Select to choose a path.

11. Copy the Java EAR file named esi_sap_lvm_saconfig.5.0.x.x.ear intothe WildFly Installation path/standalone/deployments folder.

12. Click Configure.

After the configuration is complete, esi_sap_lvm_saconfig.5.0.x.x.earis ready to be deployed.

Configuring the EHAC web service to run in HTTPS modeConfiguring the EHAC web service to communicate through HTTPS is optional but ishighly recommended.

Note

This procedure is only applicable to a Windows-based EHAC appliance. A Linux-basedEHAC virtual appliance is already configured with these settings.

Procedure

1. Click EHAC_DeploymentConsole_ESISAPLaMa.jar to start the EHACConfiguration Utility.

2. In the Configuration Utility field, click the Configure Https tab.


Configuring the EHAC web service to run in HTTPS mode 29

3. In the Configured Database on WildFly Server Path field, type the path to theWildFly installation folder.

4. Click Check Whether Configured.

If EHAC is not configured, configure it before going to the next step. Configuring WildFly by restoring the database from a backup on page 55provides details.

5. For Generate a Self Signed Certificate, do the following:

a. In the Path Where Self Signed Certificate Needs to be Stored field, clickSelect and then browse to find the path in which a certificate can begenerated.

b. Type the Name of the Keystore and the Keystore alias.

c. Click Generate.

6. For Configure Server to Use Self Signed Certificate, do the following:

a. In the Keystore alias field, click Select and then browse to find the path tothe certificate that should be used.

b. Type the applicable password and alias in the Keystore Password and theKeystore alias fields.

c. Click Configure.

Configuring residue cleanupConfigure residue cleanup.

Note

This procedure is only applicable for a Windows-based EHAC appliance. A Linux-basedappliance is already configured.

Procedure

1. In Configure Properties, select Configure Residue Clean Up.

2. In the Retry Count field, type the number of times to run the cleanup.

Note

Type a number larger than 1 to repeat the cleanup in case of failure.

3. In the Enable Residue Clean Up field, select True.

4. In the Residue Object Expiry field, type the number of hours to run thecleanup.

5. In the Residue Object Thread Sleep Time field, type the amount of time inseconds for the residue cleanup thread to sleep.

6. Click Select and browse to select the Residue Objects Directory.

7. Click Configure.



Configuring manually installed SMI-S ProviderAfter you manually install Windows SMI-S Provider, implement the configurationsettings.

Note

This procedure is only applicable to a Windows-based EHAC appliance. A Linux-basedEHAC virtual appliance is already configured with these settings.

Procedure

1. Stop the ECOM service.

2. Set the SMI-S (ECOM) job.deleteoncompletion property to True.

This setting avoids having leftover jobs in the SMI-S Provider queue.

3. Increase the job.deletion.oncompletion.timeout value to keep the jobcompleted for a long time.

4. Verify the following settings in the OSLSProvider.conf file in<ECOM_Installation_Directory>/ Providers.

l Deletion of the jobs after their successful completion: OSLSProvider/com.emc.cmp.osls.se.symm.Session.StorageConfiguration.job.deleteoncompletion = True

l Amount of minutes to wait before job removal: OSLSProvider/com.emc.cmp.osls.se.symm.Session.StorageConfiguration.job.timebeforedeletion = 00000000080000.000000:000

l Amount of time (sec) to wait for the SMI-S triggered replication:OSLSProvider/com.emc.cmp.osls.se.symm.ReplicationService.totalwaittime = 86400000

5. Restart the ECOM service.

Starting the EHAC serverStart the EHAC server.

Note

This procedure is only applicable to a Windows-based EHAC appliance.

Procedure

1. Click the Start Server tab.

2. In the Port on which the server needs to be started field, type 8080, which isthe default server port.

3. Type the IP address of the host on which the WildFly AS is configured.

4. Click Start Server to start the EHAC server.


Configuring manually installed SMI-S Provider 31

Note

After the server is started, a Deployed esi_sap_lvm_saconfig.5.0.*.ear message in the command prompt confirms the deployment.

5. Open the EHAC UI from either one of these locations:

l http://IP Address:port/ehac

l https://IP Address:port/ehac



CHAPTER 5

Logging in to EHAC


l Logging in to EHAC for the first time................................................................. 34l Logging in to EHAC with administrative credentials........................................... 34

Logging in to EHAC 33

Logging in to EHAC for the first timeThe first time that you log in to EHAC, accept the terms of the software licenseagreement and set up administrative credentials.

Procedure

1. Open EHAC in your web browser by using the following URL:

http://IPAddress:8080/ehac2. Read the Dell EMC Software License Agreement, and then click I Accept.

A window that enables you to set up administrative credentials opens.

3. Type a username and user full name.

4. Type a strong Password and type it again to confirm.

For example, use nine or more letters, and use unique combinations ofuppercase and lowercase letters, numbers, and punctuation. Do not use specificwords or phrases.

5. Type an Encryption Key and type it again to confirm.

6. From the Security Question list box, select a question.

Note

Use the security question to retrieve the password if you forget it.

7. Type a Secret Answer and type it again to confirm.

8. Click Create.

Logging in to EHAC with administrative credentialsAfter you set up administrative credentials, log in to EHAC by using the Admin Loginwindow.

Procedure


http://IPAddress:8080/ehac2. Type your username and password.

Note

If you forget your password, click Forgot Password. Retrieve your password byanswering the security question that you set up during your first login. Refer to Logging in to EHAC with administrative credentials on page 34.

3. Click Login.

The home page appears.

Logging in to EHAC


Note

The home page also appears when you click General > Home underAdministrator Menu.

The page includes two panes:

l The left-side pane displays file storage systems and the pools that areassigned to specific users.

l The right-side pane displays file and block storage and the pools that areassigned to specific users.

Logging in to EHAC

Logging in to EHAC with administrative credentials 35

Logging in to EHAC


CHAPTER 6

Configuring Storage and Virtual Systems inEHAC


l Configuring file/NAS storage.............................................................................38l Configuring block/SAN storage......................................................................... 39l Changing the global access level........................................................................44l Adding VMware vCenter virtual systems and ESXi hosts................................... 44

Configuring Storage and Virtual Systems in EHAC 37

Configuring file/NAS storageUse the following procedures to configure file/NAS storage systems.

Adding file/NAS storage systemsAdd file storage systems.

Procedure

1. From the Administrator Menu, click Storage Arrays > NAS > StorageSystems.

2. Under Storage Array Details, click Add Storage Array.

3. In the NAS Storage Array window, type the following information for the newstorage array:

l The Name for the new storage system

l The Control Station IP Address (for example, the IP address for Unispherefor VMAX eNAS)

l The Model number of the array for the storage system (for example,VMAX100K)

l The username and password for the control station

4. Click Retrieve Data Movers and select one or more Data Movers from the rightpane.

5. Click Add Storage System.

A Storage system added successfully message appears when theprocess is complete.

6. Close the New NAS Storage Array window.

The Storage Array Details screen displays the newly added array and DataMovers.

Updating file storage systemsUpdate file storage systems.

Procedure


2. Select a storage system and click Update Storage Array.

3. In the Update the Storage Array window, perform the following steps:

l To update the mover IP address, click Update Mover IP Address and typethe new information.

l To update the username or password, click Update UserName/Passwordand type the new updates.

l To update the model, click Update Model and type the new information.

4. Click Update the Storage System.

Configuring Storage and Virtual Systems in EHAC


Removing file storage systemsIf necessary, remove file storage systems.

Procedure


2. Select the storage system that is to be removed.

3. Click Remove Storage Array to remove the array from EHAC.

Configuring block/SAN storageUse the following procedures to configure block/SAN storage systems.

Adding WBEM serversAdd Web-Based Enterprise Management (WBEM) block servers.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > WBEM ManagedSystem > WBEM Servers > Storage Systems.

2. Under Add WBEM Server, complete the fields:

a. From the Connection Schema list, select either Http or Https, dependingon your security requirements.

Dell EMC recommends that you use Https for security reasons.

b. Type the IP address, server name, and port number.

Note

The IP address is usually the same as the IP address of the EHAC server, ifthe SMI-S array provider is installed in the same server. However, for VNXstorage systems only, SMI-S Provider 4.6 is in a separate Linux-based EHACvirtual appliance. This appliance is different from your Linux-based EHAC 5.0virtual appliance, or physical or virtual Windows-based EHAC server.

c. Type a username and password for the WBEM server.

3. Click Add.

If the server details are correct, an Adding Server Details Successfulmessage appears.

Note

Storage administrators must configure a WBEM infrastructure, ECOM account,with the administrator role to allow full access. For detailed information aboutECOM, see the ECOM Deployment and Configuration Guide, which is available in Dell EMC Online Support.


Removing file storage systems 39


Updating or removing WBEM serversUpdate or remove WBEM servers.

Note

Before you can remove a block server, you must first remove users who have accessto the storage arrays and storage pools.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > Server > WBEMManaged System > WBEM Servers.

2. Select a server from the right pane.

3. Click Remove/Update Server.

The Remove/Update the WBEM Server window appears.

4. Change the username or password:

a. Click Update UserName/Password.

b. Type the new information.

c. Click Update UserName/Password.

5. Update the connection type or protocol:

a. Click Update Connection Schema/Port.

b. From the Connection Schema list box, select either Http or Https.

c. Update information in thePort field.

d. Click Update Connection Schema/Port.

6. Remove a WBEM server:

a. Click Remove the WBEM Server.

b. Click Remove Server.

Adding WBEM-managed block storage systemsAdd WBEM-managed block storage systems.

Note

Before you add block storage ensure that SMI-S Provider with Solutions Enabler isalready installed on the EHAC server.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > WBEM ManagedSystem > Storage Systems.

2. Under WBEM Server, perform the following steps:

a. From the Select Server list box, select the WBEM server on which you wantto add the storage system.

You can view details for the selected server in the other fields.

b. Type the WBEM server username and password.



c. Click Retrieve.

The right pane under List of Storage Systems Managed by the Server liststhe storage systems.

3. For Dell EMC CLARiiON™ CX4 and VNX storage systems, under Add a NewStorage System, perform the following steps.

Note

This step is not required for VMAX storage systems because they arediscovered when you click Retrieve.

a. In the Select Type list box, select the type of storage system (for example,CLARiiON).

b. Type the storage processor addresses in the SP-A IP Address and SP-B IPAddress fields.

c. Type the values in the Array User Name and Array Password fields.

4. Click Add.

A Storage System Added Successful message appears.

Enabling advanced configuration for VMAX and VMAX3 arraysEnable the advanced storage configuration for VMAX and VMAX3 arrays, if advancedstorage configurations such as cascaded initiator groups, parent/child storage groups,or multiple masking views are used during the SAP system setup.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > WBEM ManagedSystem > WBEM Servers > Storage Systems.

2. Under WBEM Server, select the WBEM server that manages the VMAX array.

3. Click Retrieve to retrieve the arrays.

4. Under Select the Storage System, select the VMAX array and clickConfiguration.

5. Under Add Confguration to DB, select Storage Configuration For SpecificHost: and click Apply.

Viewing WBEM-managed block storage systems poolsView block storage pools of WBEM-managed block storage systems.

Before you begin

Add storage systems to the EHAC database before viewing the block storage pool. Dothis by clicking Access Control > Block > WBEM Storage > Grant. Select the WBEMstorage and click Retrieve to view all storage systems. Select the storage systemfrom the list and then click Add to database.Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > WBEM ManagedSystem > Storage Pools.

2. Under WBEM Server, select a server from the list box and type the usernameand password.


Enabling advanced configuration for VMAX and VMAX3 arrays 41

3. Click Retrieve.

4. Under Component Name, select a storage system and click Retrieve Pools.

Viewing WBEM-managed block storage systems volumesView block storage pool volumes of WBEM-managed block storage systems.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > WBEM ManagedSystem > Storage Pools.

2. In the left WBEM Server pane, select a server and type the username andpassword.

3. Click Retrieve Pools, and then select a pool from the list.

4. Click Retrieve Volumes.

Adding an XtremIO arrayAdd an XtremIO array.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > XtremIO.

2. Under Add New XtremIO System, type the XMS IP Address, XMS Version,Friendly Name, User Name, and Password.

Note

If the XtremIO Management Server (XMS) manages a clustered XtremIO 4.0array, the List of Available XtremIO Systems shows each of the clusters X-Brick™ building blocks that are managed by the XMS, after you add the XtremIOdetails.

Updating or removing XtremIO arraysUpdate or remove an XtremIO storage array.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > XtremIO.

2. From the List of Available XtremIO Systems, select the array and clickUpdate/Remove XtremIO.

3. To update XtremIO credential details, type the username and password, andthen click Update User Name/Password.

4. To remove XtremIO details, select Remove the XtremIO system, and thenclick Remove XtremIO Array.

Adding VPLEX storage detailsAdd details for a VPLEX storage system. These details include a friendly name,username, password, and IP address.

Procedure

1. From the Administrator Menu, click Virtual System > VPLEX.

2. Under List of VPLEX Systems, click Add VPLEX Details.



3. Under New VPLEX, type a friendly name that is unique among your VPLEXstorage systems.

4. From the VPLEX Type list box, select Local or Metro, and then click Next

5. Click Add Cluster Details.

Note

Add single cluster details for a Local VPLEX type. Add two cluster details forthe Metro VPLEX type.

6. In the Add Cluster window, perform the following steps:

a. Type the IP address.

b. Type the username and password.

c. Click Add.

7. Click Next to view cluster details in the Physical Storage Details window.

8. Click Next to open the Mapping Storage and WBEM window.

9. Do one of the following:

l If the storage systems and the corresponding WBEM servers are alreadyconfigured for EHAC, click Map at the top of the page to select all of thestorage arrays that are connected to VPLEX.

l If the storage systems and WBEM servers are not configured, click NewWBEM to configure them.

10. Click Next to open the Assign Pools window.

11. Click Retrieve Pools to view a list of the pools in an array that will be used tocreate the cloned virtual volume.

12. Select a pool, and then move the username for the user who needs to haveaccess to the pool to the list on the right.

Note

To move a username to the list on the right, either drag the username or clickthe right arrow. If no users are listed, to add them, refer to Adding a user onpage 48.

13. Under Grant Pools, move the username that requires access to the pool to thelist on the right by either dragging the username or clicking the right arrow.

14. Click Grant.

15. Click Next, and then click Add VPLEX System.

Removing VPLEX storage details

Remove VPLEX storage details.

Procedure

1. From the List of VPLEX Systems, select the VPLEX system to be removed.

2. Click Update/Remove VPLEX Details.

3. Under Update/Remove VPLEX Details, click the Remove VPLEX tab.

4. Click Remove VPLEX, and then click Yes to confirm.


Adding VPLEX storage details 43

Changing the global access levelChange a global access level to enable or disable read/write access to storagesystems for all users. When you enable global access level overrides, they override allother settings. If the Global Access Level is set to read-only, all write access is alsodisabled.

Note

You can also enable or disable access for individual users. When you add a new array,the default global access level is the read/write mode. Configuring file/NAS storageon page 38 provides more information.

Procedure

1. From the Administrator Menu, click Global Access Level.

2. Select a storage system from the list.

3. Click Change Access Type.

An Access Level Changed confirmation message appears to confirm thechange.

Adding VMware vCenter virtual systems and ESXi hostsAdd VMware vCenter virtual systems and ESXi hosts to the EHAC database.

Procedure

1. From Administrator Menu, click Virtual System > vCenter.

Note

The default Connection Schema is https.

2. Under Add New vCenter System, perform the following steps:

a. Type the IP Address.

b. Type a friendly name, which is a short name that is unique among yourvCenter storage systems.

c. Type the vCenter username and password.

This user must have administrator permission.

3. Click Add vCenter.

If the server details are correct, a Successfully Added message appears.

Note

You can click Test Connection to check the connection after adding a vCentersystem. A Successfully Added message confirms a successful connection.

4. Under List of Available vCenter Systems, select a system and click RetrieveDataCenter.



5. Under List of DataCenter in selected vCenter on the upper right, select a datacenter.

6. Click Retrieve ESX.

7. Under List of ESXs in the selected vCenter on the right, select an ESX server.

8. Click Retrieve VMs to view the virtual machines in the selected ESXi.

9. Click Add to DB to add the ESXi host to EHAC.

Note

Starting with EHAC 4.6.8, virtual machine information is no longer maintainedwithin the EHAC database, although you can retrieve virtual machines and viewthem. Only ESXi details are added to EHAC database.


Adding VMware vCenter virtual systems and ESXi hosts 45



CHAPTER 7

Managing User Accounts


l Adding and removing users................................................................................ 48l Configuring access control.................................................................................49l Securing user data............................................................................................. 52

Managing User Accounts 47

Adding and removing usersUse the following procedures to add or remove users.

Adding a userA user account is required to enable ESI for SAP LaMa to manage SAP systems withinstance-specific file systems and to communicate with the Dell EMC storage systemsin use by these systems to run System Provisioning processes that involve storageoperations like clones and snapshots.

Procedure

1. From the Administrator Menu, click General > Users.

2. Under User Details, click Add New User.

3. Under New User, perform the following steps:

a. Type a username and user full name.

b. Type a strong password and then type it again for confirmation.

4. Click Create User.

Updating a user passwordUpdate a user password.

Procedure


2. Under User Details, select a user and click Update User.

3. Under Update User/Administrator, perform the following steps:

a. Type the old password.

b. Type a new strong password and then type it again for confirmation.

4. Click Update.

Updating an administrator passwordUpdate an administrator password.

Procedure


2. Click Update User > Update Administrator.

3. In the Update Administrator Password dialog box, type the old password.

4. Type a new strong password and then type it again for confirmation.

5. Click Update.



Removing a userRemove a user.

Procedure


2. Click Remove User.

3. Select the user to be removed and click Yes to confirm the action.

Configuring access controlUse the following procedures to grant access for users to file and block storagesystems and pools, and to XtremIO storage arrays.

Granting access to file storage systems and poolsGrant access to file storage systems and pools

Procedure

1. From the Administrator Menu, click Access Control > File > Grant.

2. Select a storage system from the Select the Storage System to Grant theAccess Level pane.

3. Grant access to users:

a. Click User Level.

The Select the Users to Grant the Storage System Access Level dialogbox appears.

b. Select one or more users from the left pane of the dialog box.

c. Click the right arrow to move the user or users into the right pane.

Note

The selection list does not include users who currently have access to thestorage system.

d. Click Grant To Users.

4. Grant access to storage pools:

a. Click Pool Level to display a list of file storage pools.

b. Select a storage pool and click Grant Pool.

Note

You can only grant access to storage pools that correspond to a storagesystem where the user already has been granted access.

The Select the User to Grant the Storage Pool Access dialog box appears.



Removing a user 49

Note

The selection list does not include users who currently have access to thestorage pool.

d. Click Grant To Users.

Revoking access to file storage systems and poolsRevoke access to file storage systems and pools.

Procedure

1. From the Administrator Menu, click Access Control > File > Revoke.

2. Select a storage system from the Select the Storage System from which theAccess rights need to be revoked pane.

3. To revoke user access to file storage:

a. Click User Level.

The Select the Users to Revoke the Access Level dialog box appears.


c. Click the right arrow to move a user or users into the right pane.

Note

The selection does not include users whose access to the selected storagesystem was already revoked.

d. Click Revoke to revoke access for the selected user or users.

Note

When you revoke user access to a storage system, you also revoke access toall storage pools that are related to that storage system.

4. To revoke user access to file storage pools:

a. Click Pool Level to display a list of file storage pools.

b. Select a storage pool and click Revoke Pool.

The Select the Users to Revoke the Access Level dialog box appears.

c. Select the user or users, and then click the right arrow to move them to theright pane.

d. Click Revoke to revoke access for the selected user or users.

Granting access to block storage systems and poolsGrant access to block storage systems and pools.

Procedure

1. From the Administrator Menu, click Access Control > Block > Grant.

2. In the left WBEM Server pane, select a server from the Select Server field.



3. Type the server username and password and click Retrieve.

4. From the List of Storage Systems Available for Granting Read-Write Accesspane, select a storage system.

5. Click Grant Read/Write Access.

6. Grant access to users:

a. Click Grant to Users.




Note

The selection list also includes users who currently have access to a selectedstorage system.

d. Click Grant to grant access to the selected user or users.

7. Grant access to storage pools:

a. Click Grant Pools.




Note

The selection list does not include users who currently have access to aselected storage pool.

d. Click Grant to grant access to the selected user or users.

Granting access to XtremIO storage systemsAssign users to an XtremIO array.

Procedure

1. From the Administrator Menu, click Access Control > Block > XtremIO.

2. Select the server and click Grant to Users.

3. Under Select the Users to Grant the Storage System Access Level, selectusers from the left column.

4. Click the right arrow to move users to the right column and click Grant toconfirm your selections.


Granting access to XtremIO storage systems 51

Revoking access to XtremIO storage systemsRevoke user access to an XtremIO array.

Procedure

1. From the Administrator Menu, click Access Control > Block > XtremIO.

2. Select the server from the list box and click Revoke From Users.

3. Under Select the Users to Revoke the Storage System Access Level, selectusers from the left column.

4. Click the right arrow to move users to the right column and click Revoke toconfirm your selections.

Securing user dataEHAC safeguards sensitive information by requiring WBEM server passwords andcontrol station passwords for NAS arrays. To further reduce the risk of attacks, do thefollowing:

l Close your browser when the administration console is not in use to preventaccess by unauthorized users.

l Lock the server if you leave it unattended. Secure the EHAC server in the sameway as any other server with sensitive information.

l Set up a strong password when you log in to EHAC for the first time. Thispassword must be used each time you log in to EHAC.

l Create an ESI for SAP LaMa user on vSphere vCenter and Dell EMCstoragesystems with administrator privileges to allow tracking operations and if errorsoccur.



CHAPTER 8

Utilities


l Starting and stopping the EHAC service............................................................ 54l Changing EHAC Deployment Console settings...................................................54l Using EHAC appliance aliases ........................................................................... 54l Configuring WildFly by restoring the database from a backup........................... 55l Backing up and restoring an Apache Derby database......................................... 57l Using logs to monitor EHAC server activities..................................................... 58l Configuring ESI logs...........................................................................................58l Collecting SRM, ViClient, and SAPACOSPREP logs.......................................... 59l Upgrading the ESI web service and applying hotfixes........................................ 60

Utilities 53

Starting and stopping the EHAC serviceWhen EHAC is running, start and stop the EHAC service.

Note

This procedure is valid only for the Linux-based EHAC vSphere virtual appliance.

Procedure

1. Navigate to the /etc/init.d directory.

2. To start the service, type the following command:

./ehac start

3. To stop the service, type the following command:

./ehac stop

Changing EHAC Deployment Console settingsOn Linux-based EHAC appliances, run the EHAC Deployment Console utility toreconfigure the log level and residue cleanup settings.

Procedure

1. Open the virtual machine console.

2. Log in to the guest operating system using the following username andpassword:

root/Password!

3. Open a terminal and double-click the EHACDeploymentConsole.desktop iconon the desktop.

4. Run the EHAC_DeploymentConsole_ESISAPLaMa.jar file using thefollowing commands:

cd /root/Desktopjava - jar EHAC_DeploymentConsole_ESISAPLaMa.jar

Using EHAC appliance aliasesAliases enable you to customize the shell session interface. They provide an easymethod to access ESI-specific information about an EHAC appliance.

Note

This procedure is valid only for the Linux-based EHAC vSphere virtual appliance.

When you use an alias, you can run frequently used commands by using a different,preferred term. You can also use complex or commonly used options as the defaultsfor a specific command.

The following aliases are defined in the .bash_profile file:

Utilities


l alias cddeploy='cd /usr/local/wildfly-10.1.0.Final/standalone/deployments/'

l alias cdecomlog='cd /opt/emc/ECIM/ECOM/log/'l alias cdlog='cd /usr/local/wildfly-10.1.0.Final/standalone/

log/'l alias cdsymlog='cd /var/symapi/log'l alias cdwild='cd /usr/local/wildfly-10.1.0.Final/'l alias viesi='vi /usr/local/wildfly-10.1.0.Final/

ESI_application.properties'l alias viesilog='vi /usr/local/wildfly-10.1.0.Final/

Log.properties'l alias tails='tail -f /usr/local/wildfly-10.1.0.Final/

standalone/log/server.log'These aliases are loaded automatically when you log in to the terminal as root.

The following examples show how to use aliases:

l To scroll through the currently generating WildFly log:ehac:~ #tails

l To go to the WildFly log folder directly:ehac:~ # #cdlog

Configuring WildFly by restoring the database from abackup

Use the following procedure to configure the WildFly server from an existing databasebackup in case of a failure on the current system.

Note

Use this procedure only if you have an existing EHAC server configured and takebackups from the EHAC database by using the EHAC Deployment Console. EHACsupports database backup and restore across different operating system platforms.For example, you can take a backup of a database from an existing Windows EHACserver and restore it on a Linux EHAC appliance by using the Deployment console.

When restoring the database from the remote location to the local database directoryand configuring the WildFly server by using the database, some information might belost from the time after the last backup was performed to the time when the currentEHAC system failed

Note

Use these instructions on a separate host where you want to restore the Derbydatabase backup.

Procedure

1. To start the EHAC Deployment Console:

l On a Windows-based EHAC appliance, double-click theEHAC_DeploymentConsole_ESISAPLaMa.jar file.

Utilities

Configuring WildFly by restoring the database from a backup 55

l On a Linux-based appliance, double-click theEHACDeploymentConsole.desktop icon on the desktop.

2. Select the Configure using Remote Database Backup checkbox to configurethe database from an existing backup on a remote network share.

3. Type the Database Name.

4. In the Path where Remote Backup is Located field, type the absolute path ofthe remote path of the database backup.

Note

This field is disabled if the Configure using Remote Database Backupcheckbox is cleared.

5. In the Path Where Database Needs to be Created field, select the path.

6. In the Derby Client Jar field, select the Derby Jar file.

7. Click Configure.

Note

A Server Configuration Successful message confirms theconfiguration.

Figure 6 Configuring WildFly

8. Open the WildFly Application Server and start EHAC using the backed-up datafrom the Derby database.

Utilities


Backing up and restoring an Apache Derby databaseThe Apache Derby database runs as an in-memory database within EHAC. Thedatabase holds critical information about user-to-storage access mappings, storagearray details, and runtime information that can be used to correct SAP LandscapeManagement. For data writes, data might be lost if a user loses the host where EHAC,with the Derby database, is running. If data is lost during a data write, the user loses alldata, and the data cannot be recreated.

The Derby database backup and restore utility enables administrators to initiatebackups of the Derby database on remote network file shares and to restore the dataon a new host. To help prevent critical data loss, the administrator must only installEHAC components on a different host and restore database data through the backedup copy of data files.

This utility is critical for ESI for SAP LaMa with VPLEX because most data for VPLEXoperations persists in the Derby database. The utility is always available when theWildFly Application Server is running.

To use this utility, ensure that the following requirements are met:

l Users must have complete access privileges to place the backup of the Derbydatabase and to restore the database to any system.

l The network share must be accessible from both source and target hosts.

l The database backup must not be run while you are performing any other SAPLaMa operations, as this will result in data inconsistency in the backup.

Configure and deploy the Derby database backup and restore utility.

Procedure


http://IPAddress:8080/ehac

2. Log in with the username and password that you configured when you openedthe EHAC console the first time.

3. From the Administrator tab on the top right of the page, select Utilities.

4. Click Database Backup Utility.

5. Under Configure Database Backup Properties, perform the following steps:

a. Type the Path of Remote Directory backup.

b. Type the Time to start backup in hours.

Note

For example, type 23 for a backup time of 23 hours. Use a decimal for timesthat are less than one hour.

c. From the Backup interval list box, select Daily, Weekly, or Monthly.

6. Click Configure.

7. Click Database Backup Scheduler to display your selections.

8. Click Start Scheduler.

Utilities

Backing up and restoring an Apache Derby database 57

Note

Do not select the Force Run Now checkbox.

Using logs to monitor EHAC server activitiesESI for SAP LaMa uses logs to monitor the operation of the system. This enablessystem administrators and Dell EMC Support engineers to troubleshoot issues thatusers may encounter.

While configuring and deploying EHAC, you can also configure logging to monitor theoperation of the system. Because no logs can be kept on the SAP LaMa servers, bothEHAC and the ESI for SAP LaMa adapter store logs in the EHAC server using thesame logging facility.

The following information is collected:

l Java Thread Dump Collector logs

l WildFly and EHAC Web Service logs

l SMI-S Provider logs

In case of error, review the logs in the log folder that you specified while configuringEHAC. If users encounter issues, the storage administrator can retrieve the logs fromthe EHAC server to which the user might not have access.

Note

From the EHAC Configuration Utility, you can click Collect Logs to create a Zip filethat contains logs that are generated by ESI.

Dell EMC Support might request these logs to troubleshoot issues. Refer to Configuring ESI logs on page 58.

Collect log files:

Procedure

1. Open EHAC in your web browser by using the following URL: http://IPAddress:8080/ehac

2. Log in with the username and password that you configured when you openedthe EHAC console the first time.

3. From the Administrator list box on the top right of the page, select Utilities.

4. Click Collect WildFly, ESI, SMI-S Logs.

5. Click either Open or Save to open or save the ESI_LOGS.zip file.

Configuring ESI logsConfigure logs to monitor the operation of the system to enable system administratorsand Dell EMC Support engineers to troubleshoot issues that users might encounter.

Use the EHAC Deployment Console to modify the configuration of the log level, andresidue cleanup.

Procedure

1. To start the EHAC Deployment Console:

Utilities


l On a Windows-based EHAC appliance, double-click theEHAC_DeploymentConsole_ESISAPLaMa.jar file.

l On a Linux-based appliance, double-click theEHACDeploymentConsole.desktop icon on the desktop.

2. In the Configuration Utility, click Configure Properties > Configure Logs.

3. In the Directory Where Logs need to be Created field, type the full path of thefolder to which logs should be saved.

4. Click Select to select the directory path that you entered.

5. Select a logging level to create logs that contain the following data:

l INFO—Informational data only, which does not include errors

l DEBUG—INFO data and debugging information

l TRACE—INFO, DEBUG, and stack trace data that will generate more logs

l ERROR—INFO and error messages

6. Click Configure.

A Log Folder and Log level configured successfullyconfirmation message appears.

Note

You can click Collect Logs to create a .zip file that contains logs that aregenerated by ESI. You might need to set the error level to TRACE and run atransaction that generated an error again to create all the required logs by DellEMC Support to troubleshoot issues.

Collecting SRM, ViClient, and SAPACOSPREP logsAdministrators can collect the following logs when using Linux hosts:

l Storage Resource Manager (SRM)—Provides file system and HBA details on theSAP hosts

l Virtual Infrastructure Client (ViClient)—Provides information about the ESX/vCenter activities performed through the SRM

l SAPACOSPREP partner libraries—Provides information about the mounting,unmounting, and retrieving of file systems by SRM, and the activating anddeactivating of virtual hostnames.

Procedure

1. From the Administrator tab on the top right of the page, select Utilities.

2. Click Collect SRM, ViClient, and SAPACOSPREP LOGS and do the following:

a. Type the host IP address.

b. Type the username and password.

c. Type the Solutions Enabler location or directory where SYMCLI is installedon the host.

d. Click Collect Logs.

Utilities

Collecting SRM, ViClient, and SAPACOSPREP logs 59

3. Click either Open or Save to open or save the SRmViClient.zip file containingthe SRM, ViClient, and SAPCOSPREP logs.

Upgrading the ESI web service and applying hotfixesYou can upgrade ESI to a new version on any Windows-based or a Linux-based EHACserver without changing the configuration.

Perform this procedure only if Dell EMC ESI support instructs you to do so andprovides the updated ESI files.

This procedure is applicable only when the WildFly Application Server is alreadypresent in the server. Otherwise, backup the database in the existing EHAC applianceand restore it in the newly deployed Linux-based EHAC appliance.

Note

This procedure is applicable to both a Windows-based or a Linux-based EHAC server.

Procedure

1. Stop the EHAC server.

2. Uninstall any older version of SMI-S Provider and install the latest 8.4 version,using instructions in the Solutions Enabler Version 8.4 Installation andConfiguration Guide in Dell EMC Online Support.

3. Delete the older version of esi_sap_lvm_saconfig.4.6.8.x.ear in theWildFly installation path/standalone/deployments folder.

4. Copy the newer Java EAR file named esi_sap_lvm_saconfig.5.0.x.earinto the WildFly installation path/standalone/deploymentsfolder.

5. Restart the EHAC server.

Utilities


https://support.emc.com/docu84174_Solutions-Enabler-8.4.0-Installation-and-Configuration-Guide.pdf?language=en_US

https://support.emc.com/docu84174_Solutions-Enabler-8.4.0-Installation-and-Configuration-Guide.pdf?language=en_US

CHAPTER 9

Troubleshooting and Cleaning up Storage


l Troubleshooting................................................................................................. 62l Cleaning up VMAX storage manually after a failed operation............................. 65l Automatically cleaning up storage after a clone fails.......................................... 70

Troubleshooting and Cleaning up Storage 61

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

Table 5 Troubleshooting

Symptom Prevention, resolution, or workaround

Even after you assign the XtremIO array to auser, the array details do not appear in thehome page.

l Verify that the GlobalAccessLevel for

the XtremIO array was changed to Read-Write.

l If the level was not changed, change it to

Read-Write and then assign the array to

a user on the Access Control tab

At Storage Systems > SAN > StoragePools, trying to retrieve pools fails.

The issue occurs because the array was notregistered to EHAC. Do the following:

l Click Access Control > Block >

WBEM Storage > Grant. Select the

WBEM and click Retrieve to view allstorage systems. Select the storage

system and click Add.

l After you have added the array to theEHAC database, you can access theStorage Pools page to retrieve theneeded information.

EHAC Configuration Utility fails to startcorrectly or there are errors in the WildFlyconsole.

Ensure that:

l EHAC is configured. Configuring WildFlyby restoring the database from a backupon page 55 provides details.

l The user has:

n Full read/write control to the WildFlydirectory

n Permission to create the database inthe specified directory

n Permission to start and stop WildFly

404 not found error appears when you try

to access the EHAC URL.

Ensure that:

l The EHAC web service is configured. See Configuring WildFly by restoring thedatabase from a backup on page 55.

l WildFly is running.

l The WildFly port is not used by any otherservice.

You cannot access EHAC from anotherserver.

Ensure that both the WildFly outbound andinbound ports are open in the firewall.

You cannot add a WBEM server. Ensure that:



Table 5 Troubleshooting (continued)


l The WBEM server hostname, portnumber, connection schema, and usercredentials are all valid.

l The WBEM server is accessible fromEHAC.

l The WBEM server is running.

Note

SMI-S Provider documentation providesmore information.

You cannot remove a WBEM server. Ensure that:

l The WBEM server is accessible from theEHAC web service.

l The WBEM server is running.

You cannot add a storage system. l Ensure that the storage systemcredentials are valid.

l For file storage systems, ensure that thestorage system is accessible from theEHAC server.

l For block storage systems, ensure that:

n The storage system is managed by aWBEM server.

n The WBEM server is added to EHAC.

n SP_A and SP_B information is valid.

Storage system is not available. Check if the storage system has beenremoved from the WBEM server.

Users are suddenly unable to access EHAC. l Ensure that WildFly is still responsive.WildFly can become unresponsive duringperiods of inactivity.

l Restart WildFly.

You cannot create an admin user. Ensure that:

l The latest derby.jar file is used in the

deployment utility. Otherwise, downloadthe latest version.

l The JCE policies are copied to:C:\Program Files\Java\jdk1.8.0_131\jre\lib\security

After the EHAC appliance is deployed,WBEM-related operations fail.

ECOM may not be started on the appliance.The ECOM executable file is located in theSolutions Enabler /opt/emc/ECIM/


Troubleshooting 63

Table 5 Troubleshooting (continued)


ECOM/bin directory. Run the /ECOM -dcommand from this directory to restartECOM.

After the EHAC appliance is deployed, storagesystems zoned to the host in EHAC cannot beadded.

l Verify that the pRDM gatekeeper devicesare installed according to SMI-Srecommendations.

l Go to /opt/emc/ECIM/ECOM/bin/TestSmisProvider and run a disco

command to discover the arrays.

When EHAC retrieves storage pools, an error

occurs at Storage Arrays > SAN > WBEMManaged Systems > Storage Pools.

The issue occurs because the array was notadded to the database. To correct this

problem, go to Access Control, select the

array, and click Add to database.

Note

After you add the array to the EHAC database

on the Storage Pools page, EHAC retrievesthe required information.

EHAC deployment fails while being restoredfrom a backup database.

Ensure that:

l The remote database backup directorypath is correct, because the deploymentconsole does not have provisioning toprovide user credentials to access theremote network share.

l The remote database backup path isaccessible outside the deploymentconsole, and that the required credentialsare displayed.

Multiple NAS mount points from the same filesystem are not supported.

For SAP systems with NAS mount points, youmust have 1:1 mapping between the NAS filesystem and the NFS export on the array.

Configure individual file systems for each NASmount point because the same file systemcannot be mounted as different mount points.

An SAP LaMa System Clone or Copy processon a VMAX3-based SAP system fails with thefollowing error:

Failed to acquire device lockon all devices in the request

This issue occurs when the VMAX3 arraylocks certain devices. Release the lock byusing the following SYMCLI command on anyhost with the Solutions Enabler command lineinterface (CLI) and that is zoned to the array:symdev -lock # release



Cleaning up VMAX storage manually after a failed operationUse the following procedure to clean up VMAX storage manually after a clone, copy,or machine refresh operation fails, as shown in the following figure. This failure canoccur in the post-process clone volumes step when you select Full Clones.

Before you begin

You must be familiar with Dell EMC SYMCLI to complete the steps in this procedure.

Figure 7 Viewing a failed system clone in SAP Landscape Management

Procedure

1. Create the cleanup_clone.sh script as follows:

ecc-db-tgt:/usr/scripts # cat cleanup_clone.sh/opt/emc/SYMCLI/bin/symclone -f pair -sid 6351 query/opt/emc/SYMCLI/bin/symclone -f pair -sid 6351 terminate -nop/opt/emc/SYMCLI/bin/symclone -f pair -sid 6351 queryecc-db-tgt:/usr/scripts # ll-rw-r--r-- 1 root root 168 Apr 8 16:18 cleanup_clone.sh

2. Run the EMC Symcli symclone command to identify the stage when the cloneprocess failed:

ecc-db-tgt:/usr/scripts # /opt/emc/SYMCLI/bin/symclone listDevice's Symmetrix ID : 000192606351 Source Device Target Device State Copy------------------------------------------------------------ Protected Modified ModifiedLogical Sym Tracks Tracks Logical Sym Tracks CGDP SRC <=> TGT (%)------------------------------------------------------------N/A 0CB5 0 0 N/A 0D01 0 X... Copied 100N/A 0C9C 0 0 N/A 0D10 0


Cleaning up VMAX storage manually after a failed operation 65

X... Copied 100N/A 0C9B 0 0 N/A 0D11 0 X... Copied 100Total -------- -------- -------- Track(s) 0 0 0 MB(s) 0.0 0.0 0.0Legend:(C): X = The background copy setting is active for this pair. V = The VP Snap setting is active for this pair. . = Neither setting is active for this pair.(G): X = The Target device is associated with this group. . = The Target device is not associated with this group.(D): X = The Clone session is a differential copy session. . = The Clone session is not a differential copy session.(P): X = The pre-copy operation has completed one cycle. . = The pre-copy operation has not completed one cycle.

3. Create a file named pair executing a Linux command to identify theVMAX devices that were involved in the failed post-clone volumes process:

ecc-db-tgt:/usr/scripts # /opt/emc/SYMCLI/bin/symclone list | grep 0C | awk '{print $1 " " $3}'0CB5 0D010C9C 0D100C9B 0D11ecc-db-tgt:/usr/scripts # /opt/emc/SYMCLI/bin/symclone list | grep Copied | awk '{print $1 " " $3}' >pairecc-db-tgt:/usr/scripts # cat pair0CB5 0D010C9C 0D100C9B 0D11

4. Change the authorizations of the cleanup_clone.sh shell script to allow it tobe run:

ecc-db-tgt:/usr/scripts # ll-rw-r--r-- 1 root root 168 Apr 8 16:18 cleanup_clone.sh-rw-r--r-- 1 root root 30 Apr 8 16:15 pairecc-db-tgt:/usr/scripts # chmod 777 cleanup_clone.shecc-db-tgt:/usr/scripts # ll-rwxrwxrwx 1 root root 168 Apr 8 16:18 cleanup_clone.sh-rw-r--r-- 1 root root 30 Apr 8 16:15 pair

5. Run the cleanup clone script to release the dependency between the source andtarget devices that was created in the clone process attempt:

ecc-db-tgt:/usr/scripts # ./cleanup_clone.shDevice file : pairDevice's Symmetrix ID : 000192606351 Source Device Target Device State Copy------------------------------------------------------------ Protected Modified ModifiedLogical Sym Tracks Tracks Logical Sym Tracks CGDP SRC <=> TGT (%)------------------------------------------------------------N/A 0CB5 0 0 N/A 0D01 0 X... Copied 100N/A 0C9C 0 0 N/A 0D10 0 X... Copied 100N/A 0C9B 0 0 N/A 0D11 0



X... Copied 100Total -------- -------- -------- Track(s) 0 0 0 MB(s) 0.0 0.0 0.0Legend:(C): X = The background copy setting is active for this pair. V = The VP Snap setting is active for this pair. . = Neither setting is active for this pair.(G): X = The Target device is associated with this group. . = The Target device is not associated with this group.(D): X = The Clone session is a differential copy session. . = The Clone session is not a differential copy session.(P): X = The pre-copy operation has completed one cycle. . = The pre-copy operation has not completed one cycle.'Terminate' operation execution is in progress for the device list indevice file 'pair'. Please wait...'Terminate' operation successfully executed for the device listin device file 'pair'.The Source device and the Target device do not form a Copy sessionDevice file 'pair' does not have any devices that are Clone source devices

6. Run the EMC Symcli symclone command again to verify whether any devicesare still not detached from the source devices:

ecc-db-tgt:/usr/scripts # /opt/emc/SYMCLI/bin/symclone listSymmetrix ID: 000192606351No Copy sessions found

7. Open Unisphere for VMAX, identify the target devices that were created,remove them from the masking view, and unbind them from the SAP_LAMApool, as shown in the following figure.

Note

A storage administrator should perform this step.



Figure 8 Viewing Target devices in Unisphere for VMAX

8. In SAP Landscape Management, select Configuration > Systems.

9. SelectRemove Instance and System > Remove Selected Instances andSystems and then select the cloned system to be removed, as shown in thefollowing figure.

Figure 9 Selecting the cloned system to be removed

10. Select Advanced Operations > Hosts, and then select the target host virtualmachine.



11. From the Details tab, select Cleanup of system provisioning changes andclick Execute, as shown in the following figure.

Figure 10 Cleaning up system provisioning changes in the Host Overview window

12. Select Settings > Engine, and then click Expert mode.

13. Under Timeout for All Operations Related To, change the setting in the ASInstances and Central Instance [min] field.

You can type a minimum value of 0 to wait indefinitely, or type a maximum valueof 120 for a 120 minute wait.

14. In the EHAC server, select Program Files > EMC > ECIM > ECOM > Providers,and then select the provider file.

15. Review the OSLSProvider.conf file and add the following entries if they aremissing from the file:

l To enable the deletion of the jobs after their successful completion:OSLSProvider/com.emc.cmp.osls.se.symm.Session.StorageConfiguration.job.deleteoncompletion = true

l To specify the number of minutes to wait before a job removal:OSLSProvider/com.emc.cmp.osls.se.symm.Session.StorageConfiguration.job.timebeforedeletion = 00000000080000.000000:000

16. As shown in the following figure, in OSLSProvider.conf, set the SMI-SProvider triggered replication value as follows:

OSLSProvider/com.emc.cmp.osls.se.symm.ReplicationService.totalwaittime= 86400000The value of 86400000 seconds (24 hours) is the time to wait for the sourceand target devices to synchronize all contents.



Figure 11 Configuring SMI-S timeout values to prevent a cloning failure

Automatically cleaning up storage after a clone failsYou can use the residue cleanup procedure to clean up storage after a clone volumesprocess fails or after the post-process clone volumes process fails.

l If the clone volumes process fails, all of the residue created on the array is cleanedup.

l If the post-process clone volumes process fails, the following cleanup isperformed:

n All LUNs are cleaned up on the array created for a distributed virtual volume.

n All VPLEX virtual volumes are cleaned up.

n Clones are cleaned up based on the array type:

– For VNX arrays, all clones are cleaned up.

– For VMAX arrays, no clones are cleaned up.

Note

For information about how to configure residue cleanup, refer to Configuring residuecleanup on page 30.



Documents

Enterprise Storage Integrator for SAP Landscape Management Administrator … · 2019-11-10 · deployed inside the SAP NetWeaver Java Stack where the SAP LaMa add-on is already installed