SAP system copies and the DSGVO
Save time, money and nerves with "Systemcopy as a Service
Tests are already worthwhile for the introduction of SAP solutions in the company and also for release upgrades and migration projects, the import of patches, customizing, modifications and in-house developments. A three-tier SAP landscape typically consists of development, test and production systems. In addition, there are often training systems.
As a rule, the SAP basis has to fulfill: to provide SAP system copies as quickly as possible for the increased usage purposes. The performance of modern tools has developed rapidly. An assessment of the current situation.
Hybrid: for example, the source systems on-premises and the target systems on cloud
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.
The guideline that integrated job logic is preferable to customizing has also proven its worth. The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
Use "Shortcut for SAP Systems" to make a required SAP system copy easier and faster.
For a long time, manual procedures dominated, supported by SAP (guidelines), in particular by predefined procedures and a large number of checklists.
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.
The initial screen will then, for example, already show an overview of the - in some cases automatically - integrated systems and their status, as well as system information such as release, patch level and the like.