Create SAP HANA system replication levels
SAP system startup and shutdown, including virtual hosts
Heterogeneous system copy: As the name suggests, the operating system and/or database on the source and target systems are different. One takes thus in the context of the copy a platform change. This procedure is currently gaining in relevance, as it is required for the migration from SAP ERP to S/4HANA. If the current system runs on Windows Server and SQL Server or Oracle, the target system must now run on Linux and SAP Hana.
The different types of SAP environments must meet different requirements. Training courses, for example, can only be held expediently if the working conditions largely correspond to those on the production system. Companies can simulate real-life situations for testing purposes on the basis of consistent and realistic data alone. Users should also test their own developments and modifications with consistent data that is close to production. A test environment that is as identical as possible to the production system is suitable for testing patches and release upgrades. In development and training systems in particular, it is fundamentally important to anonymize sensitive data in order to comply with data protection rules.
Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape 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.
Regular updating reduces operational risk and improves the quality of the multi-level system landscape. To update the non-productive systems of an SAP landscape, the data must be cloned from the productive system. This is time-consuming and requires very complex rework.
Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.
The larger the table and the higher the effort for sorting, the greater the time gain during export.
Every SAP system copy then carries the risk of losing the development status achieved and can lead to inconsistencies in programs and customizing, and any damage repair is usually very time-consuming.