Ways of SAP system copy: export / import
Multicloud: the systems involved with different hyperscalers
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
Transaction IMIG comes with extensive online documentation. It describes the preparations, the general procedure in the form of a quick guide, the individual steps in detail, typical error situations and the problem-solving procedure.
Easy integration also in the system copy of systems of older releases possible!
The database import can be performed using various tools. Sapinstaller provides a working way to import the database cleanly.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
Depends on the extent of splitting and the degree of parallelization. When importing, the limiting factor is often the index structure.
With "Shortcut for SAP Systems" you get additional functions for the SAP system copy.
The IT team must regularly copy the SAP productive environment in order to be able to carry out testing and development work on the "real" system without manipulating the productive systems.
The website www.sap-corner.de offers many useful information about SAP basis.
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).