Enterprise Storage Integrator for SAP Landscape Management Storage Adapter

Transcription

1 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter Version User Guide REV 08

2 Copyright Dell Inc. or its subsidiaries All rights reserved. Published July 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 EMC Hopkinton, Massachusetts In North America Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

3 CONTENTS Preface 5 Purpose...5 Audience... 5 Scope... 5 Related documentation... 5 Conventions used in this document... 6 Where to get help...6 Your comments...7 Chapter 1 Enterprise Storage Integrator for SAP Landscape Management Overview 9 Executive summary...10 Product overview...10 Installation overview Chapter 2 Prerequisites 13 Solution prerequisites...14 Prerequisites for cloning SAP instances in a Windows OS...17 Prerequisites for cloning SAP instances in an AIX OS Chapter 3 Installing and Configuring VMware Virtual Hosts 21 Enabling the disk UUID in a VMware virtual environment...22 Configuring the VMDK so that it can respond to a SCSI inquiry...22 Installing VMware Tools...24 Enabling the VMware tools installation option for the virtual machine Verifying the VMware Tools installation...24 Verifying that the SG utility and library package files are installed on the SAP host Configuring the virtual host Downloading and running the script...26 Script functionality Adding a VMware vcenter entry to the SE database Useful commands Chapter 4 Installing ESI for SAP Landscape Management 29 Installing ESI for SAP Landscape Management Downloading ESI for SAP Landscape Management Installing the adapter Chapter 5 SAP Landscape Management-ESI Integration: Provisioning operations and processes 33 Adding an ESI storage manager...34 Caching storage information from SAP systems...36 Running the SAP Landscape Management Mass Unprepare operation...37 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide 3

4 CONTENTS Running the SAP Landscape Management Mass Prepare operation...39 Using SAP Landscape Management System Relocation, Unprepare, and Prepare operations on vsphere cluster environments...42 Configuration properties...42 Configuration property default values...43 Configuration property values for VMware vsphere clustered virtual environments...43 Using the SAP Landscape Management System Relocation operation SAP Landscape Management system provisioning prerequisites...45 Using SAP Landscape Management system provisioning to manage snapshots Creating a snapshot...47 Creating an online snapshot...48 Viewing snapshots Removing a snapshot...52 SAP Landscape Management System Provisioning Processes: System Clone, Copy, and Refresh...53 Configuring SAP target servers Managing SAP Landscape Management system provisioning processes with full clones...55 Creating a clone Creating a clone from a snapshot Using the SAP Landscape Management System Destroy process...58 Using the SAP Landscape Management System Destroy process for partially provisioned systems...58 Chapter 6 Troubleshooting 61 Troubleshooting Known limitations Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

5 Preface As part of an effort to improve its product lines, Dell EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this user guide might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your Dell EMC technical support professional if a product does not function properly or does not function as described in this document. This document was accurate at publication time. Go to Dell EMC Online Support to ensure that you are using the latest version of this document. Purpose Audience Scope This user guide describes how to use Dell EMC Enterprise Storage Integrator (ESI) for SAP Landscape Management. This user guide is for Dell EMC personnel, partners, and customers. The intended audience is an SAP Landscape Management user who wants to manage shared file or block storage by using ESI for SAP Landscape Management. This user guide is intended to provide an overview of ESI for SAP Landscape Management and its use in the SAP Landscape Management environment. Topics covered include: Prerequisites Installation, configuration, and storage management procedures Troubleshooting information Related documentation The following documents, located on Dell EMC Online Support or on EMC.com, provide additional relevant information. Access to these documents is based on your login credentials. If you do not have access to the following documents, contact your Dell EMC representative: Enterprise Storage Integrator for SAP Landscape Management Administrator Guide Enterprise Storage Integrator for SAP Landscape Management Release s Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide 5

6 Preface Conventions used in this document Dell EMC uses the following conventions for special notices: NOTICE Notice is used to address practices not related to personal injury. 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 Italic Monospace Used for names of interface elements, such as names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user specifically selects or clicks). Used for full titles of publications referenced in text. Used for: System output, such as an error message or script System code Path names, filenames, prompts, and syntax Commands and options Monospace italic Used for variables. [ ] Square brackets enclose optional values. Vertical bar indicates alternate selections the bar means or. { } Braces enclose content that the user must specify, such as x or y or z.... Ellipses indicate nonessential information omitted from the example. Where to get help Dell EMC support, product, and licensing information can be obtained as follows: Product information For documentation, release notes, software updates, or information about Dell EMC products, go to Dell EMC Online Support. Technical support Go to Dell EMC Online Support and click Service Center. You will see several options for contacting Technical Support. To open a service request, you 6 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

7 Preface Your comments must have a valid support agreement. Contact your Dell EMC sales representative for details about obtaining a valid support agreement or with questions about your account. Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to: mailto:techpubcomments@emc.com Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide 7

8 Preface 8 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

9 CHAPTER 1 Enterprise Storage Integrator for SAP Landscape Management Overview This chapter presents the following topics: Executive summary...10 Product overview Installation overview...11 Enterprise Storage Integrator for SAP Landscape Management Overview 9

10 Enterprise Storage Integrator for SAP Landscape Management Overview Executive summary Enterprise Storage Integrator (ESI) for SAP Landscape Manager is a software adapter that integrates Dell EMC storage with SAP Landscape Management. Administrators can use SAP Landscape Management to manage SAP system copies for nonproduction testing and development, using the SAP Clone, Copy, Refresh, and Relocate functions. SAP environments can have hundreds of such testing and development systems, so automating this step is a time-saver. ESI for SAP Landscape Management has the following components: ESI for SAP Landscape Management storage adapter, which is deployed as a storage manager in SAP Landscape Management Enterprise High Level Storage (HLS) Administration Console (EHAC), which is a web service layer that administrators can use to manage users, storage systems, vcenter servers, Dell EMC Common Object Manager (ECOM) servers, and access control ESI for SAP Landscape Management includes support for SAP instance file systems based on block, file, or both block and file, combined on the same SAP system that is monitored by SAP Landscape Management 3.0. The SAP installation requires that the SAP NetWeaver global file systems/sapmnt/ SID, /usr/sap/trans, and SAP HANA /hana/shared/sid are based on Network File System (NFS) file systems, because they must be shared across all the instances of an SAP system that is configured in a distributed or high-availability architecture. On SAP HANA scale-out systems, the /hana/shared/sid file system must be shared across all of the HANA nodes. ESI for SAP Landscape Management also supports physical and virtual hosts on: VMAX3 arrays that use service level objectives (SLO) storage provisioning Dell EMC XtremIO all-flash arrays Dell EMC VNX and VMAX block storage systems, which can be used in combination with VMAX3 enas file storage and VNX file storage, respectively Dell EMC VPLEX 5.5 systems Refer to the Enterprise Storage Integrator for SAP Landscape Management Release s for a complete list of all new features and changes. Product overview The ESI adapter is distributed as a Java Enterprise Archive (EAR) file that complies with SAP Landscape Management specifications. The adapter, which is shown in the following figure, runs in the SAP NetWeaver Java Stack with the SAP Landscape Management add-on installed. You can use EHAC to manage one or more Dell EMC file or block storage systems. The Java ESI storage adapter (or ESI storage plug-in) for SAP Landscape Management communicates with the EHAC server to enable the management of one or more 10 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

