SAP system update and database update
Purpose of the SAP system copy
Third-party tools sometimes have a different focus than TDMS. The tools each offer a more or less generally understandable user guidance and are thus "out-of-the-box" products that do not require external consulting on implementation or application.
The Migration Monitor: is a standalone tool implemented in Java, takes over the management and control of the R3load processes, is downward compatible. Use the latest Migration Monitor version of the highest release!
Types of SAP system copy
In the case of BSC, sophisticated mechanisms make it possible to exclude configuration errors, since relevant parameter settings are made automatically and according to predefined rules. For example, it is automatically recognized whether the system is an Abap, Java or double-stack system.
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.
SAP system copy can be done easier and faster with "Shortcut for SAP Systems".
However, when their number reaches the hundreds and thousands, the effort becomes disproportionately high.
Some useful tips about SAP basis can be found on www.sap-corner.de.
It can also accelerate the runtime of some of SAP's longer post-update transactions by analyzing and processing the underlying processes in parallel.