SAP system copy Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy - SAP Stuff

Direkt zum Seiteninhalt
Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy
The system copy
SAP recommends that you always update enterprise software in your production system using the SAP transport system and never make changes directly in the production system. In addition, SAP suggests that you validate change transports through a QA system that is approximately identical to the production system and has up-to-date transaction data. Outdated data can affect the validity of change transport tests, which can lead to errors and failures in the production system. However, end-user transaction data is received only from the production system. Such data must therefore be passed regularly throughout the SAP transport chain to ensure that your non-production systems have up-to-date and valid transaction data. This can usually be accomplished by passing a system copy of the production system, created for updates, to the QA system. To reduce the number of test cycles, it is also advisable to update your development system occasionally.

Companies with backup systems can use these for a client copy and thus save on the computing power of the productive system. However, the burden of copying falls on the SAN. Because the reliability is limited by the misuse of the backup system and the storage network is additionally burdened, users should keep the runtime of this refresh variant as short as possible.
SAP system clone and copy
For a long time, manual procedures dominated, supported by SAP (guidelines), in particular by predefined procedures and a large number of checklists. In many places, this was supplemented by scripts created in-house, which, however, only automated partial tasks/processes of an SAP system copy.

"Shortcut for SAP Systems" can considerably simplify and shorten a number of activities within the scope of a system copy or a system refresh. By using this application in conjunction with the information on system-specific tables from the PCA tool, the system-specific data can be backed up and restored after the system copy / system refresh. As a result, many of the activities mentioned here regarding data backup / restore can be performed much more easily; the creation of screenshots and the subsequent manual restoration of the state documented in this way can then be completely eliminated.


However, the burden of copying falls on the SAN.

SAP Stuff
Zurück zum Seiteninhalt