11 Enterprise Storage Integrator for SAP Landscape Management Overview Dell EMC file or block storage systems, and to enable storage provisioning as part of SAP Landscape Management system Clone, Copy, Refresh, and Destroy processes. Figure 1 ESI for SAP Landscape Management adapter Solutions Enabler is not required for NFS-based file systems. Installation overview The following table contains an ESI for SAP Landscape Management installation overview with the high-level steps that are required to implement SAP Landscape Management with ESI for SAP Landscape Management. Table 2 Installation overview Steps Chapter Verifying the prerequisites 2 Installing and configuring VMware vsphere virtual hosts 3 Installing ESI for SAP Landscape Management components 4 Configuring ESI for SAP Landscape Management adapter in SAP Landscape Management and running provisioning operations and processes for SAP systems on Dell EMC storage 5 Troubleshooting 6 Installation overview 11

12 Enterprise Storage Integrator for SAP Landscape Management Overview 12 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

13 CHAPTER 2 Prerequisites This chapter presents the following topics: Solution prerequisites Prerequisites for cloning SAP instances in a Windows OS Prerequisites for cloning SAP instances in an AIX OS...19 Prerequisites 13

14 Prerequisites Solution prerequisites Before you install the Enterprise HLS Administration Console (EHAC) and the ESI for SAP Landscape Management adapter, follow these steps: 1. Consult your storage administrator to: Configure and document the zoning and masking of the SAP systems based on the Dell EMC storage systems before the configuration described in the Enterprise Storage Integrator for SAP Landscape Management: Enterprise High- Level Storage Administration Console Administrator Guide. The document is available from Dell EMC Online Support. Deploy the EHAC Appliance as described in the ESI for SAP Landscape Management: Enterprise High-Level Storage Administration Console Administrator Guide. The document is available from Dell EMC Online Support. Dell EMC customers and partners must already have a login. If you do not, you can register at Dell EMC Online Support. 2. Install and configure SAP Landscape Management 3.0 as described in the SAP Landscape Management 3.0, Enterprise Edition Support Package in the SAP Help Portal page. Refer to the following Prerequisite software table for the required SAP NetWeaver Java Stack and SAP Landscape Management minimum software versions for the installation. 3. Install Dell EMC Solutions Enabler 8.3 in the SAP hosts to be managed by SAP Landscape Management by using the instructions in the Solutions Enabler Version 8.3 Installation and Configuration Guide from Dell EMC Online Support. 4. Deploy the EHAC Appliance as described in the Enterprise Storage Integrator for SAP Landscape Management Administrator Guide, which is available from Dell EMC Online Support. 5. From the following Prerequisite software table, install and configure Solutions Enabler, the SAP Host Agent, and browser prerequisite software on the SAP system hosts to be managed by SAP Landscape Management 3.0. Table 3 Prerequisite software Software Minimum software version Installed on SAP NetWeaver Java Stack a 7.5 SAP Landscape Management server SAP Landscape Management b 3.0, SP02 (with a minimal display resolution of 1280 x 960) SAP Landscape Management server Solutions Enabler c 8.3.x All SAP Landscape Management managed hosts 14 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

15 Prerequisites Table 3 Prerequisite software (continued) Software Minimum software version Installed on SAP Host Agent d 7.21 with the latest patch All SAP Landscape Management managed hosts SAP Adaptive Extensions 1.0 All SAP Landscape Management managed hosts Browser Internet Explorer 11 (other browsers will also work) User desktop a. Get the latest version from SAP ONE Support Launchpad. Click Installations and Upgrades > Browse By Category > SAP NetWeaver and complementary products > SAP NetWeaver > SAP NETWEAVER 7.x > Installation and Upgrade > Select the OS and database. b. Get the latest version from SAP ONE Support Launchpad. Click Installations and Upgrades > Browse By Category > SAP NetWeaver and complementary products > SAP LANDSCAPE VIRT MGT ENT > SAP LANDSCAPE VIRT MGT ENT 3.0 > INSTALLATION AND UPGRADE. c. Download Solutions Enabler from the Dell EMC Online Support Downloads for Solutions Enabler page. d. Get the latest version from SAP ONE Support Launchpad. Click Installations and Upgrades, browse your company's download catalog, type in the SAP host agent, and then select the latest Host Agent for the required OS. 6. Complete all of the SAP Landscape Management 3.0 configuration steps before you configure the infrastructure and the storage managers inside SAP Landscape Management. These configuration steps are described in SAP Landscape Management 3.0, Enterprise Edition Configuration and Deployment Information in the SAP Help Portal. 7. Install and configure the latest patch for SAP Host Agent 7.21 according to the SAP steps that are described in SAP Landscape Management Landscape Preparation instructions in the SAP Help Portal. Browse to Configuration and Deployment Information > Landscape Preparation > Configuring SAP Host Agent. 8. When working with SAP Landscape Management 3.0 and ESI storage-based cloning, the SAP instance file systems are cloned for using ESI cloning technologies at the storage level. For that reason, verify that the SAP instance file systems of your SAP systems managed by SAP Landscape Management are configured as follows: Only the SAP instance file systems mounted on the operating system (\usr \sap\sid, oracle\sid\sapdata1, oracle\sid\sapdata2, for example) must be stored in dedicated LUNs/datastores that are separated from the operating system disk of the source hosts. Solution prerequisites 15

16 Prerequisites Do one of the following: Install operating systems in advance for the physical and virtual target servers. Deploy new target hosts from VMware vsphere pre-configued templates containing the OS, SAP Host Agent, SAP Adaptive Extensions, and Solutions Enabler installed and configured. For vsphere virtual machines, the operating system (OS) disk must be in a dedicated virtual machine disk (VMDK) and stored in a shared datastore. For physical systems, the operating system must use local disks or dedicated LUNs. The SAP instance file systems must have dedicated LUNs/datastores separated from the OS LUN/datastore. This requirement enables SAP Landscape Management at the storage level to clone LUNs and datastores that contain only the SAP instance file system mount points. This avoids duplication of the OS file systems from the source system. Refer to Adaptive Computing Concept for more information about the design of the source SAP system that follows the SAP recommendations for storage-based cloning. If you plan to use the SAP Landscape Management System Relocation operation, ensure that the SAP source system instances are already installed and configured according to the SAP Adaptive Enable concept, also known as SAP Application. This concept requires that independent virtual IP addresses, virtual hostnames, and dedicated instance file systems be installed in a shared central storage system. For more information, refer to Adaptive Computing Concept on the SAP Community page. In a VMware environment, to facilitate SAP, VMware, and Dell EMC support, determine which SAP virtual machines are used and which SAP file systems are stored in which datastores. Use the following best practices to troubleshoot SAP, VMware, and Dell EMC support: For a given SAP system, document the vsphere virtual machines that it uses, and document which SAP instance file systems are stored in which datastores. To facilitate and speed up any troubleshooting, document in high-level detail the SAP, VMware, and Dell EMC environments for each virtual machine. Include the masking views being used, physical storage device IDs, datastore names, virtual machine settings, SCSI controller numbers, and ports used by each hard disk. Include also the guest operating system device IDs, volume groups, logical volumes, and file systems being used for each datastore. You can use Dell EMC Virtual Storage Integrator (VSI), a free product, to collect most of that information. 9. In a VMware environment, if you intend to use VMware VMDKs or raw device mapping disks (RDM), you must also install and configure the prerequisite software: 16 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

