Consideration of additional QA clients
Automate SAP system copies
One to two pre-tests are required, one of which should be performed on the production system. The additional load on the production system caused by the IMIG has been negligible. Split/mirror techniques allow many actions to be moved from the production machine to another machine.
Internationally active companies that operate systems with several terabytes of data and hundreds of users in different time zones depend on high system availability. If necessary, the system is copied incrementally, table by table, on weekends and at night. Complete shutdown of the production system is best avoided altogether.
What is System Copy as a Service?
Suitable tools make it possible to automate and accelerate the necessary creation of true-to-original SAP system copies, for example. This means that you have all production data available on your test system in a short time.
Test data is important for companies to eliminate risks in ongoing operations and to optimize systems or processes. But collecting this data can be challenging in times of Big Data and increased data protection, as well as due to complex IT structures.
Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.
For transport, the tool uses Idocs, which, however, can only be used to transfer small amounts of test data.
A system copy can be created either with SAP transactions (R3trans, from R4.6C SAPinst) or at file and database level.