SAP system copy Downtime

Direkt zum Seiteninhalt
Automate SAP system copies
The solution does not use software agents. The use of standard protocols for the interaction of tool (client/server) and source system and tool with target system has proven itself, exclusively for the purpose of system copy creation. Whereby the use of a single point of management and control has also proven its worth.

In terms of its architectural approach, BSC takes standards into account wherever possible. As a result, the automation tool can be installed with minimal effort, fits very well into the respective system landscape and offers a fast ROI.
Food for thought for another productive system: until when must the system be identical, keyword: transaction log
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).

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.

Until now, it has been common practice to create test systems as a client or system copy of the production system on a specific date. In these cases, a single client or the entire SAP system is duplicated. The corresponding instances of the SAP system have to be reinstalled. In addition, a copy of the source database must be created. These are standard procedures, but they can be disproportionately expensive for productive data sets of several terabytes. SAP and third-party tools for selective data extraction can significantly reduce the cost of deploying non-production SAP systems.

Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.

The default is DDLORA.TPL.

Rehau had already been using the software provider's Business Automation platform for cross-platform scheduling of complex job chains since 2004.
SAP Corner
Zurück zum Seiteninhalt