Shutting Down the Target System
Conclusion
The task of a system copy created for updates is a carefully integrated system that takes on a specific role in an SAP system landscape. That is why customizing the SAP database of the target system differs significantly from customizing the database of the production system. In a system copy-based update, the database of the target system is completely overwritten with the contents of the production system. Therefore, all SAP-specific customization of the target system must be performed after the update with the system copy. The pre- and post-processing is often performed manually while the target system is running. Specific SAP transactions are used to customize the system. Execution can take a long time and is a source of human error. To automate most transactions, UC4 Automated System Copy for SAP can also be used. Before the update, UC4 Automated System Copy takes care of downloading the required content for the SAP customization from the target system and after the update is complete, uploading the content back to the system.
A major risk to the availability of the entire SAP environment arises when system copies are not transferred to the QA system for reasons of time and resources. Development and test work then takes place on a QA system that does not correspond to the production system. The disruption of the production system - sooner or later - is then already pre-programmed.
Import of delta statuses after SAP system copy / restore
Administrators and SAP maintainers in the x86 world under Windows and various Unix derivatives can nowadays choose from a wealth of software solutions for system support. In contrast, administrators in the System i world and SAP support staff in this environment are often left to their own devices. Nevertheless, the special system architecture and the peculiarities of the DB2 database integrated in the operating system, as well as the specific applications, also pose challenges for system tool developers.
SAP recommends that you always update enterprise software in your production system using the SAP transport system and never make changes directly in the production system. In addition, SAP suggests that you validate change transports through a QA system that is approximately identical to the production system and has up-to-date transaction data. Outdated data can affect the validity of change transport tests, which can lead to errors and failures in the production system. However, end-user transaction data is received only from the production system. Such data must therefore be passed regularly throughout the SAP transport chain to ensure that your non-production systems have up-to-date and valid transaction data. This can usually be accomplished by passing a system copy of the production system, created for updates, to the QA system. To reduce the number of test cycles, it is also advisable to update your development system occasionally.
Of course, time savings also mean money savings. In addition, these processes for system copying can be planned, standardized and always run at a high level of process quality using automation tools of this kind. Especially the latter is of great importance in SAP Basis departments (and of course also for service providers). With "Shortcut for SAP Systems", a number of activities in the context of system copies can be carried out and automated. Your SAP Basis administration is thus significantly relieved. Automation also means that SAP Basis Administrators no longer have to work unreasonable hours. The product can be integrated into almost any automation software.
One takes thus in the context of the copy a platform change.
When the cause of an abort with error has been removed, the status in *state.properties can be set from '-' to '0', and the package will be processed again (i.e. exported or imported).