Applicability of Systemcopy as a Service
Automation of homogeneous SAP system copies
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.
Several advantages at once
RFC data transfer was completed within 1 day. Effort decreases from 1st test to 2nd test to final 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.
There is a useful product for SAP system copy - "Shortcut for SAP Systems".
VMware is suitable for running multiple training, development and test environments on one physical system.
SAP and third-party tools for selective data extraction can significantly reduce the cost of deploying non-production SAP systems.