Use of Virtualization Technology with SAP


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Use of Virtualization Technology with SAP

  1. 1. Use of Virtualization Technology with SAP SAP Co-Innovation Lab Tokyo VMware Inc. Shuji Watanabe Tetsuji Morita SAP Co-Innovation Lab Tokyo - Opening Commemoration Project October 2008 In cooperation with Intel Corporation
  2. 2. Use of Virtualization Technology with SAP Table of Contents Page 3 1. SAP Upgrade Page 4 2. Upgrading Using Virtualization Page 5 3. Testing at COIL Tokyo (Summary) Page 6 4. Testing Procedure at COIL Tokyo Page 10 5. Summary Page 11 6. Notes 2 SAP Co-Innovation Lab Tokyo White Paper 2
  3. 3. Use of Virtualization Technology with SAP 1. Upgrading SAP For users of core business applications such as SAP ERP and other SAP solutions, upgrading is one of those things that cannot be avoided. As a rule, SAP recommends a three-system landscape consisting of development, testing and production systems, which means that upgrading SAP typically requires upgrading these three different systems. Even if the same system is used for both development and testing, at the very least, two systems will need to be upgraded. It is also common when performing an upgrade to run a migration server separate to the server used for the new version. Figure 1 shows the typical requirements and procedures for an upgrade. Current server Current server / Migration server New server R/3 46C SP xx R/3 46C SP yy ERP 6.0 SR3 SP zz R/3 Kernel 46D R/3 Kernel 46D_EXT ERP Kernel 700 MSSQL 2000 (32bit) MSSQL 2000 (32bit) MSSQL 2005 (64bit) Windows Server 2000 (32bit) Windows Server 2000 (32bit) Windows Server 2003 (64bit) Upgrade R/3 kernel Upgrade preparation Apply R/3 support package Migration server setup Kernel upgrade System copy (Install OS and DB) Apply R/3 SP (export) System copy Update SAP Post- Update hardware, PREPARE (import) database upgrade processing Upgrade Update hardware Database upgrade OS upgrade SAP upgrade Figure 1. Requirement for upgrade from 4.6C to ECC6.0 and typical upgrade process Initial preparation required for an SAP solution upgrade includes updating the current kernel version and raising the level of each support package to the prescribed level. In the case of an upgrade to a core business system, the time available for the upgrade is limited. Similarly, any effect on the production system during these preparatory stages must be kept to an absolute minimum. This is one reason for using a migration server. Figure 1 shows a migration server in use as the production server hardware is being upgraded. The first step is to install the current operating system and database on the migration server and copy the current data from the SAP system by performing a system copy. Next, upgrade the SAP kernel and apply the SAP application support packages required for the upgrade. This completes the upgrade preparations for the current system. Now install the latest operating system on the new server. Although it is common to upgrade the database after performing the system copy, it is also possible to install the new version of MS-SQL 2005 on the new server from the beginning because MS-SQL 2005 supports database detach and attach even when migrating from 32 to 64-bit environments. 3 SAP Co-Innovation Lab Tokyo White Paper 3
  4. 4. Use of Virtualization Technology with SAP If using the detach/attach method, first install MS-SQL 2005, install the current version of SAP, attach the database, and then use the special-purpose utilities to perform post- processing (database copy) and apply the dbsl_lib patch. Once the database has been upgraded, the next step is the SAP upgrade. SAP provides the PREPARE utility (program) for performing upgrades more smoothly and efficiently. Running PREPARE provides information such as whether the prerequisites (kernel patches, support package level) required by the upgrade are present and whether any customer modifications exist. However, when you perform the actual upgrade you may encounter a number of issues that are not taken care of by PREPARE. In the process of dealing with these one by one as you perform the upgrade, it is not uncommon for users to start to become concerned about whether they have sufficient disk space. Compared to 4.6C, the disk space required by ECC6.0 is much larger. Also, the required disk space will increase even further if using the Unicode code page rather than a non-Unicode code page. After the upgrade is complete, post installation (post-processing) is the next step. Post- processing involves applying kernel patches and support packages, and requires running the transaction SGEN to recompile the ABAP program. The system administrator needs to perform this series of actions in a limited amount of time. Running the upgrade marathon to its conclusion can hardly be described as fun. 2. Upgrading Using Virtualization Technology Using virtualization technology changes the way you perform upgrades. VMware provides a utility, VMware® Converter, for creating a virtualized image, called a virtual machine, from a physical server. VMware Converter makes it easy to make a copy of the current system on VMware® ESX. Although the procedure for applying kernel patches and support packages is the same as on a physical server, the OS and DBMS installation steps and the system copy from the current server to the migration server can be omitted. If configuring the new server on VMware ESX, create a new virtual machine and install the new version of the OS. Although the subsequent procedure is the same as for a physical server, the snapshot function available with VMware ESX provides a major benefit. Snapshots save an image of the entire system at a particular instant and allow you to return to the state when the snapshot was taken. An upgrade is normally an irreversible process, and if the upgrade fails, there is no way of going back. This makes the snapshot function particularly valuable in case of mistakes that may occur during the upgrade procedure -- even elaborate rehearsals cannot completely eliminate human error. Virtualization technology also makes it easier to perform rehearsals and allows you to make do with less hardware. If you have separate development, test and production machines, configuring the migration server in a virtualization environment allows you to reduce the number of servers from three to one. Performing a rehearsal also lets you find out how much disk space will be required after the upgrade. 4 SAP Co-Innovation Lab Tokyo White Paper 4
  5. 5. Use of Virtualization Technology with SAP Figure 2 shows an example upgrade using virtualization technology. Current server New server Virtualization server 1 Virtualization server 2 R/3 46C SP xx R/3 46C SP yy ERP 6.0 SR3 SP zz R/3 Kernel 46D R/3 Kernel 46D_EXT ERP Kernel 700 MSSQL 2000(32bit) MSSQL 2005(64bit) MSSQL 2000(32bit) Windows Server 2000(32bit) Windows Server 2003(64bit) Windows Server 2000 (32bit) VMware ESX 3.5 On virtualization server 1 Upgrade R/3 kernel Apply R/3 support package Convert physical server Kernel upgrade System copy to virtual machine Apply R/3 SP (export) Configure new server on virtual System copy Upgrade Upgrade Post- PREPARE machine (import) database SAP processing On virtualization server 2 Install new OS (Upgrade OS) Upgrade SAP Upgrade database Figure 2. From 4.6C to ECC6.0 upgrade process with VMware 3. Testing at COIL Tokyo (Summary) On July 16 2008, following in the path of its site in Palo Alto in the US, SAP opened its second center for joint research and development with customers and partners, the Co- Innovation Lab Tokyo. The opening commemoration project for COIL Tokyo was the joint testing with VMware Inc. of an upgrade from R/3 Enterprise ext 2.00 + MSSQL 2000 (32- bit) to ECC 6.0 SR2 + MSSQL 2005 (64-bit). The upgrade project used servers fitted with multi-core Intel® Xeon® processors. The testing included a final step whereby a system copy was taken from the virtual machine and restored to a physical server. This last step was included to demonstrate the case when an SAP system that has been migrated to a virtualization environment needs to be restored to a physical server. 5 SAP Co-Innovation Lab Tokyo White Paper 5
  6. 6. Use of Virtualization Technology with SAP 4. Testing Procedure at COIL Tokyo The testing procedure at COIL Tokyo is described below. 4 -1. Installed R/3 Enterprise ext 2.00 + MS SQL Server 2000 (32-bit) on Windows 2003 (32-bit) on a physical server. 4 -2. Used VMware Converter to convert the physical server system to a virtual machine. 6 SAP Co-Innovation Lab Tokyo White Paper 6
  7. 7. Use of Virtualization Technology with SAP 4 -3. Applied the latest kernel patches and support packages to the virtual machine. 4 - 4. Performed a database detach. 4 -5. Installed the upgrade OS on a new virtual machine (Windows 2003 64-bit). 4 -6. Installed MSSQL 2005(64-bit) on the virtual machine, then installed R/3 Enterprise ext 2.00. Attached the database and performed post-processing for the DB upgrade. 4 -7. Ran PREPARE on the new virtual machine. 4 -8. Performed the upgrade to ECC 6.0 SR2 on the new virtual machine (disk space added three times [on c: drive]). 7 SAP Co-Innovation Lab Tokyo White Paper 7
  8. 8. Use of Virtualization Technology with SAP 4 -9. Performed a DB export on the new virtual machine. 8 SAP Co-Innovation Lab Tokyo White Paper 8
  9. 9. Use of Virtualization Technology with SAP 4 -10. Installed Windows 2003 (64-bit) and MS-SQL 2003 (64-bit) on the physical server. 4 -11. Performed a DB import on the physical server. 4 -12. Confirmed that the physical server ran without problems. 9 SAP Co-Innovation Lab Tokyo White Paper 9
  10. 10. Use of Virtualization Technology with SAP 5. Summary 5-1. No particular VMware related problems or errors occurred during the test. 5-2. GB Ethernet is required to use VMware Converter. If using 100MB/bps, locate the physical server, target virtualization server machine, and Converter server on a closed network. 5-3. Problems encountered during testing 5-3-1. "Unable to find required assembly Microsoft.VC80.CRT." (64-bit) 5-3-2. Unable to recognize "Languge Disk" when connected via Terminal Service. 5-3-3. Insufficient disk space on C drive (Increased the disk space allocated to the virtual machine then enlarged the drive area. The freeware used for this task required a reboot of the virtual machine.) 5-3- 4. note 956198 sap_deadlock_trigger should not be used - Please apply the latest basis support packages for Basis Release 4.6C and 6.20 before upgrading. To avoid problems when upgrading a system that has not had all the support packages applied prior to the upgrade, use SQL Server Query Analyzer or SQL Server Management Studio to run the following SQL commands. - - use <SID> System ID in upper case (or SAP db name) - go - - setuser '<sid>' System ID in lower case - Ignore any errors that occur - go - DROP TRIGGER sap_deadlock_trigger - go - Next, execute the upgrade phase again. 5-3-5. Table PATCHECK missing in DDIC after upgrade - - Resolve by applying SAPKD70026 10 SAP Co-Innovation Lab Tokyo White Paper 10
  11. 11. Use of Virtualization Technology with SAP 5.4 Advantages of VMware ESX and multi-core Intel® Xeon® processor The tests demonstrated that use of virtualization technology allow upgrades to be performed more easily and reliably. The tests also showed that implementation in a virtual machine makes it possible to reduce the hardware required for an upgrade.*) Improved efficiency of upgrade process: Using VMware Converter to create a virtualization image from the physical server eliminates the work associated with taking a system copy when installing or upgrading software such as the OS and DBMS. Less risk in upgrade process: Using the VMware Snapshot function allows the complete state of the system at a particular instant to be saved and this makes it possible at a later time to restore the system to its state at the time of the snapshot. This ability to restore the previous state at any time is a particularly valuable function in case operational errors or similar cause problems to occur during an upgrade, a process that is otherwise very difficult to roll back. In practice, it also reduces the total time required for the upgrade. Adequate testing: The features of virtualization make it easier to perform rehearsals. Performing a rehearsal also provides information on the amount of disk space required after the upgrade and allows detailed testing to performed as part of the upgrade, including giving warning of any potential pitfalls that are not reported by PREPARE, for example. Multi-core Intel® Xeon® processor: Multi-core Intel® Xeon® processors help virtualization by allowing you to run more virtual machines on a single physical server. The arrival of VMware virtualization technology and the multi-core Intel ® Xeon ® processor specifically designed for virtualization is truly good news for system responsible for upgrading their company's core business systems in a limited amount of time. The affinity between multi-core processors and virtualization is particularly strong and the more cores the processor has the more virtual machines it can support on a physical server due to increased cache memory and additional cores on the tested configuration. This also helps system administrators by reducing the number of servers to be managed. * It is recommended that you perform adequate testing to check for performance or other problems before adopting virtualization for your production machine. 6. Related SAP Notes 674851 Virtualization on Windows 89580 SAP Support for Linux Virtualization Environment 105605 VMware ESX Server 3.0 Setup Guidelines 1122387 Linux: Virtualization Technologies Supported by SAP 1122388 Linux: VMware ESX Server 3 Setup Guidelines 11 SAP Co-Innovation Lab Tokyo White Paper 11
  12. 12. Use of Virtualization Technology with SAP Copyright © 2008 by SAP AG. All rights reserved. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. Copyright © 2005 VMware, Inc. All rights reserved. Protected by one or more of U.S. Patent Nos. 6,397,242, 6,496,847, 6,704,925, 6,711,672, 6,725,289, 6,735,601, 6,785,886, 6,789,156, 6,795,966; patents pending. VMware, the VMware “boxes” logo and design, Virtual SMP and VMotion are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation. Linux is a registered trademark of Linus Torvalds. All other marks and names mentioned herein may be trademarks of their respective companies. SAP Japan Co., Ltd. 1-7-2 Otemachi, Chiyoda-ku, Tokyo 100 - 0004 Tel: 03-3273-3500 URL: VMware K.K 13F Hamamatsucho Square, 1-30-5 Hamamatsucho, Minato-ku, In cooperation with Intel Tokyo 105- 0013 Corporation Tel: 03- 4334 -5600 URL: 12