Pre- and post-processing
On-premises: all involved source/target systems in the company's own data centers
Post system copy rework - The collected information from the system copy prework is evaluated and the corresponding transport requests are reimported. The development status before the system copy is thus restored. In addition, this package includes a tool that, when individual transports are released, checks whether there are any overlaps on the target system with transports that are still open there. This prevents a transport from unintentionally "overtaking" an earlier released one with the same objects.
A SAN enables a system copy during dialog operation. In this way, virtual copies of a logical volume, so-called snapshots, can be created. Data is only copied if it is changed in the original data volume (copy-on-write procedure). When copying from a snapshot to file level, the affected systems remain available. However, this procedure puts a strain on the storage network. If this takes several days, the response times of the productive system deteriorate.
SAP system copies and the DSGVO
SAP system copies are necessary, regardless of the basic infrastructure. Particularly in the context of automation, preference should be given to solutions that support all relevant types of SAP system operation.
After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level. To automate the creation of the technical system copy for upgrade, HP System Copy can be used for the following steps.
The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.
Suitable tools make it possible to automate and accelerate the necessary creation of true-to-original SAP system copies, for example.
In general, this means that error situations can be handled as needed and with pinpoint accuracy.