17 Prerequisites Table 4 Prerequisite software for vsphere virtual servers Software VMware vcenter Server (virtual environments) VMware Tools Software version 5.5 U3 or 6.0 or later. Use the version that corresponds to your ESXi version. VMware Tools is bundled along with the ESXi server. When using virtual hosts: Multiple paravirtual SCSI (PVSCSI) controllers are supported, which conforms to SAP and VMware best practices. Refer to Configuring disks to use VMware Paravirtual SCSI (PVSCSI) adapters ( ) in the VMware Knowledge Base. If you use VMware vsphere in a Linux operating system, refer to the SAP note, Linux: VMware vsphere configuration guidelines in the SAP ONE Support Launchpad If you use VMware vsphere in a Windows environment, refer to the SAP, Windows: VMware vsphere configuration guidelines in the SAP ONE Support Launchpad. Configure the VMware Virtual Machine Advanced Parameter disk.enableuuid using the vsphere Web Client. Refer to Installing and Configuring VMware Virtual Hosts on page 21 for details. Plan for downtime when you add the advanced disk.enableuuid parameter to all vsphere virtual machines that run SAP instances for cloning by SAP Landscape Management with ESI for SAP Landscape Management. To install VMware Tools, refer to Installing and Configuring VMware Virtual Hosts on page 21. Configure the Virtual Hosts vcenter details by running the Configure_Virtual_v2.sh script that Dell EMC provides. Refer to Installing and Configuring VMware Virtual Hosts on page 21 for details. For SAP systems with NAS mount points, you must have 1:1 mapping between the NAS file system and the NFS export on the array. Multiple NFS exports on a single NAS file system (for example, exporting the subdirectories on a single NAS file system to be mounted to hosts) is not supported. Prerequisites for cloning SAP instances in a Windows OS The ESI for SAP Landscape Management storage adapter has the following prerequisites for cloning SAP instances in a Windows OS: Use only dynamic disks. For spanned volumes, you can use multiple dynamic disks, but ensure that disks that belong to one volume are not shared with another volume. Mount volumes only as a mount path on the C drive and do not use other drive letters such as F, G, and H. Prerequisites for cloning SAP instances in a Windows OS 17

18 Prerequisites Use the Disk Management utility and select the Mount Path option. For example, the following figure shows SAP mount points (junctions or soft links) mounted as a Windows mount path on the C drive, with MC1 mounted on disk 5 in the C:\MC1 folder. NAS/NFS file system mount points for SAP instances are not supported by SAP Landscape Management. Use the Disk Management utility and select the Mount Path option. For example, the following figure shows SAP mount points (junctions or soft links) mounted as a Windows mount path on the C drive, with MC1 mounted on disk 5 in the C:\MC1 folder. Figure 2 Managing Windows disks Refer to the SAP LVM Best Practices for System Provisioning SCN in the SAP Community page for more information about the design of the source SAP system, which follows the SAP recommendations for storage-based cloning. Refer to the SAP Landscape Preparation in the SAP Help Portal for additional requirements for Windows network-attached storage (NAS) environments. Install Solutions Enabler 8.3 on the SAP hosts running SAP systems to be managed by SAP Landscape Management using the instructions in the Solutions Enabler Version 8.3 Installation and Configuration Guide in Dell EMC Online Support. Install and configure the latest patch for SAP Host Agent 7.21 by using the instructions in the SAP Help Portal. 18 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

19 Prerequisites After you install and configure Solutions Enabler 8.3 and SAP Host Agent 7.21, integrate the Enterprise Storage Library for SAP, which is deployed inside of Solutions Enabler, with the SAP Host Agent: 1. Copy the libsapacosprep_emc.dll file from C:\ProgramFiles\EMC \SYMCLI\shlib\apps\sap to the C:\Program Files\SAP\hostctrl \exe directory. 2. Add to the system environment variable path the value as C:\Program Files \EMC\SYMCLI\bin. Run the Virtual Disk Service from services.msc. To enable cloning to work correctly: Install the Oracle database software locally on drive C of the target host. After you manually install Oracle, check whether the following services are listed in services.msc. If a service is not listed, copy the missing database service entries from the source to the target machine. The following services for the Oracle client are recommended by SAP: Microsoft SQL Server. OracleJobSchedulerMK1 OracleMK111203ClrAgent OracleMK111203TNSListener OracleMTSRecoveryService OracleServiceMK1 OracleVssWriterMK1 MK1 is the System ID (SID) of the SAP instance and registry entries are based on the SID. Turn off the domain firewall for retrieving the HBA properties. Configure port 443 to enable an outgoing OS connection to the physical host bus adapter (HBA) on the server. Run the steps at SAP Landscape Management Configuration > Systems > Instance > Network isolation to enable Solutions Enabler to communicate with the ESXi physical HBA. This is to collect properties for the SAP Landscape Management storage-based system System Clone, System Copy, and System Refresh provisioning processes. For more information, refer to Configuring Outgoing Connections for System Isolation in the SAP Help Portal. Prerequisites for cloning SAP instances in an AIX OS For SAP systems running on AIX, all SAP file systems must be configured to use INLINE logging. This is a requirement for the correct functionality of Solutions Enabler/Storage Resource Manager (SRM) operations. To check whether INLINE logging is configured, view the contents of the /etc/filesystems file, which will show Log = INLINE for each mount point if the file system is configured to use INLINE logging. Prerequisites for cloning SAP instances in an AIX OS 19

20 Prerequisites If any SAP file systems are not configured to use INLINE logging, the contents of each file must be moved to a new file system that is configured to use INLINE logging. Converting a file system from using outline logging to inline logging will corrupt its data. Refer to the IBM Conversion Between Inline and Outline JFS2 Filesystem Logs note at to verify this statement. When creating a file system in AIX, refer to AIX documentation for their recommended commands and procedures. Refer to the IBM Knowledge Center for more information about using the crfs command. The attribute logname must have the value INLINE in order to create a file system that uses INLINE logging. 20 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

21 CHAPTER 3 Installing and Configuring VMware Virtual Hosts This chapter presents the following topics: Enabling the disk UUID in a VMware virtual environment Installing VMware Tools Configuring the virtual host...26 Installing and Configuring VMware Virtual Hosts 21

22 Installing and Configuring VMware Virtual Hosts Enabling the disk UUID in a VMware virtual environment Configure the virtual machine to make the VMDK respond to a SCSI inquiry from the Guest OS to read the Vital Product Data (VPD) page. When a virtual disk (VMDK) is created in a VMware ESXi virtual machine, it is stored in a datastore, which is a storage LUN formatted with a a virtual machine file system (VMFS). A unique UUID is generated for each virtual disk and kept in the virtual disk configuration file and virtual machine configuration (.vmx) file. VPD is a collection of configuration data associated with a particular set of hardware or software. The VPD stores information such as engineering change levels. Often SCSI devices attached to a system provide VPD information. By default, the VMware ESXi host will not respond to a SCSI inquiry from the guest OS to read the VPD that is associated with the virtual disk. Solutions Enabler needs the VPD information associated with the virtual disk, which should be readable from the guest OS using a SCSI inquiry. Procedure 1. Add the disk.enableuuid advanced parameter set to TRUE in the virtual machine (.vmx) configuration file. 2. After the disk.enableuuid parameter is configured, verify that the utility and library files are installed and available for the Guest OS, as follows: vmfs/volumes/5200af ce-812c-60735c68a5da/ SAPSource/SAPSource_2.vmdk 1 The unique ID associated with the virtual disk is shown as a line in this configuration file: ddb.uuid = "60 00 C2 91 f0 3d a 1a 7b ea 0a 66" Configuring the VMDK so that it can respond to a SCSI inquiry Configure the VMDK to enable it to respond to a SCSI inquiry. Procedure 1. Log in to the VMware ESXi server, or log in to vcenter, which manages the SAP host. 2. Select the SAP host virtual machine, power it off, and then select Edit virtual machine settings, as shown in the following figure. 22 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

