SAP system copy SAP system startup and shutdown, including virtual hosts - SAP Corner

Direkt zum Seiteninhalt
SAP system startup and shutdown, including virtual hosts
The solution described in this document can be summarized as follows: The goal is to create a homogeneous copy of an SAP system. The source of the system copy is a production system. The target of the system copy is an existing non-production system. The focus is on a specific use case, a system copy created for updates. Backup and restore are performed at the SAN device level and supported by HP System Copy software. Pre- and post-processing is automated using the UC4 Automated System Copy for SAP solution. Thus, the proposed solution allows you to optimize the automation and acceleration of SAP system copies generated for upgrades and reduce IT administration costs. Automated, fast and powerful upgrade capabilities enable shorter and more flexible SAP software lifecycles, enabling more agile business processes.

The task of a system copy created for updates is a carefully integrated system that takes on a specific role in an SAP system landscape. That is why customizing the SAP database of the target system differs significantly from customizing the database of the production system. In a system copy-based update, the database of the target system is completely overwritten with the contents of the production system. Therefore, all SAP-specific customization of the target system must be performed after the update with the system copy. The pre- and post-processing is often performed manually while the target system is running. Specific SAP transactions are used to customize the system. Execution can take a long time and is a source of human error. To automate most transactions, UC4 Automated System Copy for SAP can also be used. Before the update, UC4 Automated System Copy takes care of downloading the required content for the SAP customization from the target system and after the update is complete, uploading the content back to the system.
Test and training system: data anomyization, migration of master data, migration of user data / passwords
Shutting down and copying virtualized systems, such as VMware instances, requires just a few mouse clicks. VMware is suitable for running multiple training, development and test environments on one physical system. Larger productive systems, on the other hand, are not so easy to virtualize. If users have to shut down the productive system during the copy, the runtime of the operation or the unavailability of the productive system becomes a critical factor.

On the other hand, such a tool must ensure that traceability or transparency is always available. What happens in the smallest detail during an SAP system copy creation must be visible in whatever form in order to be able to track down possible errors, but also, for example, to optimize the actual copying process or to accelerate it even further, for example by using log files and more.

Powerful and sophisticated automation tools for the creation of SAP system copies provide a remedy here and, in addition to time and cost savings, demonstrably also make it possible, for example, to increase the process quality in system copying or to maintain it at a consistently high level. In effect, they free up SAP Basis. With "Shortcut for SAP Systems", you can sustainably relieve your administrators of the time-consuming routine activities of an SAP system copy.

Disadvantages: - Potential load on the production system during IMIG - Additional resource requirements in the source system - Two systems running in parallel are needed (source and target system).

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page:

The advantages here are: After the initial setup, data is already available, and users receive a completely identical test environment.
SAP Corner
Zurück zum Seiteninhalt