Types of SAP system copy
SAP system startup and shutdown, including virtual hosts
In order to have up-to-date data and exactly the same software versions on an SAP test system for meaningful tests as are active on the production system, the production systems are regularly copied completely to the test system. However, many settings in the test system must be retained, because a test system should not act like a production system and, for example, send documents to customers and suppliers or trigger something in production.
As mentioned above, an SAP system copy created for updates is a special use case of homogeneous system copy. Here, a production system represents the source and a non-production system with a specific long-term task in the SAP system landscape represents the target. The most common update scenario involves updating a QA system in the SAP transport system.
SAP system/instance move
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.
Also of increasing relevance to companies is the rapid provision of test data or systems in different data centers or in the cloud. A modern test data solution can implement these requirements in a largely automated manner, reducing manual effort, lowering the susceptibility to errors, and saving time and money.
There is a useful product for SAP system copy - "Shortcut for SAP Systems".
RFC data transfer was completed within 1 day.
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.