SAP system copy Update more efficiently - SAP Basis

Direkt zum Seiteninhalt
Update more efficiently
Multicloud: the systems involved with different hyperscalers
What is the purpose of copying a complete SAP system? - Well, there are several reasons. Test and development system: After a new productive system has been set up, at least one identical development system or even one test system is still needed. To avoid having to repeat the customizing (settings and configurations of the SAP modules and business processes) on these systems, it makes sense to make a copy. This is clearly the faster way to achieve the goal!

Database: For some databases (MS SQL Server) there is the possibility to copy the database files and reattach them on the target system. For the following SAP installation you only have to specify that no SAP loads should be used, but that the database is already there!
Automation of homogeneous SAP system copies
With the definition of package groups, the parallel processing of packages can be configured beyond the definition of the order: All defined groups run in parallel to each other. For each group the parameters jobNum, taskArgs and loadArgs can be defined separately.

There are various ways to tame this time robber and reduce run times. For example, through parallelization or the automatic generation of secondary indices.

With "Shortcut for SAP Systems" the effort for many work steps is reduced. The work done by "Shortcut for SAP Systems" lies in the preparation and post-processing of the data - by backing up the system-specific data before the system copy and restoring it after the system copy. Efforts for preparation and post-processing are thus reduced to a minimum.

Companies with backup systems can use these for a client copy and thus save on the computing power of the productive system.

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.
Zurück zum Seiteninhalt