The system copy
Import of delta statuses after SAP system copy / restore
In this context, generated jobs adapt to changes, even if, for example, a DB change, a release change or other changes have taken place. Nevertheless, once created copy jobs can be reused, which minimizes the maintenance effort and a certain susceptibility to errors. This is also the case when switching from one Any DB to another or when moving from an Any DB to Hana.
For a heterogeneous system copy and for homogeneous system copies for which there is no special way for the database used, the source system must be exported. This is done with SAP tools (SUM). The export files are copied to the prepared target system and imported again during the SAP installation with SUM. A relatively comfortable way. But it can be even more comfortable.
Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
To build a target system that can be used for testing, development and training purposes, there are two different approaches: Users can reinstall an SAP system and import all transports and support packages that have also made it into the production system to date. However, when their number reaches the hundreds and thousands, the effort becomes disproportionately high. In addition, the data still has to be imported from the production system, for example via a client copy.
You can manage your SAP system landscape in Google Cloud with SAP Landscape Management, Enterprise Edition (SAP Landscape Management) by installing the Google Cloud Connector for SAP Landscape Management (Connector for LaMa). Google Cloud provides the Connector for LaMa free of charge. You must purchase all required licenses for SAP Landscape Management from SAP.
Tools such as "Shortcut for SAP Systems" supplement missing functions in the area of SAP system copy.
This happens in the context of a homogeneous or heterogeneous system copy.
During the export, the source system cannot be used.