SAP system copy Planning Guide for the Connector for SAP Landscape Management

Direkt zum Seiteninhalt
Planning Guide for the Connector for SAP Landscape Management
Before shutting down the target system
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.

Such system copies, with their enormous manual effort and SAP checklists that are often hundreds of items long, must be performed before every refresh. Usually, three to four days have to be planned for this, during which the QA system - which in two-tier SAP environments is also the development system - is not available for the actual work. The delay is actually only caused by the meticulous matching of trivial things, such as directory names. Because such SAP system copies have to be created for each SAP application on the QA system and can thus quickly require dozens of system copies, they tie up a lot of resources and staff.
Solution infrastructure
Even if the target system is not used for production in an update scenario based on a system copy, it is of central importance for developers and thus also the software lifecycle of the production system. That's why you should avoid upgrade downtime in both the production source system and the non-production target system. Production system downtime depends primarily on the method you use to create the image of the production data to be used in the target system. This image must be a transferable database image - for example, a database export, a backup copy, or an array-based reconciliation. To eliminate downtime in the production system and minimize the impact on application performance-regardless of the size of the production data reconciliation-you can use, for example, HP StorageWorks System Copy for SAP (HP System Copy), which has a disk array-based replication capability. Downtime in the target system depends on the following factors, among others: The time required to restore production data reconciliation in the target system The amount of pre- and post-processing in the target system With HP System Copy, images of production data can be created in minutes, with each step between shutdown and reboot of the target system occurring automatically. However, after the reboot, the target system is not immediately ready for use, as additional steps must first be performed (see description below).

Basically, a distinction is made between the initial setup and refresh of a non-productive SAP system. In the past, the cost of a refresh, i.e., updating the environment with new data, often corresponded to the cost of the initial setup. This also restricted the availability of the productive system, which is hardly tolerable for companies that operate internationally and in different time zones.

Of course, time savings also mean money savings. In addition, these processes for system copying can be planned, standardized and always run at a high level of process quality using automation tools of this kind. Especially the latter is of great importance in SAP Basis departments (and of course also for service providers). With "Shortcut for SAP Systems", a number of activities in the context of system copies can be carried out and automated. Your SAP Basis administration is thus significantly relieved. Automation also means that SAP Basis Administrators no longer have to work unreasonable hours. The product can be integrated into almost any automation software.

Provide your QA, test and training systems with current production data at the push of a button.

It describes the preparations, the general procedure in the form of a quick guide, the individual steps in detail, typical error situations and the problem-solving procedure.
SAP Corner
Zurück zum Seiteninhalt