Scenario with system copies for updating
Copy only specific data
Companies with backup systems can use these for a client copy and thus save on the computing power of the productive system. However, the burden of copying falls on the SAN. 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.
Post system copy rework - The collected information from the system copy prework is evaluated and the corresponding transport requests are reimported. The development status before the system copy is thus restored. In addition, this package includes a tool that, when individual transports are released, checks whether there are any overlaps on the target system with transports that are still open there. This prevents a transport from unintentionally "overtaking" an earlier released one with the same objects.
Multicloud: the systems involved with different hyperscalers
SAP environments can quickly become time-consuming. For example, when it comes to creating system copies of a production environment on the test and quality assurance (QA) system. Because of the time required, some QA systems turn out to be outdated and thus even ticking time bombs. A software tool from Libelle now makes it easier to update QA systems in SAP architectures on System i as well.
Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.
A disadvantage, however, is the high storage space requirement of such a test system, which corresponds to that of the productive system.