Enterprise Storage Integrator for SAP Landscape Management Storage Adapter

Transcription

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

2 Copyright Dell Inc. or its subsidiaries. All rights reserved. Published January 2018 Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS-IS. DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA. Dell EMC Hopkinton, Massachusetts In North America Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

3 CONTENTS Preface 5 Purpose...6 Audience... 6 Scope... 6 Related documentation... 6 Conventions used in this document... 6 Where to get help...7 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 Setting properties for vsphere environments...20 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 Enabling the VMware tools installation option for the virtual machine Verifying the VMware Tools installation...24 Verifying the SG utility and library package files installation Virtual host configuration script Configuring VMware virtual machines Commands for managing the vcenter server...27 Chapter 4 Installing ESI for SAP Landscape Management 29 Choosing to install the Windows EHAC server...30 Downloading ESI for SAP LaMa...30 Installing the ESI for SAP LaMa storage adapter Chapter 5 SAP LaMa-ESI Integration: System Provisioning Operations and Processes 33 Adding an ESI storage manager...34 Caching storage information from SAP systems...34 Removing SAP systems from a host...36 Mounting SAP systems to a host...37 Relocating the SAP system Accelerating relocation operations in vsphere virtual environments.. 41 SAP LaMa system provisioning prerequisites Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide 3

4 CONTENTS Managing snapshots...44 Creating a snapshot...44 Verifying Oracle redo logs...45 Creating an online snapshot...46 Viewing snapshots Removing a snapshot...49 SAP LaMa System Provisioning Processes: System Clone, Copy, and Refresh Configuring SAP target servers...51 Managing SAP LaMa system provisioning processes with full clones Creating a clone...52 Creating a clone from a snapshot Destroying volumes Destroying partially provisioned systems...55 Chapter 6 Troubleshooting 57 Troubleshooting Known limitations and problems Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 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 document 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. To ensure that you are using the latest version of this document and the release notes, go to Dell EMC Online Support. Preface 5

6 Preface 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 (SAP LaMa) user who wants to manage shared file or block storage by using ESI for SAP LaMa. This user guide is intended to provide an overview of ESI for SAP LaMa and its use in the SAP LaMa 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 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 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). 6 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

7 Preface Table 1 Typographical conventions (continued) Italic Monospace 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 Your comments You can obtain Dell EMC support, product, and licensing information 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 Dell EMC Technical Support. To open a service request, you 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 help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to: Send your comments about this document to Feedback. Where to get help 7

8 Preface 8 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 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 ESI for SAP LaMa is a software adapter that integrates Dell EMC storage with SAP LaMa. Administrators can use SAP LaMa to manage SAP system copies for nonproduction testing and development, using the SAP Clone, Copy, Refresh, and Relocate functions. Because SAP environments can have hundreds of testing and development systems, automating management of SAP system copies by using trusted storage-based cloning, saves significant time and effort, reducing the Total Cost of Ownership (TCO) of an SAP Landscape. ESI for SAP LaMa has the following components: ESI for SAP LaMa storage adapter, which is deployed as a storage manager in SAP LaMa 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 LaMa 5.0 includes support for SAP instance file systems based on block, file, or both block and file, combined on the same SAP system that is monitored by SAP Landscape Management 3.0. The SAP installation requires that the SAP NetWeaver /sapmnt/sid and /usr/sap/trans global file systems are based on Network File System (NFS) file systems. This requirement is necessary because the file systems must be shared across all the instances of an SAP system that is configured in a distributed or highavailability architecture. On SAP HANA scale-out systems, the /hana/shared/sid file system must be based on NFS and shared across all of the HANA nodes. ESI for SAP LaMa also supports physical and virtual hosts on: Dell EMC 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 for SAP LaMa storage adapter is distributed as a Java Enterprise Archive (EAR) file that complies with SAP LaMa specifications. The storage adapter, which is shown in the following figure, runs in the SAP NetWeaver Java Stack with the SAP LaMa add-on installed. You can use EHAC to manage one or more Dell EMC file and block storage systems. The Java ESI storage adapter (or ESI storage plug-in) for SAP LaMa communicates 10 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

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

12 Enterprise Storage Integrator for SAP Landscape Management Overview Table 2 Installation overview (continued) Running provisioning operations and processes for SAP systems Troubleshooting 6 12 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 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 Setting properties for vsphere environments Prerequisites 13

