SAP system copy Automatic determination of delta states after SAP system copy/recovery - SAP Basis

Direkt zum Seiteninhalt
Automatic determination of delta states after SAP system copy/recovery
Efficient options for SAP system copies
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.

Without interrupting operations, we copy your systems using established methods and products. We guarantee consistent quality and reliable reproducibility through standardized processes and a high degree of automation. Due to the SAP system copy, the test and development systems are up to date and tests can be performed reliably and trustworthily on the non-production systems.
Copying needs to be done skillfully
Normally, therefore, the target system is created using a copy of the production system. The advantages here are: After the initial setup, data is already available, and users receive a completely identical test environment. However, the disadvantages of this procedure are the high memory requirements, the lack of anonymization of the data and the long runtime of the copy process.

For a heterogeneous system copy and for homogeneous system copies for which there is no special way for the database used, the source system must be exported. This is done with SAP tools (SUM). The export files are copied to the prepared target system and imported again during the SAP installation with SUM. A relatively comfortable way. But it can be even more comfortable.

"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.

After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level.

This adds the latest transactional data from the original production system.
Zurück zum Seiteninhalt