Critical factor: Availability
Test and training system: data anomyization, migration of master data, migration of user data / passwords
In SAP, the admin must be happy to build new landscapes so that testing, development and enhancement can take place. In a system copy, the approaches are as colorful and varied as the philosophies of the administrators. The important thing is to think about the target system before building it. After all, after the database is removed and the system is rebuilt, there will be two identical systems on the network.
An alternative to this is a refresh using a client copy. The test environment will then be missing audit documents, among other things, but the development objects will remain untouched. The client copy only works from a running SAP system, but it burdens the system with database queries and transfers data more slowly than a system copy. The affected client is not available during the copy process. Since there are no options within the client to select what all should be copied, the runtime is often unacceptable.
SAP system copies and the DSGVO
An SAP system copy usually includes both the copy of the database and the copy of the file systems that contain the SAP system. There are several ways to create a system copy of an SAP system, depending on the type of database and operating system used.
Renaming and restoring the target system database - adjusting file system permissions. Renaming, recovery and startup of the target system database.
With "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.
This guide does not provide instructions for installing, configuring, or operating SAP Landscape Management.
Export and import statistics are created separately, as well as displayed in an overall view.