14 Prerequisites Solution prerequisites Before you install the Enterprise HLS Administration Console (EHAC) and the ESI for SAP LaMa storage 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, as described in the Enterprise Storage Integrator for SAP Landscape Management Administrator Guide. The document is available from Dell EMC Online Support. You must already have login credentials. If you do not, register at Dell EMC Online Support. 2. Install and configure SAP LaMa 3.0 as described in the SAP LaMa 3.0, Enterprise Edition Support Package 4 in the SAP Help Portal page. The following table lists the required SAP NetWeaver Java Stack and SAP LaMa minimum software versions for the installation. Software Minimum software version Installed on SAP NetWeaver Java Stack a 7.5 SP04 or later SAP LaMa server SAP LaMa b 3.0, SP04 SP2 (This resolution is for the end-user computer running the web browser that connects to the SAP LaMa GUI.) SAP LaMa server 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. 3. Install Dell EMC Solutions Enabler 8.3 on the SAP hosts with block-based file systems to be managed by SAP LaMa 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 that SAP LaMa 3.0 will manage. 14 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

15 Prerequisites Table 3 Prerequisite software Software Minimum software version Installed on Solutions Enabler a All SAP hosts with blockbased file systems SAP Host Agent b 7.21 with the latest patch All SAP hosts SAP Adaptive Extensions 1.0 All SAP hosts Browser Internet Explorer 11 (you can use other browsers, also) User desktop with a minimal display resolution of 1280x1024 a. Download Solutions Enabler from the Dell EMC Online Support Downloads for Solutions Enabler page. b. 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 LaMa configuration steps before you configure the infrastructure and the storage managers. 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 steps that are described in Configuring SAP Host Agent on the SAP Help Portal. 8. When working with SAP LaMa and ESI storage-based cloning, the SAP instance file systems are cloned for using ESI cloning technologies at the storage level. For that reason, verify that the SAP instance-specific file systems of your SAP systems are configured as follows: The SAP instance file systems (\usr\sap\sid, oracle\sid\sapdata1, oracle\sid\sapdata2, for example) must be stored in dedicated LUNs/ datastores that are separated from the operating system (OS) disk of the source hosts. Solution prerequisites 15

16 Prerequisites Do one of the following: Install and configure the OS, SAP Host Agent, SAP Adaptive Extensions, and Solutions Enabler for the existing physical and virtual target servers in advance. Deploy new target hosts from VMware vsphere pre-configured templates containing the OS, SAP Host Agent, SAP Adaptive Extensions, and Solutions Enabler installed and configured. For vsphere virtual machines, the OS disk must be in a dedicated VMware virtual machine disk (VMDK) and stored in a shared datastore. For physical systems, the OS must use local disks or dedicated LUNs that will not be cloned by ESI for SAP LaMa. The SAP instance file systems must have dedicated LUNs/datastores separated from the OS LUN/datastore. This requirement enables SAP LaMa to clone LUNs, with or without datastores at the storage level, that contain only the SAP instance-specific file system mount points. It avoids duplication of the OS file systems from the source system. See Adaptive Computing Concept, also called Adaptive Design, 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 LaMa System Relocation operation, ensure that the SAP source system instances are installed and configured according to the SAP Adaptive Computing concept, also known as SAP Adaptive Design or SAP Application Virtualization. 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. To facilitate SAP, VMware, and Dell EMC support in a VMware environment, use the following troubleshooting best practices: For a specified SAP system, document the vsphere virtual machines that it uses and document which SAP instance file systems are stored in which datastores. Document the SAP, VMware, and Dell EMC environments for each virtual machine in detail. 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. Also, include the guest OS device IDs, volume groups, logical volumes, and file systems used for each datastore. Use Dell EMC Virtual Storage Integrator (VSI), which is a free product, to collect most of this 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: Table 4 Prerequisite software for vsphere virtual servers Software Software version VMware vcenter Server 5.5 U3b, 6.0U3, or Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

