Automate SAP system copies
Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
The task of a system copy created for updates is a carefully integrated system that takes on a specific role in an SAP system landscape. That is why customizing the SAP database of the target system differs significantly from customizing the database of the production system. In a system copy-based update, the database of the target system is completely overwritten with the contents of the production system. Therefore, all SAP-specific customization of the target system must be performed after the update with the system copy. The pre- and post-processing is often performed manually while the target system is running. Specific SAP transactions are used to customize the system. Execution can take a long time and is a source of human error. To automate most transactions, UC4 Automated System Copy for SAP can also be used. Before the update, UC4 Automated System Copy takes care of downloading the required content for the SAP customization from the target system and after the update is complete, uploading the content back to the system.
Strategy as of NetWeaver 2007: Prerequisite: in the case of a Unicode conversion, conversion must be performed during export. If the target database can be built with unsorted unloaded data, all packages are automatically unloaded unsorted. R3load ensures that tables that must always be unloaded sorted are unloaded sorted.
Automatic determination of delta states after SAP system copy/recovery
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.
The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.
An SAP system copy is a process in which an exact copy of an existing SAP system is created. This copy can be used to run tests, perform development, or back up the system.
For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed, such as "Shortcut for SAP Systems". Nothing has to be installed in your SAP systems for this - no transport requests, no AddOns!
For this reason, when defining the processes around system copy and, if necessary, also when selecting tools for automation, care must be taken to ensure that these also map data anonymization in accordance with the GDPR.
SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
And if the SAPHana database is running on the source system, it will also be used on the target system.