Copy only specific data
SAP SYSTEM COPY - in a nutshell
One example: In an SAP environment, a system copy must be performed for various reasons - until now manually. Such a copy is always required when the QA system of a multi-level SAP architecture has to be brought up to the status of the current production system: Be it for testing new applications or during a release upgrade, for maintenance purposes or for updating the quality assurance and test system. In principle, the task proves to be simple: All files belonging to the clean configuration and implementation of the SAP environment must be transferred from the productive systems to the quality assurance system in the correct order and in the correct directories.
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.
Challenges with SAP system copies
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.
One of the most common methods of creating an SAP system copy is to use SAP's own tool "BR*Tools". This tool provides the ability to create a backup of the database, which can then be used to restore the system. It can also be used to export certain data from the database and import it into another system.
SAP system copy can be done easier and faster with "Shortcut for SAP Systems".
A system copy can be created either with SAP transactions (R3trans, from R4.6C SAPinst) or at file and database level.
What is the purpose of copying a complete SAP system? - Well, there are several reasons.