17 Prerequisites Table 4 Prerequisite software for vsphere virtual servers (continued) Software VMware Tools Software version Use the version that is bundled with the ESXi server. This software is preinstalled on a newer OS, such as SLES 12 and RHEL 7.2. When using virtual hosts: Multiple paravirtual SCSI (PVSCSI) controllers are supported, which conforms to SAP and VMware best practices. See Configuring disks to use VMware Paravirtual SCSI (PVSCSI) adapters ( ) in the VMware Knowledge Base. If you use VMware vsphere in a Linux OS, see SAP note : VMware vsphere configuration guidelines on the SAP ONE Support Launchpad. If you use VMware vsphere in a Windows environment, see SAP note : VMware vsphere configuration guideline on the SAP ONE Support Launchpad. Configure the VMware Virtual Machine Advanced Parameter disk.enableuuid using the vsphere Web Client. For more details, see Installing and Configuring VMware Virtual Hosts on page 21. Plan for downtime to add the advanced disk.enableuuid parameter to all SAP systems based on vsphere virtual machines. To install VMware Tools, refer to Installing and Configuring VMware Virtual Hosts on page 21. Configure the Virtual Hosts 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 LaMa 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 LaMa. Figure 2 Managing Windows disks For more information about the design of the source SAP system, which follows the SAP recommendations for storage-based cloning, see SAP LVM Best Practices for System Provisioning in the SAP Community page. For additional requirements for Windows network-attached storage (NAS) environments, see Landscape Preparation in the SAP Help Portal. Install Solutions Enabler 8.3 on the SAP hosts running SAP systems to be managed by SAP LaMa 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 Configuring SAP Host Agent in the SAP Help Portal. After you install and configure Solutions Enabler 8.4 and SAP Host Agent 7.21, integrate the Enterprise Storage Library for SAP Adapter (ELSA), which is deployed inside Solutions Enabler, with the SAP Host Agent: 18 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

19 Prerequisites 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: 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. SAP recommends the following services for the Oracle client: 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 from SAP LaMa Configuration > Systems > Instance > Network isolation to enable Solutions Enabler to communicate with the ESXi physical HBA. This step is for collecting properties for the SAP LaMa storage-based system System Clone, System Copy, and System Refresh provisioning processes. For more information, see 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 an AIX OS, configure all SAP file systems to use INLINE logging, which is a requirement for Solutions Enabler and Storage Resource Manager (SRM) operations. View the contents of the/etc/filesystems file, which shows Log = INLINE for each mount point if the file system is configured to use INLINE logging. If any SAP file systems are not configured to use INLINE logging, move the contents of each file to a new file system that is configured to use INLINE logging. Converting a file system from using outline logging to inline logging corrupts its data. See IBM note Conversion Between Inline and Outline JFS2 Filesystem Logs to verify this statement. Prerequisites for cloning SAP instances in an AIX OS 19

20 Prerequisites The logname attribute must use the INLINE value to create a file system that uses INLINE logging. For recommended commands and procedures to create a file system in an AIX OS, see the AIX documentation. For more information about using the crfs command, see the crfs Command in the IBM Knowledge Center. Setting properties for vsphere environments In SAP systems that use vsphere HA with VMware vsphere vmotion and Dell EMC storage arrays, all datastores that are used by SAP source systems must be visible or masked to all ESXi hosts that are in the vsphere cluster. Procedure 1. Create masking views for the individual servers with storage groups that contain only the dedicated devices that the individual servers need. 2. 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 host that were created in the first step. For a description of cascaded initiator groups, refer to the EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide. 3. Optionally, set configuration properties to avoid steps to add or remove volumes from a masking view at the storage level during virtual-to-virtual relocation operations. These settings save time during the virtual-to-virtual relocation operation. 20 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 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 Enabling the VMware tools installation option for the virtual machine...24 Virtual host configuration script...26 Configuring VMware virtual machines...26 Commands for managing the vcenter server 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 force a VMDK respond to a SCSI inquiry from the guest OS to read the Vital Product Data (VPD) page. When a VMDK is created in a VMware ESXi virtual machine, it is stored in a datastore, which is a storage LUN formatted with a virtual machine file system (VMFS). A unique UUID is generated for each VMDK and kept in the virtual disk configuration file and virtual machine configuration (.vmx) file. VPD is a collection of configuration data that is 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 does not respond to a SCSI inquiry from the guest OS to read the VPD that is associated with the virtual disk. However, Solutions Enabler requires the VPD information that is associated with the VMDK. Procedure 1. Add the disk.enableuuid advanced parameter set to TRUE in the virtual machine (.vmx) configuration file. 2. 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 5.0 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 Configuring the VMDK so that it can respond to a SCSI inquiry 23