23 Installing and Configuring VMware Virtual Hosts Figure 3 Configuring the VMDK 3. From the Virtual Machine Properties dialog box, select Options > General > Configuration Parameters as shown in the following figure. Figure 4 Clicking Configuration Parameters 4. Click Add Row, as shown in the following figure. 5. Type the following details for the new row: Name = disk.enableuuid Value = TRUE 6. Click OK to save the new configuration parameters and then power on the virtual machine. Configuring the VMDK so that it can respond to a SCSI inquiry 23

24 Installing and Configuring VMware Virtual Hosts Figure 5 Adding a new row Installing VMware Tools Use the procedures in this chapter to install VMware Tools. Enable the disk universally unique identifier (UUID) in a VMware virtual machine. Enabling the VMware tools installation option for the virtual machine To enable VMware tools to be installed on a specified virtual machine, use the procedure from General VMware Tools installation instructions ( ) article in the VMware Knowledge Base. Newer versions of Linux are provided natively with Open VM Tools (OVT), so it is not necessary to install Linux manually on the hosts. For more information, refer to the VMware support for Open VM Tools ( ) article in the VMware Knowledge Base. Verifying the VMware Tools installation Use this procedure to verify that VMware Tools have been successfully installed. Procedure 1. Log in to the ESXi server with the vsphere or vcenter credentials. 2. Select VM > Summary. 3. Click the Summary > General tab, as shown in the following figure, and check that VMware Tools is running. 24 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

25 Installing and Configuring VMware Virtual Hosts This figure shows the status of VMware Tools installed on older operating systems. The screen will be different for virtual machines with newer guest operating systems that use OVT. Figure 6 Checking that VMware Tools is running Verifying that the SG utility and library package files are installed on the SAP host Verify that the Linux SG utility and library package files are installed on the SAP virtual machines. Procedure 1. Log in as root to the guest OS of the SAP virtual machine. 2. Type the following command: rpm -qa grep sg3* The SG utility and library package files are installed on the host if the sg3 utils and sg3 utils-libs are displayed. 3. If the files are not installed, locate the package in the ISO of the Linux installer or download the binaries and install them on the host. You can type the rpm -qa command to find all rpm packages that are installed on the host. Verifying that the SG utility and library package files are installed on the SAP host 25

26 Installing and Configuring VMware Virtual Hosts Configuring the virtual host Downloading and running the script Script functionality Use the following procedures to configure the virtual machine after Solutions Enabler is installed and configured. For more information, refer to the instructions in the Solutions Enabler Version 8.3 Installation and Configuration Guide in Dell EMC Online Support. Download and run the script to configure the virtual machine after SE is installed and configured. Procedure 1. Download the Configure_VirtualHost_v2.sh script from the Dell EMC Online Support Storage Integrator for SAP Landscape Virtualization Management page, and then copy the script to both the source and target virtual machines. 2. Grant execute permission to the script: chmod 755 Configure_VirtualHost_v2.sh 3. Verify the ESXi IP/vCenter address on which the virtual machine resides. 4. Enable the Secure Shell (SSH) on the ESXi server on which the virtual machine resides. 5. Run the following script:./configure_virtualhost_v2.sh 6. As a best practice, create a new user in vcenter with administrator rights to run all the ESI required activities. Type a vcenter username that has the administrative permission and password. This best practice enables you to see the specific vcenter activities that are run by ESI for SAP Landscape Management. The script provides the following functionality: Adds a vcenter entry to the SE SYMAPI database Deletes the vcenter entry that was previously added to the SE SYMAPI database Lists entries of the SE SYMAPI database Adding a VMware vcenter entry to the SE database Add a VMware vcenter entry to the SE database. The ConfigureVirtualHost_v2 script was enhanced to register vcenter with an SE database. Procedure 1. At the command line prompt, run ConfigureVirtualHost_v2.sh. 2. Type the v option to add the vcenter server IP and credentials to register vcenter in the SE database. 26 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

27 Installing and Configuring VMware Virtual Hosts 3. After you add vcenter, type the l option to list the vcenter details. If the virtual machine is moved by vmotion or restarted by vsphere HA to another ESXi server, the SE SYMAPI database will still be able to communicate as long as vmotion occurred within the same vcenter server domain. When the ESXi server where the virtual machine is running changes, the HBA information retrieved by SE changes. Configure the Export Path of the mount points inside SAP Landscape Management at Configuration > Hosts > Select Host > Edit > Host Properties. Click Retrieve from Host at the bottom of the screen in Host-Specific Storage Properties, to update the HBA information inside SAP Landscape Management. ESI dynamically updates this information before any storage-related operation. Performing this step manually is only necessary to update the HBA information in the SAP Landscape Management GUI. SE uses vcenter host connection information to gain access to the storage array data. The ConfigureVirtualHost_v2.sh script automatically performs the following operations: Updates the SE SYMAPI database with the vcenter IP address, username, and password by running the following command: symcfg auth add -vmware -host <IP_Address> -username <UserName> -password <Password> -vmport namespace vmware/vc Confirms that the vcenter certificate is available on the vcenter server at /etc/vmware/ssl and that the vcenter certificate file name is rui.crt. The script then copies the vcenter rui.crt certificate to the /var/symapi/ config/ directory and renames it to viclient_cert.pem, to be used by SE. Copies the virtual machine certificate to the following location: /var/symapi/config/viclient_cert.pem Runs the discover command for SE to connect to the ESXi server and get details of the underlying storage array: /opt/emc/symcli/bin/symcfg scan (VMAX and VNX) /opt/emc/symcli/bin/symcfg discover (VMAX, VPLEX, XtremIO) /opt/emc/symcli/bin/symcfg discover -clariion (VNX) Useful commands Optionally, you can type commands to do the following tasks: To check which vcenter server is currently configured: symcfg auth list -vmware To manually remove a vcenter server that is no longer running, but has an entry from the virtual machine SE symapi database: symcfg auth delete -host <IP Address> -user -namspace vmware/vc Useful commands 27

28 Installing and Configuring VMware Virtual Hosts To manually add a new vcenter server entry on the SE symapi database of the virtual machine: symcfg auth add -vmware -host <IP_Address> -username <UserName> -password <Password> -vmport namespace vmware/vc You must use the Configure_VirtualHost_v2.sh script on every SAP virtual machine to be used with ESI This script adds an entry for the vcenter server in the symapi database of the virtual machine 28 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

29 CHAPTER 4 Installing ESI for SAP Landscape Management This chapter presents the following topic: Installing ESI for SAP Landscape Management...30 Installing ESI for SAP Landscape Management 29

30 Installing ESI for SAP Landscape Management Installing ESI for SAP Landscape Management Use the following procedures to undeploy an older version of ESI for SAP Landscape Management and to download and install the new adapter. Downloading ESI for SAP Landscape Management ESI for SAP Landscape Management is distributed as a Java EAR file and can be downloaded from Dell EMC Online Support. You can download and use the ESI adapter and Enterprise HLS Administration Console (EHAC) separately. This could commonly be necessary if the user is not also the storage administrator. Procedure 1. Go to the Downloads for Storage Integrator for SAP Landscape Management page. 2. Click Downloads to download the Storage Integrator for SAP Landscape Management plug-in. The ESI Web Service and ESI Deployment Console are already installed and configured on the EHAC appliance. The ESI for SAP Landscape Management adapter must be deployed inside the SAP NetWeaver Java Stack server where SAP Landscape Management is running. First deploy the EHAC appliance as described in the Enterprise Storage Integrator for SAP Landscape Management: Enterprise High-Level Storage Administration Console Administrator Guide, and then deploy the adapter as described in the following procedures. Installing the adapter After downloading ESI for SAP Landscape Management, install the adapter on the SAP Landscape Management server. Procedure 1. Copy the esi_sap_lvm_plugin x.ear file to the SAP Landscape Management server. 2. On the SAP Landscape Management server, deploy the EAR file by following these instructions. Run the Telnet commands locally on the SAP Landscape Management server. Do not run the commands remotely. SAP NetWeaver administrator privileges are required to run this step. a. Log in to SAP Java Stack using the Telnet localhost administrator password, as shown in the following figure. b. After successfully logging in, run the following command to determine if the adapter is already installed. list_app grep plugin 30 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

