SAP system copy Consistency of database disk blocks - stopping I/O activities or executing DATABASE BEGIN ONLINE BACKUP command, flushing cache, etc. - SAP Basis

Direkt zum Seiteninhalt
Consistency of database disk blocks - stopping I/O activities or executing DATABASE BEGIN ONLINE BACKUP command, flushing cache, etc.
We take over your SAP system copies as a service
Innovative test data management provides realistic, relevant and secure test data. With this data, companies are able to decisively accelerate and qualitatively improve their development and change processes and make testing and training scenarios affordable. For example, it is possible to automate quality assurance processes and successfully introduce new business functions without a costly and time-consuming SAP system copy. Software development can also be accelerated. The test data software always ensures that tests are carried out particularly thoroughly.

Regular updating reduces operational risk and improves the quality of the multi-level system landscape. To update the non-productive systems of an SAP landscape, the data must be cloned from the productive system. This is time-consuming and requires very complex rework.
Purpose of the SAP system copy
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.

Acceleration/table export: up to 4 times faster. The larger the table and the higher the effort for sorting, the greater the time gain during export.

"Shortcut for SAP Systems" can considerably simplify and shorten a number of activities within the scope of a system copy or a system refresh. By using this application in conjunction with the information on system-specific tables from the PCA tool, the system-specific data can be backed up and restored after the system copy / system refresh. As a result, many of the activities mentioned here regarding data backup / restore can be performed much more easily; the creation of screenshots and the subsequent manual restoration of the state documented in this way can then be completely eliminated.

Shortly before the start of the update, inform users again that maintenance work on the system is imminent and that they should log off from the target system.

Installation continues until the 'Load Data' phase.
SAP BASIS
Zurück zum Seiteninhalt