Conclusion
Create SAP HANA system replication levels
In order to be able to work with the most up-to-date data possible on the development and quality assurance systems, it is necessary to bring an up-to-date production status onto these systems. This is often done via a complete system copy (production system -> development system, production system -> quality assurance system) and is very error-prone and user-intensive in ad-hoc configuration (especially if each developer/customizing user is responsible for saving the transports and importing them again after the copy). 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.
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.
SAP system copy and the cloud
In the case of BSC, sophisticated mechanisms make it possible to exclude configuration errors, since relevant parameter settings are made automatically and according to predefined rules. For example, it is automatically recognized whether the system is an Abap, Java or double-stack system.
Fact: BDLS is a kind of "time eater" for system copies (except when using Hana). An important first step is to integrate the BDLS run into the system copy. Once the copy is effectively through, the BDLS is automatically started.
A solution such as "Shortcut for SAP Systems" offers an automatable solution for many of the activities involved in an SAP system copy.
Target audience: SAP technical consultants and IT decision makers who are familiar with commonly used procedures for homogeneous SAP system copies.
Some useful tips about SAP basis can be found on www.sap-corner.de.
In advanced SAP systems, there are also methods such as system cloning, which allows an exact copy of a production system to be created and used as a test system.