Types of SAP system copy
Import of delta statuses after SAP system copy / restore
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.
One of the most common methods of creating an SAP system copy is to use SAP's own tool "BR*Tools". This tool provides the ability to create a backup of the database, which can then be used to restore the system. It can also be used to export certain data from the database and import it into another system.
Scenario with system copies for updating
The initial screen will then, for example, already show an overview of the - in some cases automatically - integrated systems and their status, as well as system information such as release, patch level and the like. The use of a comprehensive dashboard will then also be included.
After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level. To automate the creation of the technical system copy for upgrade, HP System Copy can be used for the following steps.
"Shortcut for SAP Systems" offers the possibility to backup and restore any tables. Not only those that are considered in the PCA tool (Post Copy Automation) but also self-developed tables. Thanks to the simple and clear interface, backup and restore of self-developed tables can be integrated quickly and easily. The command line interface can also be used to automate the process: for example, a simple line command can be used to perform a complete backup of table contents before the system copy, and a simple line command can also be used to restore these tables after the system copy. This means that the complete backup or restore process can be integrated into any automation software.
The website www.sap-corner.de offers many useful information about SAP basis.
As a result, business processes can be made more agile, risks can be reduced, and the workload of IT administrators can be reduced.
However, updating the databases of non-production SAP systems for testing, quality assurance and development with new production data is usually a time-consuming and error-prone process that involves lengthy interruptions to the SAP software lifecycle.