31 Installing ESI for SAP Landscape Management Figure 7 Logging in to SAP Java Stack c. Undeploy any older versions of the adapter, as shown in the following figure. Figure 8 Undeploying older versions of the adapter d. Deploy the adapter, as shown in the following figure. Installing the adapter 31

32 Installing ESI for SAP Landscape Management Figure 9 Deploying the adapter e. Confirm that the plug-in was deployed, as shown in the following figure. Figure 10 Adapter is deployed 32 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

33 CHAPTER 5 SAP Landscape Management-ESI Integration: Provisioning operations and processes This chapter presents the following topics: Adding an ESI storage manager...34 Caching storage information from SAP systems Running the SAP Landscape Management Mass Unprepare operation...37 Running the SAP Landscape Management Mass Prepare operation Using SAP Landscape Management System Relocation, Unprepare, and Prepare operations on vsphere cluster environments Using the SAP Landscape Management System Relocation operation...43 SAP Landscape Management system provisioning prerequisites Using SAP Landscape Management system provisioning to manage snapshots SAP Landscape Management System Provisioning Processes: System Clone, Copy, and Refresh Using the SAP Landscape Management System Destroy process Using the SAP Landscape Management System Destroy process for partially provisioned systems...58 SAP Landscape Management-ESI Integration: Provisioning operations and processes 33

34 SAP Landscape Management-ESI Integration: Provisioning operations and processes Adding an ESI storage manager SAP Landscape Management needs a storage manager to communicate with the underlying physical storage arrays that contain the SAP instance file systems that are configured there. ESI and its associated libraries send queries to the storage system to manage relevant information, such as storage pools, mount paths, and snapshots, and provides SAP Landscape Management support for the system provisioning processes such as System Clone, System Copy, and System Refresh. Procedure 1. Open the SAP Landscape Management window. 2. Type your username and password, and then click Log On. 3. Select Infrastructure > Storage Managers as shown in the following figure, and then click Add. Figure 11 Adding an ESI storage manager 4. In the Supported Storage Manager Types list, select EMC Corp ESI for SAP NW LaMa, and then click Next, as shown in the following figure. Figure 12 Selecting the Storage Manager Type 5. Type the Basic Properties for the storage manager, as shown in the following figure. a. In the Label field, type a name that identifies this storage manager. b. Type the username and password of a registered EHAC user. Installing and Deploying the EHAC Server in the Enterprise Storage Integrator for SAP Landscape Management: Enterprise High-Level Storage Administration Console (EHAC) Administrator Guide provides details. Only the 34 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

35 SAP Landscape Management-ESI Integration: Provisioning operations and processes storage arrays added by this user will be visible to the adapter on the SAP Landscape Management server. c. In the URL field, type the IP address and port number of the EHAC server. d. In the Monitoring Interval (Seconds) field, add the monitoring interval for storage caching while configuring the adapter in SAP Landscape Management Click Test Configuration to test the configuration before adding it. Figure 13 Typing basic properties for the storage manager 7. After you receive confirmation that the configuration is correct, click Next. 8. Click Save. The storage manager is installed and a list of storage systems assigned to this user appears in the Storage Systems section of the SAP Landscape Management window. Click Reload Storage Systems to see an updated list of storage systems assigned to this user. 9. Confirm that the added storage manager is ESI version x and the Enterprise Storage Library is version 8.x or later, as shown in the following figure. Adding an ESI storage manager 35

36 SAP Landscape Management-ESI Integration: Provisioning operations and processes Figure 14 Confirming the required ESI and Enterprise Storage Library versions Caching storage information from SAP systems With SAP Landscape Management 3.0, you can use the storage cache feature to retrieve storage information from VNX, VMAX, VPLEX, and XtremIO storage arrays. This feature speeds up the storage-related operations. The cache information also shows the volume group and logical volume information. SAP Landscape Management uses the cached information during the SAP LVM system provisioning processes, such as the System Clone, System Copy, and System Refresh processes; and the Mass Unprepare, Mass Prepare, and System Relocation operations. The following figure shows a VMAX3 enas storage cache tree with block storage system, pool, and volume details at Advanced Operations > Storage > Storage Overview. The same format is used for VMAX and VNX storage arrays. Figure 15 Storage caching for VNX and VMAX block storage arrays The following figure shows storage caching for XtremIO and VNX file storage arrays. 36 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

37 SAP Landscape Management-ESI Integration: Provisioning operations and processes Figure 16 Storage caching for XtremIO and VNX file storage arrays The following figure shows storage caching for volume groups on a host. During cloning, the volume group information about the SAP hosts is retrieved and populated in the Storage tab. Figure 17 Storage caching for volume groups on a host Running the SAP Landscape Management Mass Unprepare operation You can use the Mass Unprepare operation to remove SAP systems from a specified host. Before you begin Before running this operation, ensure that Storage Manager was added. Click Advanced Operations > Storage to confirm that all volumes and volume group information are cached. If they are not cached, click Monitoring Data to cache the information. Click Advanced Operations > Hosts to check that all source hosts are in a correct state, with hosts assigned to their respective instances. Running the SAP Landscape Management Mass Unprepare operation 37

38 SAP Landscape Management-ESI Integration: Provisioning operations and processes The operation stops the running SAP system, and unmounts and detaches the SAP instance file systems and volumes. Use this operation when you want to run OS maintenance or hardware upgrades on hosts, where you can prepare the system after the maintenance activities are completed. You can remove the SAP system from the specified host indefinitely or move the SAP instance using the SAP Landscape Management System Relocation operation to prepare to another host. Procedure 1. Select Infrastructure > Storage Managers > Operations. 2. Click Systems > Configuration. Ensure that storage caching has been updated in Storage > Storage Overview and that the NFS export files for this operation are listed; otherwise, the operation will fail. 3. Select Advanced Operations > Systems > Mass Operations, then select the files for the unprepare operation, and then click Execute, as shown in the following figure. If any service or program is running and locking the SAP Instance-specific file systems on the SAP host where the Mass Unprepare operation is being executed, the operation will fail. Figure 18 Selecting files and starting the Mass Unprepare operation 4. Click Monitoring > Logs and select a log to view its details in the Details window, as shown in the following figure. Logs show the details and status of the operation and show details of all activities performed by each component in each operation step. 38 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