24 Installing and Configuring VMware Virtual Hosts 6. Click OK to save the new configuration parameters and then power on the virtual machine. Figure 5 Adding a new row 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 How to install VMware Tools ( ) 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, see VMware support for Open VM Tools ( ) in the VMware Knowledge Base. Verifying the VMware Tools installation 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. In the General pane, as shown in the following figure, check that VMware Tools is running. 24 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

25 Installing and Configuring VMware Virtual Hosts This figure shows the status of VMware Tools installed on an older operating system. The page is different for virtual machines with newer guest operating systems that use OVT. Figure 6 Checking that VMware Tools is running Verifying the SG utility and library package files installation Verify that the Linux SG utility and library package files are installed on the SAP host. Procedure 1. Log in as root to the guest OS of the SAP virtual machine. 2. Type the rpm -qa grep sg3* command. The SG utility and library package files are installed on the host if the sg3 utils and sg3 utils-libs files are displayed. 3. If the files are not installed, do one of the following: Mount the ISO of the Linux OS installer. 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 the SG utility and library package files installation 25

26 Installing and Configuring VMware Virtual Hosts Virtual host configuration script The ConfigureVirtualHost_v2 script registers the virtual host inside the Solutions Enabler SYMAPI database. The script does the following: Adds a vcenter entry to the Solutions Enabler SYMAPI database Deletes the vcenter entry that was previously added to the Solutions Enabler SYMAPI database Lists entries of the Solutions Enabler SYMAPI database Solutions Enabler uses vcenter host connection information to gain access to the storage array data. The script automatically performs the following operations: Updates the Solutions Enabler SYMAPI database with the vcenter IP address, username, and password by running the following command: symcfg auth add -vmware -host <IP_Address> -username <UserName> -password <Password> -vmport 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 for use by Solutions Enabler. Copies the virtual machine certificate to the following location: /var/symapi/config/viclient_cert.pem Runs the discover command for Solutions Enabler to connect to the ESXi server and gets 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) Configuring VMware virtual machines Download and run the ConfigureVirtualHost_v2 script to configure the virtual machine. Before you begin Solutions Enabler must be installed and configured. Procedure 1. Download the Configure_VirtualHost_v2.sh script from the Dell EMC Online Support Storage Integrator for SAP Landscape 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 26 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

27 Installing and Configuring VMware Virtual Hosts 3. Collect the vcenter IP address, hostname, and login credentials of the dedicated ESI for SAP LaMa user with admin rights to the vsphere cluster of which the SAP virtual machine is part. 4. Enable the Secure Shell (SSH) on the ESXi server on which the virtual machine resides. 5. Run the script:./configure_virtualhost_v2.sh 6. Type the v option to add the vcenter server IP and credentials to register vcenter in the Solutions Enabler database. 7. After you add vcenter, type the l option to list the vcenter details. If vsphere HA restarts the virtual machine or if vmotion moves it to another ESXi server, the Solutions Enabler SYMAPI database can still communicate as long as vmotion is in the same vcenter domain. When the ESXi server on which the virtual machine is running changes, the HBA information that is retrieved by Solutions Enabler also changes. If necessary, perform these steps: a. In SAP LaMa, go to Configuration > Hosts > Select Host > Edit > Host Properties. b. Click Retrieve from Host in Host-Specific Storage Properties to update the HBA information inside SAP LaMa. 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 LaMa GUI. 8. 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 LaMa on vcenter and when you go to Monitoring > Tasks in the SAP LaMa GUI. Commands for managing the vcenter server Optionally, you can use the following commands to manage the vcenter server: To check which vcenter server is configured: symcfg auth list -vmware To manually remove a vcenter server that is no longer running, but has an entry from the virtual machine Solutions Enabler SYMAPI database: symcfg auth delete -host <IP Address> -user -namspace vmware/vc Commands for managing the vcenter server 27

28 Installing and Configuring VMware Virtual Hosts To manually add a vcenter server entry on the Solutions Enabler 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 for SAP LaMa. 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 5.0 User Guide

29 CHAPTER 4 Installing ESI for SAP Landscape Management This chapter presents the following topic: Choosing to install the Windows EHAC server Downloading ESI for SAP LaMa Installing the ESI for SAP LaMa storage adapter...30 Installing ESI for SAP Landscape Management 29

