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

Direkt zum Seiteninhalt
Food for thought for another productive system: until when must the system be identical, keyword: transaction log
Copying needs to be done skillfully
Another method of creating an SAP system copy is to use external tools such as Oracle RMAN or Microsoft SQL Server Backup. These tools allow you to create a complete copy of the database as well as a copy of the file system. However, it is important to note that special knowledge is required when using these tools to ensure that the backup is created correctly.

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.
Challenges reduced!
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.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page:

The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years. The first tools for SAP system copy creation came from the mainframe environment.

A solution such as "Shortcut for SAP Systems" offers an automatable solution for many of the activities involved in an SAP system copy.

And this after little system training.

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.

To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
Zurück zum Seiteninhalt