SAP system copy Critical factor: Availability

Direkt zum Seiteninhalt
Critical factor: Availability
The target system
Renaming and restoring the target system database - adjusting file system permissions. Renaming, recovery and startup of the target system database.

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
Suitable tools make it possible to automate and accelerate the necessary creation of true-to-original SAP system copies, for example. This means that you have all production data available on your test system in a short time.

To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.

In order to check whether the usable settings are correctly adjusted, especially in the case of large databases, the runtimes are automatically logged during the BDLS. Based on these results, it is possible to analyze how the runtime can be further optimized. By the way, BDLS reports and optimization options are displayed in the BSC GUI, including modification options.

"Shortcut for SAP Systems" offers the possibility to backup and restore any tables. Not only those that are considered in the PCA tool (Post Copy Automation) but also self-developed tables. Thanks to the simple and clear interface, backup and restore of self-developed tables can be integrated quickly and easily. The command line interface can also be used to automate the process: for example, a simple line command can be used to perform a complete backup of table contents before the system copy, and a simple line command can also be used to restore these tables after the system copy. This means that the complete backup or restore process can be integrated into any automation software.

Unsorted unloading: - By default, R3load sorts table data by primary key before export.

We will be happy to advise you and work out the most suitable solution for you together with you - so that you profit 100% from Systemcopy as a Service.
SAP Corner
Zurück zum Seiteninhalt