We take over your SAP system copies as a service
Copying needs to be done skillfully
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.
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
Ways of SAP system copy: export / import
Acceleration/table export: up to 4 times faster. The larger the table and the higher the effort for sorting, the greater the time gain during export.
Shutting down and copying virtualized systems, such as VMware instances, requires just a few mouse clicks. VMware is suitable for running multiple training, development and test environments on one physical system. Larger productive systems, on the other hand, are not so easy to virtualize. If users have to shut down the productive system during the copy, the runtime of the operation or the unavailability of the productive system becomes a critical factor.
To shorten the list of activities and to simplify the complete process of a system copy or a system refresh and to save manual activities, you can use "Shortcut for SAP Systems". Several manual activities can be omitted because with "Shortcut for SAP Systems" the system-specific data can be saved before the copy and imported again afterwards - also automated. This reduces the error-proneness that is inevitably caused by manual activities and enormously reduces the time span until the system is available again.
All these activity groups are described individually below.
SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
What happens in the smallest detail during an SAP system copy creation must be visible in whatever form in order to be able to track down possible errors, but also, for example, to optimize the actual copying process or to accelerate it even further, for example by using log files and more.