30 Installing ESI for SAP Landscape Management Choosing to install the Windows EHAC server If you choose to install the Windows-EHAC server, you must install the ESI Web Service and ESI Deployment Console. Because the ESI Web Service and ESI Deployment Console are installed and configured on the Linux-based EHAC virtual appliance, you only download them when you install the Windows-EHAC server. Deploy the Linux-based EHAC virtual appliance as described in the Enterprise Storage Integrator for SAP Landscape Management Administrator Guide, and then deploy the ESI for SAP LaMa storage adapter. Downloading ESI for SAP LaMa ESI for SAP LaMa is distributed as a Java EAR file and can be downloaded from Dell EMC Online Support. You can download and use the ESI for SAP LaMa storage adapter and EHAC separately. This might be necessary if the user is not also the storage administrator. Procedure 1. Go to the Downloads for Storage Integrator for SAP Landscape Management page. 2. Click Downloads to download the Storage Integrator for plug-in. Installing the ESI for SAP LaMa storage adapter Install the ESI for SAP LaMa storage adapter on the SAP NetWeaver Java stack server where SAP LaMa is running. The ESI for SAP LaMa storage adapter must be deployed inside the SAP NetWeaver Java Stack server where the SAP LaMa add-on is running. Before you begin SAP NetWeaver administrator privileges are required to run this step. Run the Telnet commands locally on the SAP LaMa server. Do not run the commands remotely. Procedure 1. Copy the esi_sap_lvm_plugin.5.0.x.ear file to the server by using a tool such as FileZilla or WinSCP. 2. Log in to SAP Java Stack using the Telnet localhost administrator password, as shown in the following figure. 30 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

31 Installing ESI for SAP Landscape Management Figure 7 Logging in to SAP Java Stack 3. Run the following command to determine if the adapter is already installed: list_app grep plugin 4. Undeploy any older versions of the adapter by using the following command: undeploy name=esi_sap_lvm_plugin vendor=javaee 5. Deploy the ESI for SAP LaMa storage adapter. For example: deploy /Binaries/esi_sap_lvm_plugin.5.0.ear version_rule=all 6. Confirm that the ESI for SAP LaMa storage adapter was deployed, as shown in the following figure. Figure 8 Adapter is deployed Installing the ESI for SAP LaMa storage adapter 31

32 Installing ESI for SAP Landscape Management 32 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

33 CHAPTER 5 SAP LaMa-ESI Integration: System Provisioning Operations and Processes This chapter presents the following topics: Adding an ESI storage manager...34 Caching storage information from SAP systems Removing SAP systems from a host Mounting SAP systems to a host Relocating the SAP system...40 SAP LaMa system provisioning prerequisites Managing snapshots SAP LaMa System Provisioning Processes: System Clone, Copy, and Refresh...50 Destroying volumes...55 Destroying partially provisioned systems SAP LaMa-ESI Integration: System Provisioning Operations and Processes 33

34 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Adding an ESI storage manager SAP LaMa needs a storage manager to communicate with the underlying physical storage arrays where the SAP instance file systems are stored. 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 LaMa support for the system provisioning processes such as System Clone, System Copy, and System Refresh. Procedure 1. Open the SAP Landscape Management GUI web page. 2. Type your username and password, and then click Log On. 3. Select Infrastructure > Storage Managers and click Add. 4. In the list of supported storage manager types, select Dell EMCCorp ESI for SAP NW LaMa and click Next. 5. Type the Basic Properties for the storage manager, as shown in the following figure. a. In Label, type a name that identifies this storage manager. b. Type the username and password of a registered EHAC user. The Enterprise Storage Integrator for SAP Landscape Management Administrator Guide provides details. Only the storage arrays added by this user will be visible to the adapter on the SAP LaMa server. c. In URL, type the IP address and port number of the EHAC server. d. In Monitoring Interval (Seconds), add the monitoring interval for storage caching while configuring the adapter in SAP LaMa To test the configuration before adding it, click Test Configuration on the bottom of the page. 7. After you receive confirmation that the configuration is correct, click Next. 8. Click Save. The storage manager is installed and a list of storage systems assigned to 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 list of supported storage shows the added storage manager as ESI version 5.0.x and the ELSA as version 8.4 or later. Caching storage information from SAP systems With SAP LaMa 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. uses the cached information during the system provisioning processes, such as the: System Clone, System Copy, and System Refresh processes 34 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

