SAP system copy SAP system/instance move - SAP Basis

Direkt zum Seiteninhalt
SAP system/instance move
Tools for SAP test systems
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).

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.
Automate SAP system copies
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.

SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.

Table splitting requires 2 tools: R3ta, which determines the WHERE conditions used to access subsets of a table. TableSplitter, which splits the WHERE-conditions determined by R3ta into packages with one or more subsets.

With "Shortcut for SAP Systems" a tool is available that simplifies the SAP system copy and offers additional possibilities.

As with the latter, the configuration is retained and ongoing development and test processes remain undisturbed.

To reduce the number of test cycles, it is also advisable to update your development system occasionally.

The freeware Scribble Papers is a "note box" in which all kinds of data can be stored. It takes in typed texts as well as graphics and entire documents. The data is then organised in folders and pages.
SAP BASIS
Zurück zum Seiteninhalt