SAP system copy Copying needs to be done skillfully - SAP Corner

Direkt zum Seiteninhalt
Copying needs to be done skillfully
SAP system startup and shutdown, including virtual hosts
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).

For virtually all customers using SAP Business Suite (including All-in-One solutions), the creation of SAP system copies is in and of itself a firmly established task area. In concrete terms, the doing usually has to be performed by the SAP Basis within IT, in addition to many other activities.
Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy
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.

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!

"Shortcut for SAP Systems" provides an automated solution for many of the tasks involved in copying SAP systems by enabling the backup and restore of any table.

In addition, administrative rework is often necessary, starting with the system name and extending to printers and interfaces.

The website offers many useful information about SAP basis.

Some copies are short-term (ad hoc) in nature, while others are intended for long-term use.
SAP Corner
Zurück zum Seiteninhalt