Scope of the SAP system copy
SAP SYSTEM COPY - in a nutshell
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.
Provide your QA, test and training systems with current production data at the push of a button. Including all preparatory and finishing work - Without interfering with or changing your SAP environment - Without time-consuming pre-planning - With minimum lead time - With consistent copy quality.
Landscape copies refer to the update of not only one but a whole group of systems. This is the case when dependencies of the source systems are also to be mapped in the target environments. Similar to the simple system copy, the landscape copy also offers potential for automation, but this cannot be implemented by every tool on the market.
Security-conscious companies usually keep their mission-critical IT infrastructures redundant anyway. Storage systems are usually secured in disk arrays by multi-level raid, spatially separated from each other and networked by a storage area network (SAN). Connected to this are at least two computers, also spatially separated. One of these acts as a backup system.
With "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.
Database tuning: - Database partner recommendations - SAP notes (eg 936441).
Even companies that offer the setup of test systems as a service rarely do this for any SAP dataset.