With SAP Landscape Management Cloud (LaMa Cloud), our goal is to enable our customers to efficiently manage and run their SAP system landscapes on IaaS and streamline their operations.
As a next step towards realizing that vision, we have introduced a new SAP System Refresh operation that helps standardize and automate your end-to-end system refresh activities on IaaS including automation for pre and post-refresh manual tasks.
Tell me more!
You can now refresh an SAP system on IaaS via LaMa Cloud by using a file-based data backup of your source system's SAP HANA database (the backup is typically created using SAP HANA cockpit or SAP HANA studio).
LaMa Cloud provides a simple workflow, to streamline your system refresh activities (end-to-end) to help achieve a consistent and high quality (refreshed) system that can be used for your test and evaluation projects.
In the first increment, we decided to offer the SAP HANA file-based data backup procedure due to the following advantages: (1) it's a standard and well-established procedure for most customers, and (2) it's infrastructure and vendor agnostic, thereby reducing technical dependencies and increasing operational stability.
For future increments, we are already evaluating various alternatives to extend and optimize the system refresh operation within LaMa Cloud to offer more choice to our customers. We will communicate the future updates through our official roadmap and the community page.
How does it work?
Here's a simple illustration that provides an overview on the new system refresh operation using SAP HANA file-based data backup approach.
[click to zoom]: Overview of System Refresh Procedure using File-Based Data Backup
The end-to-end system refresh operation can be broadly divided into 3 major phases:
Phase-1: Export configuration data: to prevent the target system configuration from being overwritten, LaMa Cloud exports the target system tables that contains connectivity-related configuration data by executing the ABAP Post-Copy Automation (PCA) task list SAP_BASIS_COPY_REFRESH_EXPORT > once the export is finished, LaMa Cloud stops the target system's application server.
Phase-2: Perform database restore: LaMa Cloud restores the tenant database of the target system from a file-based data backup created from the source system. Once this is done, LaMa Cloud installs the permanent license on target system > establishes network isolation > and starts the target system's application server.
Phase-3: Import configuration data: LaMa Cloud performs the cleanup steps on the target system > imports the connectivity-related configuration data (from Phase-1) by executing the ABAP Post-Copy Automation (PCA) task list SAP_BASIS_COPY_REFRESH_IMPORT > performs final configuration steps, including additional task lists runs for example, executing task list SAP_BASIS_COPY_BDLS (if you want to run BDLS conversion steps concurrently) > and finally removes the network isolation (from Phase-2).