SAP SYSTEM COPY - in a nutshell
Individual steps know exactly where they have to restart the actual copy run in the event of an error. In general, this means that error situations can be handled as needed and with pinpoint accuracy.
There are various ways to tame this time robber and reduce run times. For example, through parallelization or the automatic generation of secondary indices.
Before shutting down the target system
In terms of its architectural approach, BSC takes standards into account wherever possible. As a result, the automation tool can be installed with minimal effort, fits very well into the respective system landscape and offers a fast ROI.
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.
With "Shortcut for SAP Systems", tasks in the area of SAP system copying are simplified and can also be automated via the command line interface.
That's why you should avoid upgrade downtime in both the production source system and the non-production target system.
For transport, the tool uses Idocs, which, however, can only be used to transfer small amounts of test data.