On-premises: all involved source/target systems in the company's own data centers
Consistency of database disk blocks - stopping I/O activities or executing DATABASE BEGIN ONLINE BACKUP command, flushing cache, etc.
Individual steps know exactly where they have to restart the actual copy run in the event of an error. In general, this means that error situations can be handled as needed and with pinpoint accuracy.
By using the automation solution, errors that typically occur with manual process steps - just like additional costs due to repetition - can be avoided. To date, the IT team has created 88 SAP system copies. "If we had wanted to do this with SAP board resources, we would not have been able to pay for it as a medium-sized company," Rudi Scharf knows.
Key solution steps
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.
The freeware Scribble Papers is a "note box" in which all kinds of data can be stored. It takes in typed texts as well as graphics and entire documents. The data is then organised in folders and pages.
One of the most common methods of creating an SAP system copy is to use SAP's own tool "BR*Tools". This tool provides the ability to create a backup of the database, which can then be used to restore the system. It can also be used to export certain data from the database and import it into another system.
Tools such as "Shortcut for SAP Systems" supplement missing functions in the area of SAP system copy.
Table splitting reduces the risk of losing a lot of time during export in case of an error.
The first tools for SAP system copy creation came from the mainframe environment.