39 SAP Landscape Management-ESI Integration: Provisioning operations and processes Figure 19 Viewing log details after the Mass Unprepare operation Running the SAP Landscape Management Mass Prepare operation You can use the Mass Prepare operation to mount the SAP instance-specific file systems to a new target host during the System Relocation operation, and during the System Clone, System Copy, and System Refresh processes. Before you begin All three source systems must be in an unprepared state without any mounted volumes. In a VMware environment, before you can use Prepare, Unprepare, Relocation, or Clone, you must add all of the SAP source and target ESXi hosts to the EHAC database. Procedure 1. Click Infrastructure > Storage Managers, and then do the following: Confirm that the storage manager was added with the correct EHAC user credentials. Test the storage manager connection and retrieve all arrays associated with the EHAC user. Confirm that all arrays associated to the SAP system are assigned to the EHAC user. If the arrays are not assigned, use the EHAC administration console to assign the required access. 2. Click Advanced Operations > Storage. Running the SAP Landscape Management Mass Prepare operation 39

40 SAP Landscape Management-ESI Integration: Provisioning operations and processes If it is not cached, click Monitoring Data to cache the information. 3. Click Advanced Operations > Hosts and check to see that all source hosts are in a correct state, with no hosts assigned to their respective instances, as shown in the following figure. Figure 20 Checking that hosts are in a correct state 4. Click Advanced Operations > Systems > Mass Operations, and either click Auto Assign or manually select the host from the available hosts, as shown in the following figure. 5. Select the instances and click Execute. Figure 21 Selecting a host during a Mass Prepare operation 40 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

41 SAP Landscape Management-ESI Integration: Provisioning operations and processes During the prepare operation on VMware environments, ESI performs the following steps for the SAP system instance-specific storage volumes: Storage volumes are added to their respective storage groups on the storage array. Datastores are attached and mounted to the ESXi host. Virtual Machine Disks (VMDKs) associated with the datastores are added to the virtual machine. SAP Landscape Management then calls the SAP Host Agent and runs the following steps: The SAP instances file systems are mounted by the SAP Host Agent sapacosprep command, which calls the Enterprise Storage Library for SAP (libsapacosprep_emc.so) that is part of Solutions Enabler software. The SAP instances are then started in order. Detailed ESI for SAP Landscape Management logs that confirm the results of the operation are generated in the configured {JBOSS_HOME}/ standalone/log folder in the EHAC server. Detailed SAP Host Agent logs that confirm the results of the operation are generated in the /usr/sap/hostctrl/work directory in the SAP host. 6. Click Monitoring > Logs and select a log to view its details in the Details window, as shown in the following figure. Logs show the details and status of the operation and show details of all activities performed by each component in each operation step. Running the SAP Landscape Management Mass Prepare operation 41

42 SAP Landscape Management-ESI Integration: Provisioning operations and processes Figure 22 Viewing log details after the Mass Prepare operation Using SAP Landscape Management System Relocation, Unprepare, and Prepare operations on vsphere cluster environments For VMware cluster-based virtual environments, ESI for SAP Landscape Management includes a set of properties that you can use manually to provide easy and efficient relocation of SAP systems from source hosts to target virtual hosts. For vsphere HA/ vmotion in SAP systems and when Dell EMC storage arrays are used, all the datastores must be visible to all ESXi hosts that are available in the VMware vsphere cluster. Start by creating masking views for the individual servers with storage groups that only contain the dedicated devices that they each individually need. Then create a separate masking view with a storage group that contains the shared devices, a port group containing the applicable ports, and an initiator group that contains the initiator groups of each individual host that were created in the first step. Cascaded initiator groups are described in the EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide in Online Support. Configuration properties You can use the following configuration properties for system relocations: UnprepareWithNoVolumes PrepareWithNoVolumes These properties can be added in ESI_application.properties, which is available in the JBoss Home directory. Use these properties only during Mass 42 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

43 SAP Landscape Management-ESI Integration: Provisioning operations and processes Unprepare and Mass Prepare operations or a virtual-to-virtual (V2V) SAP Landscape Management System Relocation operation, in a cluster-based VMware environment. During all other processes, such as System Clone, System Copy, System Destroy, and System Refresh, the property parameters should be set to default values. Configuration property default values The Mass Prepare and Mass Unprepare operations perform at the Dell EMC storage layer operation of adding or removing volumes from a masking view. These are the default values for configuration properties and are not exposed in the application properties file: UnprepareWithNoVolumes = False PrepareWithNoVolumes = False Configuration property values for VMware vsphere clustered virtual environments Add these values to avoid the extra steps of adding or removing volumes from a masking view at the storage level during Prepare and Unprepare operations. This makes the operations faster and works at the VMDK/RDM operation level in the VMware layer: UnprepareWithNoVolumes=True PrepareWithNoVolumes=True NOTICE Use these parameters only during a SAP Landscape Management Mass Unprepare, Prepare, or V2V System Relocation operation in a vsphere cluster-based environment. During all other operations, such as System Clone, System Copy, System Destroy, and System Refresh, keep the default values for the property parameters. The above configuration parameters are required for ESI for SAP Landscape Management to handle the Prepare, Unprepare, and other operations on shared datastores in VMware vsphere clusters. They protect the visibility of the datastores to the other ESXi hosts, when ESI Prepare/Unprepare operations are performed on an SAP system, avoiding the masking of the LUNs supporting the datastores to be removed from all the ESXi servers in the vsphere cluster. Using the SAP Landscape Management System Relocation operation The SAP System Relocation operation enables the SAP system to be moved from an existing host to another host, which is configured on SAP Landscape Management. Before you begin The SAP system to be relocated must be installed as Adaptive Enabled. ESI for SAP Landscape Management supports all relocation options: Configuration property default values 43

44 SAP Landscape Management-ESI Integration: Provisioning operations and processes Physical-to-physical relocation (P2P) Physical-to-virtual relocation (P2V), which is supported for physical volumes copied to vsphere using prdm disks on the target Virtual-to-virtual relocation (V2V) Virtual-to-physical relocation (V2P), which is only supported for vsphere virtual machines that use prdm disks to be copied to physical volumes Procedure 1. Click Infrastructure > Storage Managers, and then do the following: Ensure that the storage manager is added with EHAC user credentials. Test the storage manager connection and retrieve all arrays associated with the EHAC user. Ensure that all arrays associated to the SAP system are assigned to the EHAC user. If arrays are not assigned, use the EHAC administration console to get access. 2. Click Advanced Operations > Storage, and confirm that all volumes and volume group information is cached. 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 correct state, which is indicated by the green icon next to the host names. 4. Click Operations > Systems > Mass Operations, and then select Mass Relocate All in State running. 5. Click Auto Assign or manually select the host from the listed hosts, as shown in the following figure. Figure 23 Performing a System Relocation 44 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

45 SAP Landscape Management-ESI Integration: Provisioning operations and processes NOTICE In Linux/Unix systems, SAP does not persist in the changed mount options of the relocated system, but only uses it once during the Prepare step of the System Relocation operation. For that reason, any further operations on the relocated system require refreshing the export path entries in SAP Landscape Management. Changes are reflected in SAP Landscape Management only if the SAP Landscape Management administrator clicks Retrieve Mount List for the relocated system at Configuration > System > Select the instance > Edit > Mount Points. SAP Landscape Management system provisioning prerequisites Complete the prerequisites and configuration steps in this section before you manage snapshots and clone a system. 1. Create a masking view for each target. ESI for SAP Landscape Management discovers each masking view and adds the SAP instance-relevant storage volumes to the first available masking view that it finds. This discovery process makes the volume available to the target server. The operation fails if no masking views are found. Masking view is the term used for VMAX. This is equivalent to storage groups for VNX and storage views for VPLEX. For XtremIO, create the initiator groups for the target hosts ahead of time for System Clone/System Copy. 2. Ensure that you have appropriate access rights to the storage pool that you select and the storage pool has available space that is at least equal to the size of the source file system. 3. Confirm that you 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 the size of the source volumes. 4. Run all the SAP Landscape Management configure hosts steps. Install the SAP Host Agent on all SAP source and target virtual machines and install SE. Then create a symbolic link in the SAP Host Agent directory pointing to the Enterprise Storage Library for SAP. Run the following command for Linux: ln -s /opt/emc/symcli/shlib/apps/sap/libsapacosprep_emc.so libsapacosprep_emc.so Run the following command for AIX: ln -s /opt/emc/symcli/shlib/apps/sap/libsapacosprep_emc.o libsapacosprep_emc.o For Windows environments, refer to Prerequisites for cloning SAP instances in a Windows OS. SAP Landscape Management system provisioning prerequisites 45

