The system copy
Before shutting down the target system
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.
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.
Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
On the other hand, such a tool must ensure that traceability or transparency is always available. What happens in the smallest detail during an SAP system copy creation must be visible in whatever form in order to be able to track down possible errors, but also, for example, to optimize the actual copying process or to accelerate it even further, for example by using log files and more.
With "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.
Because the reliability is limited by the misuse of the backup system and the storage network is additionally burdened, users should keep the runtime of this refresh variant as short as possible.