SAP NETWEAVER LANDSCAPE VIRTUALIZATION MANAGEMENT SOFTWARE INTEGRATION WITH EMC

Transcription

1 White Paper SAP NETWEAVER LANDSCAPE VIRTUALIZATION MANAGEMENT SOFTWARE INTEGRATION WITH EMC Abstract This paper provides an introduction to the EMC integration with SAP Landscape Virtualization Management (LVM) for customers that are not familiar with the EMC products (EMC Storage Integrator (ESI) for SAP LVM, EMC HLS Administration Console (EHAC), EMC Solutions Enabler and EMC SMI-S Provider. The SAP NetWeaver Landscape Virtualization Management product provides the SAP application virtualization feature and the ability to automate end-to-end the SAP system copy process. June 2013

2 Copyright 2013 EMC Corporation. All Rights Reserved. EMC 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. EMC Corporation 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 EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other trademarks used herein are the property of their respective owners. Part Number H

3 Table of Contents Executive Summary Objective... 5 Audience... 5 SAP LVM Introduction Standard Edition... 7 Enterprise Edition... 7 EMC Integration with SAP LVM Overview... 9 EMC Storage Integrator (ESI) for SAP LVM EMC HLS Administration Console (EHAC) EMC SMI-S Provider EMC Solutions Enabler EMC SAP LVM Support Matrix Standard Edition Enterprise Edition EMC Software Installation and Preparation EMC Storage Integrator (ESI) for SAP LVM EMC HLS Administration Console (EHAC) EMC SMI-S Provider EMC Solutions Enabler Overview of SAP LVM Operations Standard Edition Enterprise Edition System Clone System Copy System Refresh Initial Setup and Configuration Setup SAP Host Control Agent and SAP Profile Parameters Retrieving SAP system mount points in SAP LVM Issuing operation functions for SAP systems and instances Advanced Configuration for Enterprise Edition Setup ESI for SAP LVM Storage Adapter Configuration Issuing clone and copy operations for SAP systems and instances Conclusion

4 4

5 Executive Summary (SAP NetWeaver LVM) is one of SAP s products in their virtualization and cloud strategy designed to take customers to the on-premise (private) cloud. SAP NETWEAVER LVM provides application virtualization and management of SAP systems through a single user interface. This powerful management tool simplifies and optimizes provisioning, deployment, and management of SAP Systems through the use of virtualization and Infrastructure as a Service (IaaS) cloud technology, providing the following benefits: Reduced TCO (Total Cost of Ownership) Increased flexibility and agility to respond to business demands SAP NetWeaver LVM s current features include: Framework for SAP system clone, copy, and refresh, including fully automated post-copy tasks Capacity management proposal-based dialog instance scaling End-to-end visibility, monitoring and management of SAP and non-sap applications in virtual infrastructures Overview dashboard with customization options Landscape visualization, from a high-level landscape view down to the infrastructure level Reporting options: on individual systems, and across landscapes Objective This focus of this document covers the integration between EMC and SAP to enable the use SAP NetWeaver LVM to execute SAP system clone, copy, and refresh processes, including the post-copy automation tasks. The post-copy automation (PCA) tasks are eligible to be executed with the SAP system copy and refresh processes only. Audience This white paper is intended for customers that are familiar with SAP NetWeaver Landscape Virtualization Management but not familiar with EMC s integration and product set to support that integration. It will document the EMC tasks required during the installation process to enable full support of our integration with SAP NetWeaver LVM. This paper is designed for the storage administrative team responsible for supporting the SAP team interested in SAP NetWeaver LVM. 5

6 SAP NetWeaver LVM Introduction SAP NetWeaver LVM provides a central point of control for flexibly assigning computing resources and managing application services in the system landscape. SAP NetWeaver LVM is built on four key principles: Unified Reduce the time and effort to transition to virtual and cloud environments by decoupling the application from the underlying infrastructure; by providing a unified view and management of the hardware, software, and virtualization layers; and by automating system relocation. Complete Improve your ability to respond to business needs with support for configuring, deploying, monitoring, and managing your SAP systems and landscapes in both physical and virtualized infrastructures, providing you more infrastructure options and faster time to value. Simplified Simplify the management of SAP landscapes by hiding the technical complexities of physical and virtualized infrastructures from day to day operations. Automated Reduce the capital investment and operational costs (TCO) of your SAP systems with capabilities including scheduling system operations in advance with a built-in task planner; and by leveraging virtualization to reduce your hardware requirements and improve resource utilization. Figure 1 provides a high level view of the features provided by SAP NetWeaver LVM. Figure 1: SAP NetWeaver LVM 1.0 key features 6

7 Feature availability is dependent on the SAP NetWeaver LVM license installed. There are two different licenses of SAP NetWeaver LVM, standard and enterprise. Figure 2 helps depict the progression from the standard edition to the enterprise edition: Figure 2: : SAP NetWeaver LVM standard edition versus enterprise edition Standard Edition The standard edition key features include: Intersystem dependency framework Single system and mass operations (for example, start, stop) Ability to relocate systems from one host to another Task planner Application server (un-)install Custom services, operations, and hooks For a deeper understanding of any of these features please contact SAP. Enterprise Edition The enterprise edition key features include: SAP system clone, copy, and refresh framework Automatic capacity management End-to-end monitoring of SAP systems and infrastructure 7

8 Visualization of the whole landscape Intersystem dependency framework Single system and mass operations (for example, start, stop) Ability to relocate systems from one host to another User configurable dashboards Reporting Task planner Application server (un-)install Custom services, operations, and hooks For more detailed information about the features of SAP NetWeaver LVM refer to or contact SAP. EMC Integration with SAP NetWeaver LVM This scope of this paper is to describe the EMC integration with SAP NetWeaver LVM software. This paper does not cover all of the available features in SAP NetWeaver Landscape Virtualization Management software. The features directly related to EMC s integration points (EMC Storage Integrator, EMC HLS Configuration Console, EMC SMI-S Provider, and EMC Solutions Enabler) are covered. Figure 3 is a big picture view of software with integration to various IT components. Figure 3: SAP NetWeaver LVM big picture 8

9 EMC Solutions Enabler, EMC Storage Integrator (ESI) for SAP NetWeaver LVM, EMC HLS Administration Console (EHAC), and EMC SMI-S Provider will integrate to the Storage Connect Attach/Detach module and the Storage Connect Clone module. VMware integration occurs in the Virtualization Connect module. EMC support for is a natural fit to EMC s strategy and direction on virtualization and cloud. EMC Integration to SAP NetWeaver LVM allows customers to maximize the value of their infrastructure while providing them with a path to virtualization and cloud technologies. Overview Figure 4 shows the SAP NetWeaver LVM design consisting of a management server, the SAP NetWeaver LVM Server itself, and managed systems, which are the SAP systems managed by SAP NetWeaver LVM server. The SAP NetWeaver LVM management server collects information from the managed servers using the SAP Host Agent software. There are two adapters available in SAP NetWeaver LVM; a virtualization adapter and a storage adapter. This paper will focus on the storage adapter. Figure 4: : SAP NetWeaver LVM overall architecture SAP Application Virtualization (Adaptive Computing) SAP provides what is called Application-based Virtualization, which decouples the SAP application and database from the underlying Operating system, differently from the hypervisor-based virtualization, offered by VMware for example, which decouples the Virtual Machine and its OS from the underlying server hardware. EMC s Integration with SAP NetWeaver LVM Figure 5 shows EMC s integration points depicted in black. These include the central storage adapter, the central storage management, and the storage library. EMC s central storage 9

10 adapter is called EMC Storage Integrator (ESI) for SAP NetWeaver LVM. The central storage management section will consist of EMC HLS Administration Console (EHAC) and EMC SMI-S Provider. The EMC SMI-S Provider is only required in SAN configurations. The EMC storage library is shipped with EMC Solutions Enabler, a widely used product by EMC customers. This is only required in SAN configurations to perform functions such as logical volume group import/export and mounts and unmount of the file systems. NAS configuration will not require these additional functions. Figure 5: : EMC s Integration with SAP NetWeaver LVM EMC Storage Integrator (ESI) for SAP NetWeaver LVM EMC Storage Integrator (ESI) for SAP NetWeaver LVM is an adapter for SAP NetWeaver Landscape Virtualization Management (LVM). ESI for SAP NetWeaver LVM has two main components, the SAP NW LVM adapter and a web service called the EMC HLS Administration Console (EHAC). ESI for SAP LVM is distributed as a Java Enterprise Archive (EAR) file that complies with SAP NetWeaver LVM specifications. The ESI for SAP LVM adapter runs in the LVM Java application server and integrates with EMC File and Block storage systems. EMC HLS Administration Console (EHAC) ESI for SAP LVM adapter includes an administration console that storage administrators can use to manage users, storage systems, ECOM servers and access control. HLS stands for High Level SMI-S. EHAC provides a single point of management used to create user accounts and assign storage systems to users. This is a gateway for the LVM adapter to access EMC file or block storage systems. With EHAC, administrators can manage storage space assigned to individual users by controlling read/write access to the storage pools for each storage system. Figure 6 demonstrates how the ESI for SAP LVM storage adapter and the EHAC console integrate with EMC storage. 10

11 Figure 6: : Overview of the ESI for SAP LVM and the EHAC integration with EMC storage EMC SMI-S S Provider EMC SMI-S (Storage Management Interface Specification) Provider supports the SNIA Storage Management Initiative (SMI), an ANSI standard for storage management. This initiative has developed a standard management interface that has culminated in a comprehensive specification. EMC SMI-S Provider is paired with the EMC CIM (Common Interface Module) Server to provide an SMI-compliant interface for EMC VMAX arrays, EMC CLARiiON arrays, and EMC VNX family storage systems. The SAP clone, copy, and refresh processes utilize EMC s integration with SMI-S, through the ESI for SAP LVM adapter. Multiple installations of EMC s SMI-S Provider are not required in a SAP NetWeaver LVM environment. One SMI-S Provider can manage up to 5 different EMC storage arrays. If more than 5 arrays are used, then an additional Provider will need to be installed. The EMC recommendations are: Install the SMI-S provider on the same server as the EHAC, provided this is a Linux or Windows server Do not install the SMI-S Provider on a SAP NW LVM managed servers because the required versions of EMC SMI-S Provider and EMC Solutions Enabler may be different The EMC SMI-S Provider package includes the installation of EMC Solutions Enabler. 11

12 EMC Solutions Enabler EMC Solutions Enabler host-based software provides an API-shared library and a special command set that comprises the Symmetrix Command Line Interface (SYMCLI) for use by storage administrators and systems engineers in SAN configurations. Solutions Enabler supports command-line entries and scripts to map and perform control operations on devices and data objects to manage your storage complex. Solutions Enabler releases are managed through a continuous lifecycle management process. SAP NetWeaver LVM programmatically manages storage for the SAP NetWeaver LVM graphical interface user. The SAP application virtualization is enhanced by two components provided by the SAP host agent package: The executable (sapacosprep), which stands for SAP Adaptive Computing Open Systems PREParation The SAP shared library (libsapacosprep) The EMC component is invoked by the EMC shared library (libsapacosprep_emc), which is packaged in EMC Solutions Enabler. The SAP executable, sapacosprep, supplements SAP NetWeaver LVM. It is invoked on behalf of SAP LVM GUI to control and establish the application virtualization layer, by attaching and detaching files systems and volume groups via the SAP and EMC shared libraries. EMC s Solutions Enabler software must be installed on every host in the SAP NetWeaver LVM SAN environment. It is not required on servers in a NAS environment. This includes any server, physical or virtual, that will have a SAP LVM managed SAP system or instance, and including potential servers to be used for storage based clones or copies. EMC SAP NetWeaver LVM Support Matrix EMC integration with SAP NetWeaver LVM will depend on the SAP LVM license purchased and the features that are planned on being used. There are currently two versions, Standard Edition and Enterprise Edition. Standard Edition The start, stop, and relocation features in the standard edition will require additional EMC integration in SAN configurations. NAS configurations are supported on EMC storage arrays without additional EMC integration. These SAP NetWeaver LVM features are the evolution from SAP Adaptive Computing Controller (SAP ACC) and will continue to be available in SAP Adaptive Computing. EMC holds numerous SAP ACC certificates of conformity and will continue to provide support for SAP ACC customer implementations. 12

13 For a better customer experience, additional enhancements were added to these features and are available in SAP NetWeaver LVM 1.0. EMC will support all of the operating systems and volume managers listed in the support matrix in Figure 7. Enterprise Edition In addition to the features supported in the standard edition, the enterprise edition SAP system clone, copy, and refresh features will require additional support from EMC for both SAN and NAS configurations. EMC will support all of the operating systems and volume managers listed in the support matrix in Figure 7. Support Matrix for EMC Solutions Enabler Figure 7 will show a quick glance support matrix but please refer to the full EMC Support Matrix referred to here. For the particular OS versions supported, please refer to the EMC Support Matrix by utilizing EMC s E-Lab Interoperability Navigator at Once you enter the E-Lab Interoperability Navigator, select the appropriate login option, that is, Customer and Partners: Login to E-Lab Interoperability Navigator through PowerLink. This will require a Powerlink ID. Figure 7: : EMC quick glance support matrix for SAP NetWeaver LVM 13

14 EMC Software Installation and Preparation This section will focus on EMC software installations related to SAP NetWeaver LVM and some of the preparatory work associated with the configuration of SAP NetWeaver LVM EMC Storage Integrator (ESI) for SAP LVM ESI for SAP LVM is available on the EMC Online Support website for download. ESI is distributed as an EAR (Java Enterprise Archive) file. You can download and use the ESI Adapter and EMC HLS Administration Console (EHAC) separately. This could commonly occur if the SAP NetWeaver LVM user is not also the storage administrator. This adapter is deployed on the SAP LVM Java Application server. For complete installation instructions please refer to the EMC Storage Integrator for SAP LVM Storage Adapter User Guide. EMC HLS Administration Console (EHAC) EHAC is distributed as an EAR (Enterprise Archive) file and two jar files used to configure the database and update the JBoss configuration files. For complete installation and configuration instructions please refer to the EMC Storage Integrator for SAP LVM: EMC HLS Administration Console. As mentioned above, you can download and use the ESI Adapter and EMC HLS Administration Console (EHAC) separately. This could commonly occur if the LVM user is not also the storage administrator. The following software must be installed and set up before you install the EMC HLS Administration Console (EHAC). Software Java Development Kit (JDK) Java Cryptography Extension 6 (JCE-6) JBoss Application Server 7 Required software version Version 1.6 JCE-6 for Java 1.6 with Unlimited Strength Jurisdiction Policy Files 6, which supports Strong Encryption Version or later The following software must be installed and set up on the EHAC server if you use block storage. Software SMI-S provider Browser Required software version IE 9 or later, if Internet Explorer is used. Other browsers can be used as well. 14

15 Note: You must also configure an SMI-S Provider account with the Administrator role to allow full access. Zoning should also be completed prior to cloning. Once the EHAC and prerequisite software is installed and configured, the administration console can be accessed by the storage administration at the following URL: server ip>:<port id>/esi_sap_lvm_saconfig.1.5 The administration console can be set up to run in SSL mode. These instructions are detailed in the EMC Storage Integrator for SAP LVM Storage Adapter User Guide. Running in SSL mode enhances the security between the client and the server, when you access the server remotely. The client is the browser from which the request comes to the server. The request and the response are both encrypted. After the storage administrator logs into EHAC, the controls are listed down the left in the Administrator Menu. These controls include defining the user accounts, accessing, listing, and granting/revoking user privileges to the available EMC storage arrays (File, Block, or Unified). On the Home page includes two panes: The left pane displays file storage systems and the pools that are assigned to specific users The right pane displays block storage and the pools that are assigned to specific users Figure 8 shows the EMC admin console where the ESIuser has been granted access to 2 storage pools residing in block Symmetrix VMAX storage id ending in 381. Figure 8: : EHAC home page 15

16 A Global Access Level can be created to enable or disable read/write access to storage systems for all users. You can do this with one click, and the Global Access Level overrides everything else. If the Global Access Level is set to read-only, all write access to users is also disabled. The user id configured in the SAP NetWeaver LVM GUI, in the Configuration section, Infrastructure tab, under Storage Manager is defined in the User section of EHAC. Figure 9 shows the EHAC screen where this user id is created. Figure 9: : EHAC user id create page Figure 10 is an example of the Storage Systems section where the storage admin will gain access to the EMC storage arrays. This can be done in two different ways for File and Block. For file arrays, the control station IP address of the array is required. This will include VNX and CX4 arrays. Figure 10: : EHAC file storage system definition page Block storage will be retrieved through the SMI-S provider for all VNX or VMAX arrays configured as block. Figure 11 shows the screen where this storage can be added in the Server section of Block Storage Systems. The SMI-S provider connection schema can be setup as http or https for added security. Refer to the SMI-S Provider Release Notes for information on how to set up the SSL mode for the SMI-S Provider. 16

17 VMAX storage will only require the server to be configured along with the appropriate gatekeeper connectivity. This is documented in the SMI-S Provider Release Notes. Figure 11: : EHAC block storage system definition page VNX and CX4 block arrays will require the SP-A and SP-B IP addresses to be configured. Refer to the EMC Storage Integrator for SAP LVM Storage Adapter User Guide or the SMI-S Provider Release Notes for more detailed instruction. EHAC Access Controls Access to the arrays is either granted or revoked in the Access Controls section of EHAC, shown in Figure 12. Access can be granted or revoked at the array level or the storage pool level. Figure 12: : EHAC grant access control c page A full explanation of how to configure EHAC is provided in the EMC Storage Integrator for SAP LVM Storage Adapter User Guide. 17

18 EMC SMI-S S Provider SMI-S Provider software can be downloaded from the EMC Support website ( under Support by Product section, as seen in Figure 13. Figure 13: : EMC Support By Product SMI-S S Provider Simply enter SMI-S Provider on the Find a Product line and click the green arrows or hit enter. On the next screen, you will be able to select Documentation or Downloads, as seen in Figure 14. Figure 14: : EMC Support Page for SMI-S S Provider The SMI-S Provider Release Notes explain how to install SMI-S Provider for either Linux or Windows environments. This section will highlight the main points to keep in mind for SMI-S during the installation process. The installation process is very similar to EMC Solutions Enabler. The SMI-S installation and setup process installs the following: 18

19 EMC CIM (Common Interface Model) server EMC Solutions Enabler runtime libraries Only the Array provider is required for SAP NetWeaver LVM software. The VASA provider will automatically be installed but you will not be required to perform any of the setup processes for this provider. The Host provider is not required and should NOT be installed. The installation process is will be different for Linux and Windows, please consult the release notes for specifics on each operating system. Symmetrix VMAX family arrays will require six (6) additional gatekeepers for SMI-S monitoring. The VNX and CLARiiON product will require a discovery process to be able to view the arrays. These will be either an in-band or out-of-band process depending on if there are VNX or CLARiiON luns present on the SMI-S host. Both of these processes are detailed in the release notes in the Post-installation tasks section. The SMI-S Provide executable (ECOM) may also need to be restarted to make sure all of the arrays can be discovered. The executable file resides in /opt/emc/ecim/ecom/bin directory for Linux configurations and C:\Program Files\EMC\ECIM\ECOM\bin directory for Windows configurations and can be restarted from this directory with the following command:./ecom -d (Linux) or sm_service start ecom.exe (Windows) The /opt/emc/ecim/ecom/bin/testsmiprovider (Linux) or C:\Program Files\EMC\ECIM\ECOM\bin\TestSmiProvider.exe (Windows) executable will be used to log into the SMI-S provider and issue commands against the arrays. There are commands to view version information, discover the arrays, refresh the arrays, and remove any arrays. Once the initial discovery and communication is defined between the SMI-S provider and the EMC storage arrays, no more manual commands need to be issued against SMI-S. The communication for the clone, copy, and refresh process will happen between SAP and EMC and be seamless to the SAP NetWeaver LVM user. Note: Do not to install Solutions Enabler over the SMI-S provider because it will prevent the SMI-S provider from working properly. This is reason why EMC SMI-S Provider contains and installs EMC Solutions Enabler. EMC Solutions Enabler EMC Solutions Enabler software can be downloaded from the EMC Support website ( under Support by Product section, as seen in Figure

20 Figure 15: : EMC Support By Product Solutions Enabler Simply enter Solutions Enabler on the Find a Product line and click the green arrows or hit enter. On the next screen, you will be able to select Documentation or Downloads, as seen in Figure 16. Figure 16: : EMC Support Page for Solutions Enabler The EMC Solutions Enabler installation guide is very thorough and should always be followed. This section will only discuss unique steps required when using the EMC integration with SAP NetWeaver LVM software. During the installation process, the defaults can be taken with the exception of whether to install EMC Solutions Enabler SRM Components. The default is N but this integration requires the SRM components to be installed. Please select Y for yes to the question, Install EMC Solutions Enabler SRM Components? 20

21 These components are the Storage Resource Management (SRM) components and provides additional functionality used with the volume groups for EMC on all platforms. Additional information can be found in the same location mentioned above on the EMC Support website in the EMC Solutions Enabler Symmetrix SRM CLI Product Guide, but in-depth knowledge of these components is not required. All of the integration is done between SAP and EMC and is not exposed to the SAP NetWeaver LVM user. After Solutions Enabler is installed, the SAP Host Control Agent must be installed, in order for sapacosprep to function properly. The latest version is recommended. This will create the SAP Host Control Agent directory, /usr/sap/hostctrl/exe (Linux) or C:\Program Files\SAP\hostctrl\exe (Windows). A symbolic link must be created in this directory to point to the EMC shared library, libsapacosprep_emc.*, which is installed by default in the /opt/emc/symcli/shlib/apps/sap/ (Linux) or C:\Program Files\EMC\SYMCLI\shlib\apps\SAP\ (Windows) directory. This library and directory is installed and created by the EMC Solutions Enabler install. The following example is using the Linux configuration and is executed from the /usr/sap/hostctrl/exe directory in order to create a symbolic link: ln -s /opt/emc/symcli/shlib/apps/sap/libsapacosprep_emc.so libsapacosprep_emc.so The format of the command is ln -s {target-filename} {symbolicfilename}. After adding the symbolic link it is recommended to stop and restart the SAP Host Control Agent from the /usr/sap/hostctrl/exe directory:./saphostexec -stop./saphostexec -restart./saphostexec -status A command line test can be run to verify the communication of shared libraries. This command will list the mount points in a format designed for SAP LVM: /usr/sap/hostctrl/exe/sapacosprep -a ListFileSystems If this command fails, please view /usr/sap/tmp/sapacosprep.log for additional information. Note: Do NOT to install Solutions Enabler over the SMI-S provider because it will prevent the SMI-S provider from working properly. This is reason why EMC SMI-S Provider contains and installs EMC Solutions Enabler. 21

22 Overview of SAP NetWeaver LVM Operations Figure 17 shows how is based on four building blocks; control, which is the SAP LVM GUI, compute resources, which includes the SAP systems/instances referred to as services and physical or virtual servers referred to as resources, network, which ties the compute resource to the 4 th building block, storage. The SAP systems and instances have to be installed on centralized storage with a virtual name in order to be controlled by SAP NetWeaver LVM. Figure 17: : SAP NetWeaver LVM Building Blocks The Standard Edition functionality, start/stop/relocate/mass operations, will provide wide support across EMC storage platforms. The Enterprise Edition features, clone/copy/refresh, will have partial support initially. Standard Edition The start and stop functions are very basic starting and stopping of an SAP system or instance. You can extend these functions by adding a prepare or unprepare function to mount or unmount the files systems or volume groups associated with the SAP system or instance in a SAN environment. In a NAS environment the equivalent process is a bind or unbind of the mount points associated with the SAP system or instances. The relocate function will simply stop and unprepare the SAP system or instance on server x and then issue a prepare and start on server y, which is shown in 22

23 Figure 18. Figure 18: : SAP NetWeaver LVM Relocate At this point, the functionality only requires EMC Solutions Enabler and does not require any of the other EMC software. One of the benefits of using this functionality is to have a single control interface to start and stop all of your SAP systems. This provides ease of management versus having to manually maintain a list of all servers and SAP systems that are used by an SAP NetWeaver Technology person (formerly referred to as Basis). This includes having a single control interface to start and stop the SAP systems versus having to log in and out of every server to issue the start or stop commands. The SAP NetWeaver LVM user will also be able to schedule start and stop operations and perform mass operations, starting or stopping more than one SAP system or instance. This functionality is providing SAP application virtualization, by allowing the SAP system or instance to be relocated to different servers (same architecture) and not being tied to the hardware it was originally installed on. SAP NetWeaver LVM also supports hypervisor or server virtualization products. One example is VMware virtualization. The SAP NetWeaver LVM user has the flexibility to choose between using application virtualization or hypervisor virtualization depending on the configuration of the SAP Landscape. For example, if there is scheduled hardware maintenance on a server, then the SAP NetWeaver LVM user may choose to use the hypervisor virtualization to move the virtual machines off that hardware. During a maintenance weekend, the SAP NetWeaver LVM user may choose to use application virtualization to move certain SAP systems to more powerful servers to speed up processing during the limited time imposed during the weekend. 23

24 Enterprise Edition SAP has extended the functionality of SAP NetWeaver LVM to include system clone, copy, and refresh and other features. Figure 19 displays the differences between clone, copy, and refresh. SAP system cloning will create an isolated copy of SAP system without renaming the system. SAP system copy will create a new, renamed SAP system. SAP system refresh will create a newer version of an existing copy. Figure 19: : SAP NetWeaver Clone / Copy / Refresh System Clone Figure 20 depicts an SAP system clone process in SAP NetWeaver LVM. SAP system cloning will create an isolated copy of the SAP system by using a fenced LAN configuration. This is done so the SAP System ID can remain the same. The integration with EMC will include the ability to make the copy of the SAP system using either full volume Clones or pointer-based Snaps within the array. EMC clones are like devices that will use the same storage space as the source SAP system. EMC Snaps are pointer-based copies that require the space for changed data. In typical environments this could be as little as 30% of the source SAP system. It depends how frequently the SAP system data is updated and changed. EMC has tools that can help determine how much space is actually needed for Snaps. Once a clone is initiated, the SAP NetWeaver LVM interface will use EMC s integration with ESI for SAP LVM, EHAC, and the SMI-S Provider software to create new devices for the clone or snap. Either a clone or a snap will be created and activated. SAP NetWeaver LVM will then create a fenced LAN environment on the target server. The clones or snaps of the cloned SAP system will be mounted or bound (prepared) on the target server, which accesses our integration with the storage library in EMC Solutions Enabler for SAN configurations. Finally the newly cloned SAP system will be started. 24

25 Figure 20: : SAP NetWeaver LVM SAP System Clone System Copy Figure 21 depicts an SAP system copy process in SAP NetWeaver LVM. SAP system copy performs many of the same steps as the clone process; additionally SAP NetWeaver LVM renames the SAP system and invokes the SAP s Post Copy Automation, PCA. The PCA process automates and performs all of the numerous post copy steps required that many SAP customers struggled with for years and are very familiar with its required effort and restrictions when executed manually. EMC s integration will create new devices in order to create either an EMC clone or Snap for the copied SAP system. Once a copy is initiated, the SAP NetWeaver LVM interface will use EMC s integration with ESI for SAP LVM, EHAC, and the SMI-S Provider software will create new devices for the clone or snap. Either a clone or a snap will be created and activated. SAP NetWeaver LVM will then rename the SAP system id and perform the post-copy automation tasks. The clones or snaps of the copied SAP system will be mounted or bound (prepared) on the target server, which accesses our integration with the storage library in EMC Solutions Enabler in SAN configurations. Finally the newly copied SAP system will be started. 25

26 Figure 21: : SAP NetWeaver LVM SAP System Copy System Refresh SAP system refresh performs many of the same steps as the copy process, while capturing certain data from the previous target SAP system, copying the source system, and then applying the data collected earlier to the new (refreshed) target system. The SAP Post Copy Automation, PCA, tasks can be invoked for full automation. Once a copy is initiated, the SAP NetWeaver LVM interface will use EMC s integration with ESI for SAP LVM, EHAC, and the SMI-S Provider software will create new devices for the clone or snap. Either a clone or a snap will be created and activated. SAP NetWeaver LVM will then rename the SAP system id and perform the post-copy automation tasks. The clones or snaps of the copied SAP system will be mounted or bound (prepared) on the target server, which accesses the EMC integration with the storage library in EMC Solutions Enabler in SAN configurations. The newly copied SAP system will be started. Initial Setup and Configur onfiguration The initial setup and configuration steps will be required whether you have a Standard or Enterprise Edition license. There are many options and configuration steps that are required that are not discussed in this paper. Please refer to the SAP 26

27 NetWeaver Landscape Virtualization Management documentation. We will only point out the important steps for the EMC integration with SAP NetWeaver Landscape Virtualization Management. Setup To the far right of the SAP NetWeaver LVM GUI is the Setup section, as seen in Figure 22: Figure 22: : SAP NetWeaver LVM GUI Figure 23 shows there are three area of configurable parameters in the Setup section; User Interface Settings, Notification Settings, and Engine Settings. Figure 23: : SAP S NetWeaver LVM Setup We recommend viewing these options in order to become familiar with what can be configured. During the testing conducted in our labs, the following options were selected on Engine Settings; Allow Multiple Services on Same Resource, Allow Multiple Database Services on Same Resource, and Show Advanced Shutdown Options when Stopping Operations to enable additional functionality. SAP Host Control Agent and SAP Profile Parameters P It is recommended by SAP to install the latest version of the SAP Host Control Agent on the server running SAP NetWeaver LVM, as well as all managed servers. It is important to apply SAP note , to add the operations.d directory with a configuration file, following the exact procedure described in this note. The SAP profiles requires additional parameters; SAPLOCALHOST, SAPLOCALHOSTFULL, icm/host_name_full. Refer to the SAP LVM 1.0 help documentation available on the link: Install EMC Solutions Enabler on all servers that currently host or will host a SAP LVM managed SAP systems. You will create the required SAP users if the target servers do 27

28 not already have them defined or if your landscape does not have a NIS or LDAP previously configured, which is recommended by SAP to simplify, automate, and centralize the user management process for SAP NetWeaver LVM. Verify all SAP LVM managed servers in a SAN configuration has the EMC shared library configured as a symbolic link /usr/sap/hostctrl/exe/libsapacosprep_emc.* (Linux) or C:\\Program Files\SAP\hostctrl\exe\libsapacosprep_emc.* (Windows). It is highly recommended to enable multi-pathing using EMC PowerPath. Native multi-pathing is also supported. Retrieving SAP system mount points in SAP NetWeaver LVM In the configuration screen of the SAP NetWeaver Landscape Virtualization Management interface, you will define pools, services, and resources, as seen in Figure 24. Figure 24: : SAP NetWeaver LVM Configuration => Services During the add services process, you will be able to define the mount points in step 3. In step 1, you will be providing the database configuration information. Step 2 you will select the system to be AC-Enabled. This allows for the management of the SAP System by SAP NetWeaver LVM. In step 3, you will add your mount points. You should retrieve the mount points automatically by selecting the Retrieve Mount List button, which is shown in Figure 25. Figure 25: : SAP NetWeaver LVM Retrieve Mount List 28

29 The button will use the binaries and the shared libraries between SAP and EMC to automatically populate the mount list with all of the mount points that are seen on the server running the SAP Host Agent and the EMC storage library. Highlight and remove the mount points that do not pertain to this SAP instance. Below is an example of what will be populated. Each field contains detailed information about the mount point, volume group, logical volume, and physical luns. The Retrieve Mount List button populates all of the required information, as shown in Figure 26. The SAP NetWeaver LVM user will not know what is required in each field. Figure 26: : SAP NetWeaver Mount List Issuing operation functions for SAP systems and instances Once the mount points are configured for all SAP systems and instances, you have the freedom to start, stop, prepare, unprepare, and relocate the SAP systems and instances in the Operations section of SAP LVM, as shown in Figure 27. Figure 27: : SAP NetWeaver Operations The SAP NetWeaver LVM interface shows the available SAP systems and instances on the top half of the screen and you can select your options on the lower half of the screen. Figure 27 shows a mass relocate of the SE1 SAP system from the saperpsrc server to the saplin249 server. 29

30 Figure 28: : SAP NetWeaver Service Locked Once the execute button is selected the services are locked and the process begins, as seen in Figure 28. You can switch to the Monitoring section of the SAP NetWeaver LVM Interface. Figure 29 shows the Monitoring screen and how it displays all of the automated steps and the progress through these steps. Figure 29: : SAP NetWeaver - Monitoring Advanced Configuration for Enterprise Edition The Enterprise Edition license is required to purchase the system clone, copy, and refresh features. The section covers the EMC specific integration requirements to enable them. Setup In order to enable clone, copy, or refresh you must first set a system profile parameter and enable the SAP system for clone and/or copy in the configuration screen. The SAP system profile, service/enableremotedeployment = true, should be looked at to 30

31 see if you require this in your environment. Also a unique identifier, system/uuid= will be required to be set but can also be set from the SAP NetWeaver LVM interface. The Configuration section, Services tab in the SAP NetWeaver LVM interface will need to have cloning or copying selected in order to access those screens. The UUID parameter mentioned above can also be added to the default profile on this screen, as shown in Figure 30. The copy option will also require RFC connections to be defined and tested. Figure 30: : SAP NetWeaver UUID ESI for SAP LVM Storage Adapter Configuration After the storage administrator has configured the user accounts for the storage adapter and granted the read/write permission to the storage for this user, the adapter must be configured in SAP NetWeaver LVM. There is also an Infrastructure tab in the Configuration section of the SAP NetWeaver LVM interface that must be completed. You will add the storage adapter user account credentials received from the storage administrator in the Storage Manager area in the Infrastructure tab, as shown in Figure

32 Figure 31: : SAP NetWeaver Storage Manager After you select the Add button, lists of supported Storage Managers are listed. You will select the one pertaining to EMC. There may be more than one in the list for EMC. The interface you want to select is listed as EMC Corp for the vendor field and ESI for SAP-LVM for the product field, as shown in Figure 32. Figure 32: : SAP NetWeaver EMC Storage Adapter On the next screen you will enter the user account information received from the storage administrator. This account information was defined in the EMC HLS Administration Console. The Label field can be named anything you desire. In our example we named it ESI_Adapter. The next two fields, User Name and Password are the user id and password provided by the storage administrator. This was defined in 32

33 the EHAC. The final field, URL, is IP address of the server that the EHAC is installed on following by a colon : and the port number for EHAC, 8080 is the default port. Once all of this information is entered, select the Test Configuration button to check if the administration console is communicating properly with SAP NetWeaver LVM. If it is you will receive a Connection successful: Connection to the ESI configuration utility web service was established successfully message at the bottom of the screen, as shown in Figure 33. Figure 33: : SAP NetWeaver EMC Storage Adapter Configuration You can select the Next button. After you select Save, Figure 34 shows you an overview of the configuration. Figure 34: : SAP NetWeaver EMC Storage Adapter Summary 33

34 Issuing clone and copy operations for SAP systems and instances Once the ESI adapter is configured properly and the proper profile parameters are specified you can begin to issue clone, copy, and refresh of the SAP systems. This document will focus on the highlights of the clone steps focusing on the storage integration from EMC. These steps will apply to clone, copy, and refresh. We will not focus on the additional steps in the copy and refresh procedure because it is related to SAP functionality only and out of the scope of this document. The Provisioning section of the SAP NetWeaver LVM interface is where you will initiate the clone, copy, and refresh procedures. The SAP NetWeaver LVM screen will list the available systems to clone on the left hand side of the screen. You will also have more options if you select additional options in the Configuration section. For example, our screen only shows Clone System and Manage System Snapshots because we did not select the copy option yet or set up the RFC connections. Highlight the SAP system you would like to clone and select the Clone System button to initiate the steps for cloning, as shown in Figure 35. Figure 35: : SAP NetWeaver LVM Provisioning System Clone This process will take you through six (6) steps to populate the information for a clone. The first step will select the pool for the clone and name the clone process as well as provide a description of the clone. The second step will allow the SAP LVM user to define the resources or servers. The source server is already populated but the target server should be selected from the available server resources defined in the 34

35 Configuration section. The third step will define the virtual host names and network information of the cloned SAP system. All of this is shown in Figure 36. Figure 36: : SAP NetWeaver LVM Cloning Steps Step four is where the storage information is populated and is shown in Figure 37. At the top of the screen you have the ability to select the consistency options; No special actions to ensure consistency, Database Consistency (Online Clone), and Stop & Restart the SAP System (Offline Clone). The lower section will list the source information on the left and the target information on the right. The target information is populated with the same Storage System array id as the source. The Storage Pool will need to be populated, and will typically be the same as the source. The storage administrator will notify the LVM administrator which pool to use. This pool will have to access provided by EHAC. A special note for Meta Volumes, it is required to leave the Storage Pool blank. If this field is left blank, EMC s SMI-S Provider will select the appropriate storage pool. The Operation field will default to Create New Volume. The Volume field will be left blank. Create New Volume will direct SMI-S to create a completely new device in the 35

36 Storage Pool provided. Figure 37: : SAP NetWeaver LVM Cloning Storage Step When the line is highlighted the mount data is listed at the bottom of the screen for that LUN. In this example, the source Volume 8E is /usr/sap/se1. Finally the last column is where you select either full volume clone or pointer-based snap from EMC. If it is checked you will receive a full volume clone, otherwise you will receive a pointer-based snap. Note: It is recommended to coordinate with the storage management personnel when setting up the clone processes to verify the proper information is used to populate this screen. The fifth step is associated with the fenced LAN isolation. The sixth step is a summary of all the steps and where you select the Start System Cloning button. Immediately SAP NetWeaver LVM will bring up the Monitoring section of the interface. This screen is shown in Figure 38 and will list all of the steps required to create the 36

37 SAP System clone. Figure 38: : SAP NetWeaver LVM SAP System Clone Monitoring The same process will occur for copy and refresh, except with additional steps for the post-copy automation steps, renaming of the SAP system, and exporting/importing the configuration. The EMC integration is very similar as what is listed above. Conclusion EMC s integration with software includes the use of a storage library for SAN configurations. This storage library, delivered through EMC Solutions Enabler, provides the ability to automatically detect and retrieve the SAP system mount points, mount and unmount file systems and volume groups. This process is used during any Prepare or Unprepare phase. This could be while Relocating SAP systems or making Clones or Copies of those SAP systems. The clone or snap process executed during a SAP Clone, Copy, or Refresh processes is a result of the integration provided by EMC Storage Integrator for SAP LVM adapter (ESI for SAP LVM) and EMC SMI-S Provider integration. This functionality will create new volumes or use existing volumes for the replication process. The EMC HLS Administration Console provides the storage administration team the ability to grant permission to storage for the SAP NetWeaver LVM administrator s use. EMC will continue to enhance the integration with SAP NetWeaver Landscape Virtualization Management. 37