SAP SYSTEM COPY - in a nutshell
The target system
SAP offers its own solution for this: With the Test Data Migration Server (TDMS), individual tables can be selected and written indirectly, via a third SAP system, from the source to the target system via Remote Function Call (RFC). However, the selection of business objects is not possible in the standard system. The tables to be copied can only be determined on the basis of the date. The content restriction applies from a certain point in time. At least the SAP tool can be used to reduce the runtime of an extraction of test data compared to the system copy or client copy.
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.
Technical system copy for the upgrade
SAP production system copies are created for a variety of reasons, including: - Generating a new non-production system for short- or long-term use - Updating an existing non-production system An SAP system copy is called homogeneous if the source and target operating and database systems are identical. If this is not the case, the system copy is considered heterogeneous. Heterogeneous system copies or platform migrations are not supported by the HP StorageWorks System Copy software for SAP and are therefore not discussed further in this document. In addition, this document deals exclusively with system copies for non-production target systems. Overview of a homogeneous system copy Figure 1 shows copies of an SAP production system that are created for non-production systems. Some copies are short-term (ad hoc) in nature, while others are intended for long-term use. Note that when a long-term system is created from a system copy, a system copy may be needed for updates later in the system's life cycle. This adds the latest transactional data from the original production system. Given their particular importance, this document focuses on scenarios with system copies created for updates. Figure 1: Overview of scenarios with homogeneous SAP system copies Scenario with system copies for updates In order to meet constantly changing business requirements, a production system must be continuously developed and adapted after the initial installation. To do this, you need development, consolidation, and quality assurance (QA) systems that can provide the production system with the appropriate updates as SAP transports.
SAP system copy can be done easier and faster with "Shortcut for SAP Systems".
System Copy from Libelle (LSC) reduces the effort required for these work steps.