SAP system copy Food for thought for another productive system: until when must the system be identical, keyword: transaction log

Direkt zum Seiteninhalt
Food for thought for another productive system: until when must the system be identical, keyword: transaction log
Test and training system: data anomyization, migration of master data, migration of user data / passwords
Companies with backup systems can use these for a client copy and thus save on the computing power of the productive system. However, the burden of copying falls on the SAN. Because the reliability is limited by the misuse of the backup system and the storage network is additionally burdened, users should keep the runtime of this refresh variant as short as possible.

Administrators and SAP maintainers in the x86 world under Windows and various Unix derivatives can nowadays choose from a wealth of software solutions for system support. In contrast, administrators in the System i world and SAP support staff in this environment are often left to their own devices. Nevertheless, the special system architecture and the peculiarities of the DB2 database integrated in the operating system, as well as the specific applications, also pose challenges for system tool developers.
Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy
Normally, therefore, the target system is created using a copy of the production system. The advantages here are: After the initial setup, data is already available, and users receive a completely identical test environment. However, the disadvantages of this procedure are the high memory requirements, the lack of anonymization of the data and the long runtime of the copy process.

Unsorted unloading: - By default, R3load sorts table data by primary key before export. This requires time and resources in the source system. Under certain conditions, this sorting can be omitted.

With "Shortcut for SAP Systems" you get additional functions for the SAP system copy.

For in-house developments and third-party software, check whether there are system-specific tables for the programs that should be backed up.

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).
SAP Corner
Zurück zum Seiteninhalt