35 SAP LaMa-ESI Integration: System Provisioning Operations and Processes 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 9 Storage caching for VNX and VMAX block storage arrays The following figure shows storage caching for XtremIO and VNX file storage arrays. Figure 10 Storage caching for XtremIO and VNX file storage arrays The following figure shows storage caching for volume groups on a host. During cloning, the volume group information about the SAP hosts is retrieved and populated in the Storage tab. Caching storage information from SAP systems 35

36 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Figure 11 Storage caching for volume groups on a host Removing SAP systems from a host Use the Mass Unprepare operation to remove SAP systems from a specified host. The operation stops the running SAP system, and unmounts and detaches the SAP instance file systems and volumes from the OS and the host. Use this operation when you want to run OS maintenance or hardware upgrades on hosts, where you can prepare the system again 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 LaMa System Relocation operation to prepare to another host. Procedure 1. Click Infrastructure > Storage Managers to ensure that Storage Manager was added. 2. Click Operations > Storage to confirm that all volumes and volume group information are cached. 3. If all volumes and volume group information are not cached, click Monitoring Data to cache the information. 4. Click Operations > Hosts to check that all source hosts are in a correct state, with hosts assigned to their respective instances. 5. Ensure that storage caching has been updated in Storage > Storage Overview and that the NFS export files for this operation are listed; otherwise the operation fails. 6. Select Operations > Systems > Mass Operations, then select the files for the Unprepare operation, and then click Execute, as shown in the following figure. The operation fails 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. For example, a user, who is logged in to the host thorough SSH, in one of the directories that belongs to the mount point being unmounted, can cause the Unprepare operation to fail. 36 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

37 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Figure 12 Selecting files and starting the Mass Unprepare operation 7. Click Monitoring > Logs, select a log, and view its details in the Details window. Logs show the details and status of the operation and show details of all activities performed by each component in each operation step. Mounting SAP systems to a host Use the Mass Prepare operation to mount the SAP instance-specific file systems to a new target host during the Prepare steps of the System Relocation operation, and during the System Clone, System Copy, and System Refresh processes. Before you begin All source systems must be in an unprepared state without any mounted volumes. In a VMware environment, before you can use Prepare, Unprepare, Relocation, or Clone, you must add all of the SAP source and target ESXi hosts to the EHAC database by using the EHAC configuration console. For more information, see the Enterprise Storage Integrator for SAP Landscape Management Administrator Guide. Procedure 1. Click Infrastructure > Storage Managers, and then perform the following steps: a. Confirm that the storage manager was added with the correct EHAC user credentials. b. Test the storage manager connection and retrieve all arrays associated with the EHAC user. c. 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. Mounting SAP systems to a host 37

38 SAP LaMa-ESI Integration: System Provisioning Operations and Processes 2. Click Advanced Operations > Storage. If the storage information is not cached, click Monitoring Data to cache the information. 3. Click Advanced Operations > Hosts and verify that all source hosts are in a correct state, with no hosts assigned to their respective instances, as shown in the following figure. Figure 13 Checking that hosts are in a correct state 4. Click Advanced Operations > Systems > Mass Operations and perform on of the following steps: Click Auto Assign Manually select the host from the available hosts, as shown in the following figure. 5. Select the instances and click Execute. Figure 14 Selecting a host during a Mass Prepare operation 38 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

