Technical system copy for the upgrade
Save time, money and nerves with "Systemcopy as a Service
After restarting the target system The SAP target instance has been started with a database that has been updated with content copied from the production database using fast and scalable disk array replication. The status of the target system now allows it to run without severe internal errors and disruption to the SAP landscape. However, the system does not have the same identity in the SAP landscape as it had before the update. That's why post-processing is required. UC4 Automated System Copy can handle most of the post-processing by restoring specific database content customizations (such as security settings, RFC targets, and operating modes) that were downloaded before the upgrade. Another goal in post-processing is to change the production system's logical system names to those used by the target system. Since these names usually need to be passed to numerous tables in a given system that have not yet been customized, SAP has the BDLS transaction that can be used to safely analyze and change logical system names. UC4 Automated System Copy can automate and accelerate this transaction by analyzing the underlying processes and executing them in parallel. It can also automate tasks such as reorganizing spools and instructing transport managers to process the delta transport list.
Especially in complex environments, SAP system copies regularly represent a critical challenge in terms of time and expertise and thus become a real cost factor in the long run. This is because system copies must be scheduled at an early stage, are complex, time-consuming and resource-intensive, require specific knowledge, tie up important employee capacities due to the large number of manual interventions, and are error-prone.
DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
In the case of BSC, sophisticated mechanisms make it possible to exclude configuration errors, since relevant parameter settings are made automatically and according to predefined rules. For example, it is automatically recognized whether the system is an Abap, Java or double-stack system.
SAP software plays a central role in the IT landscape of Rehau, a provider of polymer-based solutions for construction, automotive and industry. Currently, the IT department provides over 120 SAP systems centrally in the sense of "shared service hosting". The IT team must regularly copy the SAP productive environment in order to be able to carry out testing and development work on the "real" system without manipulating the productive systems. Rehau recently opted for the 'Automated System Copy for SAP' solution. The tool from Automic, a specialist in business automation, allows SAP system copies to be created almost fully automatically.
The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.
Decision-makers are thus able to successfully circumvent any transformation risks and define a roadmap for a smooth process.
Homogeneous system copy: In this type of copy, the operating system and database on the target system are the same as on the source system.