Several advantages at once
SAP system copies and the DSGVO
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.
Checklist for preliminary work: Comparison of database sizes (target system must be the same or larger), comparison of database versions, kernel, host agent (ideally the same software version), dump of kernel files (export via SAPINST), saves download via SWDC, compile RFC connection passwords, inform third-party system administrators, provide memory, hard disk on the system for database and software import. Perform database dump, if necessary with transaction log, if possible with downtime, then without jobs or stop running jobs with report BTCTRNS1. Adminsitration passwords (DDIC, DB-Admin, Winadmin), create system snapshots (recovery), perform database import.
Efficient options for SAP system copies
To meet ever-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 appropriate updates to the production system as SAP transports.
There is a useful product for SAP system copy - "Shortcut for SAP Systems".
In order to be able to work with the most up-to-date data possible on the development and quality assurance systems, it is necessary to bring an up-to-date production status onto these systems.