Libelle

Refresh2Cloud – Refresh of SAP Test Systems in the Cloud

The First Step into the Cloud: Hybrid environments

The use of SAP in the cloud slowly but surely enters the market. Some companies are still reluctant to remove the productive systems completely from their own infrastructure. The reasons often are a mixture of technical, commercial and not least psychological reasons. We looked at our customers how they use the cloud today in the context of SAP environments.

What we perceive is a trend towards hybrid scenarios as the first step towards the cloud: companies often continue to run productive environments on premise in their own data center, but the QA or test systems are operated in one of the known hyperscalers.

Operating QA or Test Systems in the Cloud: some things will change, but most will be easier. Also thanks to Automated System Refreshes.

The operation of QA systems in the cloud is not as complex as  on-premises. Infrastructure administration is a bit different, but not more complicated.

What also remains the same: high requirements of the departments. However, these are easier to satisfy: temporarily more CPU power and RAM, e.g. for reporting / analysis purposes, or always fresh data for QA and integration tests, anonymized GDPR-compliant, but also reduced – or better nonexistent – downtimes during the System Refresh.

Some of our customers already have very good experiences with the combination of CloudLibelleSystem Copy. The basic principle of the overall approach is to automatically supply non-productive systems with fresh production data. The system copy runs through at the touch of a button end-to-end, including all pre- and post-work – and this perfectly fits the cloud.

Refresh2Cloud: The Cloud Optimization for Libelle SystemCopy

Refresh2Cloud extends the standard solution LSC with additional tasks. Thus, systems used in the cloud can be automatically adapted. For example, depending on the progress of the system refresh, LSC dynamically modifies the CPU power and other parameters, resets them to their original values ​​when the refresh is complete. Examples of this are the task groups of BDLS or TemSe, as well as the export / import tasks, which can be massively parallelized. This reduces the runtime and thus the downtime of the target environments during system refresh to an absolute minimum.

Always on the field: Anonymization according to GDPR.

Not only since GDPR entered into force, customers increasingly request anonymization mechanisms to be integral part of each system refresh. In combination with LibelleDataMasking, LSC ensures the seamless integration of consistent anonymization with fast turnaround times. The result: realistic values ​​that developers, analysts, external consultants, and training students can work with.

You have questions and would like to know more? Get in Contact!