Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy
Scope of the SAP system copy
If the data stocks become obsolete, they can be updated by another system copy. From a technical point of view, such a refresh corresponds to the initial setup, including the associated costs as well as the load on the productive systems and manual rework. In addition, a refresh also interrupts all processes on the target system. If it is a development system, all newer development objects must be saved and transported back in after the copy. The version history is lost in the process.
The Migration Monitor: is a standalone tool implemented in Java, takes over the management and control of the R3load processes, is downward compatible. Use the latest Migration Monitor version of the highest release!
Before shutting down the target system
Renaming and restoring the target system database - adjusting file system permissions. Renaming, recovery and startup of the target system database.
Often, the development and test systems of an SAP landscape are far removed from the status of the productive systems used on a daily basis: Outdated developments, customizing settings and master data reduce the quality and trustworthiness of test and emergency scenarios. It also becomes increasingly difficult to make reliable statements about the behavior of the production system after changes in customizing.
SAP system copy can be done easier and faster with "Shortcut for SAP Systems".
Incremental Migration (IMIG): - OS- and DB- independent - for homogeneous and heterogeneous system copies - for Unicode conversions - for ABAP systems as of 4.0B.
Often, the development and test systems of an SAP landscape are far removed from the status of the productive systems used on a daily basis: Outdated developments, customizing settings and master data reduce the quality and trustworthiness of test and emergency scenarios.