SAP system copy Several advantages at once - SAP Basis

Direkt zum Seiteninhalt
Several advantages at once
Pre- and post-processing
Checklist for preliminary work: Comparison of database sizes (target system must be the same or larger), comparison of database versions, kernel, host agent (ideally the same software version), dump of kernel files (export via SAPINST), saves download via SWDC, compile RFC connection passwords, inform third-party system administrators, provide memory, hard disk on the system for database and software import. Perform database dump, if necessary with transaction log, if possible with downtime, then without jobs or stop running jobs with report BTCTRNS1. Adminsitration passwords (DDIC, DB-Admin, Winadmin), create system snapshots (recovery), perform database import.

Shutting down and copying virtualized systems, such as VMware instances, requires just a few mouse clicks. VMware is suitable for running multiple training, development and test environments on one physical system. Larger productive systems, on the other hand, are not so easy to virtualize. If users have to shut down the productive system during the copy, the runtime of the operation or the unavailability of the productive system becomes a critical factor.
Scenario with system copies for updating
The demands on your business are constantly changing. For this reason, there is also a need to adapt processes and functionalities. This cannot be done directly in the production system, but must first be extensively tested, which in turn requires data that is as realistic as possible. The SAP system copies required for this are quite time-consuming and complex, but also offer very great automation potential. We support you in the execution of SAP system copies and, within the framework of our partnership with Libelle, we can also set up automation mechanisms for you if you have the need for regular system copies. We are also happy to support you with any data anonymization that may become necessary after such a copy.

Until now, there has been no functional tool for System i to automate and optimize this task. The enormous resource requirements that arise during a refresh of the SAP QA system really cry out for an optimizing software tool. System Copy from Libelle (LSC) reduces the effort required for these work steps. Although a one-time effort is still required, the system landscape is examined so well that the system copy and any subsequent ones are performed literally at the push of a button. The work that is automated by LSC is in the preparation and post-processing of the files as well as the actual system copy.

Tools such as "Shortcut for SAP Systems" supplement missing functions in the area of SAP system copy.

Tests are already worthwhile for the introduction of SAP solutions in the company and also for release upgrades and migration projects, the import of patches, customizing, modifications and in-house developments.

In a system copy-based update, the database of the target system is completely overwritten with the contents of the production system.
SAP BASIS
Zurück zum Seiteninhalt