Detailed checks for critical order contents
Copy only specific data
The solution described in this document can be summarized as follows: The goal is to create a homogeneous copy of an SAP system. The source of the system copy is a production system. The target of the system copy is an existing non-production system. The focus is on a specific use case, a system copy created for updates. Backup and restore are performed at the SAN device level and supported by HP System Copy software. Pre- and post-processing is automated using the UC4 Automated System Copy for SAP solution. Thus, the proposed solution allows you to optimize the automation and acceleration of SAP system copies generated for upgrades and reduce IT administration costs. Automated, fast and powerful upgrade capabilities enable shorter and more flexible SAP software lifecycles, enabling more agile business processes.
An SAP system copy is not done in an hour. Due to the large amount of data in an SAP system, the individual steps can take a long time to complete. The export and the import do not always run without errors. Often one is held up by troubleshooting. Of course, the target system must be prepared before the actual copy can be performed: Setting up the server, installing the operating system and database software, downloading and copying the installation media. During the export, the source system cannot be used. Therefore, this task must be planned well and in advance.
SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE
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.
With "Shortcut for SAP Systems", a mature and yet very cost-effective product is available that offers useful functions for system copies. For example, SAP system users can be backed up and restored. Likewise, system-specific tables can be backed up before the system copy and restored after the system copy. And all this can also be automated.
The process of creating system copies for updates can be broken down into different activities, as shown in Table 1.