SAP system copy Reliable and fast rework after SAP® system copies - SAP Basis

Direkt zum Seiteninhalt
Reliable and fast rework after SAP® system copies
Copy only specific data
The steps to be taken before shutting down the target SAP system can be summarized as follows: Well before performing the upgrade, inform the target system users - especially project managers, developers, and testers - about the planned maintenance work via e-mail, SAP system messages, and/or a message at the system logon. Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible. Shortly before the start of the update, inform users again that maintenance work on the system is imminent and that they should log off from the target system. After logging users off and locking them out, download system-specific content from the target system database for customization (including security settings, Remote Function Call (RFC) targets, and operating modes).

Database: For some databases (MS SQL Server) there is the possibility to copy the database files and reattach them on the target system. For the following SAP installation you only have to specify that no SAP loads should be used, but that the database is already there!
Technical system copy for the upgrade
One example: In an SAP environment, a system copy must be performed for various reasons - until now manually. Such a copy is always required when the QA system of a multi-level SAP architecture has to be brought up to the status of the current production system: Be it for testing new applications or during a release upgrade, for maintenance purposes or for updating the quality assurance and test system. In principle, the task proves to be simple: All files belonging to the clean configuration and implementation of the SAP environment must be transferred from the productive systems to the quality assurance system in the correct order and in the correct directories.

A SAN enables a system copy during dialog operation. In this way, virtual copies of a logical volume, so-called snapshots, can be created. Data is only copied if it is changed in the original data volume (copy-on-write procedure). When copying from a snapshot to file level, the affected systems remain available. However, this procedure puts a strain on the storage network. If this takes several days, the response times of the productive system deteriorate.

For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed, such as "Shortcut for SAP Systems". Nothing has to be installed in your SAP systems for this - no transport requests, no AddOns!

An SAP system copy is a process in which an exact copy of an existing SAP system is created.

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

The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.

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.
SAP BASIS
Zurück zum Seiteninhalt