On-premises: all involved source/target systems in the company's own data centers
Tools for SAP test systems
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.
Unicode conversion: A Unicode target system is built from a non-Unicode source system. Unicode conversion can only be performed using procedures based on R3load.
The Refresh
In practice, customers have either built their own tools to make the appropriate configurations, or there are extensive lists of steps to be processed manually. This approach is time-consuming and error-prone.
Depends on the extent of splitting and the degree of parallelization. When importing, the limiting factor is often the index structure.
With "Shortcut for SAP Systems" the effort for many work steps is reduced. The work done by "Shortcut for SAP Systems" lies in the preparation and post-processing of the data - by backing up the system-specific data before the system copy and restoring it after the system copy. Efforts for preparation and post-processing are thus reduced to a minimum.
In this guide we focus on the data to be backed up.
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.