39 SAP LaMa-ESI Integration: System Provisioning Operations and Processes During the Prepare operation on VMware environments, ESI performs the following steps for the SAP system instance-specific storage volumes: Adds storage volumes to their respective storage groups on the storage array Rescans, discovers, attaches and mounts datastores to the ESXi host Adds VMDKs that are associated with the datastores to the virtual machine SAP LaMa 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 ELSA (libsapacosprep_emc.so) that is part of Solutions Enabler software. The SAP instances are then started in order. Detailed ESI for SAP LaMa logs that confirm the results of the operation are generated in the configured {WILDFLY_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. Mounting SAP systems to a host 39

40 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Figure 15 Viewing log details after the Mass Prepare operation Relocating the SAP system The SAP System Relocation operation enables the SAP system to be moved from an existing host to another host, which is previously discovered and configured on SAP LaMa. Before you begin If you are relocating an SAP instance of an SAP system, the SAP system must be installed as Adaptive Enabled. ESI for SAP LaMa supports all relocation options: 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 configuration console to get access. 40 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

41 SAP LaMa-ESI Integration: System Provisioning Operations and Processes 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 16 Performing a System Relocation WARNING 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 LaMa. Changes are reflected in SAP LaMa only if the SAP LaMa administrator clicks Retrieve Mount List for the relocated system at Configuration > System > Select the instance > Edit > Mount Points. Accelerating relocation operations in vsphere virtual environments For VMware cluster-based virtual environments, ESI for SAP LaMa Version 5.0 includes configuration properties that the storage administrator sets on the EHAC server before you perform ESI for SAP LaMa system relocation operations to provide easy and efficient relocation of SAP systems from source hosts to target virtual hosts. These configuration properties save time during virtual-to-virtual relocation operations by avoiding the storage layer operations of unmasking and masking LUNs to ESXi hosts. ESI for SAP LaMa supports System Relocation, Unprepare, and Prepare operations on vsphere cluster environments without these configuration properties. However, to Accelerating relocation operations in vsphere virtual environments 41

42 SAP LaMa-ESI Integration: System Provisioning Operations and Processes complete these operations in considerably less time, add the following configuration properties to ESI_application.properties, which is available in the WildFly Home directory: UnprepareWithNoVolumes=True PrepareWithNoVolumes=True Use these configuration properties only during a Mass Unprepare, Prepare, or virtualto-virtual (V2V) System Relocation operation in a vsphere cluster-based environment. NOTICE For all other operations, such as System Clone, System Copy, System Destroy, and System Refresh, use the default values for the configuration properties: UnprepareWithNoVolumes=False PrepareWithNoVolumes=False SAP LaMa 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 LaMa 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 and 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. The storage pool must have available space that is at least equal to the size of the source volumes. 4. Run all the SAP LaMa configure hosts steps: Install the SAP Host Agent on all SAP source and target virtual machines and install Solutions Enabler. Create a symbolic link in the SAP Host Agent directory pointing to ELSA. For Linux environments, run the following command: ln -s /opt/emc/symcli/shlib/apps/sap/libsapacosprep_emc.so libsapacosprep_emc.so For AIX environments, run the following command: ln -s /opt/emc/symcli/shlib/apps/sap/libsapacosprep_emc.o libsapacosprep_emc.o 42 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

43 SAP LaMa-ESI Integration: System Provisioning Operations and Processes For Windows environments, refer to Prerequisites for cloning SAP instances in a Windows OS on page Verify and configure all of the SAP LaMa 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 LaMa Infrastructure menu tabs, especially the Network, User Management, Name Management, and Storage Managers configuration. See SAP LaMa Infrastructure Configuration instructions on the SAP Landscape Management 3.0, Enterprise Edition page in the SAP Help Portal, and then go to Configuration and Deployment Information > Landscape Configuration > Managing System Landscapes > Provisioning Systems. 7. Configure the SAP LaMa 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 ESXi 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 a Solutions Enabler configuration issue. Review the previous configuration steps in Installing and Configuring VMware Virtual Hosts on page Configure the Systems tab in the SAP LaMa Configuration menu to discover and add the SAP instances to be managed by SAP LaMa: a. Configure all the SAP settings to allow System Clone, System Copy, System Rename, and System Refresh processes. See SAP LaMa mount points instructions on the SAP Landscape Management 3.0, Enterprise Edition page in the SAP Help Portal. b. 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 LaMa source and target systems. In addition to VMware, this can also be configured with other environments, such as baremetal or IBM AIX logical partition. c. Configure the mount points for each of the instances associated with a source system. 9. In the SAP LaMa 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. SAP LaMa system provisioning prerequisites 43

44 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Managing 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 specified 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 LaMa, 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. 44 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

45 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Figure 17 Creating a snapshot Verifying Oracle redo logs 5. 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. Before creating an online snapshot, verify that the Oracle redo logs are configured and actively generating new online redo logs. The following procedure uses an Oracle database example. Procedure 1. Click Configuration > Systems > System Details > Edit, as shown in the following figure. Verifying Oracle redo logs 45

46 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Figure 18 Checking configuration details for a snapshot 2. If the basic configuration is complete, click Provisioning & RFC to perform SAP LaMa 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 19 Reviewing the basic configuration and provisioning and RFC details Creating an online 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. Before you begin Ensure that you verified the Oracle redo logs. 46 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

47 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Procedure 1. Click Provisioning, and then click Manage System Snapshots > Take System Snapshots, as shown in the following figure. Figure 20 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 21 Selecting data for a snapshot 3. Click Provisioning > System and AS > Consistency, select the default Online Backup, type the Timeout [seconds] value, and click Next, as shown in the following figure. Creating an online snapshot 47

48 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Figure 22 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 23 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. 48 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

49 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Figure 24 Viewing snapshot log details Viewing snapshots When you view snapshots in the SAP LaMa GUI, you only see the storage snapshots created from the SAP LaMa Provisioning Manage Snapshots functionality, not any other snapshots created at the storage-array 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 pane, as shown in the following figure. Figure 25 Viewing snapshots Removing a snapshot Remove a snapshot. Viewing snapshots 49

50 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Procedure 1. Click Provisioning > Manage System Snapshots. 2. In the Manage Snapshots of System pane, select a snapshot from the list. 3. Click Remove Snapshot, and then click Remove Snapshot again to confirm your action, as shown in the following figure. Do not delete snapshots in Unisphere that were created in SAP LaMa through ESI for SAP LaMa because doing so causes data errors. Figure 26 Removing a snapshot SAP LaMa System Provisioning Processes: System Clone, Copy, and Refresh You can create system clones either from a snapshot directly from a live system, or by using an existing SAP LaMa 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. VMAX3 Dell EMC TimeFinder SnapVX snapshots and clones 50 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

51 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Table 5 Storage systems and storage replication options (continued) Storage system Storage replication options SAN VNX SAN copy full clone VNX Snapshot Enabler snapshot or new snapshot Full clone from VNX Snapshot Enabler snapshot Dell EMC Vblock Systems 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 layer replication techniques are 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 LaMa system provisioning prerequisites on page 42. 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. Confirm with the storage administrator that storage views are created for the target servers before you start SAP LaMa system provisioning processes. The ESI for SAP LaMa storage adapter can expose storage volumes to SAP LaMa 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. Configuring SAP target servers 51

52 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Managing SAP LaMa 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. For information about the limitations of full cloning, refer to Known limitations and problems on page 59. When you perform a system clone, the target system is network-isolated by the settings configured in SAP LaMa 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. See the SAP LaMa online help and follow the first three System Cloning steps: (1) Basic; (2) Hosts; and (3) Host Names. 5. Click Next when you are finished. 6. In Storage, select the Full Copy checkbox for all storage volumes for a full clone, as shown in the following figure. For snap clones, clear the checkbox for all storage volumes. 52 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

53 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Figure 27 Creating a Full Copy for all storage volumes 7. From the Storage Pool field, select a storage pool from the list and close 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. See the SAP LaMa online help and follow step (5) Consistency. Select one of the following options: Online: Backup/Suspend IO Mode to create an online clone Type 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. See SAP LaMa 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. Creating a clone 53

54 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Creating a clone from a snapshot You can clone from snapshots on VNX systems. you cannot clone from snapshots 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. See thesap LaMat online help and follow the first three System Cloning steps: (1) Basic; (2) Hosts; and (3) Host Names. 5. Click Next when you are finished. 6. In the Storage step, select the Full Copy checkbox for all storage volumes. 7. Select Clone from System Snapshot and select the previous snapshot created, as shown in the following figure. Figure 28 Selecting a snapshot 8. Select a snapshot from the Clone from system snapshot list. 9. From Storage Pool, select a storage pool from the list, and then click Go. 10. Click Next. 11. See the SAP LaMa online help and follow step (5), Consistency. Select one of the following options: Online: Backup/Suspend IO Mode to create an online clone Type 600 in the Timeout [seconds] field to avoid timeout issues. Offline to create an offline clone 12. Click Next. 13. See the SAP LaMa online help and follow System Cloning steps (6) Isolation and (7) Summary. 54 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide

55 SAP LaMa-ESI Integration: System Provisioning Operations and Processes Destroying volumes 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 29 Destroying a cloned system The SAP LaMa System Destroy process destroys all the volumes that were automatically created in the storage level during the System Cone or Copy processes. Destroying partially provisioned systems If a previous SAP LaMa System Clone or Copy process fails after the cloning volumes procedure, SAP LaMa enables the System Destroy option on partially provisioned systems. This process runs a Mass Unprepare operation before the storage volumes created during the provisioning process are deleted. The operation also removes the Destroying volumes 55

56 SAP LaMa-ESI Integration: System Provisioning Operations and Processes 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 30 Destroying a partially provisioned system 56 Enterprise Storage Integrator for SAP Landscape Management Storage Adapter 5.0 User Guide