46 SAP Landscape Management-ESI Integration: Provisioning operations and processes 5. Verify and configure all of the SAP Landscape Management Setup menu tabs, especially the timeout for operations involving SAP instances operations. This will avoid timeout of System Clone, System Copy, and System Refresh processes. 6. Configure the SAP Landscape Management Infrastructure menu tabs, especially the Network, User Management, Name Management, and Storage Managers configuration. Refer to SAP Landscape Management Infrastructure Configuration instructions on the SAP Landscape Management 3.0, Enterprise Edition page in the SAP Help Portal, and then navigate to Configuration and Deployment Information > Landscape Configuration > Managing System Landscapes > Provisioning Systems. 7. Configure the SAP Landscape Management Configuration menu Host tabs to discover and add the source and target SAP virtual machines, networks, and HBAs. In a VMware environment, the HBAs must match HBAs of the ESXi server where the virtual machine is running. To view the HBA ESXi details in a vsphere client, click ESX host > Go to configuration > Select Storage Adapters. The details list all the ESX HBAs and you can check for the Fibre Channel type HBAs You can also retrieve HBA details on a host by running the following SYMCLI command: /opt/emc/symcli/bin/syminq hba. If this command does not work, there is an SE configuration issue. Review the previous configuration steps in "Installing and Configuring VMware Virtual Hosts." 8. Configure the Systems tab in the SAP Landscape Management Configuration menu to discover and add the SAP instances to be managed by SAP Landscape Management: a. Configure all the SAP settings to allow System Clone, System Copy, System Rename, and System Refresh processes. Refer to SAP Landscape Management Mount Points instructions on the SAP Landscape Management 3.0, Enterprise Edition page in the SAP Help Portal. b. Carefully configure the network isolation settings to allow open communication at all times with the ESXi hosts, the EHAC server, and any central NFS, Domain Name System (DNS), and Lightweight Directory Access Protocol (LDAP) servers being used by the SAP Landscape Management source and target systems. In addition to VMware, this can also be configured with other environments, such as bare-metal or IBM AIX LPAR. c. Carefully configure the mount points for each of the instances associated with a source system. 9. In the SAP Landscape Management Advanced Operations menu, run all the instances and hosts validations and confirm that they are green to show that the hosts and instances are in a correct state. 10. Verify with your storage administrator that the licenses and configuration are correct, and that enough space is available in the Dell EMC storage pool for clones and snapshots. 46 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

47 SAP Landscape Management-ESI Integration: Provisioning operations and processes Using SAP Landscape Management system provisioning to manage snapshots After you have installed a storage manager and verified all of the provisioning prerequisites, click Provisioning to provision the storage system. Refer to the following procedures to create, remove, and view snapshots. Snapshots of all the source volumes for a given instance are triggered in a single call to maintain storage consistency. The snapshots are named with an SAP Instance ID and followed by a unique ID, abbreviated if necessary to fit the 64-character limitation on snapshot naming. You cannot create or manage snapshots for VPLEX systems. Creating a snapshot NOTICE All snapshot operations, including Manage Snapshots, Snap-Clones, and Snap-Copies on VMAX3, use the Symmetrix VxSnap technology. Dell EMC TimeFinder VP Snap, and TFSnaps, for the source volumes taken outside of ESI for SAP Landscape Management 4.6.8, can result in failure, as they are mutually exclusive snapshot technologies.. You can create a VNX or VMAX snapshot, or a checkpoint in time, for a selected file or block storage system. Procedure 1. Click Provisioning. 2. Click System and AS. 3. Click Manage System Snapshots. 4. In the Manage Snapshots of System dialog box, click Take Snapshot, as shown in the following figure. Using SAP Landscape Management system provisioning to manage snapshots 47

48 SAP Landscape Management-ESI Integration: Provisioning operations and processes Figure 24 Creating a snapshot Creating an online snapshot 5. Optionally, in the Description dialog box, type a meaningful description for the purpose of the snapshot, and then click Next. The snapshot appears in the Manage Snapshots of System dialog box. 6. Select the Online/Offline option for Database consistency, and then click Next. 7. Click Take Snapshot. You can create a VNX or VMAX snapshot, or a checkpoint in time, for a selected SAP system when a database is online or offline. First verify that the Oracle redo logs are configured and complete for the online operation. The following procedure uses an Oracle database example. Procedure 1. Click Configuration > Systems > System Details > Edit, as shown in the following figure. 48 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

49 SAP Landscape Management-ESI Integration: Provisioning operations and processes Figure 25 Checking configuration details for a snapshot 2. If the basic configuration is complete, click Provisioning & RFC to perform SAP Landscape Management Online System Clone, System Copy, and System Refresh processes, to ensure that the Oracle redo log is configured for the SAP system, as shown in the following figure. Click Cancel to exit this screen. Figure 26 Reviewing the basic configuration and provisioning and RFC details Creating an online snapshot After verifying the configuration, you can create an online snapshot. Procedure 1. Click Provisioning, and then click Manage System Snapshots > Take System Snapshots, as shown in the following figure. Creating an online snapshot 49

50 SAP Landscape Management-ESI Integration: Provisioning operations and processes Figure 27 Taking System Snapshots 2. In Basic > Basic Data of System Snapshot, type the snapshot description, and then click Next, as shown in the following figure. Figure 28 Selecting data for a snapshot 3. Click Provisioning > System and AS > Consistency, select the default Online Backup, type the Timeout value in seconds, and click Next, as shown in the following figure. 50 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

51 SAP Landscape Management-ESI Integration: Provisioning operations and processes Figure 29 Selecting snapshot consistency details 4. Click Take Snapshot to open the Monitoring > Activities screen that displays the high-level details and status of the operation steps of the snapshot, as shown in the following figure. Figure 30 Viewing snapshot details and operation status 5. In the Logs pane, select a Log ID to view the details and status of the operation and show details of all activities performed by each component, as shown in the following figure. Creating an online snapshot 51

52 SAP Landscape Management-ESI Integration: Provisioning operations and processes Figure 31 Viewing snapshot log details Viewing snapshots When you view snapshots in the SAP Landscape Management GUI, you only see the storage snapshots created from the SAP Landscape Management Provisioning Manage Snapshots functionality, not any other snapshots created at the storagearray level with Dell EMC Unisphere or symcli commands. Procedure 1. Click Provisioning > Manage System Snapshots. 2. View the snapshots in the Manage Snapshots of System dialog box, as shown in the following figure. Figure 32 Viewing snapshots Removing a snapshot You can remove a snapshot, as shown in the following figure. 52 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

