Import of delta statuses after SAP system copy / restore
SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE
In practice, customers have either built their own tools to make the appropriate configurations, or there are extensive lists of steps to be processed manually. This approach is time-consuming and error-prone.
Increasingly, ad hoc requests are coming from IT or SAP Basis to provide an SAP system copy as quickly as possible, for example of an SAP ERP, BW or HCM system. This often leads to special challenges due to a lack of resources or capacities.
SAP system/instance move
Without interrupting operations, we copy your systems using established methods and products. We guarantee consistent quality and reliable reproducibility through standardized processes and a high degree of automation. Due to the SAP system copy, the test and development systems are up to date and tests can be performed reliably and trustworthily on the non-production systems.
A system copy can be created either with SAP transactions (R3trans, from R4.6C SAPinst) or at file and database level. Costs and effort increase with the size of the system and the requirements for availability and data protection. In addition, administrative rework is often necessary, starting with the system name and extending to printers and interfaces.
If you have used "Shortcut for SAP Systems" to save system-specific tables before the system refresh, several manual steps can be omitted - the data can be restored by restoring the data saved before the system copy.
Primarily for security reasons, no changes to SAP source systems are enabled.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
Backup / Restore: If the source system must not fail, eg to copy the database files, one can create an online backup of the database, copy the backup files to the new server and perform a restore before performing the SAP installation over the existing database.