Challenges with SAP system copies
Easy integration also in the system copy of systems of older releases possible!
One example: In an SAP environment, a system copy must be performed for various reasons - until now manually. Such a copy is always required when the QA system of a multi-level SAP architecture has to be brought up to the status of the current production system: Be it for testing new applications or during a release upgrade, for maintenance purposes or for updating the quality assurance and test system. In principle, the task proves to be simple: All files belonging to the clean configuration and implementation of the SAP environment must be transferred from the productive systems to the quality assurance system in the correct order and in the correct directories.
Creating a consistent storage replica - splitting a clone or creating a snapshot on the disk array. Regardless of the storage size, this process takes only a few seconds.
SAP SYSTEM COPY - in a nutshell
For virtually all customers using SAP Business Suite (including All-in-One solutions), the creation of SAP system copies is in and of itself a firmly established task area. In concrete terms, the doing usually has to be performed by the SAP Basis within IT, in addition to many other activities.
In terms of its architectural approach, BSC takes standards into account wherever possible. As a result, the automation tool can be installed with minimal effort, fits very well into the respective system landscape and offers a fast ROI.
"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.
By the way, BDLS reports and optimization options are displayed in the BSC GUI, including modification options.
Every SAP system copy then carries the risk of losing the development status achieved and can lead to inconsistencies in programs and customizing, and any damage repair is usually very time-consuming.