Copy only specific data
Purpose of the SAP system copy
The need for a system refresh arises for various reasons. Often it is a matter of regular updates to ensure that test or development systems contain up-to-date data. A refresh is also indispensable before major implementations or migrations. Such a process can also be crucial for error analysis or to prepare for audits and compliance checks. The refresh ensures that everyone involved can work on a consistent and up-to-date data basis.
Table splitting reduces the risk of losing a lot of time during export in case of an error. When restarting, the complete table does not have to be exported again, but only a subset. Simultaneous processing of a table by several R3load processes can reduce the total runtime for this table.
Downtime
Internationally active companies that operate systems with several terabytes of data and hundreds of users in different time zones depend on high system availability. If necessary, the system is copied incrementally, table by table, on weekends and at night. Complete shutdown of the production system is best avoided altogether.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
The database import can be performed using various tools. Sapinstaller provides a working way to import the database cleanly.
The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.
Creating a consistent storage replica - splitting a clone or creating a snapshot on the disk array.
Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible.