August 25, 2020 Update test systems with fresh production data and make them anonymous
Our customers' main arguments in favour of the cloud are the dynamism and flexibility with which temporary systems in particular can be set up and taken down again in the cloud - at least from an infrastructure perspective.
When it comes to mapping the application level in addition to the infrastructure level, administrators face certain challenges: In many situations, providing such a system for the DEV, Q or sandbox role out-of-the-box is simply a greater effort than "just" setting up a server. This shifts the bottleneck from the earlier "I don't have sufficient hardware..." to "I don't have time right now...", and experience shows that this is not a satisfactory answer for the departments that insist on urgency.
So what can be done to increase this real or perceived service level while avoiding unnecessary discussions? A cloud-optimised automation solution, such as Libelle SystemClone, can be an approach here.
Libelle SystemClone maps the entire end-to-end process of a system rebuild based on an existing source system. It does not matter whether the source and/or target are on premise or on cloud. Thus, all possible combinations can be mapped without any issues.
Clone2Cloud is based on our solution Libelle SystemClone. This enables the automated execution of SAP system clones to build new non-production SAP systems (sandboxes, etc.) on the basis of existing environments.
For Clone2Cloud, the standard LSCL process, which is often used on-premise by our customers, was extended by cloud-specific additional tasks. Thus, systems used in the cloud can be adapted automatically. Depending on the progress of the system clone, for example, the CPU performance and other parameters are dynamically changed and reset to the initial values after completion. Classic activities here are the task groups around the BDLS or TemSe, as well as the export/import tasks, which can be massively parallelised. The result: Significant minimisation of runtime and, as a result, significantly faster responses to departmental requests for new sandboxes.