The use of SAP in the cloud is slowly but surely penetrating the market. Some companies are still hesitant to completely remove the production systems from their own infrastructure. The reasons for this are often a mixture of technical, commercial and not least psychological reasons. We have taken a look at how our customers are already using the cloud in connection with SAP environments.
What we are seeing is a trend towardshybrid scenarios as a first step towards the cloud: companies often continue to operate production environments on premise in their own data centre, but the Q or test systems at one of the well-known cloud providers.
Operating such systems in the cloud is no more complex than operating them yourself. In terms of infrastructure administration, perhaps a little differently, but no more complicated.
What also remains the same are the requirements on the part of the departments for these systems. However, these are suddenly easier to satisfy: Temporarily more performance, e.g. for reporting/analysis purposes, or always fresh data for quality/integration tests, anonymised in compliance with GDPR, but also reduced to non-existent downtimes during the data refresh.
Some of our customers have already had very good experiences with the combination Cloud & Libelle SystemCopy. The basic principle of the solution itself is to automatically supply non-production systems with fresh production data. The system copy runs end-to-end at the push of a button, including all pre- and post-processing - and this also works in the cloud.
Refresh2Cloud extends the standard solution LSC with specific additional tasks. In this way, systems used in the cloud can be automatically adapted. Depending on the progress of the system refresh, LSC dynamically changes the CPU performance and other parameters, for example, and resets them to the initial values after the refresh is complete. Examples of this are the task groups around the BDLS or TemSe, as well as the export/import tasks, which can be massively parallelised. This reduces the runtime and thus the downtime of the target environments during the system refresh to a minimum.
Anonymisation mechanisms are increasingly becoming an integral part of system refreshes, and not just since the GDPR came into force. In combination with Libelle DataMasking, LSC ensures the seamless integration of data-consistent anonymisation with a fast turnaround time. The result: realistic values that developers, analysts, external parties and training participants can work with.