WHITE PAPER Advanced Automation and Optimization of System Copy Procedures for SAP ® Systems SAP ® application environments include Quality Assurance (QA), Test, and other Staging Systems in addition to actual Production Systems. These so called “non-production sys- tems” are designated to manage the application lifecycle process. SAP recommends a specific procedure called “system copy” to provide non-production systems with produc- tion data for adequate and consistent testing. 1 Typically, there are numerous manual tasks involved for executing the system copy proce- dure which can spread over days and may block precious and expensive resources of the most skilled SAP Basis professionals. Libelle SystemCopy is a framework-based software solution to create fully automated system copies. It furnishes ready-to-go QA or test system with fresh production data. SystemCopy supports single- or dual-stack SAP software implementations on Oracle ® , SAP MaxDB ® database, SAP HANA ® , Sybase/SAP ® Adaptive Server ® Enterprise, DB2 ® , or Microsoft SQL Server ® databases, and can be integrated into popular Storage Snap- shots ® or SnapMirror ® tools. As an alternative, the solution includes a copy tool for all plat- forms. System copy tasks can run outside the ABAP ® stack and include database im- port/export operation, command scripts, SQL operations, or the execution of SAP transac- tions. This white paper describes the process involved in the creation of homogenous system copies and outlines how procedures can be automated with the SystemCopy solution. 1 SAP Help Files (Link)
15
Embed
Advanced Automation and Optimization of System Copy ... · PDF fileWHITE PAPER Advanced Automation and Optimization of System Copy Procedures for SAP® Systems SAP® application...
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
WHITE PAPER
Advanced Automation and Optimization of System Copy Procedures for SAP® Systems
SAP® application environments include Quality Assurance (QA), Test, and other Staging
Systems in addition to actual Production Systems. These so called “non-production sys-
tems” are designated to manage the application lifecycle process. SAP recommends a
specific procedure called “system copy” to provide non-production systems with produc-
tion data for adequate and consistent testing.1
Typically, there are numerous manual tasks involved for executing the system copy proce-
dure which can spread over days and may block precious and expensive resources of the
most skilled SAP Basis professionals.
Libelle SystemCopy is a framework-based software solution to create fully automated
system copies. It furnishes ready-to-go QA or test system with fresh production data.
SystemCopy supports single- or dual-stack SAP software implementations on Oracle®,
SAP MaxDB® database, SAP HANA
®, Sybase/SAP
® Adaptive Server
® Enterprise, DB2
®,
or Microsoft SQL Server®
databases, and can be integrated into popular Storage Snap-
shots® or SnapMirror
® tools. As an alternative, the solution includes a copy tool for all plat-
forms. System copy tasks can run outside the ABAP® stack and include database im-
port/export operation, command scripts, SQL operations, or the execution of SAP transac-
tions.
This white paper describes the process involved in the creation of homogenous
system copies and outlines how procedures can be automated with the
System copy procedures are executed any time, from once a year to every month de-
pending on the SAP application and implementation. This also depends on in which
stage of the deployment project a customer is and what the internal testing procedures
require.
System Copy Terminology
In the various system copy guides that SAP AG provides on the SAP Service Market-
place extranet, there is consistent terminology in regard to the system copy procedure:1
System copy: Duplication of SAP systems; certain SAP parameters change
Source system: The SAP system containing the original production database
Target system: The system to which the database copy is copied
Homogenous system copy:2 System copy to the same operating system and
database platform as the Source system
Database copy: Database-dependent part of the system copy
System Copy Dependencies
SAP AG provides specific system copy guides for each of its enterprise applications that
may differ depending on factors such as:
Type of SAP application (e.g. SAP ERP application, SAP NetWeaver BW)
Version of SAP application
Type of implementation (single- or dual-stack)
Database type and version
Operating system
Within this procedural structure, customers typically enhance, add, or remove certain
system copy tasks to adjust to their very specific installations and circumstances. While
the general procedure is then similar for certain configurations, individual installations
vary in details.
System Copy Phases
Generally, all steps necessary to successfully complete a system copy procedure can
be categorized into three steps: Before the data on the target system is refreshed, there
is certain pre-processing required. This is followed by copying the actual data, and
completed with post-processing. The steps are defined as follows:
1 E.g. “System Copy for SAP Systems based on SAP NetWeaver 7.1 Java,” December 2009. link 2 SAP also lists a Heterogeneous System Copy procedure where the database or O/S platform changes. This is currently not covered in the Libelle
SystemCopy procedure and is not part of this white paper.
Libelle AG Libelle LLC Gewerbestr. 42 3330 Cumberland Blvd., Suite 500 70565 Stuttgart, Germany Atlanta, GA 30339 USA T +49 711 / 78335-0 T +1 770 / 435 1101
Libelle does not guarantee that the information in this presentation is error free. The liability for consequential or indirect damages arising out of the reading or the use of this information is not warranted by Libelle AG within legal limits. All copyrights, especially distribution, reproduction, and translation, are reserved. No part of this presentation may be reproduced, processed, or reproduced or transmitted by electronic means without ex-plicit approval of Libelle. Under no circumstances, including, but not limited to, negligence, shall Libelle, its agents or assignees, including but not limited to its parent, subsidiary, or affiliate companies, be liable for any direct, indirect, incidental, special, or consequential damages that result from the use of the information provided herein. Libelle, the Libelle Logo and BusinessShadow are trademarks of Libelle AG in Germany and other countries. SnapMirror and Snapshot are trademarks or registered trademarks of NetApp, Inc. Windows, Microsoft, and SQL Server are regis-tered trademarks of Microsoft Corporation. Oracle is a registered trademark of Oracle Corporation. DB2 is a trademark or registered trademark of IBM Corp. MaxDB is a trademark of MySQL AB, Sweden. UNIX is a registered trademark of The Open Group. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affi liate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. V4