SAP system copy SAP system update and database update - SAP Corner

Direkt zum Seiteninhalt
SAP system update and database update
Solution infrastructure
The different types of SAP environments must meet different requirements. Training courses, for example, can only be held expediently if the working conditions largely correspond to those on the production system. Companies can simulate real-life situations for testing purposes on the basis of consistent and realistic data alone. Users should also test their own developments and modifications with consistent data that is close to production. A test environment that is as identical as possible to the production system is suitable for testing patches and release upgrades. In development and training systems in particular, it is fundamentally important to anonymize sensitive data in order to comply with data protection rules.

Internationally active companies that operate systems with several terabytes of data and hundreds of users in different time zones depend on high system availability. If necessary, the system is copied incrementally, table by table, on weekends and at night. Complete shutdown of the production system is best avoided altogether.
We take over your SAP system copies as a service
This means that the time required to create an SAP system copy - be it for providing a system copy for training purposes, be it for testing purposes or whatever - is drastically minimized. Instead of several days, only hours are required for system copying.

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).

"Shortcut for SAP Systems" offers the possibility to backup and restore any tables. Not only those that are considered in the PCA tool (Post Copy Automation) but also self-developed tables. Thanks to the simple and clear interface, backup and restore of self-developed tables can be integrated quickly and easily. The command line interface can also be used to automate the process: for example, a simple line command can be used to perform a complete backup of table contents before the system copy, and a simple line command can also be used to restore these tables after the system copy. This means that the complete backup or restore process can be integrated into any automation software.

The performance of modern tools has developed rapidly.

Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page you will find useful information on this topic.

The pre- and post-processing is often performed manually while the target system is running.
SAP Corner
Zurück zum Seiteninhalt