SAP system copy SAP system copy and the cloud - SAP Basis

Direkt zum Seiteninhalt
SAP system copy and the cloud
Import of delta statuses after SAP system copy / restore
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.

Typically, the "homogeneous SAP system copy" process involves a large number of manual activities. A certain skill level is required for this, which leads to the fact that usually the employees of the SAP Basis department or external service providers realize the system copy. Depending on the structure and size of the systems, this process can take anywhere from hours to several days. In addition to making the target systems unavailable to operations and project teams, system and landscape copies also block SAP Basis administrators. Other challenges include the varying duration and quality (completeness) of the results depending on the processor, time dependency on the employees performing the work, etc..
Hybrid: for example, the source systems on-premises and the target systems on cloud
Administrators and SAP maintainers in the x86 world under Windows and various Unix derivatives can nowadays choose from a wealth of software solutions for system support. In contrast, administrators in the System i world and SAP support staff in this environment are often left to their own devices. Nevertheless, the special system architecture and the peculiarities of the DB2 database integrated in the operating system, as well as the specific applications, also pose challenges for system tool developers.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.

As mentioned above, an SAP system copy created for updates is a special use case of homogeneous system copy. Here, a production system represents the source and a non-production system with a specific long-term task in the SAP system landscape represents the target. The most common update scenario involves updating a QA system in the SAP transport system.

"Shortcut for SAP Systems" provides an automated solution for many of the tasks involved in copying SAP systems by enabling the backup and restore of any table.

Prepare SAP system/instance, undo preparation.

One to two pre-tests are required, one of which should be performed on the production system.

To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
SAP BASIS
Zurück zum Seiteninhalt