53 SAP Landscape Management-ESI Integration: Provisioning operations and processes Procedure 1. Click Provisioning > Manage System Snapshots. 2. In the Manage Snapshots of System dialog box, select a snapshot from the list. 3. Click Remove Snapshot, and then click Remove Snapshot again to confirm your action. Do not delete snapshots in Unisphere that were created in SAP Landscape Management because doing this will cause data errors. Figure 33 Removing a snapshot SAP Landscape Management System Provisioning Processes: System Clone, Copy, and Refresh You can create system clones either from a snapshot directly from a live system, or by using an existing SAP Landscape Management snapshot created at an earlier point in time. The available storage replication options depend on the type of storage system. The following table provides details. Table 5 Storage systems and storage replication options Storage system Storage replication options VMAX TimeFinder Snap or VP Snap Time Finder Snap or VP Snap from full clone VP Snap is the default snapshot technology used for VMAX, although Time Finder Snap can also be used. SAP Landscape Management System Provisioning Processes: System Clone, Copy, and Refresh 53

54 SAP Landscape Management-ESI Integration: Provisioning operations and processes Table 5 Storage systems and storage replication options (continued) Storage system VMAX3 Storage replication options Dell EMC TimeFinder SnapVX snapshots and clones SAN VNX SAN copy full clone VNX Snapshot Enabler snapshot or new snapshot Full clone from VNX Snapshot Enabler snapshot Dell EMC VCE vblock SAN copy full clone VNX Snapshot Enabler snapshot or new snapshot Full clone from VNX Snapshot Enabler snapshot A full clone cannot be used with XtremIO. The cloning process in XtremIO creates a snapshot on the array, and mounts it on the target machine. The snapshots created on the array are named with prefixes of ESISnap and ESIClone and are based on the type of cloning process that you use. NAS VNX SnapView clone SnapView snapshot VPLEX Full clones using storage cloning is supported by underlying VPLEX storage arrays XtremIO Snap clone Full clone For information about the prerequisites and configuration steps that must be completed before you can clone a system, refer to SAP Landscape Management system provisioning prerequisites on page 45. Configuring SAP target servers When cloning using a file or block storage system, do not change the name of either the source or the target file systems. You must have sufficient disk space in a target pool to clone the source. You must create masking views on target servers before users can perform system cloning. The ESI for SAP Landscape Management adapter can expose storage volumes to SAP Landscape Management targets only by using existing zoning and masking views. Masking view is the term used for VMAX. This is equivalent to storage groups for VNX and storage views for VPLEX. For XtremIO, create the initiator groups for the target hosts ahead of time for system cloning/copy. 54 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

55 SAP Landscape Management-ESI Integration: Provisioning operations and processes Managing SAP Landscape Management system provisioning processes with full clones Creating a full clone causes the storage manager to perform a full copy of the volumes, instead of only taking snapshots. Confirm that the storage system has enough space to perform this operation. Full cloning is supported for both file and block storage systems. Making full copies of storage volumes might take a long time, depending on the size of the volume. Known limitations provides information about the limitations of full cloning. When you perform a system clone, the target system is isolated by the settings configured in SAP Landscape Management Configuration > Instances > Network Isolation. If you forgot to maintain an existing outgoing connection, you can add the connection in the isolation step. Creating a clone You can create a clone to cause the storage manager to perform a full copy of the volumes. Procedure 1. Click Provisioning. 2. From System Landscape, select the source system that you want to clone. 3. Click Clone System. If you want to use the SAP Online Cloning option, be sure to select a source system that contains the mount configuration for database online redo logs. 4. Refer to SAP Landscape Management online help and follow the first three System Cloning steps: (1) Basic; (2) Hosts; and (3) Host Names. 5. Click Next when you are finished. 6. In Storage, select the Full Copy checkbox for all storage volumes for a full clone, as shown in the following figure. For snap clones, clear the checkbox for all storage volumes. Managing SAP Landscape Management system provisioning processes with full clones 55

56 SAP Landscape Management-ESI Integration: Provisioning operations and processes Figure 34 Creating a Full Copy for all storage volumes 7. From the Storage Pool field, select a storage pool from the list and close the dialog box. 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 the size of the source volumes. For VPLEX systems, you do not need to select a storage pool, because ESI automatically selects the storage pool based on access rights and the maximum space that is available on the storage pool. For XtremIO volumes-based SAP systems: For an XtremIO RDM/physical volume, the storage system component name is displayed in the Storage System column. For virtual environments or VMDKs, the VMWARE_vmdk token is displayed in the Storage System tab. 8. Click Next. 9. Refer to SAP Landscape Management online help and follow step (5) Consistency. Select one of the following options: Online: Backup/Suspend IO Mode to create an online clone Enter 600 in the Timeout [seconds] field to avoid any timeout issues. Offline to create an offline clone 10. Click Next. 11. Follow System Cloning steps (6) Isolation and (7) Summary. Refer to SAP Landscape Management Provisioning instructions in the SAP Landscape Management 3.0, Enterprise Edition page on the SAP Help Portal, and then navigate to Configuration and Deployment Information > Landscape Configuration > Managing System Landscapes > Provisioning Systems. 56 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

57 SAP Landscape Management-ESI Integration: Provisioning operations and processes Creating a clone from a snapshot You can clone from snapshots on VNX systems, but not on VMAX or VPLEX systems. Procedure 1. Click Provisioning. 2. From System Landscape, select the source system that you want to clone. 3. Click System Clone. 4. Refer to SAP Landscape Management online help and follow the first three System Cloning steps: (1) Basic; (2) Hosts; and (3) Host Names. 5. Click Next when you are finished. 6. In the Storage step, select the Full Copy checkbox for all storage volumes. 7. Select Clone from System Snapshot and select the previous snapshot created, as shown in the following figure. Figure 35 Selecting a snapshot 8. Select a snapshot from the Clone from system snapshot list. 9. From Storage Pool, select a storage pool from the list, and then click Go. 10. Click Next. 11. Refer to SAP Landscape Management online help and follow step (5), Consistency. Select one of the following options: Online: Backup/Suspend IO Mode to create an online clone Also type 600 in the Timeout [seconds] field to avoid timeout issues. Offline to create an offline clone 12. Click Next. 13. Refer to SAP Landscape Management online help and follow System Cloning steps (6) Isolation and (7) Summary. Creating a clone from a snapshot 57

58 SAP Landscape Management-ESI Integration: Provisioning operations and processes Using the SAP Landscape Management System Destroy process The System Destroy process, as shown in the following figure, destroys all of the volumes that were automatically created at the storage level during a previous System Clone or System Copy process: Procedure 1. Confirm that the SAP System that you want to destroy is unprepared. 2. Click Provisioning. 3. Select a cloned system from the list of systems. The SAP instances file systems of an SAP clone must be unprepared before the System Destroy process can take place. 4. Click Destroy System. 5. Select all volumes to be deleted, and then click Next. Figure 36 Destroying a cloned system The SAP Landscape Management System Destroy process destroys all the volumes that were automatically created in the storage level during the system clone or copy processes. Using the SAP Landscape Management System Destroy process for partially provisioned systems If a previous SAP Landscape Management system Clone/Copy process fails, SAP Landscape Management enables the System Destroy option on partially provisioned 58 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter User Guide

59 SAP Landscape Management-ESI Integration: Provisioning operations and processes systems. This process runs a Mass Unprepare operation before the storage volumes created during the provisioning process are deleted. The operation also removes the target SAP systems from SAP LaMa Infrastructure > Configuration > Hosts if they were created during the provisioning process. Procedure 1. Click Provisioning. 2. Select a cloned system from the list of systems. 3. Click Destroy System > Destroy Partially Provisioned System. 4. Select all volumes to be deleted, and then click Next until finished, as shown in the following figure. Figure 37 Destroying a partially provisioned system Using the SAP Landscape Management System Destroy process for partially provisioned systems 59